t:dojoInitializer djConfig.baseScriptUri has no properties

[Juan Ignacio Sánchez Lara <ju...@gmail.com>]

At the documentation of t:dojoInitializer there's no comment on
baseScriptUri, but Javascript throws "djConfig.baseScriptUri has no
properties". Must I set it? What value to?

-- 
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl

Re: t:dojoInitializer djConfig.baseScriptUri has no properties

[Juan Ignacio Sánchez Lara <ju...@gmail.com>]

Ok, I'll try and tell. Thank you _very_ much for your suggestions!!!

On 6/20/07, Werner Punz <we...@gmail.com> wrote:
>
> Juan Ignacio Sánchez Lara schrieb:
> > This is just the beginning:
> >
> > <
> >
> > a4j:outputPanel ajaxRendered="true" >
> >
> > <f:verbatim>
> >
> > <t:dojoInitializer require= "dojo.io.*" />
> >
> > <t:dojoInitializer require="dojo.io.IframeIO " />
> >
> > I'm using it inside a Facelet component inside a RichFaces tab. It gets
> > rendered depending on user role. If it gets rendered at page load time
> > there's no problem, but it won't work if it doesn't :-\
> >
> > Is there any way to hard code something like "ya, dojo, initialize
> > yourself?" (well, you know, to tell dojo to initialize). Maybe
> > dojoInitializer uses addOnLoad and it doesn't get called...
> >
> >
> >
> No add onLoad is used,
> but... I assume something dojo like is called outside of your tabs. I
> assume you have handcoded some javascripts calling dojo, otherwise the
> initializer would not bee needed.
>
>
> Following push the initializer outside of your tab and render it all the
> time.
> All the initializer in your case does is to render dojo.require(...
> statements at the correct code positions)
>
> See if that helps your problem.
> If speed is a concern you always can turn off the dojo tag parsing this
> should improve page rendering times by the factor of two, but adds the
> burdent hat you have to declare your dojo components programmatically
> instead of the dojo tags.
>
> <t:dojoInitializer parseWidgets="false" searchIds="[]" />
>
> this turns off the dojo parsing entirely...
> (if you have a handful of tags with fixed ids you always can add them
> via searchIds...)
>
>
>
>


-- 
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl

Re: t:dojoInitializer djConfig.baseScriptUri has no properties

[Werner Punz <we...@gmail.com>]

Juan Ignacio Sánchez Lara schrieb:
> This is just the beginning:
> 
> <
> 
> a4j:outputPanel ajaxRendered="true" >
> 
> <f:verbatim>
> 
> <t:dojoInitializer require= "dojo.io.*" />
> 
> <t:dojoInitializer require="dojo.io.IframeIO " />
>  
> I'm using it inside a Facelet component inside a RichFaces tab. It gets
> rendered depending on user role. If it gets rendered at page load time
> there's no problem, but it won't work if it doesn't :-\
>  
> Is there any way to hard code something like "ya, dojo, initialize
> yourself?" (well, you know, to tell dojo to initialize). Maybe
> dojoInitializer uses addOnLoad and it doesn't get called...
>  
> 
> 
No add onLoad is used,
but... I assume something dojo like is called outside of your tabs. I
assume you have handcoded some javascripts calling dojo, otherwise the
initializer would not bee needed.


Following push the initializer outside of your tab and render it all the
time.
All the initializer in your case does is to render dojo.require(...
statements at the correct code positions)

See if that helps your problem.
If speed is a concern you always can turn off the dojo tag parsing this
should improve page rendering times by the factor of two, but adds the
burdent hat you have to declare your dojo components programmatically
instead of the dojo tags.

<t:dojoInitializer parseWidgets="false" searchIds="[]" />

this turns off the dojo parsing entirely...
(if you have a handful of tags with fixed ids you always can add them
via searchIds...)

Re: t:dojoInitializer djConfig.baseScriptUri has no properties

[Juan Ignacio Sánchez Lara <ju...@gmail.com>]

This is just the beginning:

<a4j:outputPanel ajaxRendered="true">

<f:verbatim>

<t:dojoInitializer require="dojo.io.*" />

<t:dojoInitializer require="dojo.io.IframeIO" />

I'm using it inside a Facelet component inside a RichFaces tab. It gets
rendered depending on user role. If it gets rendered at page load time
there's no problem, but it won't work if it doesn't :-\

Is there any way to hard code something like "ya, dojo, initialize
yourself?" (well, you know, to tell dojo to initialize). Maybe
dojoInitializer uses addOnLoad and it doesn't get called...




On 6/20/07, Werner Punz <we...@gmail.com> wrote:
>
> Juan Ignacio Sánchez Lara schrieb:
> > At the documentation of t:dojoInitializer there's no comment on
> > baseScriptUri, but Javascript throws "djConfig.baseScriptUri has no
> > properties". Must I set it? What value to?
> >
> This is hard to tell, can you post one of your jsf pages
> (the source code not the rendered code)
>
>


-- 
Juan Ignacio Sánchez Lara
Ingeniero Informático + Técnico de Sistemas

Diario: http://juanignaciosl.blogspot.com
Ideas + Ingeniería del Software: http://iiso.blogspot.com/

Fotos (todas): http://www.flickr.com/photos/juanignaciosl
Fotos (selección): http://jpgmag.com/people/juanignaciosl

Re: t:dojoInitializer djConfig.baseScriptUri has no properties

[Werner Punz <we...@gmail.com>]

Juan Ignacio Sánchez Lara schrieb:
> At the documentation of t:dojoInitializer there's no comment on
> baseScriptUri, but Javascript throws "djConfig.baseScriptUri has no
> properties". Must I set it? What value to?
> 
This is hard to tell, can you post one of your jsf pages
(the source code not the rendered code)