Hi

I have grown to rather like javascript. I have been using the QooxDoo framework and I am building classes the same way I did in VFP in the sense that I am using OOP and have my own base classes in fact I am using all the same techniques I used in VFP such as delayed initiation so I only load the controls when the user activates the forms or the page in the pageFrame. I have added data binding in almost the same way I did in own VFP framework. I use the Chrome debugger now that I understand it and it works well. I have a command prompt to evaluate javascript.

I have added a screen shot of a project I am working on now so you can see what it looks like.

Simon


>Interesting discussion. I believe anyone that takes on a major web project is in trouble. The web is changing so fast and new tech
>is almost constant. Today we can say the HTML5 and javascript have a fighting chance to win the hearts and minds of programmers.
>But I'm not even sure of that. There has always been a cross over between the web techs (HTML, CSS, and JavaScript) and today several
>framework people have decided to transform the three into just one - 'JavaScript'. Will it be that javascript lib's will win the day? I don't
>know - but I can say - I hope not. Javascript as it stands today is a terrible language - specially for large projects. The only reason several companies have moved that direction is because it's already there in the web browser. Not because the language is eloquent.
>
>Google on the other hand has started an effort to replace the entire underlining of the web with "Dart". Of course to get others to accept
>the new way to program the web they have a hybird way of producing javascript. But their main goal is to replace all of the current web
>tech. There are others that have presented other protocols in similar efforts. I wish them well because I'll be very sad if javascript wins.
>
>Building for the web today (and all the new form factors and input methods) is like building on quicksand!
>
>Johnf