[xwiki-devs] [VOTE] Disable (hide) the xwiki/1.0 syntax
Hi devs, It's been a (long) while since the introduction of the xwiki/2.0 syntax and the new rendering engine (introduced in 1.5, declared "usable" in 1.8, set as default in 1.9). This means that since ~2008, most of the development and maintenance effort has gone into the new rendering engine and the new WYSIWYG, and this left the xwiki/1.0 syntax and old WYSIWYG editor mostly unmaintained. All the platform and XE documents have been migrated away, but there are still XEM documents using the old syntax. I'm proposing to hide the xwiki/1.0 syntax by default, so that it's no longer easy to create a new document in that syntax (unless a template is used) or to select it as the new syntax for an existing document. It will continue to be available for existing documents. +1 from me. (I guess the 72h rule won't be applied since the next 72 hours are holidays for lots of developers) -- Sergiu Dumitriu http://purl.org/net/sergiu/
If you are talking about removing it from xwiki.rendering.syntaxes in xwiki.cfg by default. +1
On 03/30/2013 04:07 PM, Denis Gervalle wrote:
If you are talking about removing it from xwiki.rendering.syntaxes in xwiki.cfg by default. +1
Yes, xwiki.rendering.syntaxes + remove the hardcoded special case from Panels.DocumentInformation. -- Sergiu Dumitriu http://purl.org/net/sergiu
+1 Thanks, Caleb On 03/30/2013 02:40 PM, Sergiu Dumitriu wrote:
Hi devs,
It's been a (long) while since the introduction of the xwiki/2.0 syntax and the new rendering engine (introduced in 1.5, declared "usable" in 1.8, set as default in 1.9). This means that since ~2008, most of the development and maintenance effort has gone into the new rendering engine and the new WYSIWYG, and this left the xwiki/1.0 syntax and old WYSIWYG editor mostly unmaintained.
All the platform and XE documents have been migrated away, but there are still XEM documents using the old syntax.
I'm proposing to hide the xwiki/1.0 syntax by default, so that it's no longer easy to create a new document in that syntax (unless a template is used) or to select it as the new syntax for an existing document. It will continue to be available for existing documents.
+1 from me.
(I guess the 72h rule won't be applied since the next 72 hours are holidays for lots of developers)
On Mar 30, 2013, at 7:40 PM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
It's been a (long) while since the introduction of the xwiki/2.0 syntax and the new rendering engine (introduced in 1.5, declared "usable" in 1.8, set as default in 1.9). This means that since ~2008, most of the development and maintenance effort has gone into the new rendering engine and the new WYSIWYG, and this left the xwiki/1.0 syntax and old WYSIWYG editor mostly unmaintained.
All the platform and XE documents have been migrated away, but there are still XEM documents using the old syntax.
I'm proposing to hide the xwiki/1.0 syntax by default, so that it's no longer easy to create a new document in that syntax (unless a template is used) or to select it as the new syntax for an existing document. It will continue to be available for existing documents.
+1 from me.
(I guess the 72h rule won't be applied since the next 72 hours are holidays for lots of developers)
AFAIK the good part is that even if an extension uses xwiki/1.0 syntax it'll still work since the xwiki.rendering.syntaxes property only controls the list of syntaxes listed when editing a page. Thus to summarize: * users will not be able to create new pages in xwiki/1.0 syntax * existing apps will not fail If I'm not wrong then it's great and +1 from me. Thanks -Vincent
+1 On Sat, Mar 30, 2013 at 7:40 PM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
It's been a (long) while since the introduction of the xwiki/2.0 syntax and the new rendering engine (introduced in 1.5, declared "usable" in 1.8, set as default in 1.9). This means that since ~2008, most of the development and maintenance effort has gone into the new rendering engine and the new WYSIWYG, and this left the xwiki/1.0 syntax and old WYSIWYG editor mostly unmaintained.
All the platform and XE documents have been migrated away, but there are still XEM documents using the old syntax.
I'm proposing to hide the xwiki/1.0 syntax by default, so that it's no longer easy to create a new document in that syntax (unless a template is used) or to select it as the new syntax for an existing document. It will continue to be available for existing documents.
+1 from me.
(I guess the 72h rule won't be applied since the next 72 hours are holidays for lots of developers) -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 Thanks, Marius On Sat, Mar 30, 2013 at 8:40 PM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
It's been a (long) while since the introduction of the xwiki/2.0 syntax and the new rendering engine (introduced in 1.5, declared "usable" in 1.8, set as default in 1.9). This means that since ~2008, most of the development and maintenance effort has gone into the new rendering engine and the new WYSIWYG, and this left the xwiki/1.0 syntax and old WYSIWYG editor mostly unmaintained.
All the platform and XE documents have been migrated away, but there are still XEM documents using the old syntax.
I'm proposing to hide the xwiki/1.0 syntax by default, so that it's no longer easy to create a new document in that syntax (unless a template is used) or to select it as the new syntax for an existing document. It will continue to be available for existing documents.
+1 from me.
(I guess the 72h rule won't be applied since the next 72 hours are holidays for lots of developers) -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (7)
-
Caleb James DeLisle -
Denis Gervalle -
Marius Dumitru Florea -
Sergiu Dumitriu -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol