http://cia.vc/stats/project/e/edje1057183613210Graphical layout and animation libraryEdje is a complex graphical design and layout library based on Evas that provides an abstraction layer between the application code and the interface, while allowing extremely flexible dynamic layouts and animations. In more popular terms, Edje makes every application that uses it "skinable" . "Edje is an attempt to find a middleground between theming and programming without turning the theme itself into just yet another program." -- Carsten Haitzler (The Rasterman) It's purpose is to be a sequel to "Ebits" which to date has serviced the needs of Enlightenment development for version 0.17. The original design parameters under which Ebits came about were a lot more restricted than the resulting use of them, thus Edje was born. Edje is a more complex layout engine compared to Ebits. It doesn't pretend to do containing and regular layout like a widget set. It still inherits the more simplistic layout ideas behind Ebits, but it now does them a lot more cleanly, allowing for easy expansion, and the ability to cover much more ground than Ebits ever could. For the purposes of Enlightenment 0.17, Edje should serve all the purposes of creating visual elements (borders of windows, scrollbars, etc.) and allow the designer the ability to animate, layout and control the look and feel of any program using Edje as its basic GUI constructor. This library allows for multiple collections of Layouts in one file, sharing the same image database and thus allowing a whole theme to be conveniently packaged into 1 file and shipped around. Edje, unlike Ebits, separates the layout and behavior logic. Edje files ship with an image database, used by all the parts in all the collections to source graphical data. It has a directory of logical part names pointing to the part collection entry ID in the file (thus allowing for multiple logical names to point to the same part collection, allowing for the sharing of data between display elements). Each part collection consists of a list of visual parts, as well as a list of programs. A program is a conditionally run program that if a particular event occurs (a button is pressed, a mouse enters or leaves a part) will trigger an action that may affect other parts. In this way a part collection can be "programmed" via its file as to hilight buttons when the mouse passes over them or show hidden parts when a button is clicked somewhere etc. The actions performed in changing from one state to another are also allowed to transition over a period of time, allowing animation. This separation and simplistic event driven style of programming can produce almost any look and feel one could want for basic visual elements. Anything more complex is likely the domain of an application or widget set that may use Edje as a convenient way of being able to configure parts of the display. NoneEdjehttp://trac.enlightenment.org/e/wiki/EdjeNonePython Subversion client for CIA1.20eedje71436devilhornsEdje: Cleanup compiler warnings if NEWPARTLOOKUP is not defined. 65http://trac.enlightenment.org/e/changeset/71436src/bin/edje_cc_out.c1338037659Python Subversion client for CIA1.20eedje71435devilhornsEdje: Fix compiler warnings for edje_entry_input_panel functions when Ecore is built without IMF support. 62http://trac.enlightenment.org/e/changeset/71435src/lib/edje_entry.c1338037215Python Subversion client for CIA1.20eedje71387rasterfix async embryo_cc stuff. it was losing all the embyro compiles! 61http://trac.enlightenment.org/e/changeset/71387src/bin/edje_cc_out.c1337853734Python Subversion client for CIA1.20eedje71378rasteradd a -threads mode and make non-threaded compile the default... no pending threads then. we can change this later for more testing. trying to narrow down issues anyway. 68http://trac.enlightenment.org/e/changeset/71378src/bin/edje_cc.csrc/bin/edje_cc.hsrc/bin/edje_cc_out.c1337847819Python Subversion client for CIA1.20eedje71344rasteradd brackets.. to if... 15http://trac.enlightenment.org/e/changeset/71344src/bin/edje_cc_out.c1337762802Python Subversion client for CIA1.20eedje71341rasterfound scrollbar bug in e17 theme... something to do with my making part lookups faster (O(1)). disable new part lookup code until i've figured it out. 86http://trac.enlightenment.org/e/changeset/71341src/bin/edje_cc_out.c1337758585Python Subversion client for CIA1.20eedje71309rasterdont eet_close on error/abort as it can cause segv's now due to threads. 14http://trac.enlightenment.org/e/changeset/71309src/bin/edje_cc_out.c1337693606Python Subversion client for CIA1.20eedje71285seozedje edje_cc_handlers.c: Fixed formatting while reading the code. 644http://trac.enlightenment.org/e/changeset/71285src/bin/edje_cc_handlers.c1337622385Python Subversion client for CIA1.20eedje71277rasterFrom: SHILPA ONKAR SINGH <shilpa.singh@samsung.com> Subject: [E-devel] [Edje]: Bug Fix: Edje draggable jumps when external events is used. Please find attached bug fix patch for edje draggable jump issue when external event area is used. Bug: When an external event area is used for edje draggable and when after mouse move if immediate mouse down is done then the draggable jumps back to its original position. Analysis: In _edje_mouse_down_signal_cb When an external event area is set i.e., when rp->events_to is set. tmp.x value is set to 0, need_reset is set to 1 and also _edje_recalc_do is called including emitting "drag" signal. this code is unnecessary/buggy and instead it causes the jump. 1. In mouse down only drag->down.x and drag->down.y needs to be set which is being set below and tmp value need not be reset to 0 as tmp value is calculated in mouse move based on drag->down.x and drag->down.y values. 2. need_reset is already set in mouse up hence need not be set in mouse down again. 3. edje_recalc_do is the function which actually causes the movement of draggable based on tmp value hence need not be called in mouse down. because of the above code race condition happens and as tmp value is being set to 0 and need reset is also enabled the draggable jumps back to where it started. 4. "drag": is sent even before "drag,start" [ should not /need not be sent in mouse down ] All the above code is added only when external event area is set and the above code is not even related to whether external event is set or not. Solution: When an external event area is set directly equating rp = rp->events_to and sending mouse,down would be enough, as down.x and down.y is set below including sending drag,start. Recalc_do should be called only in mouse move as its responsible for movement including setting tmp value. need_reset is already set in mouse up. drag should not be sent from mouse down. Change Description: Bug Fix: Edje Draggable jumps when mouse down is done immediately after mouse move when an external event area is used. demo edc pasted below to reproduce the issue. Please find attached bug fix patch for edje draggable jump issue when external event area is used. Bug: When an external event area is used for edje draggable and when after mouse move if immediate mouse down is done then the draggable jumps back to its original position. Analysis: In _edje_mouse_down_signal_cb When an external event area is set i.e., when rp->events_to is set. tmp.x value is set to 0, need_reset is set to 1 and also _edje_recalc_do is called including emitting "drag" signal. this code is unnecessary/buggy and instead it causes the jump. 1. In mouse down only drag->down.x and drag->down.y needs to be set which is being set below and tmp value need not be reset to 0 as tmp value is calculated in mouse move based on drag->down.x and drag->down.y values. 2. need_reset is already set in mouse up hence need not be set in mouse down again. 3. edje_recalc_do is the function which actually causes the movement of draggable based on tmp value hence need not be called in mouse down. because of the above code race condition happens and as tmp value is being set to 0 and need reset is also enabled the draggable jumps back to where it started. 4. "drag": is sent even before "drag,start" [ should not /need not be sent in mouse down ] All the above code is added only when external event area is set and the above code is not even related to whether external event is set or not. Solution: When an external event area is set directly equating rp = rp->events_to and sending mouse,down would be enough, as down.x and down.y is set below including sending drag,start. Recalc_do should be called only in mouse move as its responsible for movement including setting tmp value. need_reset is already set in mouse up. drag should not be sent from mouse down. Change Description: Bug Fix: Edje Draggable jumps when mouse down is done immediately after mouse move when an external event area is used. demo edc pasted below to reproduce the issue. Please find attached bug fix patch for edje draggable jump issue when external event area is used. Bug: When an external event area is used for edje draggable and when after mouse move if immediate mouse down is done then the draggable jumps back to its original position. Analysis: In _edje_mouse_down_signal_cb When an external event area is set i.e., when rp->events_to is set. tmp.x value is set to 0, need_reset is set to 1 and also _edje_recalc_do is called including emitting "drag" signal. this code is unnecessary/buggy and instead it causes the jump. 1. In mouse down only drag->down.x and drag->down.y needs to be set which is being set below and tmp value need not be reset to 0 as tmp value is calculated in mouse move based on drag->down.x and drag->down.y values. 2. need_reset is already set in mouse up hence need not be set in mouse down again. 3. edje_recalc_do is the function which actually causes the movement of draggable based on tmp value hence need not be called in mouse down. because of the above code race condition happens and as tmp value is being set to 0 and need reset is also enabled the draggable jumps back to where it started. 4. "drag": is sent even before "drag,start" [ should not /need not be sent in mouse down ] All the above code is added only when external event area is set and the above code is not even related to whether external event is set or not. Solution: When an external event area is set directly equating rp = rp->events_to and sending mouse,down would be enough, as down.x and down.y is set below including sending drag,start. Recalc_do should be called only in mouse move as its responsible for movement including setting tmp value. need_reset is already set in mouse up. drag should not be sent from mouse down. Change Description: Bug Fix: Edje Draggable jumps when mouse down is done immediately after mouse move when an external event area is used. demo edc pasted below to reproduce the issue. Please find attached bug fix patch for edje draggable jump issue when external event area is used. Bug: When an external event area is used for edje draggable and when after mouse move if immediate mouse down is done then the draggable jumps back to its original position. Analysis: In _edje_mouse_down_signal_cb When an external event area is set i.e., when rp->events_to is set. tmp.x value is set to 0, need_reset is set to 1 and also _edje_recalc_do is called including emitting "drag" signal. this code is unnecessary/buggy and instead it causes the jump. 1. In mouse down only drag->down.x and drag->down.y needs to be set which is being set below and tmp value need not be reset to 0 as tmp value is calculated in mouse move based on drag->down.x and drag->down.y values. 2. need_reset is already set in mouse up hence need not be set in mouse down again. 3. edje_recalc_do is the function which actually causes the movement of draggable based on tmp value hence need not be called in mouse down. because of the above code race condition happens and as tmp value is being set to 0 and need reset is also enabled the draggable jumps back to where it started. 4. "drag": is sent even before "drag,start" [ should not /need not be sent in mouse down ] All the above code is added only when external event area is set and the above code is not even related to whether external event is set or not. Solution: When an external event area is set directly equating rp = rp->events_to and sending mouse,down would be enough, as down.x and down.y is set below including sending drag,start. Recalc_do should be called only in mouse move as its responsible for movement including setting tmp value. need_reset is already set in mouse up. drag should not be sent from mouse down. Change Description: Bug Fix: Edje Draggable jumps when mouse down is done immediately after mouse move when an external event area is used. 91http://trac.enlightenment.org/e/changeset/71277ChangeLogsrc/lib/edje_callbacks.c1337610678Python Subversion client for CIA1.20eedje71264hyoyoungedje/multisense: add checking sample,tone name at playing. and some indent fixes 132http://trac.enlightenment.org/e/changeset/71264src/lib/edje_multisense.c1337591439Python Subversion client for CIA1.20eedje71243cedricedje: fix little oopsie on theme change. 15http://trac.enlightenment.org/e/changeset/71243src/lib/edje_load.c1337513925Python Subversion client for CIA1.20eedje71242cedricedje: reduce memcpy in edje_cc by using Eina_File. 307http://trac.enlightenment.org/e/changeset/71242ChangeLogNEWSsrc/bin/edje_cc_out.c1337513358Python Subversion client for CIA1.20eedje71241cedricedje: remove useless printf. 22http://trac.enlightenment.org/e/changeset/71241src/lib/edje_util.c1337513332Python Subversion client for CIA1.20eedje71235cedricedje: fix double opening of edje file. NOTE: know issue, in elementary_config the size of the icon change after a theme reload. I don't know what information is lost between to reload. If someone can point at them, thanks. 1220http://trac.enlightenment.org/e/changeset/71235src/lib/edje_load.csrc/lib/edje_private.hsrc/lib/edje_smart.csrc/lib/edje_util.c1337367526Python Subversion client for CIA1.20eedje71229hyoyoungedje: add sample and tone of multisense to edje inheritance 17http://trac.enlightenment.org/e/changeset/71229src/bin/edje_cc_handlers.c1337345696Python Subversion client for CIA1.20eedje71155rasterwork around the workaround so it works until ecore thread goop fixed. 30http://trac.enlightenment.org/e/changeset/71155src/bin/edje_cc_out.c1337181889Python Subversion client for CIA1.20eedje71152cedricedje: fix text and table with fixed point and clamp image tween. 170http://trac.enlightenment.org/e/changeset/71152ChangeLogNEWSsrc/bin/edje_watch.csrc/lib/edje_calc.csrc/lib/edje_load.csrc/lib/edje_text.c1337180273Python Subversion client for CIA1.20eedje71144rasterwork around race condition bug in ecore for now so edje_cc is reliable again. CEDRIIIIIIIIIIIIIIIIIIIC! 176http://trac.enlightenment.org/e/changeset/71144src/bin/edje_cc_out.c1337169799Python Subversion client for CIA1.20eedje71138rasterand clean up some of the work on parallelized edje_cc. code less ugly now. 404http://trac.enlightenment.org/e/changeset/71138src/bin/edje_cc_out.c1337150146Python Subversion client for CIA1.20eedje71112rasteroptimize edje_cc - now betwene 3.5 x and 4x as fast. new options (-fastcomp and -fastdecomp) -fastcomp makes for faster decompressing AND faster compressing of edj files, -fastdecomp is a bit slower on compression but also as fast as -fastcomp in decompression. note that edje files built with these optiosn will not work on older edje installations, thus they are options. 2197http://trac.enlightenment.org/e/changeset/71112ChangeLogsrc/bin/edje_cc.csrc/bin/edje_cc.hsrc/bin/edje_cc_out.csrc/bin/edje_cc_parse.csrc/bin/edje_cc_sources.csrc/bin/edje_decc.c1337100539