tag:blogger.com,1999:blog-4110180.post2716201699355162922..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: Id conflict inside Web BrowserAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4110180.post-82391908176797893042008-09-02T00:32:00.000-07:002008-09-02T00:32:00.000-07:00The way Tapestry 4.1 generates ids and names for e...The way Tapestry 4.1 generates ids and names for elements is very valuable. It is not 100% fault proof but helps you avoid many errors. I then use expension with ${myComp.id} in my javascript code to get the component or element id. It even corrects mistake on partial renders....<BR/>You should check with Jesse the implementation of ajax, I think he made a brillant job with Tap4.1. What's missing also is that you rely completely on prototype. Prototype is cool for quick js development, but if you intend to develop some components then there are better frameworks out there. You should make tapestry JS library independent with the ability to plug in different JS libraries. There should be a tapestry.js with all the methods and events listener/register needed. And one implements this file with the JS library of its choice.<BR/><BR/>And also all css should be set with class and never element id...Unknownhttps://www.blogger.com/profile/09239014020482680492noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-14065017092148276402008-09-01T04:46:00.000-07:002008-09-01T04:46:00.000-07:00A compile-time check doesn't have to find 100% of ...A compile-time check doesn't have to find 100% of the errors in order to be valuable....Noel Grandinhttps://www.blogger.com/profile/00203932250096476916noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-2514146005499987062008-08-30T14:45:00.000-07:002008-08-30T14:45:00.000-07:00Or maybe for debugging, use a param to the servlet...Or maybe for debugging, use a param to the servlet that enables ID checking for development (maybe give the option of outputting via logger, or throwing an exception on those pages).<BR/><BR/>If not, maybe some javascript library that can be run on page load and after ajax calls in development that alerts the user?Craig St. Jeanhttps://www.blogger.com/profile/07800109712106266214noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-50218996171361988062008-08-29T13:41:00.000-07:002008-08-29T13:41:00.000-07:00Hi, Howard!I prefer to have some tag id (not check...Hi, Howard!<BR/><BR/>I prefer to have some tag id (not checking tags created via AJAX) than checking no checking at all.Thiago H. de Paula Figueiredohttps://www.blogger.com/profile/07307722531281751788noreply@blogger.com