Jesse, Don't misunderstand me, I wasn't asking anyone to support T3 anymore than they already are, which is mainly bug fixing and answering questions. I believe that Spindle for T3 and T4 is pretty much dead. T5 will be a whole new beast and maybe there will be some tool support then. As far as components for T3, we who are still on T3 are on our own.
I believe you have your hands full with T4. When T5 comes out maybe someone will want to create a tool then, I guess we will have to wait and see. regards, Mark -----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Tue 8/29/2006 11:20 AM To: Tapestry users Subject: Re: Progress Bar These points are certainly valid sounding. I don't want people to think I don't care about what the community wants. My hands are unfortunately tied. I barely have enough time to work on Tapestry as it is, let alone another project like plugins..Trying to find time to work on a project I would never use is something I find hard to swallow. I can only hope if the community wants it bad enough someone will eventually step forward and decide to do it. As much as I think spindle really does provide a lot of value to the community, I personally have used it once - for less than a day. Now a combination of T5 + something like www.eclipse.org/atf ~is~ something I would find personal value in using...That may be something I investigate at some point in the future when both projects mature a little more. I know one of the core devs on that project and how it is laid out, so I don't think adding a "Tapestry" personality would be very far fetched.. Eithery way I don't think Howard or I will be going away anytime soon, which also means T4/T5 won't stop being supported anytime soon. I don't know what else to say...I'm trying my best to do what I can...I can't do everything :( On 8/29/06, Mark Stang <[EMAIL PROTECTED]> wrote: > > Th original problem was that 3.x needed to evolve. So, 4.x was the next > generation. However, as Howard was creating 4.x he realized that he > wanted to skip ahead to the next generation of Tapestry. Tapestry users > were not ready, so Howard left "4.xers" behind. And Jesse took over the > evolution of 4.x. 4.x is very different from 3.x, for people who needed > the next generation of Tapestry but couldn't wait for Howard it serves a > very valuable purpose. And from what I read on the list, Jesse did a great > deal of the work in making it what it is and has done a fine job. > > I was waiting on Spindle before moving to 4.x. Now what do I do? I guess > the question is what of 4.x do I need? For our application, 3.x is doing > what we need. And if it is doing what I need what do I gain from 4.x? I > guess I would gain that I am on the current release with necessary bug fixes > and enhancements. And probably new and improved components. > > When 5.x comes out, I will have to decide whether to switch or not. Once > again what will my ROI be on the move to 5.x? > > What if I waited for 5.x and it never comes? What if I switch to 4.x and > then 5.x arrives shortly after? Will 5.x go the route of Spindle? > Bottom-line is that there isn't an intuitively obvious upgrade route. What > I have is "FUD", Fear, Uncertainty and Doubt. > > > > -----Original Message----- > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > Sent: Tue 8/29/2006 10:13 AM > To: Tapestry users > Subject: Re: Progress Bar > > It is an open source project, anyone can make Tap3 / 4 / 5 anything they > want it to be. > > I work on 4.X because that's what I currently enjoy. > > On 8/29/06, Mark Stang <[EMAIL PROTECTED]> wrote: > > > > Some of us have a large projects. Or could it be that Tapestry > > > 3.999999999999 is so unstable as to be not worth the effort. First, > > there isn't a Spindle product, then there is and now there isn't. Then > > 4.x is the Holy Grail of web frameworks until Howard starts making is so > > incompatible with 3.x that he has to divide it into 4.x and 5.x. And of > > the three which is compatible with the others? NONE!!! So, do we > upgrade > > to 4.x and then later to 5.x or do we skip 4.x because 5.x is coming > soon > > and who wants to repeat the same upgrade twice or do we sit on 3.x and > > wait for the dust to settle. And it is so much fun knowing that we are > on a > > DEAD branch with no new components or real enhancements. > > > > I think I will switch to Swing. > > > > > > -----Original Message----- > > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > > Sent: Mon 8/28/2006 7:54 PM > > To: Tapestry users > > Subject: Re: Progress Bar > > > > From the sound of things it seems like you must either really enjoy pain > > or > > have an incredibly large project that would prevent you from upgrading > to > > 4.1 ;) > > > > On 8/28/06, Peter Dawn <[EMAIL PROTECTED]> wrote: > > > > > > guys, > > > > > > is there a component available for tap3 for a progress bar or anything > > > else which can help me display a progress bar. > > > > > > now i am thinking of generating something myself using a frames and > > > constantly updating the main page with the status (1%, 50%, 100% and > > > so on). this can be using either css or something else. but if there > > > is something within tapestry i can use, it would save me time. > > > > > > any ideas. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Jesse Kuhnert > > Tapestry/Dojo/(and a dash of TestNG), team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > > > > > > > > -- > Jesse Kuhnert > Tapestry/Dojo/(and a dash of TestNG), team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > > -- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
