yeah ignore that. i was thinking that the strategy can decide whether or not to add id based on something about the component. this of course is not enough because most components will not be aware of being ajaxified at all.

i guess we will always have to add it if its not there.

getMarkupId() doesnt sound right.

i guess i can live with getDomId()

how about getHtmlId()

-Igor


On 2/1/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
That CssId name is not right though. What about markup id or - when
you want to stay close to what it actually is - DomId.

I don't understand the second part. If behaviors can call getMarkupId,
that's just fine isn't it? Why would we need an extra interface?

And getting the id is one thing; the id needs to get rendered too. Are
we going to implement that the ids are always rendered when they are
not-null?

Eelco


On 2/1/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote:
> indeed. lets do it. how would it work? we can add component.getCssId() which
> can call some kind of a ICssIdFactory { String getCssId(Component c) } that
> you can set in markup settings?
>
> maybe have INeedCssId interface that a behavior can implement, and so the
> cssidfactory can look at behaviors and if one needs it it can return a non
> null? kinda like its there ondemand.
>
> its late, does that make any sense?
>
> -Igor
>
>
>
> On 2/1/06, Marco van de Haar <[EMAIL PROTECTED] > wrote:
> > I'm not a core dev, but I'm using _javascript_ in combination with Wicket
> > a lot in contrib-dojo, and I would say that a standard way of doing this
> > in Wicket would be a great asset.
> >
> > Marco
> >
> > Eelco Hillenius schreef:
> > > Hi,
> > >
> > > I quite lost what our status is concerning the id of rendering HTML
> > > ids by default for all components. I thought the last idea was to make
> > > it an application wide setting (turned of by default?).
> > >
> > > Any reason why we don't have this yet? Time or didn't we agree after
> all?
> > >
> > > Eelco
> > >
> > >
> > > -------------------------------------------------------
> > > 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://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> > > _______________________________________________
> > > Wicket-develop mailing list
> > > Wicket-develop@lists.sourceforge.net
> > >
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > Wicket-develop mailing list
> > Wicket-develop@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
>
>


-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to