tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Saltiel" <adam.salt...@btinternet.com>
Subject RE: [DISCUSS] Tapestry Release Names
Date Fri, 01 Apr 2005 21:56:34 GMT
I'm not too fond of the idea of using names rather than version numbers.
But I can see two reasons for it. The first is for marketing reasons
(what I had always thought *was* the reason for Catalina, Tiger,
Longhorn etc.). But be careful, in this case there must be a clear and
acceptable theme. The second reason is more interesting to me. That it
would encourage a broader roadmap.
As Ruby had now been put on that map (if only tentatively) this brings
me to Rails. As DHH writes here
http://www.loudthinking.com/arc/000408.html about Active Record, it
seems to me that the construction of this ORM solution is bound to the
nature of the Ruby language. Am I right, and if so how would Tapestry
transition to Ruby and take advantage of the nature that language? It
seems different to me to bridge to Ruby as at the moment, to actually
implement the whole framework.
Any pointers?
I have another architectural question I think mention of a road map
excuses :). I do not believe that anyone on this list has yet mentioned
the Dexter project, which originated in the HP labs in Bristol and is
now commercialised by 1060Research as the 1060 REST Microkernel with
plugable services.
To me, HiveMind in particular and also Spring, seem to overlap with
1060. What maybe a significant difference is the way in which Tapestry
and Hivemind are used. Might it be that they are better at integrating
into existing environments? If so, would that point at one of the areas
that these projects should continue to concentrate on, for instance the
means to wrestle with existing Struts apps and extend them into
HiveMind/Tapestry (just a possible example)?
Any ideas?

Adam Saltiel



> -----Original Message-----
> From: Erik Hatcher [mailto:erik@ehatchersolutions.com]
> Sent: Friday, April 01, 2005 7:20 PM
> To: Tapestry development
> Subject: Re: [DISCUSS] Tapestry Release Names
>
>
> On Apr 1, 2005, at 12:23 PM, Howard Lewis Ship wrote:
> > I think Tapestry should start doing that; express the road map with
> > release
> > names.
> >
> > I was just IM-ing with Erik, and brainstorming a "theme" for release
> > names.
> > The one we liked was city names. I chose a few favorite
> cities, with
> > easy
> > (single word) names: Portland, Vancouver, Boston, Amsterdam , etc.
> >
> > So here's a possible roadmap:
> >
> >    - Tapestry Portland: HiveMind integration + Portlet support (aka
> > 3.1or
> >    4.0)
>
> +1
>
> This will be timely with OSCON in Portland this summer :)
>
> >     - Tapestry Amsterdam: Re-implement in Ruby :-)
>
> What about GCJ'ing Java Tapestry and wrapping with SWIG to interface
> with Ruby?!   (yes, I'm kidding - though this is similar to what
> PyLucene did as well as a Ruby Lucene in the works).
>
> 	Erik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message