Re: [E-devel] E CVS: libs/etk andrunko
> Log Message: > Added new widget Etk_Mdi_Window. MDI ? you mean "multiple document interface" ? windows inside a window ? Vincent - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
On Thu, 19 Jul 2007 23:44:53 +0200 Andreas Volz <[EMAIL PROTECTED]> wrote: > Am Fri, 20 Jul 2007 02:04:46 +1000 schrieb David Seikel: > > > raster highly recommends that everything get updated at once. I > > agree with him. > > If I have one two hours a day to spend for EFL programming I don't > waste half of the time to setup a daily build system. So this is a > risk if I update only some packages that I need. Perhaps a CVS install > script would help here. Could you publish your nightly build script? morlenxus and I are modifying easy_e17.sh to do these nightly builds. The modifications are going into his svn server, and will be in the next release he makes. His svn server is readable by the public. Details are at http://omicron.homeip.net/projects/#easy_e17.sh . signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Problem with edje and its way of dispatching mouse, * signals
On 7/18/07, Brian Mattern <[EMAIL PROTECTED]> wrote: > On Wed, Jul 18, 2007 at 12:56:17AM -0300, Gustavo Sverzut Barbieri wrote: > > On 7/18/07, Brian Mattern <[EMAIL PROTECTED]> wrote: > >> On Tue, Jul 17, 2007 at 06:15:51PM -0300, Gustavo Sverzut Barbieri wrote: > >> > Notice that edje property is no_mouse_grab, because then we can keep > >> > compatibility with existent .edj files. > >> > > >> > I don't like evas_object_mouse_grab_set() very much, it looks like > >> > mouse will be immediately grab, which is not the case. But I don't > >> > have any better word for that. > >> > >> > + EAPI void evas_object_mouse_grab_set > >> (Evas_Object *obj, Evas_Bool no_mouse_grab); > >> > + EAPI Evas_Bool evas_object_mouse_grab_get > >> (Evas_Object *obj); > >> > >> > >> Maybe evas_object_auto_grab_set(Evas_Object *obj, Evas_Bool auto_grab) ? > >> (or _mouse_auto_grab_) > > > > it's not that better... other suggestions? > > > > can_grab_mouse? > > That makes even less sense. Maybe "grab" isn't a good choice. Really > we're picking between two alternate methods of presenting mouse events. > So, maybe evas_object_mouse_event_mode_set(obj, EVAS_EVENT_MODE_X) > > I'm at a loss atm as to what the two names should be though. (Maybe > ORIGINAL and RAW... not happy with those...) > > > > > > >> Whatever we call it, the second parameter should NOT be no_*. It should > >> be TRUE for "grab the mouse", and simply default to TRUE. > > > > yes, I agree, but how about edje files? Can I rely on people updating > > their edje files? Remember that edje files will not be recompiled > > since they have not changed, users may issue "make clean" to get it > > updated. > > For edje files, you either need compatibility code (where the version is > checked on load and the value is set properly), OR you can just make the > edje option 'negative' (it doesn't have to be the same as the c api). > However, with the above suggestion for an API, the 'original' mode would > just be equal to 0. Ok, anyone more like it like Brian? I don't. Any other ideas? I'll wait until sunday, but it would be great if it don't last that long, my virtual keyboard demo is almost ready, just some images and this to be in then I can release it! :-) http://barbieri-playground.googlecode.com/svn/efl-tests/vkbd/ -- Gustavo Sverzut Barbieri -- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
Am Fri, 20 Jul 2007 02:04:46 +1000 schrieb David Seikel: > On Thu, 19 Jul 2007 17:46:16 +0200 Andreas Volz <[EMAIL PROTECTED]> > wrote: > > > Am Thu, 19 Jul 2007 12:27:54 +1000 schrieb David Seikel: > > > > >... > > > eflppbootstrap configure make ERROR > > >... > > > > Hm, don't know why this failed. I don't update the complete EFL each > > day. Perhaps an API changed somewhere. Do you think it's possible to > > setup a webpage with the build log (if a package failed)? > > Putting the complete build logs on the web is the plan. A link to the > web copy would also be a good idea. Still working on this, it's not > finished yet. The current results are more for comment while we work > out the details. > > I'll email this eflpp build log directly to you. Thanks. The reason was that it seems the build server doesn't build ecore_fb. eflpp doesn't check this correct and try to build it as default. > raster highly recommends that everything get updated at once. I agree > with him. If I have one two hours a day to spend for EFL programming I don't waste half of the time to setup a daily build system. So this is a risk if I update only some packages that I need. Perhaps a CVS install script would help here. Could you publish your nightly build script? regards Andreas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] entropy 20070715 fails to build
Michael Jennings wrote: > On Monday, 16 July 2007, at 08:39:27 (+0200), > Vincent Torri wrote: >> I think that the .spec file of evfs should be updated, but I don't touch >> that beast :) > > The spec files are my problem. Those who are competent with them (a > very short list, I might add) are welcome to help out, but for the > most part it's better for folks to steer clear. I speak rpm spec.. Once I get around to fixing my linux desktop, I'll see if I can help out with that. (Will probably take me a while as I'm busy nowadays) -- Cheers, Morten :wq - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
On Fri, 20 Jul 2007 02:04:46 +1000 David Seikel <[EMAIL PROTECTED]> wrote: > On Thu, 19 Jul 2007 17:46:16 +0200 Andreas Volz <[EMAIL PROTECTED]> > wrote: > > > Do you think it's possible to setup a webpage with the build log (if > > a package failed)? > > Putting the complete build logs on the web is the plan. During this testing phase, the build logs will be available at http://onefang.humbug.org.au/E-build-logs/ This is only during the initial testing phase, when it is mature enough we can move this to the real enlightenment web server. onefang.humbug.org.au is not up all of the time, but it is likely to be up most of the time. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
On Thu, 19 Jul 2007 12:18:58 -0400 dan sinclair <[EMAIL PROTECTED]> wrote: > David Seikel wrote: > > raster highly recommends that everything get updated at once. I > > agree with him. > > > > If by that you mean that the person changing the API fix everything > in cvs, that's the exact opposite of what Raster said. He said it can > take a lot of time to fix, and you should only break after the right > amount of consideration but he never said the breaker should have to > fix everything in cvs. No, I meant that cvs users should cvs update and build everything at once, not just update bits and pieces. Nothing to do with breaking APIs this time. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
David Seikel wrote: > raster highly recommends that everything get updated at once. I agree > with him. > If by that you mean that the person changing the API fix everything in cvs, that's the exact opposite of what Raster said. He said it can take a lot of time to fix, and you should only break after the right amount of consideration but he never said the breaker should have to fix everything in cvs. dan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
On Thu, 19 Jul 2007 17:46:16 +0200 Andreas Volz <[EMAIL PROTECTED]> wrote: > Am Thu, 19 Jul 2007 12:27:54 +1000 schrieb David Seikel: > > >... > > eflppbootstrap configure make ERROR > >... > > Hm, don't know why this failed. I don't update the complete EFL each > day. Perhaps an API changed somewhere. Do you think it's possible to > setup a webpage with the build log (if a package failed)? Putting the complete build logs on the web is the plan. A link to the web copy would also be a good idea. Still working on this, it's not finished yet. The current results are more for comment while we work out the details. I'll email this eflpp build log directly to you. raster highly recommends that everything get updated at once. I agree with him. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly build log for E17
Am Thu, 19 Jul 2007 12:27:54 +1000 schrieb David Seikel: >... > eflppbootstrap configure make ERROR >... Hm, don't know why this failed. I don't update the complete EFL each day. Perhaps an API changed somewhere. Do you think it's possible to setup a webpage with the build log (if a package failed)? regards Andreas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] E CVS: libs/etk-perl leviathan
On Thu, 19 Jul 2007 03:00:35 -0400 (EDT) Enlightenment CVS <[EMAIL PROTECTED]> wrote: > Enlightenment CVS committal > > Author : leviathan > Project : e17 > Module : libs/etk-perl > > Dir : e17/libs/etk-perl > > > Added Files: > autogen.sh > > > Log Message: > Added autogen.sh so it goes through the nightly build That wasn't needed, I'm going to add Makefile.PL support soon. signature.asc Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
Greetings. I'm not an E developer at all but thought I'd chime in anyways. I'm probably trying to teach the choir how to sing but it appears to me that what people seem to be looking for here, essentially, is a buildbot. [ http://en.wikipedia.org/wiki/Buildbot ] If the need is along the lines of : a. Triggering a build of specific components of the e source base in response to a commit (amongst a host of other build triggers) b. Automatic intimation to "culprit" developers, lists etc c. IRC integration for build breakages alerts (which would be cool for #e etc) d. Automated testing where appropriate ..then the buildbot sounds like a good fit. I guess this has probably been discussed in the past and shelved because of the extra work involved in setting this up (among other things) but it does sound like exactly what's needed. That said, I'm a huge fan of the easy_e17.sh project which, it appears, is the cornerstone on which the implementation being discussed currently seems to rest. Cheerio! Robin On Thu, 2007-07-19 at 10:51 +0300, Chady Kassouf wrote: > On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > > > Stashing it all on a web page means that people will not bother to look > > > at it. Sending a built/not built summary to this list means that > > > people will actually read it. Stashing the full build logs on the web > > > is good, it doesn't fill the list with tons of shit no one needs to > > > look at, and the one or two people that note that their project is not > > > building know where to find the full build log to investigate further. > > > > > Maybe the the full output could be sent to the CVS mailing list. That > > sounds a bit counterintuitive but if you think about it it's purpose is to > > alert developers of changes to the codebase. This is somewhat similar. > > > Well, not really... > when information get bigger, you will tend to start skipping it. > A summary like this is great, cause all you have to do is skim the list for > ERROR and then you'll know what broke and you go check it out, but trying to > wade through all the output of a build to find an error is painful. > > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Thu, 19 Jul 2007 10:51:13 +0300 "Chady Kassouf" <[EMAIL PROTECTED]> wrote: > On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > > > Stashing it all on a web page means that people will not bother to look > > > at it. Sending a built/not built summary to this list means that > > > people will actually read it. Stashing the full build logs on the web > > > is good, it doesn't fill the list with tons of shit no one needs to > > > look at, and the one or two people that note that their project is not > > > building know where to find the full build log to investigate further. > > > > > Maybe the the full output could be sent to the CVS mailing list. That > > sounds a bit counterintuitive but if you think about it it's purpose is to > > alert developers of changes to the codebase. This is somewhat similar. > > > Well, not really... > when information get bigger, you will tend to start skipping it. > A summary like this is great, cause all you have to do is skim the list for > ERROR and then you'll know what broke and you go check it out, but trying to > wade through all the output of a build to find an error is painful. That's probably true. However it could be shortened a bit. You could have the script output something like this: Build results: 232 passed, 5 failed. Failing modules: To see a full output of the build script please go to . Pretty please ;) I think that's short enough not to hurt anyone's eyes. > > > -- > Chady 'Leviathan' Kassouf > http://chady.net/ > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Eugen Minciu. Wasting valuable time since 1985. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > Stashing it all on a web page means that people will not bother to look > > at it. Sending a built/not built summary to this list means that > > people will actually read it. Stashing the full build logs on the web > > is good, it doesn't fill the list with tons of shit no one needs to > > look at, and the one or two people that note that their project is not > > building know where to find the full build log to investigate further. > > > Maybe the the full output could be sent to the CVS mailing list. That > sounds a bit counterintuitive but if you think about it it's purpose is to > alert developers of changes to the codebase. This is somewhat similar. Well, not really... when information get bigger, you will tend to start skipping it. A summary like this is great, cause all you have to do is skim the list for ERROR and then you'll know what broke and you go check it out, but trying to wade through all the output of a build to find an error is painful. -- Chady 'Leviathan' Kassouf http://chady.net/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
> Stashing it all on a web page means that people will not bother to look > at it. Sending a built/not built summary to this list means that > people will actually read it. Stashing the full build logs on the web > is good, it doesn't fill the list with tons of shit no one needs to > look at, and the one or two people that note that their project is not > building know where to find the full build log to investigate further. > Maybe the the full output could be sent to the CVS mailing list. That sounds a bit counterintuitive but if you think about it it's purpose is to alert developers of changes to the codebase. This is somewhat similar. Then again, I don't know ... Just my 2% of a dollar. -- Eugen Minciu. Wasting valuable time since 1985. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
