Hi all, perhaps concerning the pilCon tomorrow or next times, if it's of general interest:
what about talking a bit about how to use HTML5/CSS3 in picolisp apps? Topics, which may come into mind: - where to add the functions for new html elements? - how to safeguard that non-css-aware browsers will still render a useful gui -- how to detect capabilities of browser? -- if some detection would work, where to put the switch for the fallback solution? Imagine the e.g. <grid> function which is provided by xhtml.l at the moment (is it really? I did not check). If one would code another <grid> function, which prints out html5+css3 stuff with same optical result: Where or how to put the latter <grid> function, so that the app GUI pages - are rendered with responsive, flexible elements in html5+css3-capable browsers - and still are rendered as tables for lynx and other non-firefox-nor-chrome-based browsers Another point (might be more out of personal interest): I would prefer to distinguish between picolisp functions, which simply print a html-tag and those, which introduce different behaviour, e.g. <table> in xhtml.l(?) is not simply printing <table>.... but handles the <row> functions in picolisp code. When using HTML5 I would not like to look into a (let's say newly created) html5.l file, if <menu> is the semantic tag of html5 or the Picolisp function which does a lot more useful settings. What would be the picolisp'ish way of naming functions, which belong to a certain group or category? What about h5:table besides <table> and h5:menu (semantic html5 tag) in opposite to <menu> (picolisp dropdown workhorse)? (Does'nt prefix':' (as in ht:Prin) stand for sth special and should not be used here?) I would be glad to hear advices and opinions. Kind Regards, Olaf -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
