On Tue, 2003-01-21 at 14:25, Leo Simons wrote: > J Aaron Farr wrote: > > 2. I've pulled the fortress code from CVS, but it seems as if this can't be > > built against avalon-framework 4.1.3. (If I'm wrong here, please let me know). > > I'll check asap. The goal is definately to get it to build against that! >
I won't be able to double check this until Thursday, but if I remember correctly, there was a class "missing" in the framework release. The class is in CVS, but not in 4.1.3 and Fortress uses this class. Which one? I can't remember right now. Wrapper something or other. I'll check Thursday. > > I've tried reading over the dev mailing list > > archives, but I'm not sure what the status is. Is there anything that a lowly > > user might be able to do to get Fortress out (docs, patches, testing...)? > > all of the above! Some docs stuff that would be nice: > - javadocs. You can easily find dozens of class members or even whole > classes without docs > - an actual hands-down user guide which talks one through the existing > examples (I'm wanting to rip stuff out of the tweety quick start guide) > - update of "Developing with Avalon" for fortress > - migration guide for ECM users > I can't help with migration docs, since this is a new project and I haven't used ECM before, but I'll see what I can do about javadocs and general tutorial stuff. I need to get a better handle on Fortress as it is. Perhaps I'll take some notes as I go that could be useful for other new users. Documentation is going to be in Forrest format, right? > code stuff: > - more and more sensible debug logging output > - we need to look at exception handling > - i18n (using the excalibur i18n package of course :) > - inline code comments to clear some things up > - checking code for any hard-coded parameters and make them less hardcoded > - unit tests. Loads and loads of classes don't have 'em > > testing: > - always welcome! Since you're actually building an app, what issues > have you run into? What did you like? What not? > > this holds not just for fortress, but for all packages it depends on as > well, like event. In short, there's loads of stuff you can do, with > varying degrees of difficulty :D > > cheers, > > - Leo I have a few comments about my first project with Avalon (and specifically Fortress). In general I would say that I read the "Developing with Avalon" article, which was wonderful (although needs updated for Fortress), and then I went to start on my own project and that's where things got hard. I didn't really know where to start. Or I thought I did, but then found out, no I didn't quite get it right. Some of the code examples under CVS really helped me, but I think some more developed examples like Tweety would be great. Perhaps even a project template of some sort that could get people started, or a guide on how to take an existing project and "Avalonize" it (which is a fairly common practice from what I can see). Understanding a framework like Avalon is much more difficult than understanding something like Struts or even Cocoon. It's not just like you can look at an API and some config docs and start using it. It's a whole philosophy. Maybe I'm making it harder than it should be, but I think to get it right, you need to understand Avalon at a more fundamental level than other projects. Well, I'm going to start diving into the cvs code and see what I can do. Thanks for all the suggestions. I would have to say that the Avalon users list is one of the most responsive and helpful mailing lists I've ever been on. Thanks for all the hard work. -- jaaron <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
