[dojo-contributors] Re: Figuring out what Dojo needs to become. A few questions.

[Tom Trenka]

As long as we are clear about not tying it down to a specific tech, I'm more
than fine with it.  If we want to try to support something along the lines
of the way JSON is supported (i.e. many implementations available), I'm
definitely game.

And yes, JS itself should be supported as well; as I may or may not have
mentioned in the past, a good portion of my own JS chops came from
developing ASP code in JScript.

trt

On 12/28/06, Eugene Lazutkin <eugene at lazutkin.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tom Trenka wrote:
> >
> > 2. I will definitely block any attempt to lock Dojo down to a specific
> > server language or application; I know you're only mentioning the
> > possibility here but this is something that is *extremely* important.
>
> Agreed. But in my opinion Dojo *has to have* special provisions for
> integration with a server side. I am not talking about any specific
> server side framework/app, but about the approach in general.
>
> For example the calendar (DatePicker) widget has pretty elaborate visual
> implementation, which is initialized dynamically (when the page has
> loaded). Why? It would be much better to generate all necessary HTML for
> it on the server in a proper state showing an exact date: 12/28/2006. It
> will cut down on initialization time, user will see the result much
> earlier, and it will prevent flickering. Right now there is no way to do
> it because:
>
> 1) It is unpublished what HTML should be generated for any specific state.
> 2) There is no way to tell a widget to skip unnecessary visual
> initialization and to use a preinitialized HTML fragment.
>
> #1 can be deduced from templates and/or initialization code. #2 is not
> supported by the existing Dojo widget system (but you can create your
> own widgets supporting this concept somehow).
>
> To sum it up --- lets make life easier for server-side guys helping them
> to create integrated systems with Dojo. It will improve Dojo-based
> applications and help us all. Obviously while doing so we have to be
> server-side agnostic.
>
> Yes, I know that splitting a rendering code across languages and
> platforms may introduce synchronization issues, but to me this is a
> technical detail. It would be better (but not necessary), if widgets
> came with a reference server-side "renderer", which is just a simple
> function that takes necessary widget parameters, and produces an HTML
> string, which corresponds to these parameters. Such renderers could be
> provided for most popular server-side languages like Python, Java, PHP,
> Perl, and, dare I say?, JavaScript. Obviously such code should be a part
> of some specialized Dojo subproject, which aims to cover all frameworks
> written in its language, e.g., Dojo-Python integration library can cover
> Django, TurboGears, Pylons, and myriads of other Python-based frameworks.
>
> Thanks,
>
> Eugene
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFk/h1Y214tZwSfCsRAtgoAJ9KkxGLmm2dXN5kH6ZyoSYvqJ2GkQCgyo0+
> VrQ/S2LWqnizmyqze/NlC1o=
> =PCHh
> -----END PGP SIGNATURE-----
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-contributors
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20061228/ef590536/attachment.htm