31 ms·
Almost impossible in an automated fashion. You can extract all of the data but it's very hard to know what links are supposed to do, how pieces of content shou
by nkozyra 12y ago
Almost impossible in an automated fashion.
You can extract all of the data but it's very hard to know what links are supposed to do, how pieces of content should be presented, etc.
- krrishd 12y agoWhat if there was a standard created for the markup, so that the parser would know what the links were supposed to do and how the content shoud be presented, because there would be structured data everywhere specific to the parser?
- nkozyra 12y agoI immediately thought about that after posting, but in reality markup is a clunky and expensive way to dictate this and it would create a lot of waste for something that would be used infrequently. An interesting idea that comes to mind is the concept of a Mobile Stylesheet / .mss file that would define elements by ID / class and dictate what those elements would represent in a mobile UI. Then you wouldn't have a bunch of needless data-mobile-intent="blah"
- krrishd 12y agoThat does sound like a good idea, definitely preferable to keep the markup a bit cleaner. Honestly, I don't know if I care as much for a web-view based product, as Phonegap/Cordova have already been serving that purpose (at least for me), but what you've mentioned, if implemented, would definitely be something I'd use.