>>>as Thomas implied, Lianja is a complete development and deployment stack.
>>>Mobile, e.g., uses a lot of open source components (boostrap, jQuery, jQueryMobile, etc.) and provides oData-based Ajax connections -- but you don't have to fiddle with those things. You design the app using components, write the code you need to provide special functions (business rules), and deploy (desktop, web, mobile). That doesn't mean it writes it for you :), but it sure beats having to learn the intricacies of the frameworks, and work around bugs in them (including QT), because Lianja already has.
>>>
>>>It's a different way of thinking about apps, to be sure, because it is aimed at today's world. PC use is declining, because people are using their phablets.
>>
>>
>>It is also half way a framework in the Meremortals, Promatrix sense, geared towards availability on many screen sizes and using different technology stacks with common or at least similar APIs. They created an architecture that makes sense to the changes in technology and their current customers. It is flexible enough for you to perhaps add/exchange parts that do not fit your use cases, but swimming upriver is always harder ;-)
>>
>>Eample: mobile data pattern is oData-based Ajax, which in my mind is nore often needed than reactive (in the Meteor database usage term, not Facebook "React" JS).
>>But there certainly are use cases where the Meteor approach is the better fit.
>>
>>@ Steve : Take a mental step back and analyze your architectural and technological needs. You know your customers and products best. Also check if any large customer might balk at something rather unknown as Lianja - which was one of the biggest reasons for me to put it on the back burner and deliver some Java/JS based stuff the last 2 years.
>
>did you do the project in Java/JS or did you link manage to link Java/JS to Foxpro? Thank you, Steve

On linking Java to vfp: we did it "traditionally" using a COM bridge. Google for JACOB. We also had another approach where the the Java runtime was hosted by the vfp exe
and calls were made in through a marshalling layer in C using JNI based on a Pascal based example - worked as well if not a littlt bit faster at least in a dummy approach, but the more often used COM approach was decided upon to be certain the project is not cut on a bleeding edge ;-)