- From: cr <_@whats-your.name>
- Date: Tue, 20 May 2014 12:34:21 +0000
- To: public-rww@w3.org
> Nice JS for UI (1) appears as a retro stop-motion animation of noticeable jaggy/chunkiness due to frame-dropping or so, on a 1ghz ULV notebook computer from 2008 with Xorg, Firefox and Intel GM965/GL960 Integrated Graphics (2) left pane became unscrollable, despite showing a scrollbar, maybe virtual, maybe browser-stock styled w/ CSS and and input-grab issue from the other 2 panes preventing rx'ing of scroll events? (3) sometimes, text is rendered to pixels (via <canvas> ?), causing it to be unselectable/copyable (4) after WM resized firefox for orthogonal popup, nothing short of Ctrl-R (and losing place/state) could convince it that the bottom half of the viewable area was there again - rendering squished tiny demo in the top half )!?( (5) text is unreadable due to hinting + quantization (?) issue, eg 'r' is just an umbrella, vertical portion is not there at all. this never happens on firefox so they must be doing something exotic with font handling that few are. XFT makes vertical portion dimmer if sub-1px, not invisible given that it's inevitable companies are going to try to woo users w/ slick effects, and many of these libraries have a take on writeback, and their authors have likely never read http://www.w3.org/2012/ldp/wiki/LDP_PATCH_Proposals or tried POSTing a Turtle file, and they will go ahead and accrue millions of users anyway.. then it'd be instructive to look at this pop-culture of libraries , how they are POST/PUT/PATCHing, and which offerings could be used for RDF minimally-modified, or how an arguably simpler + more-flexible solution can be presented as less-daunting and more mainstream - and even better - ie don't throw away library/client/server interopability and unforseen reuse/mashup in lieu of slicklibJS's ad-hoc modelSync methods hidden under that slick investor demo http://backbonejs.org/#Sync , and the like
Received on Tuesday, 20 May 2014 12:34:54 UTC