Re: [E-devel] Time for efl-one

Hey, On 28/05/2020 15:17, Marcel Hollerbach wrote: > > Yeah, something like that was planned in the future, or building small > stubs without code that are just dragging in efl-one.so This way we do > not have to worry about platforms with problems about symlinks etc. > The problem is that the

Re: [E-devel] Time for efl-one

On 27/05/2020 12:34, Marcel Hollerbach wrote: > Hi, > > after quite a big amount of work we have successfully landed this > morning a update to our build system which enables to build efl as a > single big .so instead of multiple seperated .so's. The layout is that > every single .so is merged

Re: [E-devel] Memory optimizing EO

Hey, As discussed on IRC: all look like promising ideas, just please make sure to benchmark both speed and memory usage to make sure there are no regressions. The eo benchmark suite should already be fairly complete for speed, but there are no benchmarks for memory usage if memory serves. I'd

Re: [E-devel] EO compositing "leaking" interfaces

That's part of the problem I described in https://phab.enlightenment.org/T8184 and specifically mentioned this. Eo is doing nothing wrong, it's working as designed, it's the new restrictions that were added only to Eolian that are wrong and made things inconsistent. Eo doesn't even have a concept

Re: [E-devel] Eolian property setters with return values

On 21/10/2019 18:54, Xavi Artigas wrote: >> >> Maybe in general we need a way to mark a return/parameter as an error >> indicator? It's just a half-baked thought, though maybe worth exploring. >> > > There's already a couple of ideas on Phab in this direction: Add custom > tags to Eolian (

Re: [E-devel] Eolian property setters with return values

On 21/10/2019 18:51, Marcel Hollerbach wrote: > On 10/21/19 5:37 PM, Tom Hacohen wrote: >> I agree it's most of them, though it's not all of them. IIRC there are >> some that indicate "nothing happened", at least in textblock. It >> shouldn't be too hard t

Re: [E-devel] Eolian property setters with return values

I agree it's most of them, though it's not all of them. IIRC there are some that indicate "nothing happened", at least in textblock. It shouldn't be too hard to fix these though. Maybe in general we need a way to mark a return/parameter as an error indicator? It's just a half-baked thought,

Re: [E-devel] RFC: Text interface + advice regarding interface splitting

yet. >> >>> - You have a few places where you have explicitly x,y,w,h (x,y) in your >>> API, can you replace them with rect (position) handles from eina, that >>> would make it more aligned with the rest of efl. >>> >> >> Could you please provid

[EGIT] [editors/vim-configs] master 01/01: Update according to eolian changes.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/vim-configs.git/commit/?id=d3d028da20afd7118eb0e5c99446db6b10a158c1 commit d3d028da20afd7118eb0e5c99446db6b10a158c1 Author: Tom Hacohen Date: Tue Oct 1 17:40:12 2019 +0300 Update according to eolian changes

Re: [E-devel] RFC: Text interface + advice regarding interface splitting

ina, that > would make it more aligned with the rest of efl. > Could you please provide an example? Thanks! -- Tom > Greetings, >    bu5hm4n > > On 9/19/19 4:15 PM, Tom Hacohen wrote: >> Hey, >> >> As most of you (at least the IRC lurkers) know, I've been r

[E-devel] RFC: Text interface + advice regarding interface splitting

Hey, As most of you (at least the IRC lurkers) know, I've been recently working on the text interfaces. Trying to clean them up and stabilise them. The discussion and work has been covered on phab at: https://phab.enlightenment.org/T8151 And the new (suggested) interfaces are all the files

[EGIT] [editors/vim-configs] master 01/01: eolian: update vim synatx file based on recent eolian changes.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/vim-configs.git/commit/?id=c2ebd6aae1da03bd1d74f8296fbc8dc09e0c68f8 commit c2ebd6aae1da03bd1d74f8296fbc8dc09e0c68f8 Author: Tom Hacohen Date: Wed Aug 28 15:32:44 2019 +0100 eolian: update vim synatx file based

[EGIT] [editors/vim-configs] master 01/01: Eolian: update according to eolian changes and fix implements/extends.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/vim-configs.git/commit/?id=8779a31d4af1342264afc455674bca737ecdc828 commit 8779a31d4af1342264afc455674bca737ecdc828 Author: Tom Hacohen Date: Mon Aug 19 12:52:30 2019 +0100 Eolian: update according to eolian

[EGIT] [editors/vim-configs] master 01/01: eolian: update vim synatx file based on recent eolian changes.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/vim-configs.git/commit/?id=f6e51963a4746cbb854ae351fe22be8e077a4aea commit f6e51963a4746cbb854ae351fe22be8e077a4aea Author: Tom Hacohen Date: Fri Aug 16 17:35:35 2019 +0100 eolian: update vim synatx file based

[EGIT] [core/efl] master 01/01: Evas: migrate Evas_BiDi_Direction -> Efl_Text_Bidirectional_Type.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=84e06f7234335836d175cb1583aa91f183b98803 commit 84e06f7234335836d175cb1583aa91f183b98803 Author: Tom Hacohen Date: Wed Aug 7 14:54:45 2019 +0100 Evas: migrate Evas_BiDi_Direction

Re: [E-devel] Discussions here.

On 05/09/2019 14:41, Carsten Haitzler (The Rasterman) wrote: > On Thu, 5 Sep 2019 20:28:50 +0900 Hermet Park said: > >> I think it's just preference problem. >> >> Anyhow, I prefer e-devel discussion >> >> But both are fine to me because both do functions enough. > > phab can't thread so it

Re: [E-devel] Discussions here.

Hey, That's something I've been complaining about both on IRC and recently on phab too, so glad to see you take action about it! It's really hard to follow what's going on in the EFL world if you just want to follow the high-level design discussions rather than every typo fix patch / bug. I

Re: [E-devel] Discussions here.

Hey, That's something I've been complaining about both on IRC and recently on phab too, so glad to see you take action about it! It's really hard to follow what's going on in the EFL world if you just want to follow the high-level design discussions rather than every typo fix patch / bug. I

Re: [E-devel] FOSDEM 2019

Hey, I'll be there! Looking forward to seeing everyone! -- Tom On Thu, Dec 20, 2018 at 11:25 AM Daniel Zaoui wrote: > > Hi guys, > > FOSDEM is coming! A little more than one month! I plan to come. Are there > other folks that come too? > > Are there good, cheap and close-to-the-center hotels

Re: [E-devel] Gitlab

I'm all in favour moving to a self-hosted Gitlab instance. Phabricator is pretty awful and is not very approachable. Also, Gitlab has really overtaken Phab in both popularity and maturity in the last 5 years since we switched. This will also reduce the admin burden of managing Gitolite, and

Re: [E-devel] FOSDEM

I'm also coming. Want to book my travel. When is everyone getting there/leaving? I'm thinking doing Friday - Sunday? -- Tom On 17 Dec 2017 15:01, "Carsten Haitzler" wrote: > On Wed, 22 Nov 2017 18:02:56 + Andrew Williams > said: > > > Hi, > > >

Re: [E-devel] FOSDEM 2017

This one is from last year. ;) On 17 Dec 2017 15:01, "Carsten Haitzler" wrote: > On Mon, 5 Dec 2016 14:09:00 +0100 Philippe Caseiro < > caseiro.phili...@gmail.com> > said: > > didn't submit... but i'm coming. :) > > > Hi, falks > > > >Sorry for the late notice I had

Re: [E-devel] Git Feature/ Proposal

I meant that you *should* configure something like this. I don't remember if it was per project or global, but I remember there was something. -- Tom. On Thu, Nov 30, 2017 at 7:46 AM, Stefan Schmidt <ste...@osg.samsung.com> wrote: > Hello. > > > On 11/29/2017 06:04 PM, Tom Hac

Re: [E-devel] Git Feature/ Proposal

by people pulling other devs branches, and then >> rebasing >> >> onto master in their own dev branch. >> >> >> >> Rewriting history on a shared branch has major downsides too. No problem >> >> for dev branches as there's only one committer, but any

Re: [E-devel] Git Feature/ Proposal

kra...@gmail.com> wrote: > In the issue where a significant rebase against master is necessary then > it's trivial enough to either push to a new feature branch or delete and > re-create the existing branch. > > On Tue, Nov 21, 2017 at 1:36 PM Tom Hacohen <t...@stosb.com> wrote: > &g

Re: [E-devel] Git Feature/ Proposal

e merge to/from master? >> Usually when we merge a branch to master, we rebase it on top of master >> first and then rebase. That's how our history remains linear and simple. >> >> What's the idea here? I wonder. >> >> Thanks for implementing this btw, >

Re: [E-devel] Git Feature/ Proposal

te: > I've added all the necessary info to the documentation at > https://www.enlightenment.org/contrib/devs/git-guide.md#Feature_Branches > > If the jenkins concept is not possible then feel free to remove, but the > rest should be in line with what we want. > > On Mon, N

Re: [E-devel] Terminology, one of the coolest linux terminal emulators

Very nice. On Mon, Nov 20, 2017 at 10:24 PM, Boris Faure wrote: > Hi :) > > Linux.com published an article [1] on the top 5 coolest linux terminal > emulators. > Terminology is nicely described there. You shall all be proud of it > and the great work on EFL! > > Thanks! > > 1.

Re: [E-devel] Git Feature/ Proposal

delete? > > Good point. these need deletion. after a few years it'll be a mess of old > feature branches no one will ever look at again. The merge to master should > contain all the history and log that is needed at that point for history > digging. > >> * do probies get feature/ p

Re: [E-devel] Git Feature/ Proposal

Yeah, good idea. I'll take a look into implementing it soon. On Tue, Nov 7, 2017 at 8:50 PM, Andrew Williams wrote: > Hi, > > That sounds great - the ability to work together on features off-master > would be really helpful. > > Andy > > On Tue, 7 Nov 2017 at 16:15, Mike

Re: [E-devel] GitFlow

you personally, but for us to be basing > any decision on the above statement is, at this time, nothing more than a > false premise (https://en.wikipedia.org/wiki/False_premise) argument. > > On Thu, Oct 26, 2017 at 8:39 AM Tom Hacohen <t...@stosb.com> wrote: > >> I acci

Re: [E-devel] GitFlow

this will make it slightly more compatible for you, and actually makes sense regardless (was a mistake in the first place). -- Tom On Thu, Oct 26, 2017 at 1:20 PM, Tom Hacohen <t...@stosb.com> wrote: > It is possible, yes. > > On Thu, Oct 26, 2017 at 10:50 AM, Carsten Haitzler &

Re: [E-devel] GitFlow

y person looking to take >> > up >> > > > development has to configure it before getting started, so the >> > defaults are >> > > > best if possible. >> > > > >> > > > I appreciate that consistency is important but taken s

[E-devel] E git administrators

Hey, I added zmike as an admin to our Git infrastructure. He rightfully pointed out that we currently have no representation in his timezone (America), and that our bus factor is kind of low. Just wanted to post it here so everyone is aware. The list of mostly available git admins is thus:

Re: [E-devel] GitFlow

Heya, I don't quite understand what you are trying to do here. I mean, I understand you are trying to have these, but what are these branches for? If it's for you developing your own features why not put it in a dev branch? We have these enforcements because we want to enforce branch names to

Re: [E-devel] Taking over as maintainer of ecrire

Replying to both of you in one go. On Wed, May 10, 2017 at 1:38 AM, Simon Lees <sfl...@suse.de> wrote: > > > On 05/10/2017 08:39 AM, William L. Thomson Jr. wrote: >> I finally got in touch with Tom Hacohen/tasn. Turns out IRC was best >> form, as phab and mailing list w

Re: [E-devel] edevelop.slack.com experiment

Heya, I personally think it's a bad idea to rely on a proprietary tool for open source development, and from what I remember, I'm not the only one. This is partially why we self host git and not use Github et al. Long live IRC. https://xkcd.com/1782/ -- Tom On Tue, Mar 21, 2017 at 2:52 PM,

Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

On 20/12/16 11:03, Gustavo Sverzut Barbieri wrote: > On Mon, Dec 19, 2016 at 11:05 PM, Jean-Philippe André > wrote: >> Hi, >> >> On 19 December 2016 at 21:10, Gustavo Sverzut Barbieri >> wrote: >> >>> Hi all, >>> >>> In Efl.Net I've created couple of

[EGIT] [core/efl] master 01/01: Eo: remove unreachable code in isa.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=78bbd29720ea21cda59ec96ddba9aa1f165ccba0 commit 78bbd29720ea21cda59ec96ddba9aa1f165ccba0 Author: Tom Hacohen <t...@stosb.com> Date: Thu Dec 15 11:18:24 2016 + Eo: remove unreachable code

Re: [E-devel] [E-b0rk] Build failed in Jenkins: nightly_efl_gcc_x86_64 #1417

On 13/12/16 10:26, Stefan Schmidt wrote: > Hello. > > On 13/12/16 02:15, Gustavo Sverzut Barbieri wrote: >> Stefan, >> >> Could you check the environment where the test runs? In the log >> https://build.enlightenment.org/job/nightly_efl_gcc_x86_64/ws/src/test-suite.log >> I see: >> >> WARNING:

Re: [E-devel] [EGIT] [core/efl] master 01/01: elementary: atspi accepts UTF-8 text

Based on your commit message, your change looks wrong. Atspi accepts utf-8 not markup, it should be passed utf-8 without the markup. I think the code that was there was correct, but furthermore, this code was just recently put there to fix an issue, so please speak to whoever added it. Also,

Re: [E-devel] eo_isa() buggy

On 07/12/16 20:18, Gustavo Sverzut Barbieri wrote: > On Wed, Dec 7, 2016 at 12:00 PM, Tom Hacohen <t...@osg.samsung.com> wrote: >> Hey, >> >> I just pushed 5424cdbd810042ba59e71bec6b8d91cb6a2c3e9c that I hope >> should fix it. This commit fixes a bug I've kno

[EGIT] [core/efl] efl-1.16 01/02: Eo gdb: Add workaround for gdb oddities.

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=1a39c10ccbbe9be8e92165268e06329c2ccd2649 commit 1a39c10ccbbe9be8e92165268e06329c2ccd2649 Author: Tom Hacohen <t...@stosb.com> Date: Thu Dec 8 11:03:25 2016 + Eo gdb: Add workaround f

[EGIT] [core/efl] master 01/01: Eo gdb: Add workaround for gdb oddities.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=874071ca42d59d0870b2f7055c15d878cbdf1368 commit 874071ca42d59d0870b2f7055c15d878cbdf1368 Author: Tom Hacohen <t...@stosb.com> Date: Thu Dec 8 11:03:25 2016 + Eo gdb: Add workaround f

[EGIT] [core/efl] efl-1.16 02/02: Eo gdb: Fix data_get calculation.

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=46d08ae4152210c8aa7a34dd1acea812f68b9bda commit 46d08ae4152210c8aa7a34dd1acea812f68b9bda Author: Tom Hacohen <t...@stosb.com> Date: Thu Dec 8 11:15:21 2016 + Eo gdb: Fix data_get calcu

Re: [E-devel] eo_isa() buggy

Hey, I just pushed 5424cdbd810042ba59e71bec6b8d91cb6a2c3e9c that I hope should fix it. This commit fixes a bug I've known for a while and just forgot to fix. From your description, I believe it is the same issue, but please verify. Thanks for reporting. -- Tom. On 07/12/16 02:14, Gustavo

[EGIT] [core/efl] master 01/01: Eo: Fix efl_isa() sometimes returning wrong results with extensions

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=5424cdbd810042ba59e71bec6b8d91cb6a2c3e9c commit 5424cdbd810042ba59e71bec6b8d91cb6a2c3e9c Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 13:55:13 2016 + Eo: Fix efl_isa() som

[EGIT] [core/efl] master 02/02: Eo tests: Adjust according to latest commit.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=900b1726e6c8205c8f6c9c74ffa6579e2c15809f commit 900b1726e6c8205c8f6c9c74ffa6579e2c15809f Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 13:18:41 2016 + Eo tests: Adjust acc

[EGIT] [core/efl] efl-1.16 01/02: Eo gdb: Implement eo_data_get to get eo data.

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=7492b67e65b48a7835c5fee671b181803a7e5896 commit 7492b67e65b48a7835c5fee671b181803a7e5896 Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 12:33:59 2016 + Eo gdb: Implement eo_da

[EGIT] [core/efl] efl-1.16 02/02: Eo gdb: Be more strict with types and convert Eo * to uintptr_t.

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=692276ad548eb6d00ffbc399c9af3226574342af commit 692276ad548eb6d00ffbc399c9af3226574342af Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 12:50:52 2016 + Eo gdb: Be more strict with

[EGIT] [core/efl] master 02/02: Eo gdb: Be more strict with types and convert Eo * to uintptr_t.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=ddf940320dba33e9b3e52aa5ba4ddc1b8ca1c499 commit ddf940320dba33e9b3e52aa5ba4ddc1b8ca1c499 Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 12:50:52 2016 + Eo gdb: Be more strict with

[EGIT] [core/efl] master 01/02: Eo gdb: Implement eo_data_get to get eo data.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=5614e46f1f01aa02a779358177907fc08223f3ac commit 5614e46f1f01aa02a779358177907fc08223f3ac Author: Tom Hacohen <t...@stosb.com> Date: Wed Dec 7 12:33:59 2016 + Eo gdb: Implement eo_da

[EGIT] [core/efl] master 01/01: Static deps unibreak: Update to latest version.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=abb7310506ce825404788b7674f2bf3961c9df45 commit abb7310506ce825404788b7674f2bf3961c9df45 Author: Tom Hacohen <t...@stosb.com> Date: Tue Dec 6 12:45:40 2016 + Static deps unibreak:

Re: [E-devel] [EGIT] [core/efl] master 03/03: eo: if EO_DEBUG, check if efl_super() object 'isa' the given class.

This is wrong, and as JP and Stefan said, breaks things. First of all, why add code to the non-debug variation? Also, if you're already adding to the non-debug variation, why not include it in the commit message? This is very misleading. Anyhow, as the tests clearly show, efl_super() is also

Re: [E-devel] [EGIT] [core/efl] master 02/05: Eo: Add efl_replace() function.

I never liked the stringshare function that does it, so it comes with no surprise that I don't like this one either. Regardless of that, I find the name very confusing. I didn't understand what it does when I saw the name nor when I read the docs. I had to read the code to understand what it's

[EGIT] [core/efl] master 01/01: Emacs config: Also remove from extra_dist.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=3302ce54998ab66adeddbe273cf105309061a809 commit 3302ce54998ab66adeddbe273cf105309061a809 Author: Tom Hacohen <t...@stosb.com> Date: Mon Dec 5 12:35:40 2016 + Emacs config: Also remov

[EGIT] [editors/emacs-configs] master 01/01: Initial import for emacs config files.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/emacs-configs.git/commit/?id=aa190cb127749c90392b7b1288758ba0ee422b95 commit aa190cb127749c90392b7b1288758ba0ee422b95 Author: Tom Hacohen <t...@stosb.com> Date: Mon Dec 5 12:34:21 2016 + Initial

[EGIT] [core/efl] master 01/01: Emacs configs: Move to designated repo.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=92f8e013eaa62da6658556924f9a08cf31c75565 commit 92f8e013eaa62da6658556924f9a08cf31c75565 Author: Tom Hacohen <t...@stosb.com> Date: Mon Dec 5 12:34:43 2016 + Emacs configs: Move to desi

[EGIT] [core/efl] efl-1.16 02/02: Eo gdb: add a way to resolve Eo ids from GDB without a running process

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=34efbca16e954d994a26d730753b8fbd1d4a37ec commit 34efbca16e954d994a26d730753b8fbd1d4a37ec Author: Tom Hacohen <t...@stosb.com> Date: Fri Nov 18 08:44:21 2016 + Eo gdb: add a way to reso

[EGIT] [core/efl] efl-1.16 01/02: Eo gdb: remove old and broken gdb macro.

tasn pushed a commit to branch efl-1.16. http://git.enlightenment.org/core/efl.git/commit/?id=0a278f566ab60bd63da02670937c4c4b11ff8052 commit 0a278f566ab60bd63da02670937c4c4b11ff8052 Author: Tom Hacohen <t...@stosb.com> Date: Fri Nov 18 07:31:39 2016 + Eo gdb: remove old and

[EGIT] [core/efl] master 01/01: Eo gdb: Remove redundant variable setting.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=0431dd24fd971149878ccbfb48c87f500d9b027c commit 0431dd24fd971149878ccbfb48c87f500d9b027c Author: Tom Hacohen <t...@stosb.com> Date: Mon Dec 5 12:06:20 2016 + Eo gdb: Remove redundant va

[EGIT] [core/efl] master 01/02: Eo gdb: remove old and broken gdb macro.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=3dd51bf53de9003e0e3ba396a5c0f2b10c44c1fd commit 3dd51bf53de9003e0e3ba396a5c0f2b10c44c1fd Author: Tom Hacohen <t...@stosb.com> Date: Fri Nov 18 07:31:39 2016 + Eo gdb: remove old and brok

[EGIT] [core/efl] master 02/02: Eo gdb: add a way to resolve Eo ids from GDB without a running process

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=79d76fb25ece4ffbf5785b4be2b030f062ef9f2c commit 79d76fb25ece4ffbf5785b4be2b030f062ef9f2c Author: Tom Hacohen <t...@stosb.com> Date: Fri Nov 18 08:44:21 2016 + Eo gdb: add a way to reso

Re: [E-devel] [EGIT] [core/enlightenment] master 02/03: Merge branch 'master' of git+ssh://git.enlightenment.org/core/enlightenment

I was away, so the reply is a bit late, but: you should "git log" or better yet: "git log --graph" before you push to make sure it does what you intended. Furthermore, always do "git pull --rebase", not "git pull". You can change this as a setting. -- Tom. On 02/11/16 11:50, Stephen Houston

Re: [E-devel] EDD 2017 location discussion

On 01/11/16 10:51, Stefan Schmidt wrote: > Hello. > > On 01/11/16 11:19, Tom Hacohen wrote: >> And London, we can probably get hosting at the London hackspace, if not, >> there are more options. With the pound as low as it is, it's going to be >> like going to a 3rd worl

Re: [E-devel] EDD 2017 location discussion

t; I'm happy to organise and I think CodeBase (the tech incubator I am in) > will provide event space if we book far enough ahead. > > I'll update phab, > Andy > On Tue, 1 Nov 2016 at 10:11, Tom Hacohen <t...@osg.samsung.com> wrote: > >> On 01/11/16 09:58, Stefan Schmid

Re: [E-devel] EDD 2017 location discussion

evelopers from there > - To high travel costs for many attendees > - We did it once on the west coast and sadly almost only people with > company baking attended > - Meeting space offering is missing > > > Tel Aviv (proposed by Tom Hacohen) > * Local organiser: Non

[EGIT] [core/efl] master 02/02: Input events cache: use the new mechanism to reuse eo objects.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=f2e049c81853d4f1a57b61d57688248c3da4 commit f2e049c81853d4f1a57b61d57688248c3da4 Author: Tom Hacohen <t...@stosb.com> Date: Fri Oct 28 13:20:56 2016 +0100 Input events cache: use t

[EGIT] [core/efl] master 01/02: Eo: Add a method to mark objects for reuse.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=f736946d10d519fe959bef84914e4ca3d91e7db8 commit f736946d10d519fe959bef84914e4ca3d91e7db8 Author: Tom Hacohen <t...@stosb.com> Date: Fri Oct 28 13:19:10 2016 +0100 Eo: Add a method to mark o

[EGIT] [core/efl] master 02/03: Eo: Fix references of objects

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=25242e6af9b44ce0b31c66396ba1afbc75bb29a8 commit 25242e6af9b44ce0b31c66396ba1afbc75bb29a8 Author: Tom Hacohen <t...@stosb.com> Date: Fri Oct 21 15:02:27 2016 +0100 Eo: Fix references of o

[EGIT] [core/efl] master 01/03: Eo test: Fix cleanup of objects.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=6c8489c3b76ab1d5548e7786c9b7e6fcfddba581 commit 6c8489c3b76ab1d5548e7786c9b7e6fcfddba581 Author: Tom Hacohen <t...@stosb.com> Date: Fri Oct 21 15:18:46 2016 +0100 Eo test: Fix cleanup of o

[EGIT] [core/efl] master 03/03: Eo: Add test for refcount in efl_add_ref

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=047d88caa00db9e9b31c88682703462d0d6fa201 commit 047d88caa00db9e9b31c88682703462d0d6fa201 Author: Tom Hacohen <t...@stosb.com> Date: Fri Oct 21 15:25:52 2016 +0100 Eo: Add test for re

Re: [E-devel] Repos sending mails to git@lists

On 20/10/16 20:50, Bruno Dilly wrote: > Hey guys, > > I realized apparently changes on apps/eruler are not sent to our git mails > list. > > How is it managed? Do we have a list of repos with hooks to send emails to > such list? Could you guys please add eruler to this list? > > Thanks in advance

[EGIT] [core/efl] master 02/03: Eo: Fix reference leak when failing to resolve function.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=5a659fafd22de295f8a4fb276e343f0da870779f commit 5a659fafd22de295f8a4fb276e343f0da870779f Author: Tom Hacohen <t...@stosb.com> Date: Wed Oct 19 16:14:15 2016 +0100 Eo: Fix reference lea

[EGIT] [core/efl] master 03/03: Eo: Add a regression test for ref leak in function resolve

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=d952b350982aa8ad7575fcceec18d0075034b41c commit d952b350982aa8ad7575fcceec18d0075034b41c Author: Tom Hacohen <t...@stosb.com> Date: Wed Oct 19 16:20:19 2016 +0100 Eo: Add a regression test f

[EGIT] [core/efl] master 01/03: Eo: Remove no longer relevant tests.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=f4eb94a7d8d2b57cc7856596e6489c339482e9dd commit f4eb94a7d8d2b57cc7856596e6489c339482e9dd Author: Tom Hacohen <t...@stosb.com> Date: Wed Oct 19 16:14:03 2016 +0100 Eo: Remove no longer re

Re: [E-devel] Server De spanking is required

Sorry, I misread what you wrote! We could maybe put the link to my mirror somewhere? Though I doubt that would be helpful, and I'm not in favour of making it "official". On 17/10/16 13:53, Andrew Williams wrote: > Agreed, that's what I meant > On Mon, 17 Oct 2016 at 13:40

Re: [E-devel] Server De spanking is required

On 09/10/16 10:15, Jonathan Aquilina wrote: > Hi Carsten, > > I think a good way forward would be to get a small server, I would even > be willing to sponsor a vps and use puppet. It would make automation > deployments and system management alot easier. I am going to be setting > up puppet for my

Re: [E-devel] Server De spanking is required

On 16/10/16 00:40, Andrew Williams wrote: > Right now if we continue to have issues it seems a lot like GitHub or other > services may be more available than our own? > Things have come a long way since sourceforge. > > Andy > > P.s. If we advertise an automated clone all it means is someone

Re: [E-devel] Server Down

This is actually not an Einstein quote, just commonly and falsely attributed to him. :) On 17/10/16 12:57, Stephen Houston wrote: > Hey Einstein... how dare you question Einstein!! :-) > > On Mon, Oct 17, 2016, 6:54 AM Tom Hacohen <t...@osg.samsung.com> wrote: > >> On

Re: [E-devel] Server Down

On 15/10/16 17:11, Stephen Houston wrote: > This is getting REALLY annoying at how often this happens and never gets > fixed. Insanity is defined as doing the same thing over and over expecting > a different result. > Not the definition of insanity[1]. 1: https://en.wikipedia.org/wiki/Insanity

Re: [E-devel] github mirror

On 09/10/16 13:08, Vincent Torri wrote: > Hey > > responding to > https://www.mail-archive.com/enlightenment-devel@lists.sourceforge.net/msg87948.html, > i can also have a mirror of the EFL and E, and others > > I also usually setup my projects or projects I'm working on with > drone.io, with

[EGIT] [editors/vim-configs] master 01/01: Eo: Add ref tag.

tasn pushed a commit to branch master. http://git.enlightenment.org/editors/vim-configs.git/commit/?id=8a6682cb492cf1b739160374713ac0968b72b3fd commit 8a6682cb492cf1b739160374713ac0968b72b3fd Author: Tom Hacohen <t...@stosb.com> Date: Fri Sep 30 15:08:42 2016 +0100 Eo: Add r

Re: [E-devel] EFL interface, what's left to be done

On 24/09/16 02:59, Cedric BAIL wrote: > On Thu, Sep 22, 2016 at 4:35 AM, Tom Hacohen <t...@osg.samsung.com> wrote: >> On 22/09/16 00:34, Cedric BAIL wrote: >>> On Wed, Sep 21, 2016 at 1:46 AM, Tom Hacohen <t...@osg.samsung.com> wrote: >>>> On 19/09/16 23:3

Re: [E-devel] EFL interface, what's left to be done

On 24/09/16 10:07, marcel-hollerb...@t-online.de wrote: > On Fri, Sep 23, 2016 at 06:59:14PM -0700, Cedric BAIL wrote: >> On Thu, Sep 22, 2016 at 4:35 AM, Tom Hacohen <t...@osg.samsung.com> wrote: >>> On 22/09/16 00:34, Cedric BAIL wrote: >>>> On Wed, Sep

Re: [E-devel] [YAPT] Promise instant resolution

On 29/09/16 17:03, Gustavo Sverzut Barbieri wrote: > Next mainloop iteration is essential to make user code "always work", no > special cases. > > This was in my other thread commentary about "resolved promise", that is, > to return a promise with a well known (resolved) value I completely agree,

Re: [E-devel] Efl_Promise and Efl_Future

On 13/09/16 01:09, Cedric BAIL wrote: > On Mon, Sep 12, 2016 at 2:11 AM, Tom Hacohen <t...@osg.samsung.com> wrote: >> On 08/09/16 23:29, Cedric BAIL wrote: >>> So I have now landed Efl_Future and Efl_Promise as previously >>> discussed in a lengthy email thread

Re: [E-devel] Efl_Promise and Efl_Future

On 28/09/16 13:42, Tom Hacohen wrote: > On 21/09/16 03:35, Felipe Magno de Almeida wrote: >> On Sun, Sep 18, 2016 at 3:35 AM, Davide Andreoli <d...@gurumeditation.it> >> wrote: >>> 2016-09-18 4:30 GMT+02:00 Felipe Magno de Almeida < >>> felipe.m.alme..

Re: [E-devel] Efl_Promise and Efl_Future

On 21/09/16 03:35, Felipe Magno de Almeida wrote: > On Sun, Sep 18, 2016 at 3:35 AM, Davide Andreoli > wrote: >> 2016-09-18 4:30 GMT+02:00 Felipe Magno de Almeida < >> felipe.m.alme...@gmail.com>: >>> On Sep 17, 2016 3:53 AM, "Davide Andreoli"

[EGIT] [core/efl] master 01/01: Ecore promise: Renamed shadow variable.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=65367a4a076b9bfb4b3d58bdc87c2f5f677c8b70 commit 65367a4a076b9bfb4b3d58bdc87c2f5f677c8b70 Author: Tom Hacohen <t...@stosb.com> Date: Mon Sep 26 14:50:08 2016 +0100 Ecore promise: Renamed

[EGIT] [core/efl] master 01/02: Eo: introducing libeo_dbg.so.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=b242f50626c57212d2b6525d8bddc8f0595971f4 commit b242f50626c57212d2b6525d8bddc8f0595971f4 Author: Tom Hacohen <t...@stosb.com> Date: Thu Sep 22 13:16:18 2016 +0100 Eo: introducing libeo_

[EGIT] [core/efl] master 02/02: Update gitignore.

tasn pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=04f1483a82a2537c568e44cb55f06a61b2d6a839 commit 04f1483a82a2537c568e44cb55f06a61b2d6a839 Author: Tom Hacohen <t...@stosb.com> Date: Thu Sep 22 14:07:44 2016 +0100 Update gitignore. --- .git

Re: [E-devel] EFL interface, what's left to be done

On 22/09/16 00:34, Cedric BAIL wrote: > On Wed, Sep 21, 2016 at 1:46 AM, Tom Hacohen <t...@osg.samsung.com> wrote: >> On 19/09/16 23:33, Cedric BAIL wrote: >>> On Mon, Sep 19, 2016 at 2:48 PM, Tom Hacohen <t...@stosb.com> wrote: >>>> We haven't agreed

Re: [E-devel] EFL interface, what's left to be done

On 22/09/16 07:55, Jean-Philippe André wrote: > Hi, > > On 22 September 2016 at 15:34, Davide Andreoli <d...@gurumeditation.it> > wrote: > >> 2016-09-22 0:45 GMT+02:00 Gustavo Sverzut Barbieri <barbi...@gmail.com>: >> >>> On Wed, Sep 21, 201

Re: [E-devel] EFL interface, what's left to be done

On 21/09/16 15:10, Gustavo Sverzut Barbieri wrote: > On Wed, Sep 21, 2016 at 5:26 AM, Tom Hacohen <t...@osg.samsung.com> wrote: > [...] >>> promise/future should be first-class citizen... as well as iterator >>> and the likes. There is a start already, but refinem

Re: [E-devel] EFL interface, what's left to be done

On 19/09/16 23:33, Cedric BAIL wrote: > On Mon, Sep 19, 2016 at 2:48 PM, Tom Hacohen <t...@stosb.com> wrote: >> We haven't agreed on merging Eo, Efl and Ecore. I'm actually pretty much >> against it. > > There was a thread weeks ago. You indeed didn't take part of that

Re: [E-devel] EFL interface, what's left to be done

On 20/09/16 05:14, Gustavo Sverzut Barbieri wrote: > On Mon, Sep 19, 2016 at 7:33 PM, Cedric BAIL <cedric.b...@free.fr> wrote: >> On Mon, Sep 19, 2016 at 2:48 PM, Tom Hacohen <t...@stosb.com> wrote: >>> We haven't agreed on merging Eo, Efl and Ecore. I'm ac

Re: [E-devel] [EGIT] [core/efl] master 01/01: tests: ecore: relax the timing precision for the promise timeout test

On 20/09/16 00:30, Carsten Haitzler (The Rasterman) wrote: > On Mon, 19 Sep 2016 13:18:47 +0100 Tom Hacohen <t...@osg.samsung.com> said: > >> On 19/09/16 13:08, Stefan Schmidt wrote: >>> stefan pushed a commit to branch master. >>> >>> http://

Re: [E-devel] EFL interface, what's left to be done

We haven't agreed on merging Eo, Efl and Ecore. I'm actually pretty much against it. Eo is clean and hasn't been "polluted" by async, mainloop and etc. That's a good thing. This makes our infrastructure easier to test. If you mean just compile them together, then there's no point in it. I know why

Re: [E-devel] [EGIT] [core/efl] master 01/01: tests: ecore: relax the timing precision for the promise timeout test

On 19/09/16 14:01, Stefan Schmidt wrote: > Hello. > > On 19/09/16 14:18, Tom Hacohen wrote: >> On 19/09/16 13:08, Stefan Schmidt wrote: >>> stefan pushed a commit to branch master. >>> >>> http://git.enlightenment.org/core/efl.git/commit/?id=c25d4e8325b42

  1   2   3   4   5   6   7   8   9   10   >