A lot of discussions for new features for Tapestry occurs in this group, and that's great.
What I've seen is that a lot of these discussions wind down and no bug or feature request is added. No amount of dicussion in this group is going to result in any changes to Tapestry. If you've brought up an issue here, don't expect any changes to occur unless you add a bug or feature request ... and when you do, make sure you capture all the relevant discussions. For example, a recent discussion about improving localization petered out ... fortunately for whoever initiated the dicussions, this was important enough to me to reconstruct the discussions and add a new feature request. I've noticed this a bit over the last week, and I just don't want to leave people with the wrong impression. For example, there was a question about the Palette component, and I replied with "the Palette could be changed ...". That was me with my Tapestry contributor hat on, just brainstorming ideas with my fellow contributors ... not me with my Tapestry administrator hat on, deciding what to put into the framework. The administrator hat is driven by the feature requests and bug lists (even if the contributor hat has to add those requests). -- [EMAIL PROTECTED] http://tapestry.sf.net _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
