From: Enlightenment S. <no-...@en...> - 2011-10-24 03:31:44
|
Log: Add Button and FileSelector feedback. Author: sanjeev Date: 2011-10-23 20:31:37 -0700 (Sun, 23 Oct 2011) New Revision: 64347 Trac: http://trac.enlightenment.org/e/changeset/64347 Modified: trunk/devs/sanjeev/elm_api_feedback.txt Modified: trunk/devs/sanjeev/elm_api_feedback.txt =================================================================== --- trunk/devs/sanjeev/elm_api_feedback.txt 2011-10-24 02:34:46 UTC (rev 64346) +++ trunk/devs/sanjeev/elm_api_feedback.txt 2011-10-24 03:31:37 UTC (rev 64347) @@ -92,16 +92,47 @@ Creating an object that holds the function pointers and passing it as a *data to another function that takes a function pointer... Does not look elegant. Should be a better way of doing this. +How about individual API? +Button +------ +elm_button_icon_set/unset - deleting the previous icon object seems dangerous. +What if same icon object is used elsewhere as well? +Makes it easier for developer to commit mistakes. +elev8 reuses icon object and resets them in some examples. +If user created icon, it is his job to delete it. +FileSelector +------------ +elm_fileselector_button_path_set - return type could be int giving errno value. +No API for showing/hiding hidden files. +File Selector API and File Manager module provide different levels of functionality. +Would be good to add some more functionality. +File_Selector_Entry seems wrong name, it must be File_Selector_Label. +Changing the entry doesn't really mean anything. +General +------- +Smart callbacks, smart API - needs more highlighting. +Is it smart for the API users or developers? Why is it called smart? + + + + + + + + + + + |