Interesting resource

Interesting resource

by Tim Hunt -
Number of replies: 7
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

Ages ago, I remember Stuart Lamour starting a thread saying more or less "Do we need to depend on a JS library at all?" In the same vein I just saw this http://youmightnotneedjquery.com and thought folks here might be interested.

Seems like http://youmightnotneedyui.com does not exist yet, but the same point applies.

Average of ratings: Useful (6)
In reply to Tim Hunt

Re: Interesting resource

by Mary Evans -

Oh this is interesting Tim. Thanks for posting.

I know next to nothing about JavaScript and even less about jQuery, but this makes it all look really easy.

Thanks

Mary

Average of ratings: Useful (1)
In reply to Tim Hunt

Re: Interesting resource

by Julian Ridden -

Thanks for sharing Tim. Interesting read.

I do worry about cross browser support with what they are suggesting. But I guess no matter what you use that is always an issue.

Julian

In reply to Tim Hunt

Re: Interesting resource

by Urs Hunkler -
Picture of Core developers

When I had read the article I thought the aspect of loading huge libraries might be interesting for Moodle.

With more and more people being aware that less JavaScript is better than more is there a discussion at Moodle HQ or somewhere about the amount of JavaScript transferred and initialized in the browser to get Moodle working? The tendency in Moodle I see seams to be not to care about the amount of data. With the decision to load "simpleyui" as the default huge parts of the library are loaded by default. And with the decision to include jQuery it is easy to add an additional library which does basically the same as YUI but offers much more solutions because it is wider used.

I know that these decisions have been made due to common demand. But when we think about mobile use with less bandwidth and less powerful devices these decisions may need to be rethought.

It would be interesting to hear from the front-end team if they see JavaScript (and CSS) use as it is now as an issue and if so if they have started to think about possible solutions.

In reply to Urs Hunkler

Re: Interesting resource

by David Scotson -
I'm not sure what the frontend team has planned, but I've been tracking my ideas for smaller CSS here in MDL-39094 (and child bugs).

I also think there's some of the javascript that gets loaded on every page that could be replaced with smaller CSS, though I've not written that up yet.
In reply to Tim Hunt

Re: Interesting resource

by David Scotson -
That's the second link youve shared recently about how simple and exciting modern web development is if you don't have to support IE8.

I'm beginning to think you're teasing us!

Oh well, gives us something to look forward to I suppose.
In reply to David Scotson

Re: Interesting resource

by Urs Hunkler -
Picture of Core developers

When looking at desktop browsers the situation gets better.

But Scott Jehl's (Filament Group) Tweet shows that the browser issues never end - Android browsers are the new IEs:

 

In reply to Urs Hunkler

Re: Interesting resource

by Bob Puffer -

If I wanted to maximize my resources on such a project I'd force them to Chrome.