>>Let's see, I have to put this in the JS, that in the HTML, and this other in the CSS. No thanks. I think I'll just drop a control on, and pick a CSS theme for the app, thank you. :)
> I have a business app to write.
>
>>I think systems fairly well. And I do not remember (as in "recall out of context") details well. So my approach is to design the system, write it, and then use it to create software.
>This is of necessity, not choice. The system >becomes my memory for details. :)
>
>>There are more folks like me then there are those who can merrily type away knowing what goes where on all the different documents. So my necessity can prove useful for others who share the need.
>
>>Beyond that, there is the problem of application mangement. This applies to everyone. "In what ways is Business Rule 3122 implemented?" That's a reasonable question, and actually one that needs
> to be able to be >answered without relying on memory. That's the next step. Once the Metadata API is implemented in Lianja (it's in QA) comes the Metadata Manager (by me). And then after that,
>the Business Rule Manager (which will >of course refer to the Metadata Manager data), also by me. When released they will be available in LianjaX, the Lianja open source git repository. Oh, yes:
>also the Lianja Git Manager (by me), which will solve the issue >of how to have a Library versioned with the apps that use the library, without using problematic submodules, and how to have
>developers who don't know git use it correctly.
>
>>re: data binding -- when Lianja creates a browser/mobile page, it injects a library that does all the binding. Guess what: oData. As simple as can be. Of course it's
>got all the plumbing built-in to handle updates, events, >etc., all done without typing a character.
>
>>I agree, fwiw, that Electron, Nodal, Susy and Typi, etc. are all great, all going in the right direction. If I had time for a hobby, I'd try to figure out a way to make them all "just work" without typing.
>
>>Hank
>
>Oh Hank you have hit my weak spot! Not only is it a pain dealing with three different files - they overlap! Almost everything I can do in CSS can be done in Javascript or HTML. HTML and Javascript overlap. So the question is - what file should I use to get the job done.
>
>You keep self-deprecating! I think what you really mean is you are like the rest of us - lazy! All programmers are lazy ! We invented cut and paste almost immediately! LOL! Think about the knowledge you now have and how you can get just write a few lines of code to get the job done.
>
>Bujsiness rules! This sounds like a plugin. Be careful - every plugin system I seen ends up being a security issue - think WordPress!
>
>Yes Data binding Data binding Data binding Data binding Data binding and of course Data binding!
>
>Johnf

Hi John,

no, not a plugin. The way metadata works in Lianja is that in development when an app is opened in the App Builder for development, a versioned routine (that you provide) is called that, working with the Lianja DOM (every app is a big xml file -- ready for PhoneGap, not by accident), attributes are set from the metadata (that you supply). All attributes for every object are accessible. So, everything is set in "code", but without one's typing. If an object/attribute needs to be skipped in a given UI instance, there are ad-hoc metadata properties that can be set for that purpose on each UI object (and used by your code).

When a Database opens in the App Builder, another routine is called (which the developer supplies) that can be used to modify the database (based on your code -- or in my case my code derived from xCase).

Data binding: good, good. (Get the reference to the "good" Bush president? <s>)

Yes, I am lazy. And my inabilities are real. I met a client back in the day who needed some work done. He wanted to know if I was going to write it right then: he had Les Pinter in his office 6 months before and that's what Les did. Les is on the opposite end of the spectrum.

Hank