Berin Loritsch wrote: > > Leo Simons wrote: > > > > > > PS: anyone know a good paper about COP to refer to? > > > > > > :) I'm writing it. Really though, I am writing a three part paper > > > that I am going to donate to the Avalon project--I just need a word > > > processor to write it at the beginning. > > > > Good you repeated that. I think I'll go and work on the phoenix > > design documentation and javadoc then (I am assuming you are just > > doing a 'hands-on' for your presentation?) > > 'hands-on'? > > The ApacheCon specifies all papers and slides need to be > made available in RTF (not HTML, Doc, PDF, or anything else). > If only FOP handled RTF.... > > I am doing a practical approach to Avalon programming. > > Part 1: What is Avalon (and Why should I use it) > > Part 2: How to break down a system (COP, SOP, OOP, patterns, etc). > > Part 3: How to use Avalon to realize my design. > > Those aren't the official titles, but give you an idea > of what I am writing.
Here is my biggest delimna: I don't think I requested enough time with my session. There is just too much information. I think that it's a double edged sword, and if I make the session too long, it will be a deterent, and if I make it too short I won't be able to disseminate the information. I may have to break it down into 2 or three sessions. But, I would need to know--if you were at the ApacheCon (hypothetically speaking) how many sessions on Avalon would you attend? I am thinking of doing the following approach: 30min: Introduction to Avalon 60min: Programming with Avalon 60min: Designing with Avalon Is this too much? Or, should I do two sessions: 60min: Designing with Avalon (introduction and analysis techniques) 60min: Programming with Avalon I am finding that it is very difficult to cram everything into one hour. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
