Lianja concept

a Lianja app is made up of pages.
Pages are made up of
sections of which their are many types, and
form sections are made up of
fields and gadgets.

if you want to hand code php you create your php files and specify them as the URL in either WebView sections or WebView gadgets.
You can write this server side code in whatever you like. It generates HTML/JavaScript and sends to the client which renders it.

If you are developing desktop applications you can write in Lianja/VFP, PHP, Python, JavaScript and in 3.1 typescript.
Each section or gadget can be written in a different scripting language which is specified in the attributes for the UI element.

PHP, Python, JavaScript and typescript are not database languages.
In Lianja however when you design a page/section you can
bind server side data to the UI elements contained within them.
There is
no need to write any server side CRUD code at all. It is all magically handled for you between the web client and the Lianja cloud server.
This reduces a large mount of development and later on, maintenance time.

The Visual Foxpro 9 core UI classes are available in Lianja for use from any of the supported scripting languages.
Take a look at lianjademo example app and you will see it has custom sections and WebView sections coded in Lianja/VFP, PHP, Python and JavaScript. All within the same app.

You visually design pages iteratively, laying them out as you see them in your mind.
customize their behavior using attributes and delegates.
You can specify validation, input masks, custom actions etc etc and
call either client side JavaScript code or server side Lianja/VFP or JavaScript code.
Server side php and python will be added in a future release as stated on the roadmap.

Note that the Lianja cloud server has its own implementation of Lianja/VFP embedded in it as well as support for any third party ODBC data source using virtual tables.
Additionally it has
googles v8 JavaScript engine embedded in it (same engine that node.js) uses.

Server side pages can currently be written in Lianja/VFP (.rsp) or JavaScript (.jssp).
These provide the
same functionality as .php pages with many extensions to simplify development.

So just to summarize, you don’t need to write oodles of php code to handle database CRUD operations as this is all handled by Lianja without the need to code anything.

The whole point of Lianja is to simplify the development and deployment of business applications and this is achieved cross platform and cross device by providing a common design and development philosophy which is…
Lianja Apps are made out of pages. Pages are built out of a wide range of sections and form sections out of formitems and gadgets.

you are using the standard sections and tying to customize them to fit what you are trying to accomplish.
It’s a valid approach. No doubt about that.

However, you may be relying too much on the no code aspect of Lianja, and not utilizing the custom code that sounds more appropriate to your needs.

Look at the developers guide for creating custom sections in VFP.…-visual-FoxPro

When you need the level of control you are looking for, I would suggest handling the majority of what you are looking to do with your own code.

There is an appropriate place for no code (drag and drop) and appropriate place for custom code.
Meaning – you do not use the action bar at the bottom of the page, but rather create your own custom canvas section to handle navigation.
you have done this before in VFP, so you know how to do it.

You can create your own grid, append it, filter it, delete from it and the behavior will be exactly as you want it to be.
Look at the Lianja example app called “Lianja Demo” look at the menu options “Custom” and then select VFP Custom Section” and “VFP Custom Gadget”
I think you should figure out what the core functionality of your application is, get that working, then see how you can hook into the features you like from the standard sections.

I would suggest that you create your own classes and subclass them. You can 100% do that in the custom code.

If you are looking to make sure this will run in the web, then I suggest you use the custom JavaScript sections and not the custom VFP sections.
While the custom JavaScript sections are not fully exposed in the webclient yet, they will be, so the investment makes sense.

I personally am combining RSP pages with standard sections, it’s what works for me.
Lianja is giving you many options, you just need to make sure you understand how each works so you mix them appropriately.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.