Manual:JS/API/UI Extension Developer Library

From MediaWiki.org
(Redirected from JEDL)
Jump to: navigation, search
shortcut: JEDL
This is the storage place of a book (collection of pages). You can load it from here, generate a PDF, let a book printed, edit it or otherwise update its content. Be reminded that when overwriting this book storage page with an updated version of the book, the previously assigned categories are not automatically copied to the recent version: you need to manually copy the categories from the former version. (Problem has been filed as enhancement request 27952)
JS/API/UI Extension Developer Library
Monobook icon.svg
This is a MediaWiki book, a collection of MediaWiki articles that can be easily saved, rendered electronically, and ordered as a printed book. For information and help on MediaWiki books in general, see Help:Books (general tips) and WikiProject Wikipedia-Books (questions and assistance).
PDF ]  [ epub ]  [ ODT ]  [ ZIM ]

Open in Book Creator ]  [ Order Printed Book ]

[ About ] [ FAQ ] [ Feedback ] [ Help ] [ WikiProject ] [ Recent Changes ]


The JS/API/UI Extension Developer Library (JEDL) is a collection of pages on the MediaWiki.org website which can help developers in regards to using JavaScript (JS) within MediaWiki, MediaWiki's Application Programming Interface (API) and MediaWiki's User Interface (UI).

We expect that this will be especially useful for gadget authors — those people who extend Wikipedia and other MediaWiki sites primarily through Javascript.

JS/API/UI Extension Developer Resources[edit | edit source]

API
ResourceLoader
Origins
Requirements
Migration guide for users
Default modules
Developing with ResourceLoader
Migration guide for extension developers
JavaScript Deprecations
List of JavaScript Deprecations
Vocabulary
Version 1 Design Specification
Version 2 Design Specification
List of ResourceLoader-compatible extensions
GlobalFunctions.php
CSS

Help desk[edit | edit source]

Contents

Thread titleRepliesLast modified
Best practice? Offer possibility of auto-reporting errors303:07, 20 March 2012
Intro?314:22, 19 March 2012
What else should we add?217:51, 9 March 2012

Best practice? Offer possibility of auto-reporting errors

I think what User:Rillke has done here -- offering the user a way to automatically report errors -- should be considered a best practice and documented more thoroughly here.

MarkAHershberger(talk)21:22, 19 March 2012

User:Rillke also pointed me to w:de:Wikipedia:Technik/Skin/JS which has lots of helpful pointers.

MarkAHershberger(talk)21:46, 19 March 2012

On Polish wikipedia there is also this:

Helder03:07, 20 March 2012
 

And here is a request to have some sort of error reporting added to RL core.

MarkAHershberger(talk)22:59, 19 March 2012
 

I think this needs a small introductory text, perhaps defining the scope, target audience, etc. Right now it feels like merely a collection of related resources and doesn't make it clear what goal it aims to assist (maybe a few examples would help).

For instance, MAH called it "documentation for gadget authors" in the message he left me on my user page; that's a good start, I believe, but I guess it might be useful for other audiences and purposes as well.

Waldir (talk)18:53, 14 March 2012

Thanks for pointing this out!

MarkAHershberger(talk)19:34, 14 March 2012

Is the above a fair start?

Varnent (talk)18:40, 18 March 2012

I appreciate it. I've added a little bit more about the intended audience.

MarkAHershberger(talk)14:22, 19 March 2012
 
 
 

What else should we add?

What else is needed here? What should we add?

MarkAHershberger(talk)02:07, 9 March 2012

Maybe a simpler name or a shortcut? ;-)

Helder16:53, 9 March 2012

JEDL is the shortcut.

MarkAHershberger(talk)17:51, 9 March 2012