Lianja MetaDataBuilder API

[barrymavin]

The metadata is only applied at development time.

Web and mobile apps are generated based in the attributes of the app at the time of code generation.

You can write your own script that opens each app that you want regenerated. You have access to this with Lianja.openApp().

And you also have the ability to write your own extensions in whatever supported language you want.

[barrymavin]

Hi Tek Hong

It's all described in the draft specification.

It all magically happens when a table is bound to a section.

MetaData will be available for the database, table and columns. The whole point of metadata is that you can code key/value pairs up in whatever way you want. Lianja doesn't care. It just calls the procs to process and apply the metadata key/value pairs to a UI element.

[phabio]

The metadata is only applied at development time.

Web and mobile apps are generated based in the attributes of the app at the time of code generation.

You can write your own script that opens each app that you want regenerated. You have access to this with Lianja.openApp().

And you also have the ability to write your own extensions in whatever supported language you want.

Ok, Barry, with Lianja.openApp() it's ok..

thanks

[barrymavin]

The development of the Lianja MetaDataBuilder API has now been completed and will be available in the next release.

[tekhong]

Hi Barry

Thanks! Best Christmas present for a lot of us!

Best Regards

[barrymavin]

As well as the new MetaDataBuilder API (for databases, tables and columns), v2.1 will include a graphical "Meta Type Editor" and support user defined meta types as described in the roadmap for v2.1.

• Added a new attribute called "Meta Types" in the app, page, section, and formitem attributes. This should be a comma separated list of typenames. You create "Meta Types" using the new "Meta Type Editor" in the "Apps" workspace or the "Projects" workspace. Additionally, in the App settings there is a new attribute "Meta Types Table" where the meta types are read from and applied to the App when it is loaded. For example, based on the meta types specified for a section you could set its header and footer menus and the delegate that handles actions performed on these menus. You can reference this attribute using the name metatypes.

This adheres to the Lianja App Builder core philosophy of declarative device-independent UI building but provides the ability to inherit common appearance and behavior without needing to set individual attributes for each UI element, resulting in increased developer productivity and more rapid application development.

[tekhong]

HI Barry

Would this be similar to providing a means to the developer to extend the standard app, page, section, form item attributes to include additional user defined attributes?

Your advice is much apprciated

Thanks & Best Regards

[barrymavin]

Hi Tek Hong

Please read the last post of this thread.

[barrymavin]

If my understanding of your question is correct...

You can do that already for a long time using addProperty(). This adds a new attribute and prefixes it with user_ internally.

Any attributes that you set that are prefixed with user_ are user defined.