On Sat, Feb 19, 2011 at 3:43 AM, Igor Drobiazko <[email protected]> wrote: > Thanks. I still was using the formos repo. Now it works. > > BTW, the Dynamic component is great. I'm using it for dynamic selection of a > skin to be used in the layout component. It's just great and I would love to > see it in Tapestry core.
Yes, it is "have your cake and eat it too". > > On Fri, Feb 18, 2011 at 9:16 PM, Howard Lewis Ship <[email protected]> wrote: > >> On Fri, Feb 18, 2011 at 11:49 AM, Igor Drobiazko >> <[email protected]> wrote: >> > Hi Howard, >> > >> > what is the status of tapx? In my project I need the Dynamic and >> > KaptchaImage components from tapx. Unfortunately the tapx nightly build >> is >> > not running, so the latest snapshot is from 18th August 2010. This >> snapshot >> > is not compatible with 5.2.4. Of course I can clone the project from >> github >> > and run the build manually, but the built jar would be available only on >> my >> > local machine. >> >> I'm getting away from using the formos machine. I've been setting up a >> new Maven repository at howardlewisship.com that will host the >> artifacts. >> >> I'm actively working on Tapx. Tapx is a place for me to build things >> outside of the Tapestry development cycle; the components and features >> you see there are directly driven by my client projects. >> >> Tapx is also a place for me to experiment on other things, such as the >> Gradle build, and so forth. >> >> >> > >> > Is there a chance to make the current snapshot available? >> >> I'll look into getting the lastest snapshot up at the >> howardlewisship.com repository. >> >> >> http://howardlewisship.com/snapshot-repository/com/howardlewisship/tapx-core/1.1-SNAPSHOT/ >> >> Looks like I last pushed around Jan 18th. I'll push up a newer copy right >> now. >> >> > >> > Again, I would like to see a lot of tapx components built-in into >> Tapestry. >> > Is there any reason why new and very useful components, which don't have >> any >> > license issues, are in tapx and not in Tapestry? >> >> I agree ... I have no problem with moving (and improving) the Tapx >> code to become future Tapestry components. I'm sure the finished Tree >> component would be a big hit, as well as the Ajax editor, etc. I can >> see deprecated Tapx code when it moves to Tapestry proper. >> >> > >> > -- >> > Best regards, >> > >> > Igor Drobiazko >> > http://tapestry5.de >> > >> >> >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
