Re: [E-devel] E19 black screen on startup - how to debug?

Don't see a wizard. Will trying wiping out my cache. Someone in IRC said it might be related to this -> https://phab.enlightenment.org/T2336 On Mon, Apr 20, 2015 at 6:18 PM, Carsten Haitzler wrote: > On Mon, 20 Apr 2015 10:24:49 -0500 Jeff Hoogland > said: > > > Just rebuilt E19 with latest EF

Re: [E-devel] EAPI considered harmful

On Thu, 16 Apr 2015 21:52:37 +0200 Cedric BAIL said: > On Thu, Apr 16, 2015 at 8:25 PM, Adrien Nader wrote: > > After discussing this a bit more on #e.fr, it occurred to me the > > simplest would be to #undef EAPI at the end of headers. Basically this > > turns EAPI into a header-specific define

Re: [E-devel] E19 black screen on startup - how to debug?

On Mon, 20 Apr 2015 10:24:49 -0500 Jeff Hoogland said: > Just rebuilt E19 with latest EFL/Elementary from GIT to test if a bug had > been resolved. After updating and restarting E I am just getting a black > screen. > > Tried wiping out my ~/.e directory to no effect. How can I even go about > f

Re: [E-devel] [EGIT] [core/efl] master 01/01: ecore-drm: Remove 'defined but not used' function

On Mon, Apr 20, 2015 at 5:16 PM, Christopher Michael < cpmich...@osg.samsung.com> wrote: > On 04/20/2015 12:10 PM, Daniel Kolesa wrote: > > On Mon, Apr 20, 2015 at 4:49 PM, Christopher Michael < > devilho...@comcast.net > >> wrote: > > > >> devilhorns pushed a commit to branch master. > >> > >> >

Re: [E-devel] [EGIT] [core/efl] master 01/01: ecore-drm: Remove 'defined but not used' function

On 04/20/2015 12:10 PM, Daniel Kolesa wrote: > On Mon, Apr 20, 2015 at 4:49 PM, Christopher Michael > wrote: > >> devilhorns pushed a commit to branch master. >> >> >> http://git.enlightenment.org/core/efl.git/commit/?id=d625167e0707cca3648e9933ef65936043372447 >> >> commit d625167e0707cca3648e9933

Re: [E-devel] [EGIT] [core/efl] master 01/01: ecore-drm: Remove 'defined but not used' function

On Mon, Apr 20, 2015 at 4:49 PM, Christopher Michael wrote: > devilhorns pushed a commit to branch master. > > > http://git.enlightenment.org/core/efl.git/commit/?id=d625167e0707cca3648e9933ef65936043372447 > > commit d625167e0707cca3648e9933ef65936043372447 > Author: Chris Michael > Date: Mon

[E-devel] E19 black screen on startup - how to debug?

Just rebuilt E19 with latest EFL/Elementary from GIT to test if a bug had been resolved. After updating and restarting E I am just getting a black screen. Tried wiping out my ~/.e directory to no effect. How can I even go about figuring out what is wrong? -- ~Jeff Hoogland

Re: [E-devel] 1.15 release cycle schedule proposal

Hello. On 20/04/15 14:53, Daniel Juyung Seo wrote: > On Mon, Apr 20, 2015 at 9:25 PM, Tom Hacohen wrote: > >> On 20/04/15 13:15, Stefan Schmidt wrote: >>> Hello. >>> >>> 1.14 is one a good way now an it is about time to discuss the schedule >> for 1.15 >>> Tom approached me with a suggestion to e

Re: [E-devel] Usage of compiler #warning as a TODO

On 20/04/15 09:42, Stefan Schmidt wrote: > Hello. > > On 17/04/15 18:07, Tom Hacohen wrote: >> Hey, >> >> As you guys may have noticed, a few people have started using the >> compiler #warning directive as their public TODO. I guess it makes >> sense, because it's distributed and safer than a piece

Re: [E-devel] 1.15 release cycle schedule proposal

On Mon, Apr 20, 2015 at 9:25 PM, Tom Hacohen wrote: > On 20/04/15 13:15, Stefan Schmidt wrote: > > Hello. > > > > 1.14 is one a good way now an it is about time to discuss the schedule > for 1.15 > > > > Tom approached me with a suggestion to ease the predictability of our > release dates. > > In

Re: [E-devel] 1.15 release cycle schedule proposal

On 20/04/15 13:15, Stefan Schmidt wrote: > Hello. > > 1.14 is one a good way now an it is about time to discuss the schedule for > 1.15 > > Tom approached me with a suggestion to ease the predictability of our release > dates. > Instead of doing a schedule being aligned with the 12 weeks he sugge

[E-devel] 1.15 release cycle schedule proposal

Hello. 1.14 is one a good way now an it is about time to discuss the schedule for 1.15 Tom approached me with a suggestion to ease the predictability of our release dates. Instead of doing a schedule being aligned with the 12 weeks he suggested that we use the first Monday of a month every thre

Re: [E-devel] EFL + Elementary ABI report v1.14.0 alpha1

On 13/04/15 15:34, Tom Hacohen wrote: > On 07/04/15 16:05, Tom Hacohen wrote: >> Hey, >> >> Here again, the new EFL + Elementary ABI reports. >> >> As usual: >> https://devs.enlightenment.org/~tasn/abi/ >> >> Things look mostly OK. There are maybe some issues with data types in >> the EFL. I need t

[E-devel] EFL and friends 1.14.0 beta 2

A bunch of fresh new tarballs with our latest work waiting for your testing before we can go into the final stages of releases. = EFL, Elementary and friends 1.14 beta2 tarballs = One week after our beta1 tarballs we just released our first beta tarballs. Please grab and test. == Download == It

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Coverage increasing, bugs and coverity issues decreasing. That's how I like my stabilization weeks. This should give everyone an overview over what has happened in the last week on the QA front. The numbers in parentheses reflect the values from last week to give you a trend. C

Re: [E-devel] Work items for 1.14 stabilization phase

Hello. Thanks to everyone who already had a look at these. Updated list below. Phab issues: https://phab.enlightenment.org/T2129 EFL/ELM 1.13+ cause E19.X to segfault when changing themes https://phab.enlightenment.org/T2285 Edje_CC does not handle nbsp properly on arm / remove nbsp in whitespace

Re: [E-devel] Usage of compiler #warning as a TODO

Hello. On 17/04/15 18:07, Tom Hacohen wrote: > Hey, > > As you guys may have noticed, a few people have started using the > compiler #warning directive as their public TODO. I guess it makes > sense, because it's distributed and safer than a piece of paper. However > it's really bad, and is pol