>Hi Srdjan,
>
>>mostly non visual foxpro stuff kept in prg files.
>
>PRgs can contain visual code, as well. To convert an existing form into a PRG, you can use Arto's ClassBrowserX extension that is available from VFPX. For me the reason to start with FXPs was because they are easier to parse.
>
>> >Does it mean that your goal is to eventually execute entire VFP app or exe file as it is, including GUI elements
>
>The goal is to be able to turn a project into an EXE or something else that can be executed with Guineu. It might be the APP file or a different format that is better suited.
>
>> and reports ?
>
>Much later... In the first stage I implement those features that are needed to run VFP applications on Windows Mobile and PocketPCs.

Sounds great :)
I know that you can turn forms into code or define them completely in code
at first place. Just tought then you would naturally start with 'simpler'
(nothing simple2ME here <g>) tasks like data handling, string manipulation functions etc which is normally kept in prg/fxp files, and then gradually move to OOP gui stuf reports etc. But as you explained it is readability of fxp format which matter in this case.
I saw that you don't support (data)Session object yet. Is that in short or long term plans? Please don't undermine this particular object.
Makes things really nice/easy/clean when it comes to dealing with meny tables in code. I could not personally leave without that one :)

As you correctly prioritised ;
GUI/reporting people naturally change/redo all the time (almost like clothes<g>) ; but having core data handling features of VFP implemented solid/stable/1:1 would be imho something as important as pair of lungs!
That is If we are talking about full conversions some time in future.
I never built PDA/Mobile apps so I can't talk about that, but perhaps
much less is needed.

By all means great & brave development / All the best :)
Srdjan