Re: Class/method organization

> I agree there is several way to do. And my suggestion is to choose one 
> for static files and package organisation and avoid mixe.

It's a question of priorities, and how to use our time most efficiently. 
Working on tools will give a better result in the end, and other advantages as 
well.

Given that there are several possible organisations, it's also a problem to 
enforce one by the compiler, as the user might prefer another one, equally 
sensible. This is especially important as Nice brings more flexibility 
compared to Java, so it should appeal to people who enjoy that flexibility.

So it seems to me that following some conventions in your own projects is the 
best compromise until more advanced tools can be used.

> Currently there is no NiceDoc and IDE for Nice, and the only tool is 
> FileSystem navigation. 

Well, nicedoc and the eclipse plugin exist, but I agree they don't solve this 
problem in their current form.

> Note that some time it's the only tool also for 
> Java and other language (throught CVSWeb,...). 

Agreed, although it should be rare enough. Most of the time you could also 
check out the code from CVS and use your editor.

> Yesterday I start to 
> explore NiceDoc source and my first reaction was were is the 
> implementation of this class/method/function, idem when I go into the 
> source of Nice to search for AST, Document,...

Yes, I understand the difficulty. Don't hesitate to ask for help, I should be 
on IRC more often these days. (Oh, and I'm embarrased to say this, but grep 
might help ;-)

Cheers,

Daniel



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click