On Tue, 08 Mar 2016 18:14:42 +0200 Yakov Goldberg <yako...@samsung.com> said:
> Hello everyone, > I had discussions with Tom and as a result updated wiki page. > > You can find it here: > https://phab.enlightenment.org/w/ui_builders_format/ > > > Most things are clear there are several questions to be discussed: > > * fixed indentation (4 spaces) or not fixed i personally think 2 spaces is fine. 4 is just "too much". the reason is most monospace fonts are taller than they are wide so "2" ends up a nice diagonal like: \ \ \ but well more actual 45 degrees. :) > * Widget vs Elm.Widget: all widgets - are they Elm Widgets only and thus > "Elm" can be skipped or we want to use namespace yes. in fact we will skip elm in eo api. they'll be efl.ui.xxxx - you want the ability to strip the efl.ui bit away though so people are not writing Efl.Ui.Button (...) as opposed to: Button (...) which is what they should > * button vs Button: starts with capital letter? i prefer smalls... i don't see the value of forcing people to hit an extra shift when it provides no extra syntatic/semantic value. if you supported variables for example then it may be useful to differentiate object types/constructors as "Button" vs a variable which might be "button", but then this begins to become a programming language. actually you MAY need to support this. edje_cc supports basic math like: (2+3)/8 it'll evaluate as edje_cc goes - this is REALLY helpful in making your stuff readable as you can actually give fractions like 2/3 as opposed to 0.66666666666666666 :) since edje_cc also supports cpp this effectively allows for variable substitution with math.. of course loading a file into a gui editor and writing it back out may lose this math magic so it'd only be useful for purely "hand edited" stuff... > * callbacks format - options: > Button() > on clicked("callback_name") > on("clicked", "callback_name") the first one... :) > #and whether allow or not property modification and object creations in > #callbacks: > on("clicked", "callback_name", box_1.visible = true, #and more ui > updates) on clicked,double(box_1.visible = true) > on clicked,double(create ("window_2", null)) oh this is where things go bad - this begins to look like code where you can define "properties and objects to modify". :( i would say "no". be VERY careful walking down this path. it's a slippery slope into a programming language. > * snippets support - please read in wiki > https://phab.enlightenment.org/w/ui_builders_format/#snippets beginning to look good i think. i dont have any objections. :) > > Regards > Yakov > > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://makebettercode.com/inteldaal-eval > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
