The things that are not the most trivial are the most challenging and fun. I'd hate to wait for Parsoid - if anything this would help Parsoid by defining the needs of mediawiki's parser.
I would suggest starting with just extracting table of contents and section data into individual components... On Tue, Apr 23, 2013 at 12:27 PM, Daniel Friesen <[email protected]> wrote: > It's an interesting idea. Though it won't be trivial. But we could start to > express the parser output of pages as high level components nested in each > other. Like a document with a TOC nested in it, as well as high-level > headers (or maybe sections), emeded image frames, etc... where things like > the headers and image frames are components with their own rendering that > the skin could create components to replace the rendering for. And even > strip the component out of the page and put it somewhere else. > > Though it can't be a simple list of components since many of these things > have specific locations inside the content to go in. > > Then again. Ideas like this may just make VisualEditor/Parsoid harder. We > might want to come back to this once Parsoid is done with it's dom, etc... > > > On Tue, 23 Apr 2013 12:01:00 -0700, Jon Robson <[email protected]> wrote: > >> Daniel >> Great to hear I'm not alone in my thoughts. Things like the edit >> section link shouldn't have to be hacked in at the parser level - if >> the parser returned the components of a page it would be trivial for >> the skin to add these itself. >> >> The fact you are resorting to hacks to do things which should be >> trivial (the infoboxes is a great example) suggest that this is a >> smell that would be good to fix. >> >> I can't help but think of Wikipedia redefined [1] which had some >> interesting ideas that alas would be very hard to try out in the >> current setup. >> >> Another example I can give is in mobile is we render cleanup templates >> as an overlay as these can fill an entire mobile screen on certain >> articles making the content unreadable (very much against "a world in >> which every single human being can freely share in the sum of all >> knowledge." :)). We have had to add some javascript which collapses >> them but it would be great to have a better solution for >> non-javascript users (maybe hide the cleanup templates or put them at >> the bottom of the page and create a link to that at the top for those >> who need them) as currently this "a world in which every single human >> being" ... with javascript .. " can freely share in the sum of all >> knowledge." :) >> >> [1] http://www.wikipediaredefined.com/ > > > -- > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson http://jonrobson.me.uk @rakugojon _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
