Hello everyone, Already miss you all! (besides Jack and hedsy :) ) After meetings in HQ, I updated UI format description and you can take a look on it.
I've not fully switched to interfaces yet, so some points could be not relevant. Please correct. You can find it here: https://phab.enlightenment.org/w/ui_builders_format/ Further I add issues/questions which are not very clear and require help of world brain :) I'm sure this is not all the problems I could think about, so add yours... Let's go: * Brackets to use for parameter values, *[] or ()*: size=[100, 100], size = (100, 100) * All widgets - are they Elm Widgets only or optional namespace attribute can be provided: i.e. Image (namespace="Evas") * How to describe translatable text * During our meeting someone mentioned that comments will be objects... and comments can be added as properties to objects. What does it mean? * Should we use "pack" implicitly for Windows, Boxes and other containers which require only object parameter, and "not_packed" key word for objects we don't want to pack. Or should we use "pack" explicitly for all objects we want to pack? * Do we need data inside callbacks? How we want define and pass it? Actually lately I started to think, that UI context should be passed as data to all callbacks. And user can add his data to context with "data_set/get" API * How to describe create callback for a new window. on clicked(create ("window_2", null)) And one more big note: Erigo supports snippets. Example: Let's say there are "win1" and "conf1" on a canvas. Check screenshot: http://www.enlightenment.org/ss/e-56d5b05d67d658.81288411.jpg "conf1" is a snippet. Create function, structure with all the content, etc will be generated for it. Thus: - user can manually call "conf1_create" function and handle its context; - or user can add creation callback using Erigo. User adds callback for a object, chooses type "create" for a callback, sets parent, other actions and etc. In this way snippet can be reused as many times as needed. Question: do we want to support described usecase? If so we have several thoughts how to describe this: Conformant(id="conf1") Layout Button Window(id="win1") Box(id = "box1") Button(id="but1") on clicked(create("conf1", "win1"), box1.pack("conf1"), conf1.visible) #or --------------------------------------- Button(id="but1") on clicked #in this case id "conf1" used as constructor conf1(id = "my_conf", parent = "win1") box1.pack("my_conf") my_conf.visible #or --------------------------------------- #also snippet can be described as a new function.... MyConf = Conformant(id="conf1") Layout Button #...and then used... Button(id="but1") on clicked MyConf(id = "new_conf", parent = "win1") box1.pack("my_conf") new_conf.visible --- Yakov ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
