Hello to everyone,

I decided to create a developer manual but i realize that it's not so easy.
I cannot understand the structure of the project (i'm a newbie).

So, I have some questions:
1) there are a lot of subdirectories in the svn trunk. It's easy to understand 
what there's inside "data", "docs" and "gui" (i suppose that here there's the 
front end in QT), but what part of the project is inside "extra" and "libs"?
For example, suppose i want to take a look at the class that plays the whole 
song (i don't know if there's or not, but suppose), where i should find it?

2)May someone explains me the "structure" of the program? For example, an 
explanation like this may be good:
there are <n> main components. <component1> do <something>, <component2> do 
<something else>. 
<component1> is located in <relative path>.

and so on...

Well, you know, there are very few informations in the doxygen documentation: 
for example, there's no explanation of the classes and only few methods seems 
to have annotation.

3)Doxygen says that the doxygen file is not update.
"Tag `DETAILS_AT_TOP' at line 34 of file Doxyfile has become obsolete."
Well, it's easy to fix with "doxygen -u Doxyfile", but i don't know how to 
apply this change in the main project. So, I hope that someone will do this for 
me :-)
(i use svn only very few few times and so, i'm not skilled using this.)

Well... now i don't have any others question. 

Bye,
Paolo Parisen Toldin


      

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel

Reply via email to