Lianja MetaDataBuilder API

[barrymavin]

Hi David,

Development tasks and expected availability are all added to the development roadmap.

Currently this is a draft specification which you should see in a forthcoming point release and the roadmap will be updated to reflect progress.

[avianmanagement]

Thanks Barry,

I will keep an eye on the roadmap as this is something that will be a really game changer.

[tekhong]

HI Barry

With the coming metadata API, would we be able to centrally setup the getdata and setdata mapping for FK fields in our app?

This will be a great time saver as my apps has 100's of tables and 100's of FKs and able to do this from metadata will ensures consistency across the entire app

Your advice is much appreciated

Thanks & Best Regards

[barrymavin]

Hi Tek Hong,

If the attribute is exposed you will be able to set it as per the specification document.

[tekhong]

Hi Barry

Sounds great!

Thanks & Best Regards

[HankFay]

Note that how this works (manual or automatic) depends entirely on what metadata is available (e.g., the List Fields, the FK Description, and the relations/indexes). Those then have to be "templated" to create the correct attribute/method values to make it work. That's what we have done for VPM. The same metadata will be used to create the appropriate Lianja JSON metadata.

I can envision there being more than one approach to this. That's the beauty of what Barry has done: he has opened the door to programmatic metadata use within the development environment. It's very elegant in its simplicity and power.

Hank

[barrymavin]

Hi Hank,

What I am intending to do is add a setAttribute() method to each UI object.

The reason for this is that the attribute you specify (first argument) and its value (second argument) will match what is in the .lianja file.

The will provide the ability to specify any of the attributes not just those exposed.

So as part of the MetaDataBuilder API their will be a table of attributes and what they affect.

[HankFay]

So as part of the MetaDataBuilder API their will be a table of attributes and what they affect.

I was just thinking about that Saturday, as I was hauling and sawing wood. "There needs to be an updated -- because new attributes pop up quite often -- list of attributes," said I to myself.

I'm glad you got the message. <s> I beamed it in your direction.

thanks,

Hank

[tekhong]

Hi Barry

Would the developer be able to execute global change of UI attribute by specifying the following

a) table name
b) field names
c) attribute name
d) new value for attribute

Your advice is much appreciated

Thanks & Best Regards

[phabio]

Hi Barry,
in your first post, you wrote:
When you create a new section by dragging a table onto a page (or opening an existing App) Lianja will layout the section, then if the script setupUI.prg exists in the App or setupUI_tablename exists in the database it will be called with the section id as the first parameter and the cursor for the table bound to that section will be current.

So, if I've 50-100 app for the same big project and I modify some metadata property, I need to re-open all app before deploy my project?

And is possible to make the changes at runtime or only in develop time?

thanks
Fabio