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

[Jesse Kuhnert]

Those are nice features I think. I guess I'm looking at it more like
if I had to stake Dojo's future on doing ~one~ thing really well out
of :

-) normal html
-) disabled javascript
-) mobile

I'd go with html. (i've never had much like with going to production
with the same content being served on mobile/normal browsers in an
intuitive way anyways - at least not if it's an application you expect
people to use in a mobile environment on a daily basis)

On 12/28/06, Jon Sykes <jon.sykes at media-hive.com> wrote:
<snipped>
> As a flip to that, I always liked the fact that Dojo widgets acted as
> a garnish to existing functional code.  It sits nicely with my
> progressive enhancement hat wearing.  I love the fact that you can
> build a functional web page that works in almost every browser, PDA,
> etc, and then add the flourishes and richness by add OOTB widgets or
> custom made widgets.
>
> If you start outputting full widget HTML and then worrying about
> degradation in browsers with no JS you run in issues where it won't
> degrade gracefully.
>
>
> Jon Sykes
>
>
>

-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com