tchay wrote:

I wrote parseDescription() as more a test. I felt that editors who might be more comfortable writing a feature that might be complex (video embed, for example) would probably be more familiar with Wikitext so it'd be interesting to make it available.

I wrote getPageAsDescription() because I thought that it'd make sense to open the tours themselves (without opening the javascript hardware which needs to be locked behind a higher access control) to the community at large to allow them to be improved. This way we adopt the same security protocol that has already been put in mediawiki itself.

I believe that getPageAsDescription() while it generates a HTTP request to the server probably might be more efficient than parseDescription() in the long run since the parser cache should probably cache it avoiding the need of the parser to be triggered.

We should probably thinking of migrating the guided tour to Ori's JSON schema or something. It's awfully close. Right now it has to be javascript because we don't know what sort of auto-advance/etc. that our guided tours will actually have. Once a library of common use cases are made, we could abstract this into a javascript generator and allow the tours to be created in JSON schema without allowing arbitrary javascript injection (and thus the need to protect the tours namespace).