Agreed but only if the id is conform wicket standards (starting with wicket-) This will allow code like <div id="myCustomId" wicket="myPanel"/> to be used. The output would then be <div id="myCustomId">....</div>
I'm not too happy about the generated id's either but I can live with them as long as I can fall back to this stuff. Maurice -----Oorspronkelijk bericht----- Van: Juergen Donnerstag [mailto:[EMAIL PROTECTED] Verzonden: woensdag 16 februari 2005 12:56 Aan: [email protected] Onderwerp: Re: [Wicket-develop] id of elemets and listviews I guess what I also don't like too much are the autogenerated ids (40+ chars). Why not just a switch (application only) which removes all attributes (id and wicket) which Wicket used to identify components. Making it default would generate valid (x)html. If I understand you correct, you say that probably no one (css and js) will use these autogenerated names anyway. If they need an id, they should go for an wicket attribute. The more I think about it, the less I like it. Juergen On Wed, 16 Feb 2005 12:35:47 +0100, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > I don't think it would be difficult to implement. It is only I did not > come accross a situation where I wished I have that feature (but I'm > not an expert on this). Which is probably as well why I'd prefer to > have it off as default. But I admit I lost somehow track of the > discussion. Mind you writing a summary of the pros and cons (may be it > is already there and I missed it in all the emails about that topic). > > Juergen > > > On Wed, 16 Feb 2005 12:22:17 +0100, Eelco Hillenius > <[EMAIL PROTECTED]> wrote: > > Martijn, Maurice and I had an offline discussion about the whole thing. > > There are definitively pro's (like being complient, for generated JS, > > etc) and con's (using non-generated JS etc) for the whole case. We would > > be +1 for making this configurable. It would be a setting (default to > > true?) that when true, would replace the id attribute values (if id is > > used as the wicket attribute) with the unique path to that component > > (but probably without the pagenumber and rendering). Besides being a > > global setting, it is likely (we think) that people want to override > > this on a page basis. > > > > Jonathan, Juergen, would that be hard to implement? And do you agree? > > > > Eelco > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Wicket-develop mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
