> While not trying to throw another log into the fire here, do we want to > keep the current code examples, albeit modified for the > Component/Manager interfaces?
No. All of them should be re-evaluated as we've moved around and cleaned up quite a bit. > I think one thing that might help newbies in understand where Avalon can > fit in is an example app of sorts outside the scope of Phoenix. I know > most(?) of you are involved with Phoenix and so it is easy to point > things in that direction. But what if the viewer then sees Avalon as > only a way to build complete apps, ala JAMES, Cocoon, etc. instead of as > a way to build a complete app OR a way to enhance their custom app. The > code examples go a long way to saying this, but there isn't that 'hello > world', real code base for them to look at. Well, we have hello world server in avalon-apps. Examples of projects moved over to avalon instead of starting out here...maybe look at Jo! ? cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>