On Wed, 21 Mar 2012 22:30:27 +0100 Andreas Volz <li...@brachttal.net> said:

rotary.. what?

> Hi,
> 
> I've some special widgets which I couldn't assemble from other existing
> widgets (rotary). So I like to create a new one. Could you tell me the
> way how to do this?
> 
> Should I create a new one in elementary/src/lib/ (I won't commit it
> without permission!) or is there some elementary-extras library in
> PROTO? Or should I create a private lib on top of elementary for my
> special widgets?

depends on what your widget is exactly. u can create private widgets... but the
widget api for elm is explicitly unstable (elm_widget.h) and marked and
documented as such.

> Could someone explain me a difference between elm_*.c, elc_*.c, elu_*.c
> and els_*.c. Is this documented somewhere? I'm not sure which one to
> take as template for my new widget.

elm == widgets/core
elc == collection widgets -> widgets that pretty much glue existing widgets
together in a useful "collection"
elu == utils
els == smart objects (not widgets).


> regards
>       Andreas
> 
> -- 
> Technical Blog <http://andreasvolz.wordpress.com/>
> 
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here 
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> 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


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to