On 11/25/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
> cssid is something completely internal. And i hope that the current limiting
> factor (that you have to render it first one time)
May I ask 2 questions :
- What does the cssId name mean ? Because css already means something
very concrete to me (cascading style sheet), but I'm almost certain it
is not the intended meaning in cssId ?
- What is the reason for having almost reimplemented the
getPageRelativePath() algorithm in the getCssId() method (except the
fact that you truncate the Id when it is more than 100 characters,
which I considerer a little bit dangerous, because you could have
sibling forms included in a ListView deep in the Component hierarchy,
then resulting, with the truncation, in duplicate ids form the form).
I would suggest (if I understand the things well), the following for
the getCssId() method :
protected final String getCssId()
{
return getPageRelativePath();
}
and get rid of the cssId field as well ?
Oh, and also maybe rename the field and method ? What about getId(),
or getDocumentId(), or getHtmlId(), or something like that ?
ids are concepts used throughout the XML format & variants, they have
primarily nothing to do with css ?
Hope I don't upset you with my remarks,
cu,
--
laurent
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
