Perth Hackfest October 2012/AJAX: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) (copied session notes from google doc) |
(This page will not be migrated to new devdocs) |
||
Line 1: | Line 1: | ||
{{Template:WillNotMigrate}} | |||
Why keep YUI? | Why keep YUI? | ||
Latest revision as of 11:17, 23 May 2023
Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable. |
Why keep YUI?
- Important
- Lots of work to convert
- Cannot do piece by piece migration, need to convert everything at same time
- JQuery doesn’t have widgets that Moodle uses
- Has loader and dependency handlers
- Adding another AJAX framework would cause performance problems
- Lots of work to convert
- Not important
- Can be done inline with SimpleYUI
Why move away from YUI/Allow a second framework?
- Important
- JQuery easier for simple things
- YUI is massive to load
- Plugin developers are using JQuery
- Hard to theme
- Not important
- Hard to find YUI devs
- YUI is hard to learn
- Easier to find code examples/help with JQuery than YUI
- Requires greater JS understanding and we don’t have good documentation for it.
What needs to change?
- Better documentation
- Need to have plan to include/support JQuery
- Need policy
- No core code will use it. If you want something included in core you will need to convert it.
Forum thread on this discussion:
- https://moodle.org/mod/forum/discuss.php?d=211454
- Dear moodle, can we stop having the YUI lib yet?