My intention is not to be harsh. I could not be harsh to anyone giving me something as open and free. It's a gift. We have a proverb that you don't check and complain about the teeth of a horse you got as a gift. First of all it would be impolite and unfair.
We are just really unhappy if Equanda or Chenillekit are not updated very soon and they don't work with latest Tapestry, since we wont be able to go further and have them included, since our plans are to always go with the latest of Tapestry, until we like it :) Tomorrow we might be unhappy if there were some new exciting features in latest hibernate, but tapestry-hibernate would not work with it and there were no news or published plans of intention to make it work. In that case we would be forced to change to something else. Sad but true. Our project is an ongoing project with frequent releases, used at university department - build by students for usage by students and teaching and administration staff, it is going on since 1992 (as far as I know, maybe even before) and it will probably go on in the future. We are rebuilding all our applications that need new features (almost all) with Tapestry, and we worked with JSP/JSF before that, Oracle PL/SQL and Forms before that, MS Access before that and Clipper before that. I don't know before that but I know that somebody did something with punched cards some 30-40 years ago. I am happy with Tapestry, and I lead the project for now. But for example nowadays Kuali Project is grabbing forward in many US universities and they have based their "Kuali Rice" framework on a stack with another web/view layer technology, so it might become alternative some time in the future, who knows. One has to always think outside the box. On 10/19/2010 05:43 PM, Howard Lewis Ship wrote: > Don't be too harsh on the 3rd party developers; we're still working > out what needs to be public and how.
smime.p7s
Description: S/MIME Cryptographic Signature
