On Fri, 2 Jan 2009 15:11:33 -0200 andres <andresbl...@gmail.com> babbled:
> On Wednesday 31 December 2008 23:36:16 Carsten Haitzler wrote: > > On Fri, 5 Dec 2008 12:21:13 -0200 andres <andresbl...@gmail.com> babbled: > > > El Thursday 04 December 2008 09:46:13 Viktor Kojouharov escribió: > > > > Lets say that a part has 3 states. The first defines the rels and a > > > > color. The second inherits from the first, and defines a new color. If > > > > I want the third part to inherit from the second (to make a smooth > > > > transition from a second color to the third), edje will not doo the > > > > lookup for the rels properly, meaning that the rels for the 3rd state > > > > will be 0, since the 2nd state did not define rels, but inherited them. > > > > It should be though that if the 3rd state wants something from the > > > > second state, and the second state does not have the needed item, but > > > > inherits from the first, the lookup should proceed to search in the > > > > first as well. > > > > > > yes, that is known as multiple level inheritance and it does not work on > > > Edje as it is. > > > > > > Its one of the things I would like to implement down the road but I > > > haven't assessed the requirements for it yet. Since its not implemented I > > > assume its not easy. > > > > > > Does anyone know what it would take to implement this? > > > > it's actually pretty easy. just hasnt been done :) it's only done at > > edje_cc time - the inherit: "xx" x; simply copes the state description from > > "xxx" x to the current one. then any more delcarations just modify the > > state. so all it needs to do is make sure it copies to the parent before > > using it - if the parent has also done an inherit... :) or maybe move the > > inherit to parse time and do it in-line (this means though anything you > > inherit from must be declared before the current one in the file). > > great! thanks for the explanations. > another two more things I would like to implement while writting my "design > with Edje" and "development with Edje" books: > 1. Group inheritance that allows you to override one or more parts. possible - but harder than parts - how do you delete a part or re-order them in stacking? :) > 2. Group A has part B of type GROUP that swallows group C:. > a) Programs in A beign able to STATE_SET on part of C. > b) Singals from A echoing in C. this is where the sandboxing of edje objects begins to hurt - so you need to basically access the child like you do from c - explicitly sending signals or listening for them. > hard? easy? already in the works? :) > Thanks! > > ------------------------------------------------------------------------------ > _______________________________________________ > 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 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
