4 ms·
(I'm 1/3 of 280 North, btw) In Cappuccino each "view" object (CPView, CPButton, etc) has a DIV element as it's base, and other elements contained in that (usua
by tlrobinson 17y ago
(I'm 1/3 of 280 North, btw)
In Cappuccino each "view" object (CPView, CPButton, etc) has a DIV element as it's base, and other elements contained in that (usually just IMG, canvas/VML, or subviews' DIVs). We don't output HTML at all, but rather manipulate the DOM elements at runtime.
This sort of approach definitely makes sense for the kind of highly interactive applications Cappuccino is designed for, but maybe not for more "pagey" websites where you want search engines to be able to index it, etc.
- gord 17y agoabsolutely.. [Greets + Kudos, btw] But then so many 'web pages' now are really js apps, that google must effectively do screen scraping anyway... Perhaps we should just admit that we always need an alternate feed to provide semantic meaning [aka tags] to web crawlers/readers, and be done with it. Maybe a system where each widget can be queried for its textual content, via a standard simple API would mean all apps made with say Cappucino would be able to emit text to a crawler, without [too much] special code being written - the framework could do it? Running a JS program on the browser to generate the page should be a legit technique, even for pages that remain static thereafter. Have you had a look at RaphaelJS? [normalized SVG support via JS : allows JS to do flash-style animations with an open standard behind it].