Hi Francis,

I've been working off and on with the betas for a year.

When you say the model is not VFP-compatible, what do you mean, other than the old menuing and floating forms model, which doesn't work in touch devices?

Although you can in fact do menus, and you can in fact do forms: it's just not what Lianja is about: it's about bringing a VFP application to the place where modern users reside. Just saw a graph today of how much internet usage is being affected: in India, desktop usage now equals smartdevice usage, or to put it another way, smartdevice usage is rising sharply, computer usage is dropping sharply. The same trend is present worldwide, just a bit more slowly. So Lianja is addressing the need to write one application that can run on the desktop, while also running these other places.

In our case, over the 10 years our flagship app (retail inventory management, selling in Tier 2, with growth in Tier 1), we have seen our forms go from related tabs to one-to-many's and finally to single ui surface forms with hyperlinks on the right. And that was before we saw Lianja, which has an (optional) right sidebar, just for that purpose. We were responding to our customer's usage patterns and experiences, without a theoretical thought in sight, fwiw.

So let me know what you mean, and I'll let you know my experience in the betas (in which the product is getting better and better in response to user feedback). It may not be what you are looking for, but at least I can tell you what it is and isn't.

Hank

>Accord to their website, it looks like Lianja is getting near its 1.0 release.
>
>http://www.lianja.com/resources/roadmap
>
>As everyone knows 1.0 release can mean differents things to different people. But it is always a meaningful moment in a project history.
>
>I am in no situation to evaluate the product from their sheet. Since they are pushing for quite a distinct UI model. However as a VFP-addict moving to python (and quite comfortably so) I am quite interested in getting feedback on their stuff by those of you who spent the time to make a full eval.
>
>Especially interested in a possible feedback on their UI paradigm, The model is certainly not VFP-compatible.
>
>Any input welcome
>
>François