Wondering about LC and HTML5

Pierre Sahores psahores at free.fr
Tue Jun 21 13:26:45 EDT 2011


I just have to follow Richard, Andre, ... on this.

The way i implement HTML5/CSS3/JS in my LC-server driven apps is not really complex at all and no far from funny to the end, something in between the feelings we had, as kids, in playing Lego and Meccano :D

I use HTML templates build on top of, in between other possible choices, the very simple to learn "Fluid 960GS" HTML/CSS/JQuery template framework :


About CSS, i use the CSSEdit 2 editor (Mac only) available there :


and the Stylizer app (Mac only) when i find on the web an interesting HTML/CSS template i want to learn about :


To the end, the LC-server xtalk code handle 95% of the final app logic and we just need to care about HTML/CSS/JS for the last 5%, and best, full reusable from an app to an other.

I don't think that having LC handling those 5% would help us at all, because the collision's troubles we could get in this way because HTMLText, Unicode glichies and more.

Just put the hand inside alike the first time you did with (wind)surfing or bicycle... The first steep will be a little unfriendly but after a week you will like to save lots of time in combining the power of LC with the primitive ways HTML5/CSS3/JS can be handle ;-)

Do you know that Danny Goodman is a long time Javascript unconditional fan ?



Le 21 juin 2011 à 17:14, Richard Gaskin a écrit :

> That said, one of the most useful things about CSS, JS, and HTML is that they're all just plain text, and LiveCode is unusually adept and manipulating text.
> I've ported some LiveCode apps to the web, and with new versions of my WebMerge product I'm expanding on those systems quite a bit.
> But I don't attempt to translate code.  Too much work.  There are so many great resources for learning JavaScript, and the language itself is reasonably sensible and kinda fun to use, that translation carries a very low ROI (usually negative).
> In the 21st century, not learning JavaScript is IMNSHO the biggest mistake any software consultant can make.  Given the ubiquity of the web, the fact that JavaScript is the only native language browsers provide, and the many millions being poured into enhancing its performance and capabilities by Apple, Microsoft, Google, and others, there's no reason not to become competent with it.
> Besides, as numerous studies show, learning new things keeps the mind nimble and helps prevent some of the cognitive effects of aging. :)
> So my own approach is very much like Andre's, using LiveCode for its GUI strengths but avoiding the tilting-at-windmills of language/object model translation.
> I've been advocating this model here for many years:
> <http://lists.runrev.com/pipermail/use-livecode/2006-June/083956.html>
> There's a lot that can be done with LiveCode to build toolkits to assist with production of web apps, but the client-side business logic and interactivity in those apps is best served by writing native JavaScript.
> It's not hard to learn, and it can be a lot of fun.  The tools and resources for learning it are completely free and widely available.

Pierre Sahores
mobile : (33) 6 03 95 77 70


More information about the Use-livecode mailing list