tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jamie <ja...@dang.com>
Subject Re: [VOTE] Tapestry Release Names
Date Mon, 04 Apr 2005 16:15:59 GMT
It's interesting that as I read this with the new names, it seems more 
personal. Subtle, but interesting and I like it.

Aside from that psychological little tidbit, Howard and Erik, could you 
expand on the light-weight vs. heavy-weight approaches toward POJO pages 
for Magritte?

Thanks,
Jamie

Howard Lewis Ship wrote:

>I like to say that, five years ago, when I sat down and started building my 
>Tapestry prototype, I made about 10 critical architectural descions, and got 
>about eight of them right. The ones I missed on, perhaps because I was 
>following the WebObjects programming model too closely, are related to the 
>Java classes Tapestry developers write.
>
>In hindsight, it is obvious that those classes should be POJOs, but that's 
>the kind of thinking I've grown into in the last five years. Additionally, 
>there should have been a more direct mapping from page name or component 
>name, to page/component class and from there to the page/component 
>specification and template. The fact that a single class could be used for 
>multiple pages/components has turned out to get in the way.
>
>The 3.0, Picasso (4.0) and Magritte (5.0) releases are a stepwise 
>progression towards fixing this key aspect of Tapestry.
>
>3.0's abtract properties were a step in the right direction, but not nearly 
>far enough. I wonder, if I had not been working on the book, whether I would 
>have had the time to have gotten that right then? In some ways, I needed to 
>wait for HiveMind to be able to build a sufficiently sophisticated 
>infrastructure to support the goals of Magritte.
>
>Tapestry Picasso is still transition, but is introducing the idea that the 
>important details of a page or component are injected into it from HiveMind. 
>It also gets component parameters very, very right (i.e., much more 
>efficient, and no direction). This kind of thinking sets the stage for 
>Tapestry Magritte. Also, the Portlet support in Picasso is very important 
>for Tapestry's future success.
>
>Tapestry Magritte will get away from inheritance from base classes and away 
>from abstract classes. The POJO classes you write will be peers, plugged 
>into the page/component hierarchy. There are a couple of possible approaches 
>to this; I tend to favor a "heavy" route centered around runtime 
>modification of page and component peer classes as they are loaded. Erik 
>favors a lighter approach, where the classes start and stay as POJOs. In 
>either cases, JDK 1.5 annotations will take primary stage, and the XML files 
>will be sidelined or eliminated entirely.
>
>On Apr 3, 2005 2:16 PM, Brian McCallister <brianm@apache.org> wrote:
>  
>
>>I think version numbers are going up awfully fast =)
>>
>>-Brian
>>
>>On Apr 3, 2005, at 2:12 PM, Howard Lewis Ship wrote:
>>
>>    
>>
>>>I really liked Harish's suggestion, it had class.
>>>
>>>I like "Picasso" for Tapestry 3.1/4.0 (i.e., the code under
>>>development) and
>>>Magritte for the following release (Tapestry 5.0). Let's put it to a
>>>vote:
>>>
>>>Howard M. Lewis Ship: +1
>>>
>>>
>>>
>>>On Apr 1, 2005 3:00 PM, Harish Krishnaswamy <harishkswamy@gmail.com>
>>>wrote:
>>>      
>>>
>>>>How about the names of famous artists? Would be in the spirit of the
>>>>framework!
>>>>
>>>>Picasso
>>>>Van Gogh
>>>>Monet
>>>>Kinkade
>>>>...
>>>>
>>>>On Apr 1, 2005 1:42 PM, Geoff Longman <glongman@gmail.com> wrote:
>>>>        
>>>>
>>>>>or use unusual color names:
>>>>>
>>>>>Amethyst
>>>>>Carnelian
>>>>>Cinnamon
>>>>>Coral
>>>>>Crimson
>>>>>Ebony
>>>>>Emerald
>>>>>Indigo
>>>>>Scarlett
>>>>>Sienna
>>>>>Silver
>>>>>Xanthe (Pronounced: Zan-thee. Meaning: yellow)
>>>>>
>>>>>more
>>>>>
>>>>>Auburn
>>>>>Azure
>>>>>Cobalt
>>>>>Granite
>>>>>Slate
>>>>>Teal
>>>>>Topaz
>>>>>
>>>>>I like Cobalt, Indigo, Topaz, and Xanthe
>>>>>
>>>>>Geoff
>>>>>
>>>>>
>>>>>On Apr 1, 2005 1:28 PM, Jamie <jamie@dang.com> wrote:
>>>>>          
>>>>>
>>>>>>Or how about a Simpsons theme:
>>>>>>
>>>>>>Barney
>>>>>>Apu
>>>>>>Mo
>>>>>>Bart
>>>>>>Lisa
>>>>>>maybe we oughtta stay away from Homer... D'OH!
>>>>>>
>>>>>>Or we could be self-referential to Tapestry:
>>>>>>(Did you know we're on Wikipedia?
>>>>>>            
>>>>>>
>>>>http://en.wikipedia.org/wiki/Tapestry)
>>>>        
>>>>
>>>>>>Bayeux: http://en.wikipedia.org/wiki/Bayeux_Tapestry
>>>>>>Unicorn: http://en.wikipedia.org/wiki/The_Lady_and_the_Unicorn
>>>>>>
>>>>>>
>>>>>>Howard Lewis Ship wrote:
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>So, the current debate about Tapestry 3.1 vs. Tapestry
>>>>>>>4.0underscores why
>>>>>>>so many projects use a release name not a release number for
>>>>>>>upcoming
>>>>>>>releases.
>>>>>>>
>>>>>>>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)
>>>>>>>- Tapestry Vancouver: Remove inheritance requirements, remove
>>>>>>>              
>>>>>>>
>>>>abstract
>>>>        
>>>>
>>>>>>>methods/classes (probably 5.0), more sensible naming, etc.
>>>>>>>- Tapestry Amsterdam: Re-implement in Ruby :-)
>>>>>>>
>>>>>>>
>>>>>>>Thoughts?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>--------------------------------------------------------------------
>>>>>>-
>>>>>>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
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>>>
>>>>
>>>>        
>>>>
>>>--
>>>Howard M. Lewis Ship
>>>Independent J2EE / Open-Source Java Consultant
>>>Creator, Jakarta Tapestry
>>>Creator, Jakarta HiveMind
>>>
>>>Professional Tapestry training, mentoring, support
>>>and project work. http://howardlewisship.com
>>>      
>>>
>>---------------------------------------------------------------------
>>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