On 2005-03-16, Felix Breuer <[EMAIL PROTECTED]> wrote: > If I get you correctly the conceptual difference between Edje and Vis > is, that Vis > > 1) defines semantics for standard variables/types/signals an app might > want to expose > 2) builds upon this definition to autogenerate UIs. > > So, to clarify the difference, Vis might be a tool that defines a > standard for Edje interface definitions and generates Edje "themes" from > a conforming interface definition.
Vis would be the framework consistent of the high-level API, standard "accessible" names, and a set of UI backends. One of these backends could use something like Edje as the final phase of generating the UI. > (I know you have a more sophisticated interface definition language > and you wouldn't want to generate Edje "themes".) I don't really have a language, just a simple API (in Lua in the paper). Different UI backends could use whatever language they deem most fit for fine-tuning "stylesheets" specific to that type of UI. -- Tuomo
