> Howard, how do you do? > > At this time, we've a migration project for a customer. The migration is > basically from WebLogic 5.1 to WebLogic 6.x o 7.0. In addition, we've to > migrate a portal from Commerce Server 3.2 to Portal 4.0. > However, some of the current applications have bad design and worse > implementation and is easier to make a new implementation than to change > the code. I'm thinking to use Tapestry instead of JSP or Struts.
Obviously, that's what I'd do. > > I can work in Tapestry and Spindle at company time. I modified Spindle > code to be complaint with Tapestry 2.0.4, but it wasn't enough. > > How can I get the changes list between versions? For example, I believed The "New" tab on the home page lists fixed issues in the release; you can get the details from SourceForge. At one time, I kept more detailed change log, but the effort involved detracted from my time for making changes, with little benefit evident. For production, I would recommend keeping to major dot releases (i.e. 2.0.0 or the upcoming 2.1.0). The minor releases are not fully stable. I understand and apologize that 2.0.3 really is a difficult, difficult change, what with the package renames. My thinking is that it had to happen sometime and the longer the wait, the greater the cumulative pain. > Tapestry 2.0.4 changes were bug fixes and a change in the namespace > (from com.primix to net.sf) and some refactorings. I don't know about > the new DTD for the spec. What are the DTD changes? The changes are additions and are otherwise backwards compatible to the 1.1 spec. The details are in header comments in the 1.2 DTD ... basically, adding support for the new direction attribute on <parameter> and for the new <string-binding> element. > What is the current procedure to commit changes to the cvs repository? 2.0.4 includes a "Tapestry Contributor's Guide" that answers most of these questions. Ant 1.4 is used to build Tapestry. > Do you have any info about the validation tool for Tapestry? I sent an > email to Mr. Bridge but I got an answer. I have yet to get a chance to look at this; it may be more suitable for inclusion in Spindle than in the Tapestry distribution. Does anyone care about the size of the distro? > Do you have a roadmap for Tapestry future versions? > A vague one; I keep thinking "its almost finished" but never quite. I have other things I want to work on, particularily Sabertooth. And my day job. Garret Suhm is putting together a Wiki for Tapestry; it will be a good place for the community to plan future directions. My current directions with Tapestry: 1) Autoconfigure for JBoss 3.0.0 (not 2.4.3) 2) Create JMX Control panel for JBoss 3) Add support for bundling components in namespaces #3 is very recent; the current implementation uses a single namespace for all components which is limiting. I want to create a mechanism that allow several related components to be created as a "library" or "bundle", with thier own namespace. This would allow several different developers to create a "Palette" or "DateField" without fear of collision ... the application developer would be able to mix and match as appropriate. > Regards > > David > > BTW, what is the ant version to build Tapestry? > > -----Original Message----- > From: Geoff Longman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 6:34 AM > To: David Solis > Subject: Re: Spindle for Tapestry 2.0.4 (was RE: Spindle port for > Eclipse F1 is up) > > David, I was just conversing with Howard and porting to 2.0.4 is much > more > than getting the existing source to compile. > I commited to having a good look at you changes this weekend, and I > stick to > that. > > But, Tap 2.0.4 has some significant changes including a new DTD for the > spec > files. That impacts at least the package > com.iw.plugins.spindle.spec, com.iw.plugins.spindle.model, and all of > the > editor/ui packages. Its a lot of work. > > I know everyone is clamouring for this support. I'm lucky that my > employer > allows me to work on SPindle on company time but only when Company work > is > done first. I desperately need the support too! But, I doubt that I'll > get > to it before the end of the month when Spindle 1.0.0 final comes out. > > Once that happens, I plan to stick the source in CVS at sourceforge and > invite the community to contribute more directly. > I thank you for the work you've done, keep it up. I'm sure that the > source > you sent will form the basis of a 2.0.3+ version of spindle and that > your changes will definitely speed along the new version! > > Geoff > > > ----- Original Message ----- > From: "David Solis" <[EMAIL PROTECTED]> > To: "'Geoff Longman'" <[EMAIL PROTECTED]> > Sent: Tuesday, June 04, 2002 9:10 PM > Subject: Spindle for Tapestry 2.0.4 (was RE: Spindle port for Eclipse F1 > is > up) > > > > > > Hi Geoff, > > > > I modified Spindle sources to work with Tapestry 2.0.4. > > I haven't tested well but it is working. > > > > I enclosed the sources and the plug-in ready for deployment > > > > Regards > > > > David > > -----Original Message----- > > From: Geoff Longman [mailto:[EMAIL PROTECTED]] > > Sent: Monday, May 27, 2002 1:18 PM > > To: David Solis > > Cc: [EMAIL PROTECTED] > > Subject: Re: Spindle port for Eclipse F1 is up > > > > Thanks for the input! As for Tapestry 2.0.1, it all boils down to > this. > > > > Pretty much all of my effort to date has gone towards chasing Eclipse > > stable > > builds as they approach > > R2.0. Spindle breaks with almost every Eclispe build as thier codebase > > is > > quite fluid. The current release of Spindle > > works, at the time I write this, with the latest stable build of > > Eclipse. > > > > 2.0.1 is the last version that I have downloaded. I know that there > are > > newer ones, I should check > > if 2.02. breaks spindle. From what Howard has told me he has > significant > > changes in 2.0.3 that will break spindle. > > In fact, from the release notes for 2.0.3: > > > > "This release is for Tapestry early adopters; most of the changes are > > not > > backwards compatible to earlier releases of Tapestry." > > > > IBM is coming down the backstretch with R2.0. Once that is out I can > > then > > give the newer versions of Tapestry the > > attention they really do deserve. > > > > I just checked and the current version of spindle might well work with > > Tapestry 2.0.0 anybody tried it? > > > > ----- Original Message ----- > > From: David Solis > > To: 'Geoff Longman' > > Sent: Monday, May 27, 2002 12:02 PM > > Subject: Spindle port for Eclipse F1 is up > > > > > > Hi Geoff, > > > > Just a question: > > > > Why just Tapestry 2.0.1? > > > > Anyway, Thanks for your excellent Tapestry contribution. > > > > > > Regards > > > > David > > -- [EMAIL PROTECTED] http://tapestry.sf.net _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
