On 7/11/2011 5:28 PM, Thierry Nivelet wrote:
> All controls are supported right now except timer, toolbar and formset; the 3
> latter are just a matter of time to spend on developping support, no other
> issue involved.
>
> Timer will be supported, VFP timer() method executed when timer elapses on
> client browser.
>
> Pageframe is indeed supported, you even have options to raise active tab,
> fade/appear on page activate, change tab's CSS background, etc. The app I
> mentioned has a form with a 7-page pageframe, each page holding an editable
> grid.
>
> CSS .class {...} definitions are based on VFP classes hierarchy:
> commandbutton, awcmd, mycmd, myappcmd, etc. Each object is also defined by
> its ID : #cmdSave{top:...;left:...;etc.}
>
> This 'awDefault.css' file is generated by traversing all form in the app. It
> can be copy-pasted into app's CSS and overridden afterwards.
I am so strongly rooting for this. I can just see the jaw dropping of
the many who said we couldn't go to the web easily and thought we were
totally "stuck" with our FoxPro apps. Assuming this really works as
good as you say, this is some of the best FoxPro news I've heard...ever.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
http://fabmate.com
http://twitter.com/mbabcock16
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
