|Nicolas Lenz 2f25bc2663 Update 'README.md'||1 month ago|
|README.md||1 month ago|
Targets that should be possible do realize using the language
Point being: The UI descriptions should be general enough to target a wide range of devices at once.
The actual interface is described on a meta level using general terms like
form, which can be translated to fitting widgets and elements depending on the target and the theme.
E.g.: A text field is displayed on Android as a text field with the prompt inside and on desktops as a text field with label.
It should also be possible to generate forms and the likes from data types.
Things to figure out:
The goal is to have a tool to create UIs for a wide range of devices with minimal effort in a declarative way. Themes make it possible to choose the look and feel of the results. Custom themes allow to fine tune the results.
But if you want to create UIs with advanced features and fine-tune the results for the devices it is used on, you’re probably better off using the native toolkits available or some of the other, more powerful, but also more complicated, cross-platform technologies.
Also, if you want a customized and uniform look, you’re probably better off using some HTML- and CSS-based technology.
In short, the objective is to create some kind of Pandoc for GUIs. You can use a simple language to generate all sorts of outputs, even in complicated platforms, all looking great and containing the content you specified, but if you need fine-tuning and advanced features you might be better off using the target platform directly.