J Aaron Farr wrote:
Hello all.

I've been slowly working on a Fortress Newbie Tutorial.  Shash
Chatterjee has also volunteered to help me.
way cool! I'll be happy to answer any questions I can :D

Thus far I've mostly just been jotting down notes as I've been building
my own first Fortress app, but I hope to start really writing something
over the next few days (goal is to have at least "something" by
Sunday).  Anyway, I know that Fortress has just undergone significant
refactoring and I was planning on basing the tutorial on the updated
CVS.  Before I went through all the work to do that I wanted to check if
this was a wise idea.  I'm assuming the refactored code is what's being
targeted for the 1.0 release.
yes. Note the refactoring is 99% class movement and only 1% something else. You probably only have to change package names for various classes.

I've divided the tutorial into a number of parts, but my first target
will simply be a "jump right in and get something running" document
based on the existing Fortress examples. Sort of a "hello world" in
Fortress followed by a detail explanation of how and why it works --
something that complements the "Developing with Avalon" documentation.
sounds smart. It would be nice to have the code from that helloworld example in source code form in the source tree (ie @ jakarta-avalon-excalibur/fortress/examples/).

After that I'd like to write more about the other examples and then
about writing new services/components for Fortress.
sounds good, too.

Hopefully I'll have something finished in time for the 1.0 release.  Any
suggestions or direction would be appriciated.
my suggestion would be "release early, release often". Once you get something up you are not afraid of showing to the outside world, put it somewhere public (you could put a zipfile in bugzilla or something like that, for example), and providing feedback would be easier.

Also, don't worry too much about release schedules. Your tutorial can go online regardless of whether it is completely polished, and we can reference it from the distribution.

cheers (and thanks for taking this up!),

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to