My project is a Guild hosting site (for mmorpgs and other games) and
Gamer social networking site, with everything integrated  (the current
crop of them all have stand alone projects tied together from a portal
like page).

First thing that is probably a good discussion for this group is
design methodology.  Everyone is familiar with use cases, but I found
a methodology that seems to produce code faster with a test bed
prebuilt.  It is an offshoot of XP call Behavior Driven Design (BDD).
It has its own testing library built on top of JUnit called JBehave
http://jbehave.org/  .  This all flows nicely with the techniques in
the best practices video - seems to fit better than use case
methodology to me - but this is the point of discussion for the group.

A short summary in case you are not familiar with XP and/or BDD.

Instead of writing use cases, you and a user write user stories.  A
user story is a written as scenarios.  And if you follow the bdd
template JBehave stubs out your test class for you.  
http://dannorth.net/introducing-bdd
http://dannorth.net/whats-in-a-story  .  When you have a user story
finished you can go ahead and code the test cases for it.  Then create
the code that makes the test case work.  In XP design it is deemed
better to refactor the code as you go than to complete a complicated
design up front - so you don't even have to have all your user stories
done to start coding.  A user can go back and add a missed scenario to
a story, a coder gets assigned that as a task, creates the test case
for it,  then codes the change.

Of course all this fits inside a framework like mvp and command
pattern - so you take those as givens.

On Jan 24, 9:35 am, andreas_b <[email protected]> wrote:
> Hi.
>
> Preferrably via the project page if you can find an appropriate place
> for the discussion, but if its something that might be of value for
> other forum visitors here, we can discuss it here and I can simply add/
> link to it from the project page.
> What kind of project are you working on?
>
> BR, Andreas
>
> On 24 Jan, 16:27, Deanna Bonds <[email protected]> wrote:
>
>
>
> > Would you prefer to discuss any ideas here, or through your project
> > page?
>
> > On Jan 24, 9:08 am, Deanna Bonds <[email protected]> wrote:
>
> > > I am about to code a new project where I intend to use the approach in
> > > Ray Ryan's video.   I will send your project any tidbits I find.
>
> > > On Jan 24, 9:05 am, andreas_b <[email protected]> wrote:
>
> > > > Yes. I actually refer to that blog in my pages..it is a great
> > > > walkthrough and is a good starting point for learning about the best
> > > > practices.
> > > > However, it is still only a hello world example and it's a whole other
> > > > story to apply these practices and design patterns to a more complex,
> > > > "real world" application.
>
> > > > Thanks for pointing it out nonetheless :-).
>
> > > > On 24 Jan, 15:55, Deanna <[email protected]> wrote:
>
> > > > > Have you seen 
> > > > > thishttp://blog.hivedevelopment.co.uk/2009/08/google-web-toolkit-gwt-mvp-...
>
> > > > > It is a sample project that uses the best practices from that video.
>
> > > > > On Jan 24, 8:44 am, andreas_b <[email protected]> wrote:
>
> > > > > > Hi all.
>
> > > > > > I've just started a new open source GWT/GAE project where I will be
> > > > > > following Ray Ryan's best practices and recommended design patterns.
> > > > > > Every step of the way will be posted on the web and I will try to
> > > > > > initiate discussions with readers on how to solve problems along the
> > > > > > way.
>
> > > > > > If you are trying to learn GWT/GAE or already know a lot about it 
> > > > > > and
> > > > > > want to help, I would love to hear your ideas and comments.
>
> > > > > > Head over tohttp://borglin.net/gwt-project/anddecideifyouare
> > > > > > interested in learning/helping out!
>
> > > > > > BR, Andreas

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to