Yzis devs, Is anyone still actively working on the project? I'm very interested in the concepts behind Yzis, but I'm quite tempted to fork off my own branch. Just wanted to check with folks here before that. Diwaker -- -- http://floatingsun.net/
I found out that even if I follow the documentation and add -DCMAKE_BUILD_TYPE=debugfull, no debugging information is included in the binaries. Using "make VERBOSE=1" I found out that no -g switch is given to gcc at all. I decided to read about it at the cmake website and found out that we should probably stick to the predefined build types like "Debug" "Release". These will automatically use the C[XX]_FLAGS defined with CMAKE_CXX_FLAGS_DEBUG and similar. I made the following patch to adjust our CMakeLists.txt to use this, and I wonder if I should apply, or if there's a good reason to stick with "debugfull"? In either case I guess we should define debugging and release flags in our CMakeLists file? :) Basically, all there is to it is: +set( CCMAKE_CXX_FLAGS_RELEASE "-O3" ) +set( CCMAKE_C_FLAGS_RELEASE "-O3" ) + +set( CMAKE_CXX_FLAGS_DEBUG "-g3 -Wall" ) +set( CMAKE_C_FLAGS_DEBUG "-g3 -Wall" ) and to switch the documentation to use -DCMAKE_BUILD_TYPE=Debug (and release for released). Should I commit? :) -- -- Erlend Hamberg hamberg@...
Hello, Who knows where YZIS_WIN32_MSVC is supposed to be defined ? i can't find it in neither include files or cmake files.. Could that be some old stuff from autotools time ? ++ Thomas -- -- Thomas Capricelli <orzel@...> http://orzel.freehackers.org/
So here it is :) Based on Craig's suggestion this patch removes YZSession::me in favour of YZSession::self(). Two notes: 1. At the moment I didn't done reimplementation of self() in QYZisSession for automatic type conversion as Craig suggested because I still believe that this can lead to some clutter and should be done only if there's a real need for it. Currently there's only one such static_cast conversion needed - in nyzis. I've put it explicitly. 2. I tried to write some doc along the way, please check my English as it may be not very perfect ;). A lot of find-replace stuff in patch, but don't miss the few real changes while reviewing :). QYzis, NYzis compile and run so I guess the patch is ok :). Cheers, Dmitry.
On Monday 18 December 2006 20:20, Philippe Fremy wrote: > Thomas Capricelli wrote: > > It looks ok, and i like the fact that there's one single point of > > documentation (not doxygen and handbook). If you decide to go with Doxygen, please don't delete the Latex documentation stuff. Just keep it as an option that defaults to OFF as it is now. I might want to keep it updated as I think it could be a nice starting point for new developers. (I would find a "book" more appealing and more fun to read to begin with.) However, I agree that the Doxygen solution sounds really nice, and also that we should concentrate on documenting the source as well (also in Doxygen :). > > Although,.. do you really need to put all *.dx content in C coment /* ... > > */ ?? That's disturbing. Yes ;) -- -- Erlend Hamberg hamberg@...
Dmitry Suzdalev wrote: >> So, the solution would be to use only YZSession::self() and >> QYZSession::self(), and have the YZSession::me private or protected. That >> way, we would always know exactly what is returned. > In fact there's no YZSession::self() method. And there can't be. > Because then it would clash with QYzisSession::self(). > And overriding non-virtual methods is a bad thing (tm). > And X::self() can't be virtual because it's static(Continue reading). > >> Did you see in the code any reason why YZSession::me is used in some >> places >> and not YZSession::self() ? It might just be because it is easier to type >>
> "cd qyzis && grep self *" gives me: > > editor.cpp: QYZisSession::self()->setCurrentView( mParent ); > main.cpp: v = > QYZisSession::self()->createBufferAndView( args.at(i) ); > main.cpp: first = > QYZisSession::self()->createBufferAndView(); > main.cpp: QYZisSession::self()->setCurrentView( first ); > qsession.cpp:QYZisSession* QYZisSession::self() { > qsession.h: static QYZisSession* self(); > viewwidget.cpp: : YZView( _buffer, QYZisSession::self(), 10 ), buffer( > _buffer ), m_popup( 0 ) > > So it seems like in all these cases YZSession::me would do - no need > for QYzisSession::self() at all. Correct me if I wrong.
On Tuesday 19 December 2006 14:13, Panard wrote: > Well, the first problem I see with these classes, is they are belonging to > QtGui, and we have made efforts to avoid linking against it (because it's a > really big library)... Agh. This is a big issue indeed. Thanks for pointing this out. No need to rush on those until we have put a lot more thoughts into it. Thomas -- -- Thomas Capricelli <orzel@...> http://orzel.freehackers.org/
I know that soon we may change to doxygen, but it's still not bad to have some new information in the manual. Known issues: * I'm not sure if the gentoo ebuild depends on subversion * I get question mark instead of '>' in the pdf David
Hi, I have committed some doxygen files, one is the beginning of the documentation about lua scripting with Yzis. The other is a conversion from latex to doxygen of the Architecture overview chapter, initially written in latex. I was wondering if doxygen was more suitable than latex for this job. You can look at the result and evaluate both solutions yourself. The latex generated handbook: http://orzel.freehackers.org/yzis/YzisDeveloperHandbook.pdf The doxygen generated handbook: http://phil.freehackers.org/programs/yzis/apidoc/apidoc-2006-12-15.zip check the chapter yzis scripting and architecture overview. Pro Latex: - more control on the detailed rendering of individual elements - more structure available for chaptering (automatic numbering, ...) Contra Latex: - no html generation of the developer handbook - need to learn another presentation language (I don't know latex for example) - the tool suite to generate latex is complicated, you need the right package, and to make it work. It is especially difficult to generate it on windows. Generating it on linux gives 1000 warnings. - links to the actual api documentation is not easy to make. Pro Doxygen:(Continue reading)
 |
|
|
|
|
|
|
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
RSS Feed3 | |
|---|---|
1 | |
2 | |
6 | |
4 | |
22 | |
3 | |
4 | |
4 | |
6 | |
6 | |
10 | |
2 | |
13 | |
4 | |
37 | |
1 | |
17 | |
19 | |
42 | |
5 | |
108 | |
56 | |
46 | |
79 | |
15 | |
21 | |
92 | |
16 | |
25 | |
31 | |
97 | |
86 | |
88 | |
44 |
