On 12.01.2013 16:02, Mark A. Hershberger wrote: > On 01/12/2013 09:32 AM, Matthew Flaschen wrote: >> Last I heard, significant progress was made on 2.0, but the project is >> currently on hold. Thus, there's not a need to notify people right >> away. When the time comes, I don't think initial migration will be >> overly complicated, because the existing syntax has a clear mapping to >> the new one. > > Clear mapping or no, it is a change and the old Gadget 1.0 pages will > cease to work unless the people integrating ContentHandler make > backwards compatibility a priority. > > That will cause problems throughout wikidom.
Changing the way something is represented always causes compatibility issues. But that's a problem of the respective application (read: MediaWiki Extension), not the framework. Of any by itself, ContentHandler does not change anything about how Gadgets are defined or stored. It just *allows* for new ways of storing gadget definitions. If the Gadget extension starts to use the new way, it needs to worry about b/c. The ContentHandler framework provides support for this by recording the content model and, separately, the serialization format for every revision of a page (at last if $wgContentHandlerUseDB is turned on). So: The introduction of ContentHandler doesn't mean anything for Gadgets. The migration from Gadget 1.0 to 2.0 does. -- daniel _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
