Re: [Tapestry-contrib] Getting back into it

[Geoff L. <glo...@in...>]

Yeah, the module idea works too. Although, I dunno how it would work in  =
the Vlib case specifically as there are three folders at the same level, =
Vlib, VlibBeans, and VlibEAR.

I will browse around some jakarta projects to see how they have laid =
things out. Will post findings to the wiki.

Geoff
  ----- Original Message -----=20
  From: Howard M. Lewis Ship=20
  To: Geoff Longman ; Tapestry Contrib=20
  Cc: tap...@ja...=20
  Sent: Sunday, January 12, 2003 11:46 AM
  Subject: Re: [Tapestry-contrib] Getting back into it


  Part of what you discuss may involve having multiple Tapestry modules. =
 Not good or bad, just a statement.

  Yes, and we may need to reorganize things further to reflect the =
standard Apache project layout ... if we want to get the synnergy thing =
going, we want to make Tapestry "friendly" to other Apache developers.

  Renaming packages looks like a big delete-and-add to CVS, so that's a =
good time to also reorganize directory structure.  We should brainstorm =
what that structure should look like.
    ----- Original Message -----=20
    From: Geoff Longman=20
    To: Tapestry Contrib=20
    Cc: tap...@ja...=20
    Sent: Sunday, January 12, 2003 11:34 AM
    Subject: [Tapestry-contrib] Getting back into it


    Whoo-ee, I have to say that this past holiday season was the worst =
on record for me.
    Just before Christmas good friends of ours had a terrible accident =
and their little girl was quite badly burned.=20
    It'll be a tough road ahead for their family but everything is =
relatively ok now.

    Also, I had a bit of a health scare myself last week and on top of =
all that we have a baby due imminently.
    Note: having a baby ids a good thing, it just added to the overall =
stress this holiday season!

    So, forgive if I've been quite the last while. I'm easing back into =
the 'normal' things now...

    Glad to see that the Apache thing is rolling along. Kudos to Andy et =
al!

    Looking for something to do Tapestry-wise and I was wondering if =
anybody had any thoughts on
    the structure for the code base in CVS.

    Currently, everything is located under the top-level Tapestry =
folder. That incl the framework, vlib, clover, contrib, workbench, and =
the=20
    mock opera :-) that Howard has built for testing.

    Would it make sense, after the move, the package rename, the Gump =
build (don't really understand that) was done
    if we examined the structure and split some of it out to the top =
level?

    The current advantage is that one can check out 'Tapestry' and get =
everything at once. One disadvantage is that to examine, for example, =
the vlib using Spindle is quite difficult.

    As I said, I realize there's still a lot of work to do before making =
these kind of changes. But I'm willing to play around with this.

    Geoff

    Geoffrey Longman
    Intelligent Works Inc.