https://bugzilla.wikimedia.org/show_bug.cgi?id=37992
--- Comment #45 from Kunal Mehta (Legoktm) <[email protected]> --- I'm not sure this is should be discussed on this bug but... (In reply to comment #44) > Just a quick note, in case people are pushing hard on getting this done so it > can be used for VisualEditor, it's not the direction we're looking at taking > for VE. Thanks for the comment. Really I'm just trying to get this extension to not suck ;-) > * We would need something that lets us persist VE linear-models, or at least > Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of > computation, slowing clients down and adding to burdens on the cluster; until > server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere > really > appropriate for this to be saved for the Drafts extension to implement, which > is currently wikitext-based) Technically Drafts is set up to store anything that is text based, and I think HTML+RDFa can be serialized into text (or is already text)? We might need to add a column for contentmodel in the drafts db schema though... > * We would want (but not strictly /need/) something very flexible, so we > could > persist undo stacks, etc. which could add a huge amount of complexity to the > Drafts extension for just one use case/client. Ideally the Drafts extension would also have some kind of history/undo, but this is kind of a slippery slope and at some point you end up with essentially private user sandboxes. > > Though I think that the Drafts extension could be useful for wikitext users, > I > don't think it's right for VisualEditor; see bug 55370 for VisualEditor's > take. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
