CIA.vc
Edje
Graphical layout and animation library
Stats » Projects » Enlightenment » Edje
information
Photo
Edje 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.
syndicateUTC clock
10:19 on May 28, 2012
event counters
The last message was received 1.88 days ago at 13:07 on May 26, 2012
0 messages so far today, 0 messages yesterday
0 messages so far this week, 10 messages last week
36 messages so far this month, 18 messages last month
1057 messages since the first one, 2.31 years ago, for an average of 19.11 hours between messages
recent messages
dateReversed sort columnprojectcontentlink
13:07 Saturdaye
Commit by devilhorns :: r71436 edje/src/bin/edje_cc_out.c: (link)
Edje: Cleanup compiler warnings if NEWPARTLOOKUP is not defined.
#
13:00 Saturdaye
Commit by devilhorns :: r71435 edje/src/lib/edje_entry.c: (link)
Edje: Fix compiler warnings for edje_entry_input_panel functions when
Ecore is built without IMF support.
#
10:02 Thursdaye
Commit by raster :: r71387 edje/src/bin/edje_cc_out.c: (link)
fix async embryo_cc stuff. it was losing all the embyro compiles!
#
08:23 Thursdaye
Commit by raster :: r71378 edje/src/bin/ (edje_cc.c edje_cc.h edje_cc_out.c): (link)
add 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.
#
08:46 Wednesdaye
Commit by raster :: r71344 edje/src/bin/edje_cc_out.c: (link)
add brackets.. to if...
#
07:36 Wednesdaye
Commit by raster :: r71341 edje/src/bin/edje_cc_out.c: (link)
found 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.
#
13:33 Tuesdaye
Commit by raster :: r71309 edje/src/bin/edje_cc_out.c: (link)
dont eet_close on error/abort as it can cause segv's now due to threads.
#
17:46 on May 21e
Commit by seoz :: r71285 edje/src/bin/edje_cc_handlers.c: (link)
edje edje_cc_handlers.c: Fixed formatting while reading the code.
#
14:31 on May 21e
Commit by raster :: r71277 edje/ (ChangeLog src/lib/edje_callbacks.c): (link)
From: SHILPA ONKAR SINGH <shilpa dot singh at samsung dot 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.
#
09:10 on May 21e
Commit by hyoyoung :: r71264 edje/src/lib/edje_multisense.c: (link)
edje/multisense: add checking sample,tone name at playing. and some indent fixes
#
11:38 on May 20e
Commit by cedric :: r71243 edje/src/lib/edje_load.c: (link)
edje: fix little oopsie on theme change.
#
11:29 on May 20e
Commit by cedric :: r71242 edje/ (ChangeLog NEWS src/bin/edje_cc_out.c): (link)
edje: reduce memcpy in edje_cc by using Eina_File.
#
11:28 on May 20e
Commit by cedric :: r71241 edje/src/lib/edje_util.c: (link)
edje: remove useless printf.
#
18:58 on May 18e
Commit by cedric :: r71235 edje/src/lib/ (4 files): (link)
edje: 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.
#
12:54 on May 18e
Commit by hyoyoung :: r71229 edje/src/bin/edje_cc_handlers.c: (link)
edje: add sample and tone of multisense to edje inheritance
#
15:24 on May 16e
Commit by raster :: r71155 edje/src/bin/edje_cc_out.c: (link)
work around the workaround so it works until ecore thread goop fixed.
#
14:57 on May 16e
Commit by cedric :: r71152 edje/ (6 files in 3 dirs): (link)
edje: fix text and table with fixed point and clamp image tween.
#
12:03 on May 16e
Commit by raster :: r71144 edje/src/bin/edje_cc_out.c: (link)
work around race condition bug in ecore for now so edje_cc is reliable
again. CEDRIIIIIIIIIIIIIIIIIIIC!
#
06:35 on May 16e
Commit by raster :: r71138 edje/src/bin/edje_cc_out.c: (link)
and clean up some of the work on parallelized edje_cc. code less ugly
now.
#
16:48 on May 15e
Commit by raster :: r71112 edje/ (7 files in 2 dirs): (link)
optimize 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.
#