Dear Mike and everyone else, As you may know, mike_m recently added elm_object_label_set/get API and elm_object_text_set/get macros as a generic way to set/get text for elementary widgets. Not all the widgets are supported yet, but some are.
I like this change a lot as it makes the API smaller, nicer, more consistent and easier to remember. Currently, elm_object_label_get accepts two parameters, the object, and the "part" in that object. So for example one would call: elm_object_label_get(some_label, "default") for getting the default string of the label. I'm sending this mail because I disagree with Mike's choice of naming. He chose elm_object_label_set/get because in most cases we are setting labels, but since we also support setting entries, this name is just not good enough. I suggest renaming elm_object_label_set/get to elm_object_text_part_set/get or something similar which is, in my pov, better suiting than the former since we are using it to set/get more than just labels. What do you guys think? Should I rename them to elm_object_text_part_set/get? Thanks, Tom. P.S, again, thanks a lot to mike for doing this awesome change. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
