> Leo Simons wrote: > > all, > > > > tweety is ready to go online. Dist are at > > > > http://cvs.apache.org/~leosimons/excalibur/tweety/ > > cool :-) > > Leo, I still think that having made the main class a Component itself > with the lifecycle methods is confusing for early users, as well as the > fact that main() makes it call them on itself :-S
hmm. having main() instantiate a copy of itself is, I think, quite common behaviour. The alternative is to have another class, called Main, that instantiates Tweety. Wonder what is clearer. > I would just revert to the old behaviour which is more simple, and > thought you kinda agreed on this... > > What do you think? Like I said earlier (I think), not making Tweety a component would be an example of bad design. If you just use tweety, you just type 'ant run' and never deal with anything of its internals, so the *exposed* behaviour is exactly the same. If you want to look at the source to Tweety to learn what it does, I think it is very important that the source is well-written according to our own standards. And the less pronounced motive is that I'm sure people will be misusing Tweety, for example putting it inside phoenix or somethin'. While I 'officially' disprove, I can see why =) cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
