On Nov 30, 2007, at 1:24 PM, johnf wrote:

> I'd love to help.  I'm sure I would learn something in the  
> process.  The other
> day Nate and I were discussing what we could present as demo.

        If there is one thing I would insist on, it's focus. A bunch of  
stray programs that illustrate one thing here and another thing  
there, while well-intentioned, will not help anyone. For things like  
that, a wiki page with a link to files that can be downloaded from  
either your site or the dabodev site would be best.

> It's sort of tuff when you consider all of the subjects that should  
> be covered.

        A journey of a thousand miles begins with a single step. What was  
the hardest one for you? IOW, what took the most time for you to  
understand and do correctly? Start there; if you complete nothing  
else, you will have helped lots of people who will not have to  
struggle as you did.

> For example just the differences between platforms (although minor)  
> can hinder a
> newbie.

        A wiki page on platform differences sounds perfect for this, since  
everyone can add to it as they are uncovered.

> Then there is the database that will be used (I of course would like
> to see Postgres used).

        Why should that matter? Anything instructional for Dabo should be  
database agnostic.

> Just explaining the power of biz objects could take up a lot of time.

        Of course. Again, pick something and run with it.

> Then what about the question of using the ClassDesigner vs hand  
> coding.

        That's not a show-stopper, since people will pick one or the other  
and go from there. A better focus would be on strategies for the  
(hand-coding/cdxml) process.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]

Reply via email to