I did notice namespaces for wicket javascript. I wonder what can be done to
namespace javascript associated with each component. "Nothing" is acceptable
answer, I think.

Alex

On 4/13/07, Matej Knopp <[EMAIL PROTECTED]> wrote:

In case you didn't notice all wicket javascript (except for backward
compatibility function aliases) is namespaced Wicket.

As for custom components, wicket can't parse your javascript and
namespace each identifier.

-Matej

On 4/14/07, Alexei Sokolov <[EMAIL PROTECTED]> wrote:
> It is not a big problem, because I can take care of namespaces myself in
the
> javascript (good example of using namespaces in javascipt - dojo or
yui).
> However, since the framework takes care of component resources, it can
take
> care of javascript namespaces as well. This has nothing to do with what
> library you use, just make sure that all objects, variables, etc are
local
> to the component's namespace. This make sense only if you think that
> component itself consist of html and associated javascript (if any). If
you
> view components as static html with some resources attached to it - you
> don't have to worry about that. But then again, these days it is pretty
much
> always dynamic html on the client, and you don't want to be late on this
> train...
>
> Alex
>
> On 4/13/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > Also, at the moment
> > > javascript files (and other resources) are nicely packages, but
there
> are no
> > > mechanism for javascript namespaces (i'd like to see all
> component-related
> > > javascript to reside in its own private namespace on the client, so
> there
> > > are no conflicts).
> >
> > How should that work though. Currently, Java script support is pretty
> > free form. Which can be explained from the fact that Wicket is not
> > primarily a Javascript library and the design goal we have that you
> > can plug in any javascript library you want.
> >
> > But maybe you can expand a bit on where the lack of name spacing is
> > giving you problems right now?
> >
> > Eelco
> >
> >
>
-------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to
share
> your
> > opinions on IT & business topics through brief surveys-and earn cash
> >
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Wicket-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
>
>
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
your
> opinions on IT & business topics through brief surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-user

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to