Hi Ralf,

> > As I wrote, you can. Have a look at "dojo.requireLocalization" [1,2].
> 
> I don't really get it. Do I need to add the dojo.requireLocalization()
> to my layer file for the build? And if so, which should be entered? All
> the stuff I am referring to in my layer?

Sorry, my fault.

"dojo.requireLocalization()" is used within a widget, which should support i18n.

Currently it looks like, that it isn't possible to also embed the localization 
into the layer. The argumentation seems to be, that Dojo wants to support every 
language. So the application knows only at runtime from the browser, which 
language is needed.

But it should be possible to merge the flattened NLS file into the layer on 
your own.


> > Check your "templateString" line...
> 
> Finally, that was the key hint to get the whole solution. In the
> GroupedFilteringSelect.js source file there were these two lines
> 
> templatePath:
> dojo.moduleUrl("interpersonal","GroupedFilteringSelect.html"),
> templateString: "",
> 
> When the build was created the templatePath line was converted to a
> templateString which included the content from the
> GroupedFilteringSelect.html file. So in MyApp.js I have to lines of
> "templateString". One with the content and one setting it to an empty
> string right afterwards.
> 
> So, all I did was deleting the <templateString: "",> line in the source
> and start the build again. Now in MyApp.js there was only one
> "templateString" line and the widget was shown again! Success! :-)

Seems like you started building your widgets with Dojo 1.3.x?
Take a look at 
http://dojotoolkit.org/reference-guide/releasenotes/1.4.html#dijit-templated

I don't know what your "GroupedFilteringSelect.html" is, I guess it is a 
template for a widget/control. I recommend to use the "new" dojo.cache().


-- 
Regards,
Thomas


Reply via email to