click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Schellink <>
Subject Re: Confusing page class mapping
Date Tue, 22 Jun 2010 07:33:25 GMT
After Malcolm's comment I don't think we should move in this direction. The classname should
treated as an absolute name. Logically that makes sense and both IDE implementers interpreted
this way too. Having absolute classname makes hotlinking quite straightforward, no mucking
with the package name.

Another advantage of this approach is its possible to define a page outside the defined "package"
without having to create another <pages> element.

Wrt the docs, the only incorrect section is the second and third examples here:

To keep backward compatibility we can still load the classname with the package prefixed if
classname can't be found.

Kind regards


On 22/06/2010 17:10, Adrian A. wrote:
>> I've improved the error message if the classname cannot be loaded.
> Nice.
>> I also agree that we should
>> update the docs and add the pages element where absolute page
>> classnames are specified.
> OK. I'll look into those places and upgrade the docs.
> I only wonder if IDE plug-ins could use this Click API directly so that
> they behave consistently with Click.
> Adrian.

View raw message