[E-devel] Documentation in wiki
Hey, I have group some items related to doc in the main page of wiki. What would be nice would be to "fill" some pages with the documentation of the EFL generated by doxygen. Is it possible ? Vincent -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Was: Re: [e-users] get introduced to eina_log
On 18 September 14:22 2009 =?UTF-8?Q?Iv=C3=A1n_Briano_=28Sachiel=29?= spoke: | On Fri, Sep 18, 2009 at 1:59 PM, Dave Andreoli wrote: | > 2009/9/17 Vincent Torri | > | >> | >> | >> On Thu, 17 Sep 2009, Gustavo Sverzut Barbieri wrote: | >> | >>  On Thu, Sep 17, 2009 at 3:22 AM, Vincent Torri | >>> wrote: | >>> | | Currently, in "Core EFL items needed for Enlightenment", we have various | doc | in the pages, but it's  not consistent at all. And it's not obvious that | we | should go into the Eina page to read the eina log documentation. | Especially | as there is a section below that is named "Programming with the EFL" | | so it is beggining to be a mess, imho | | >>> | >>> Yes, I also found it hard to find out where to add these stuff. If you | >>> know a better place to add those, please be my guest and move | >>> contents. You can either delete the old or redirect. And doing it | >>> sooner than latter will be easier as we can use timeline to easily | >>> spot links that were added referring to new page. | >>> | >> | >> What I suggest, is to group the "Enlightenment FAQ" and "Programming with | >> the EFL" sections into only one "Documentation" section (I think that it is | >> important that the word 'Documentation' appears somewhere): | >> | >> Documentation | >>  * FAQ | >>  * User guides (note the plural) | >>  * Programming with the EFL | >>  * Autotools integration | >>  * Eina | >>  * Eet | >>  * etc... | >> | >> FAQ is the current FAQ page, maybe to update (i don't know its status) | >> | >> User Guides is a page that containes user guides (!) for the applications | >> like e16, e17, exalt or eyelight) | >> | >> Autotools integration is the current page | >> | >> Eina is a page with some doc (so you eina log page would be here) | >> Eet same than Eina | >> | >> We can of course put Ethumb here too. | >> | >> Maybe we can also link to pages that are created by the script in | >> /home/ewww. That would allow to have the tutorials linked automatically, | >> and, as you say below, it will be more sync with the modifications. | >> | >>  All in all, i guess it's better to move that stuff to source files as | >>> @page tutorial_* stuff, it's not as visible or easier to have users to | >>> contribute (do they do it anyway?), but it's closer to the problem and | >>> possibly will be less out-of-sync (it is impossible to keep it sync'ed | >>> I know). | >>> | >> | >> indeed | >> | >>  Still about documentation, I noticed docs.enlightenment.org APIs are | >>> bit behind, who manages that? Could you update? Could you include | >>> ethumb as well? | >>> | >> | >> I don't know who manages that. | >> | > | > I think that mekius should manage the server... but the doxy | > generation is broken since months (like also the images in trac) | > | > The doxy generation are broken becouse of the new 'make doc' | > command, that require a successfull autogen on every packages. but packages | > are not installed on the server and autogen fails searching deps. | > | | The script is fixed to work with that, and afaik, it was once used and | it does work. | The problem is, no job running it frequently to update the docs. | | > DaveMDS | > | > | > | > | >> Vincent | >> | >> -- | >> Come build with us! The BlackBerry® Developer Conference in SF, CA | >> is the only developer event you need to attend this year. Jumpstart your | >> developing skills, take BlackBerry mobile applications to market and stay | >> ahead of the curve. Join us from November 9-12, 2009. Register now! | >> http://p.sf.net/sfu/devconf | >> ___ | >> enlightenment-devel mailing list | >> enlightenment-devel@lists.sourceforge.net | >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel | >> | >> | > -- | > Come build with us! The BlackBerry® Developer Conference in SF, CA | > is the only developer event you need to attend this year. Jumpstart your | > developing skills, take BlackBerry mobile applications to market and stay | > ahead of the curve. Join us from November 9-12, 2009. Register now! | > http://p.sf.net/sfu/devconf | > ___ | > enlightenment-users mailing list | > enlightenment-us...@lists.sourceforge.net | > https://lists.sourceforge.net/lists/listinfo/enlightenment-users | > | | -- | Come build with us! The BlackBerry® Developer Conference in SF, CA | is the only developer event you need to attend this year. Jumpstart your | developing skills, take BlackBerry mobile applications to market and stay | ahead of the curve. Join u
[E-devel] Was: Re: get introduced to eina_log
On 18 September 14:25 2009 Gustavo Sverzut Barbieri spoke: | On Fri, Sep 18, 2009 at 1:59 PM, Dave Andreoli wrote: | > | > | > 2009/9/17 Vincent Torri | >> | >> | >> On Thu, 17 Sep 2009, Gustavo Sverzut Barbieri wrote: | >> | >>> On Thu, Sep 17, 2009 at 3:22 AM, Vincent Torri | >>> wrote: | | Currently, in "Core EFL items needed for Enlightenment", we have various | doc | in the pages, but it's  not consistent at all. And it's not obvious that | we | should go into the Eina page to read the eina log documentation. | Especially | as there is a section below that is named "Programming with the EFL" | | so it is beggining to be a mess, imho | >>> | >>> Yes, I also found it hard to find out where to add these stuff. If you | >>> know a better place to add those, please be my guest and move | >>> contents. You can either delete the old or redirect. And doing it | >>> sooner than latter will be easier as we can use timeline to easily | >>> spot links that were added referring to new page. | >> | >> What I suggest, is to group the "Enlightenment FAQ" and "Programming with | >> the EFL" sections into only one "Documentation" section (I think that it is | >> important that the word 'Documentation' appears somewhere): | >> | >> Documentation | >>  * FAQ | >>  * User guides (note the plural) | >>  * Programming with the EFL | >>  * Autotools integration | >>  * Eina | >>  * Eet | >>  * etc... | >> | >> FAQ is the current FAQ page, maybe to update (i don't know its status) | >> | >> User Guides is a page that containes user guides (!) for the applications | >> like e16, e17, exalt or eyelight) | >> | >> Autotools integration is the current page | >> | >> Eina is a page with some doc (so you eina log page would be here) | >> Eet same than Eina | >> | >> We can of course put Ethumb here too. | >> | >> Maybe we can also link to pages that are created by the script in | >> /home/ewww. That would allow to have the tutorials linked automatically, | >> and, as you say below, it will be more sync with the modifications. | >> | >>> All in all, i guess it's better to move that stuff to source files as | >>> @page tutorial_* stuff, it's not as visible or easier to have users to | >>> contribute (do they do it anyway?), but it's closer to the problem and | >>> possibly will be less out-of-sync (it is impossible to keep it sync'ed | >>> I know). | >> | >> indeed | >> | >>> Still about documentation, I noticed docs.enlightenment.org APIs are | >>> bit behind, who manages that? Could you update? Could you include | >>> ethumb as well? | >> | >> I don't know who manages that. | > | > I think that mekius should manage the server... but the doxy | > generation is broken since months (like also the images in trac) | > | > The doxy generation are broken becouse of the new 'make doc' | > command, that require a successfull autogen on every packages. but packages | > are not installed on the server and autogen fails searching deps. | | I understand why having "make doc" and it depending on autoconf, but | the server do not need to rely on it, it's much easier to have a shell | script with doxygen calls directly... we just few packages that is | easily to maintain... or we can agree that packages should have a | folder "doc" with file "Doxfile" in it. | | -- | Gustavo Sverzut Barbieri | http://profusion.mobi embedded systems | -- | MSN: barbi...@gmail.com | Skype: gsbarbieri | Mobile: +55 (19) 9225-2202 | | -- | Come build with us! The BlackBerry® Developer Conference in SF, CA | is the only developer event you need to attend this year. Jumpstart your | developing skills, take BlackBerry mobile applications to market and stay | ahead of the curve. Join us from November 9-12, 2009. Register now! | http://p.sf.net/sfu/devconf | ___ | enlightenment-devel mailing list | enlightenment-devel@lists.sourceforge.net | https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Rocco Carbone mail-to: Pisa Italy Life is in the details -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Was: Re: E SVN: watchwolf trunk/TMP/st/elementary-generator
On 18 September 18:49 2009 Gustavo Sverzut Barbieri spoke:
| well, idea was to show an UI inwin with the last message and an option
| to show the full log.
|
| On Fri, Sep 18, 2009 at 6:42 PM, Enlightenment SVN
| wrote:
| > Log:
| > Â elm generator : print the generation errors with eina_log
| >
| >
| > Author: Â Â Â watchwolf
| > Date: Â Â Â Â 2009-09-18 14:42:06 -0700 (Fri, 18 Sep 2009)
| > New Revision: 42561
| >
| > Modified:
| > Â trunk/TMP/st/elementary-generator/ui.c
| >
| > Modified: trunk/TMP/st/elementary-generator/ui.c
| > ===
| > --- trunk/TMP/st/elementary-generator/ui.c    2009-09-18 20:38:46 UTC
(rev 42560)
| > +++ trunk/TMP/st/elementary-generator/ui.c    2009-09-18 21:42:06 UTC
(rev 42561)
| > @@ -115,12 +115,15 @@
| > Â {
| > Â Â App *app = data;
| > Â Â Ecore_Exe_Event_Data *e = event;
| > -
| > + Â int i;
| > Â Â if (app->exe != e->exe)
| > Â Â Â return 1;
| >
| > Â Â printf(" TODO: show inwin with error message: [close] [try
again]\n");
| >
| > + Â for (i = 0; e->lines[i].line != NULL; i++)
| > + Â Â Â ERR(e->lines[i].line);
| > +
| > Â Â return 1;
| > Â }
| >
| >
| >
| >
--
| > Come build with us! The BlackBerry® Developer Conference in SF, CA
| > is the only developer event you need to attend this year. Jumpstart your
| > developing skills, take BlackBerry mobile applications to market and stay
| > ahead of the curve. Join us from November 9-12, 2009. Register now!
| > http://p.sf.net/sfu/devconf
| > ___
| > enlightenment-svn mailing list
| > enlightenment-...@lists.sourceforge.net
| > https://lists.sourceforge.net/lists/listinfo/enlightenment-svn
| >
|
|
|
| --
| Gustavo Sverzut Barbieri
| http://profusion.mobi embedded systems
| --
| MSN: barbi...@gmail.com
| Skype: gsbarbieri
| Mobile: +55 (19) 9225-2202
|
|
--
| Come build with us! The BlackBerry® Developer Conference in SF, CA
| is the only developer event you need to attend this year. Jumpstart your
| developing skills, take BlackBerry mobile applications to market and stay
| ahead of the curve. Join us from November 9-12, 2009. Register now!
| http://p.sf.net/sfu/devconf
| ___
| enlightenment-devel mailing list
| enlightenment-devel@lists.sourceforge.net
| https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
--
Rocco Carbone mail-to:
Pisa Italy
Life is in the details
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] E SVN: watchwolf trunk/TMP/st/elementary-generator
yes but print the errors in stdout is always a good idea :)
2009/9/18 Gustavo Sverzut Barbieri
> well, idea was to show an UI inwin with the last message and an option
> to show the full log.
>
> On Fri, Sep 18, 2009 at 6:42 PM, Enlightenment SVN
> wrote:
> > Log:
> > elm generator : print the generation errors with eina_log
> >
> >
> > Author: watchwolf
> > Date: 2009-09-18 14:42:06 -0700 (Fri, 18 Sep 2009)
> > New Revision: 42561
> >
> > Modified:
> > trunk/TMP/st/elementary-generator/ui.c
> >
> > Modified: trunk/TMP/st/elementary-generator/ui.c
> > ===
> > --- trunk/TMP/st/elementary-generator/ui.c 2009-09-18 20:38:46 UTC
> (rev 42560)
> > +++ trunk/TMP/st/elementary-generator/ui.c 2009-09-18 21:42:06 UTC
> (rev 42561)
> > @@ -115,12 +115,15 @@
> > {
> >App *app = data;
> >Ecore_Exe_Event_Data *e = event;
> > -
> > + int i;
> >if (app->exe != e->exe)
> > return 1;
> >
> >printf(" TODO: show inwin with error message: [close] [try
> again]\n");
> >
> > + for (i = 0; e->lines[i].line != NULL; i++)
> > + ERR(e->lines[i].line);
> > +
> >return 1;
> > }
> >
> >
> >
> >
> --
> > Come build with us! The BlackBerry® Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> > http://p.sf.net/sfu/devconf
> > ___
> > enlightenment-svn mailing list
> > enlightenment-...@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-svn
> >
>
>
>
> --
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> --
> MSN: barbi...@gmail.com
> Skype: gsbarbieri
> Mobile: +55 (19) 9225-2202
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
--
Regards.
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Implementing default gadcon client size for EFM toolbar
Hi guys
On adding a gadcon client to EFM toolbar, its width used hardcoded value
regardless of gadcon client type. Here is patchset allowing to define
default (preferred) width for each type of EFM toolbar client.
- edje changed so a collections.group of .edc collection file can have
"prefer" value.
- on creating a new, unconfigured gadcon client, it uses preferred size
of underlying Evas object as its width.
- appropriate sizes applied to EFM modules
Hope you'll find it useful.
Sincerely, Victor.
On creating new gadcon client, make it honors size preferences of container Evas_Object. On loading scrollframe content from a file, apply preferred size of contained object as preferred size to scrollframe itself.
e_gadcon.c | 54 +++---
e_scrollframe.c |7 +++
2 files changed, 42 insertions(+), 19 deletions(-)
Index: e17-svn/src/bin/e_gadcon.c
===
--- e17-svn/src/bin/e_gadcon.c (revision 42565)
+++ e17-svn/src/bin/e_gadcon.c (working copy)
@@ -398,6 +398,36 @@
/* FIXME: delete container obj, re-pack all clients */
}
+static void
+_e_gadcon_client_adjust_size(E_Gadcon_Client *gcc, E_Config_Gadcon_Client *cf_gcc)
+{
+ Evas_Coord w = 0;
+ Evas_Object *obj = NULL;
+
+ cf_gcc->geom.res = 800;
+ if (gcc->o_frame)
+ obj = gcc->o_frame;
+ else if (gcc->o_base)
+ obj = gcc->o_base;
+ if (0 == cf_gcc->geom.size)
+ {
+ /* this gadcon client don't configured yet */
+ if (obj)
+ evas_object_size_hint_request_get(obj, &w, NULL);
+ if (0 == w)
+ /* evas object don't provide size hint, use default */
+ cf_gcc->geom.size = 80;
+ else
+ /* use evas object size hint */
+ cf_gcc->geom.size = w;
+ }
+ gcc->config.pos = cf_gcc->geom.pos;
+ gcc->config.size = cf_gcc->geom.size;
+ gcc->config.res = cf_gcc->geom.res;
+ if (obj)
+ e_gadcon_layout_pack_options_set(obj, gcc);
+}
+
EAPI void
e_gadcon_populate(E_Gadcon *gc)
{
@@ -437,16 +467,9 @@
{
gcc->cf = cf_gcc;
gcc->client_class = cc;
- gcc->config.pos = cf_gcc->geom.pos;
- gcc->config.size = cf_gcc->geom.size;
- gcc->config.res = cf_gcc->geom.res;
gcc->state_info.seq = cf_gcc->state_info.seq;
gcc->state_info.flags = cf_gcc->state_info.flags;
- if (gcc->o_frame)
- e_gadcon_layout_pack_options_set(gcc->o_frame, gcc);
- else if (gcc->o_base)
- e_gadcon_layout_pack_options_set(gcc->o_base, gcc);
-
+ _e_gadcon_client_adjust_size(gcc, cf_gcc);
e_gadcon_client_autoscroll_set(gcc, cf_gcc->autoscroll);
e_gadcon_client_resizable_set(gcc, cf_gcc->resizable);
if (gcc->client_class->func.orient)
@@ -510,16 +533,9 @@
{
gcc->cf = cf_gcc;
gcc->client_class = cc;
- gcc->config.pos = cf_gcc->geom.pos;
- gcc->config.size = cf_gcc->geom.size;
- gcc->config.res = cf_gcc->geom.res;
gcc->state_info.seq = cf_gcc->state_info.seq;
gcc->state_info.flags = cf_gcc->state_info.flags;
- if (gcc->o_frame)
- e_gadcon_layout_pack_options_set(gcc->o_frame, gcc);
- else if (gcc->o_base)
- e_gadcon_layout_pack_options_set(gcc->o_base, gcc);
-
+ _e_gadcon_client_adjust_size(gcc, cf_gcc);
e_gadcon_client_autoscroll_set(gcc, cf_gcc->autoscroll);
e_gadcon_client_resizable_set(gcc, cf_gcc->resizable);
if (gcc->client_class->func.orient)
@@ -794,9 +810,9 @@
if (!cf_gcc) return NULL;
cf_gcc->name = eina_stringshare_add(name);
cf_gcc->id = eina_stringshare_add(cc->func.id_new(cc));
- cf_gcc->geom.res = 800;
- cf_gcc->geom.size = 80;
- cf_gcc->geom.pos = cf_gcc->geom.res - cf_gcc->geom.size;
+ cf_gcc->geom.res = 0;
+ cf_gcc->geom.size = 0;
+ cf_gcc->geom.pos = 0;
cf_gcc->style = NULL;
cf_gcc->autoscroll = 0;
cf_gcc->resizable = 0;
Index: e17-svn/src/bin/e_scrollframe.c
===
--- e17-svn/src/bin/e_scrollframe.c (revision 42565)
+++ e17-svn/src/bin/e_scrollframe.c (working copy)
@@ -215,8 +215,15 @@
e_scrollframe_custom_edje_file_set(Evas_Object *obj, char *file, char *group)
{
API_ENTRY return 0;
+ Evas_Coord w = 0, h = 0;
if (!edje_object_file_set(sd->edje_obj, file, group)) return 0;
+
+ /* use same size hints for container object */
+ evas_object_size_hint_request_get(sd->edje_obj, &w, &h);
+ if (0 != w || 0 != h)
+ evas_object_size_hint_request_set(obj, w, h);
+
if (sd->pan_obj)
edje_object_part_swallow(sd->edje_obj, "e.swallow.content", sd->pan_obj);
sd->vbar_visible = !sd->vbar_visible;
Adds "prefer" keyword support to collections.group of .edc files.
bin/edje_cc_handlers.c | 25 +
lib/edje_data.c|2 ++
lib/edje_load.c|3 ++-
lib/edje_private.h |2 +-
4 files changed, 30 insertions(+), 2 deletions(-)
Index: edje-svn/src/lib/edje_data.c
==
Re: [E-devel] restore internal window
no time to look, may raster will have... but if it works, does something great, then commit it. On Sat, Sep 19, 2009 at 8:30 PM, hannes.janet...@gmail.com wrote: > Hello, > attached is a patch that allows e's internal windows to be restored > after restart. It saves an extra list of e's window remember struct > and applies them after restart. To make it work I have changed the > window class of dialogs to match the config registry path on which the > are registered. For efm windows the window class contains the full > path. It can later be improved by also saving params that are given to > the dialog, though this feature is not used more than twice atm as far > as I can see. > > Also with this patch the geometry saving of efm is removed and > replaced by using e_remember. One can now select in window remember > config dialogs whether dialogs and/or efm windows should be saved by > default. > > Comments or suggestions? > > > Regards, > Hannes > > -- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
