Re: myWishList

>> If so great. My concern was that it explicitly be found under the 
>> Object class's javadoc, despite the fact that it is not generated form 
>> that file.
> 
> 
> I did not yet find a way to automatically modify the Object.html file on 
> Sun servers ;-)
> 
> Seriously, given that Nice is not class-centric, it's a good question 
> where such a method should be presented. One benefit of being able to 
> add methods to existing classes in new packages is that those methods 
> might only be useful in certain contexts, when you decide to import that 
> package. However, I agree that given a set of packages, it can make 
> sense to be able to see all methods whose first argument is a given 
> class, regardless of the package they are defined in. That is, I believe 
> that multiple views are useful: package-based and class-based at least, 
> and it should be easy to switch views. The same possibility would be 
> useful in editors too (eclipse).
> 
> At the moment nicedoc output is package-based only, so this should be 
> added.
> 

 From the point of integrating nicedoc with javadoc, i thought the 
package level will be represented as the methods of the 'fun' class.
It is, perhaps, possible to generate nicedoc-javadoc documentation for 
the Objec as well, although it will contain no documentation for 
Object's inherent methods.

>> Also is it possible to do compile time unit testing in Nice? If not, I 
>> could work on it.
> 
> At the moment you start them with a separate tool (niceunit). I agree it 
> would be practical to integrate it with nicec, and it would probably be 
> a good idea to run the tests by default if there are some present.
> 
> It should not be hard to implement this. Basically, import 
> nice.tools.unit from nice.tools.compiler, and if compilation succeeded, 
> call the right method to start the tests (which is harmless if there are 
> no tests). Don't hesitate to ask for help, and please submit a patch.

Currently in my project i just invoke niceunit after nicec from the ant.
If taken into the nicec itself, there is an interesting question: how do 
i test the whole application? I have a package which imports all other 
application packages, and to rebuild the application as a whole i invoke 
nicec on that particular package, but for niceunit tests currently i 
just invoke all the niceunit's one by one from a separate target. If 
niceunits are invoked from the nicec, then it would somewhat weir to 
test only the uniting package after compiling all the other packages.


-------------------------------------------------------
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