Gustavo wrote:
> On Thu, Oct 30, 2008 at 9:51 AM, Nicolas Aguirre
> <[EMAIL PROTECTED]> wrote:
>
>> 2008/10/30 Jose Gonzalez <[EMAIL PROTECTED]>
>>
>>>> This last mail that request users to do power-of-2 on their side is as
>>>
Gustavo wrote:
> On Thu, Oct 30, 2008 at 7:05 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> And btw, why would one be so foolish, when implementing the size-load-opts
>> down-scaling for jpgs, that they would simply software down-scale all the way
>> from the
>> ...
>>
>>> that. if we ALWAYS scaled to the EXACT SIZE requested - we would be forced
>>> to
>>> always do it in software (as part of the generic loader) AND we now need to
>>> also add flags as to if you want raw speed (nearest sampling) or filtered
>>> scaling too - so it adds to th
I wrote:
> ...
>> that. if we ALWAYS scaled to the EXACT SIZE requested - we would be forced to
>> always do it in software (as part of the generic loader) AND we now need to
>> also add flags as to if you want raw speed (nearest sampling) or filtered
>> scaling too - so it adds to the api,
>>> I wonder if it's not better to make their thumbnailer suck less (dump
>>> jpg thumbnailer, use code from EPEG or Evas) instead of adding all
>>> this complexity.
>>>
>>> And still we cannot select custom thumbnail sizes, so useless for
>>> media centers and lots of fancy systems that might cho
Gustavo wrote:
> I wonder if it's not better to make their thumbnailer suck less (dump
> jpg thumbnailer, use code from EPEG or Evas) instead of adding all
> this complexity.
>
> And still we cannot select custom thumbnail sizes, so useless for
> media centers and lots of fancy systems that mig
Jorge wrote:
> Hi all,
>
> Here i attach a patch that wraps all the calls to
> obj->layer->evas->engine.func inside the objects into a function
> itself. So instead of doing evas->engine.func->image_border_set you
> should call evas_engine_image_border_set. It looks like a cosmetic
> patch, but
Gustavo wrote:
>
>
Ok, let me pose this this from a different view.. let's not worry about
whether
or not such 'layout' or 'widgetry' or 'special-purpose' or whatever kinds
of
objects
should be added to the evas lib *api* -- I don't think they should in
Gustavo wrote:
> On Tue, Oct 28, 2008 at 6:05 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Gustavo wrote:
>>
>>
>>>>> This code is part of our effort to unify common code into base libs,
>>>>> where its worth to avoid du
I wrote:
>Ok, let me pose this this from a different view.. let's not worry about
> whether
> or not such 'layout' or 'widgetry' or 'special-purpose' or whatever kinds of
> objects
> should be added to the evas lib *api* -- I don't think they should in some
> cases,
> but that's partly i
Gustavo wrote:
>>> This code is part of our effort to unify common code into base libs,
>>> where its worth to avoid duplicating code over and over again.
>>>
>>> With that in Evas, we can now expose it in Edje and use it in Guarana
>>> and Elementary and possible any other toolkit. It uses Eva
Gustavo wrote:
> On Mon, Oct 27, 2008 at 12:22 AM, Enlightenment SVN
> <[EMAIL PROTECTED]> wrote:
>
>> Log:
>> add evas_object_box.
>>
>> Box is a smart object to help with the common task of laying out lots
>> of objects. It's very flexibile and one can customize the layout
>> function
>> I think the vote is over. The result from
>> http://www.misterpoll.com/polls/362996/results collected the opinion
>> of 52 people. So I will stick with this result (and staying with eina,
>> is sadly not an opinion). So I am going to rename eina with enema next
>> week.
>>
>>
> You're kidd
I wrote:
>
>
>What would be 'nice', and is doable now, would be the basics of
> custom objs.
> ie. separately declared objs (ie. their apis) which the lib could load..
> even if their
> implementation would be much like what is done now and would still depend
> on knowing evas int
using freetype directly probably.
Again, this is easier to do IMO. Doing that inside Evas will be bit
harder I guess, maybe not because engine stuff remains unchanged
you know better than me, does it worth to have such restricted-use
object built-in in Evas?
Carsten wrote:
> On Sun, 19 Oct 2008 22:26:05 -0200 "Gustavo Sverzut Barbieri"
> <[EMAIL PROTECTED]> babbled:
>
>
>> using freetype directly probably.
>>
>> Again, this is easier to do IMO. Doing that inside Evas will be bit
>> harder I guess, maybe not because engine stuff remains unchanged
Peter Wehrfritz wrote:
> Gustavo Sverzut Barbieri schrieb:
>
>> On Thu, Oct 16, 2008 at 7:53 PM, Michael Feiri <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Now, eCos is owned by the FSF and is licensed under the GPLv2 with a
>>> linking exception that makes it completely non-viral. This exceptio
Michael Feiri wrote:
> On monday, starting with revision 36622, all vital EFL components have
> been configured to depend on copylefted code (eina is licensed under
> LGPLv2.1). This is unfortunate, as it renders the existing BSD-style
> license agreement essentially worthless. It is especially unf
I missed this thread earlier, so let me reply separately..
Dave wrote:
> I want to make an e17 module that expose simple edje objects as gadgets.
> The idea is that people can download edje file from the net(calculator,
> clocks and whatever next), put it in the right directory and then my
Gustavo wrote:
> On Wed, Sep 17, 2008 at 11:59 PM, Chia-I Wu <[EMAIL PROTECTED]> wrote:
>
>> Sorry, I just realized that I mailed to the wrong list.
>>
>> On Wed, Sep 17, 2008 at 09:44:15AM -0300, Gustavo Sverzut Barbieri wrote:
>>
I am working on a map application and I would like to
> Author: cedric
> Date: 2008-09-12 06:14:08 -0700 (Fri, 12 Sep 2008)
> New Revision: 35965
>
> Modified:
> trunk/evas/configure.in trunk/evas/src/lib/include/evas_private.h
> Log:
>
> When you know what you do, it could make sense to remove all magic check
> from Evas and win so
Carsten wrote:
> or just be able to select the theme/object or "Wallpaper" :)
>
> also being able to have modules be different on different virtual desktops
> would be nice... maybe... one day... :)
>
Or better yet, for a truly flexible, 'hyperlinked' e, extend virtual desktops
to "virtu
Carsten wrote:
> On Tue, 02 Sep 2008 13:32:46 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>
>
>>Freetype actually allows one to use a matrix for scaling the glyphs that
>> it will rasterize (for given face/size). But this isn't being used by evas
>
Gustavo wrote:
> On Tue, Sep 2, 2008 at 8:28 AM, Dave Andreoli <[EMAIL PROTECTED]> wrote:
>
>> - "Cedric BAIL" <[EMAIL PROTECTED]> ha scritto:
>>
>>
>>> On Tue, Sep 2, 2008 at 12:34 PM, Nicolas Aguirre
>>> <[EMAIL PROTECTED]> wrote:
>>>
2008/9/2 Atton Jonathan <[EMAIL PR
Carsten Haitzler (The Rasterman) wrote:
> On Tue, 2 Sep 2008 08:48:17 +0200 Matteo <[EMAIL PROTECTED]> babbled:
>
> seriously guys... SIMPLE! making it some javascript extravaganza is just going
> to waste time and make ti hard to update. we are about writing a wm and
> toolkit
>
That soun
Dmitriy wrote:
>> ...
>>
>>This is great opportunity for those who are evas engineers to start
>> thinking/
>> working on 'native' implementations for their engine of interest -- I can't
>> do
>> *all* engines in x amount of time.. and while a simple mechanism to
>> implicitly
>> 'fall-b
Vincent wrote:
> ...
>>
>> Any comments, suggestions, or help with implementing things for
>> the various
>> engines, are highly welcome.
>
> I've already talked about that with my student who works on the
> Direct3D engine, and he says that using the pixels shaders for that
> engine
Gustavo wrote:
> On Thu, Aug 28, 2008 at 9:01 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> The patch contains some further improvements on the new grads, and the
>> start
>> of some new things to come for evas, so let me briefly go over some of them
Toma wrote:
I think the most recent patches for gradients have totally destroyed
all gradients in E. Poor lil Edjy is ruined and so is the Gradient
wallpaper selector and all the things associated with that.
Attached (I hope) is a patch to fix those 'old' grads.. they should be back,
fo
Carsten wrote:
> On Wed, 27 Aug 2008 21:21:33 +0800 Toma <[EMAIL PROTECTED]> babbled:
>
>
>> I think the most recent patches for gradients have totally destroyed
>> all gradients in E. Poor lil Edjy is ruined and so is the Gradient
>> wallpaper selector and all the things associated with that.
>
Gustavo wrote:
> Guys,
>
> Batch of patches covering most of SVN. I changed it a bit, but on top
> of Cedric changes.
>
> New version provides a need_recalculate flag for smart objects, this
> flag, when set and SmartObject provides calculate(), will call this
> function before doing any work on re
Cedric BAIL wrote:
> On Sat, Aug 16, 2008 at 3:15 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Just to make it clear what I think about this: This kind of thing is
>> something that really needs to be done, one way or another. :)
>>
>> Some t
Just to make it clear what I think about this: This kind of thing is
something that really needs to be done, one way or another. :)
Some time back, I thought about having the edje recalc function called
by smart class render-pre/post funcs, and these funcs I wanted to be called
by the ob
I wrote:
> Gustavo wrote:
>
>> ...
>> Ok, if you suggest a better name, it can be used, but since it's used
>> for pre-render, it is a good name, maybe before_render is an option.
>> Too bad it conflicts with internal evas names, however it has nothing
>> to do with the internal usage.
Gustavo wrote:
> ...
> Ok, if you suggest a better name, it can be used, but since it's used
> for pre-render, it is a good name, maybe before_render is an option.
> Too bad it conflicts with internal evas names, however it has nothing
> to do with the internal usage.
>
> As for restack, m
Gustavo wrote:
>
> WHY SMART OBJECTS NEEDS TO BE DIFFERENT:
>
> Evas is not an immediate render library, instead it will do all the
> calcs and render at the "render phase". Evas has a number of
> pre-defined objects, like Rectangle, Text and more, but it also have
> what we call "Smart O
I wrote:
> Gustavo wrote:
>
>> On Thu, Aug 14, 2008 at 9:36 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Gustavo wrote:
>>>
>>>
>>>> Attached is a patch (txt so gmail/firefox don't think i
Gustavo wrote:
> On Thu, Aug 14, 2008 at 9:36 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Gustavo wrote:
>>
>>> Attached is a patch (txt so gmail/firefox don't think it's an
>>> octet-stream and is removed by mailman) to add pre_ren
Gustavo wrote:
> Attached is a patch (txt so gmail/firefox don't think it's an
> octet-stream and is removed by mailman) to add pre_render() to
> Evas_Smart_Class. This patch applies on e17/libs and hacks edje and
> emotion so we can test.
>
> CAUTION: if you compile and install Evas with this patc
Nick Hughart wrote:
> Jose Gonzalez wrote:
>> Nick wrote:
>>
>>> Jose Gonzalez wrote:
>>>> Carsten wrote:
>>>>
>>>>> ok. enough of the squabbling. e is not a political football.
>>>>> license is not a
>>&g
Nick wrote:
> Jose Gonzalez wrote:
>> Carsten wrote:
>>
>>> ok. enough of the squabbling. e is not a political football. license
>>> is not a
>>> reason one way or another for success or failure if licenses are oss
>>> anyway.
Carsten wrote:
> ok. enough of the squabbling. e is not a political football. license is not a
> reason one way or another for success or failure if licenses are oss anyway.
> we're squabbling about strawberry vs chocolate.
>
>
That's no doubt true as a rule on any given project, but st
Luchezar Petkov wrote:
>> Cedric was interested on the project by himself and because it was
>> technically good, i think having a common library for data types is
>> something we all agree. I think he will reply on this. And yes, the
>> license do has something to do with this, as *i* want it to
Carsten wrote:
> On Mon, 4 Aug 2008 10:50:10 +0200 "Cedric BAIL" <[EMAIL PROTECTED]> babbled:
>
>
>> On Mon, Aug 4, 2008 at 2:25 AM, The Rasterman Carsten Haitzler
>> <[EMAIL PROTECTED]> wrote:
>>
>>> On Mon, 04 Aug 2008 02:43:33 +0300 Viktor Kojouharov <[EMAIL PROTECTED]>
>>> babbled:
>>>
Vincent Torri wrote:
> On Sat, 2 Aug 2008, dan sinclair wrote:
>
>
>>> 2. What will be the reaction from developers that want BSD license?
>>> from what i've deduced on IRC and ML, several of this developers
>>> *won't* contribute to this library if it is not BSD, (please those
>>> developers th
I wrote:
> Carsten wrote:
>
>> .
>>
>>> Exactly. It's useful to have a variety of 'objs', some compound,
>>> some primitive, etc.
>>> I think both an "svg" object (set an svg file/group, support affine
>>> transforms) and a "cairo"
>>> object (an implicit cairo surface to dr
dan sinclair wrote:
>
>> License
>>
>>
>
> I won't help if it's LGPL. I also won't link to it in my code as I
> won't fix bugs in it.
>
> dan
>
I have to respect your strong and decisive view here, certainly your
decision to not contribute to a library under a license you feel
Carsten wrote:
> On Sat, 2 Aug 2008 00:12:00 -0500 "Nathan Ingersoll" <[EMAIL PROTECTED]>
> babbled:
>
>
>> On Fri, Aug 1, 2008 at 7:46 PM, The Rasterman Carsten Haitzler
>> <[EMAIL PROTECTED]> wrote:
>>
>>> oh of course. details! :) we can dot the i's and cross the t's soon
>>> enough. :)
Gustavo wrote:
> On Sat, Aug 2, 2008 at 1:40 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Gustavo wrote:
>>
>>> Since Edje is target at designers (ie: colors are not premul, etc), I
>>> think we should go with JS since most designers know it s
Gustavo wrote:
> Since Edje is target at designers (ie: colors are not premul, etc), I
> think we should go with JS since most designers know it somehow, even
> if they don't really know, they think they do and they will not be
> afraid of trying it... Also, many systems use it as scripting
> langu
Carsten wrote:
> .
>> Exactly. It's useful to have a variety of 'objs', some compound,
>> some primitive, etc.
>> I think both an "svg" object (set an svg file/group, support affine
>> transforms) and a "cairo"
>> object (an implicit cairo surface to draw on, set updates, etc), and
Gustavo wrote:
> Join late the discussion and badly starting with a top-post, I think
> that trying to make Evas a canvas that supports both raster, vector
> and maybe other (3d?) is bad, it will increase complexity, decrease
> performance or both.
>
>
Increased complexity, yes - in the s
I wrote:
> Jorge wrote:
>
>> ...
>>
>>> Ummm... That kind of depends on the api exposed.. which is somewhat
>>> varied there. You could use this or that part - say the vgfx stuff plus
>>> whatever image stuff.. very similar to the frameworks we mentioned.
>>> But it's still too 'bac
Jorge wrote:
> ...
>> Ummm... That kind of depends on the api exposed.. which is somewhat
>> varied there. You could use this or that part - say the vgfx stuff plus
>> whatever image stuff.. very similar to the frameworks we mentioned.
>> But it's still too 'backend' specific. Better to hav
Jorge wrote:
>
>> Ummm... Just took a quick look at ekeko (been a long time since I last
>> looked at it) and no, what you have there is not the same thing at all.
>> You have something we'd mentioned before, long ago.. namely, having
>> 'object modules' wherein the objs provide their
Jose Gonzalez wrote:
> I wrote:
>> Jorge wrote:
>>
>>> On Fri, Aug 1, 2008 at 10:01 AM, Jose Gonzalez <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>> Let me give Carsten and Jorge a few more philosophical
>>>> spec
Jorge wrote:
> On Fri, Aug 1, 2008 at 11:21 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Jorge wrote:
>>
>>> .
>>>
>>>>Let's consider the first part above only, and let me ask you this:
>>>> What
>
I wrote:
> Jorge wrote:
>
>> On Fri, Aug 1, 2008 at 10:01 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Let me give Carsten and Jorge a few more philosophical speculations
>>> here
>>> on this stuff.
>>>
&g
Jorge wrote:
> On Fri, Aug 1, 2008 at 10:01 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Let me give Carsten and Jorge a few more philosophical speculations here
>> on this stuff.
>>
>> If you've followed this "vgfx api" proposal
Jorge wrote:
> .
>> Let's consider the first part above only, and let me ask you this: What
>> are the successful/modern gfx *apis* out there used for building guis, what
>> are
>> their models, what are their primitives, how do they deal with extensibility
>> or custom rendering. Take a lo
Let me give Carsten and Jorge a few more philosophical speculations here
on this stuff.
If you've followed this "vgfx api" proposal you'll see that it introduces
such concepts to evas by allowing for one to set relevant properties on evas
objects that might support such - rects, lines,
Jorge wrote:
> Some time ago i had another idea that i've been implementing, some of
> you already know enesim and ekeko, some other dont, let me explain why
> i think adding this to evas is not good imho.
>
> One of the main reasons of not releasing software is that it evolves
> too fast or it
I wrote:
> Toma wrote:
>
>> On 31/07/2008, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>>
>>
>>> I wrote:
>>>
>>>
>>>> ...
>>>>
>>>>
>>>>>>
Toma wrote:
> On 31/07/2008, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> I wrote:
>>
>>> ...
>>>
>>>>> As to the above mentioned steps.. I disagree with some of the
>>>>> arguments,
>>>>
I wrote:
> ...
>>> As to the above mentioned steps.. I disagree with some of the
>>> arguments,
>>> but they are also not unreasonable - so long as everyone realizes that the
>>> state
>>> of many things in E is still rather basic and are willing to 'break' apis on
>>> major releases
Toma wrote:
> On 30/07/2008, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> Vincent wrote:
>>
>>
>>> Quoting Nathan Ingersoll <[EMAIL PROTECTED]>:
>>>
>>>
>>>> One idea I discussed with Vincent today is tha
Gustavo wrote:
> On Sat, Jul 26, 2008 at 9:08 PM, Nick Hughart <[EMAIL PROTECTED]> wrote:
>
>> Gustavo Sverzut Barbieri wrote:
>>
>>> On Sat, Jul 26, 2008 at 10:10 AM, The Rasterman Carsten Haitzler
>>> <[EMAIL PROTECTED]> wrote:
>>>
>>>
On Wed, 23 Jul 2008 17:27:35 -0300 "i
Vincent wrote:
> Quoting Nathan Ingersoll <[EMAIL PROTECTED]>:
>
>> One idea I discussed with Vincent today is that our lack of releases
>> has caused many users to lose interest and stop taking notice of the
>> project. I realize that there is a lot of talk surrounding changes to
>> core in
Carsten wrote:
> On Sat, 19 Jul 2008 05:56:53 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>
>
>> Or rather, what to do with "edc" and its use for representing gfx
>> components in both edje and evolve... that's the real question here.
&
Carsten wrote:
> On Thu, 17 Jul 2008 04:36:05 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>
>
>> As the subject states, let me make a (relatively) short summary of some
>> proposed changes and additions to the evas gfx api -- and I'll deal with
Carsten wrote:
> On Thu, 17 Jul 2008 05:58:24 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>
>
>> Ok, now for a proposed api for evas "vgfx objects" -- a very simple
>> one, but general enough to allow for the overwhelming majority of vgfx
Michael Jennings wrote:
> On Thursday, 24 July 2008, at 19:25:42 (+0200),
> Vincent Torri wrote:
>
>
>> I've learned a lot about the licences reading these mails, and it seems
>> that the fact is not "such licence is a hindrance" but "such licence can
>> give us developpers". That's different.
Peter wrote:
> to it and the original code was LGPL. But would you share code with
> someone, that doesn't share code with you?
>
Good point. And that's precisely why many people don't like to
contribute to bsd licensed projects. In the case of corporations, this
is an even more seri
Michael wrote:
> On Tuesday, 22 July 2008, at 19:32:21 (-0400),
> Jose Gonzalez wrote:
>
>
>> In any case Nathan, as I've stated before, if you feel comfortable
>> with such licenses, then good for you. I just don't share that view.
>>
>
>
Nathan wrote:
> On Tue, Jul 22, 2008 at 12:30 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> This issue is a long and complex one, and I really have no desire to
>> get into the specifics of it. You and Nathan and Carsten and maybe many
>> others,
>
Michael wrote:
> On Tuesday, 22 July 2008, at 13:30:42 (-0400),
> Jose Gonzalez wrote:
>
>
>> This issue is a long and complex one, and I really have no desire to
>> get into the specifics of it.
>>
>
> Then
Michael wrote:
>
>> Often, I saw some people react with hostility to any attempt to even
>> bring up the issue, and basically deliver a wide-ranging ultimatum
>> that no code was ever going to be accepted into E's cvs unless it
>> was under a BSD/MIT license -- consider Michael Jenning's recent
Michael Jennings wrote:
> On Tuesday, 22 July 2008, at 13:20:07 (-0400),
> Jose Gonzalez wrote:
>
>
>> I'm not sure that the 'majority of the work' was done by people who
>> *like* that license, not for every sub-project.. or even if partly
>> so, wh
Michael Jennings wrote:
> On Tuesday, 22 July 2008, at 08:33:13 (-0400),
> Jose Gonzalez wrote:
>
>
>> Personally, I'd *never* contribute anything that I'd consider to be
>> a truly serious, dedicated, body of time and work to a project that
>>
Gustavo wrote:
> On Mon, Jul 21, 2008 at 8:45 AM, Jorge Luis Zapata Muga
> <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>>
>> I dont pretend to start a flamewar, if you do, please dont answer this
>> thread.The thing is that right now, the EFL has arrived to a place
>> where different companies a
Jorge wrote:
> Hi all,
>
> I dont pretend to start a flamewar, if you do, please dont answer this
> thread.The thing is that right now, the EFL has arrived to a place
> where different companies are using this software, and several of us
> are working on a company using the efl (raster, gustavo
Cedric wrote:
> On Tue, Jul 22, 2008 at 2:33 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> What are the reasons people prefer one type of license over another..
>> and
>> does that affect the number or quality of contributors or contributions?
>&g
Ah yes, the licensing issue. Is it something which has helped or hindered
the "E" project? Who knows. There are several other factors besides that one
which
one could point to as well, it's possible those may even be intertwined with
this
one... Again, who really knows for certain.
O
Michael wrote:
> Get-E is already gone, so I think it's time to stop talking about it.
> :-)
>
That's too bad. I liked get-e, even the original one - which then
also went 'gone', and was subsequently
reborn again, but is now gone.. yet again. So, who knows how gone is
'gone' and who
Vincent wrote:
>
>> There's got to be more to a web presence to E than themes... and
>> if you think
>> about it. :)
>
> i have nothing against exchange. Absolutely nothing. I even dreamt of
> such a thing for the Windows packages i want to build. I'm against
> that 2 sets of people
Vincent wrote:
>
> On Mon, 21 Jul 2008, Jose Gonzalez wrote:
>>
>> Get-e *was* good, and useful. It could've done more in terms of
>> this and that,
>> but so could everything. But I don't see why everyone feels that
>> 'there can b
Sthithaprajna wrote:
> Indeed, one of the main reasons for creating exchange was to make a
> webapp that was a lot more tightly integrated with the efl.
> Personally, I would like to see a ecore-style C library for exchange,
> so that people can just plop it into their apps and get a full
> rep
Brian wrote:
> Hello everyone,
>
> to make this clear, GET-E.org will be closed. Exchange is a good
> improvement and i like the idea to have everything under the e.org
> domain. Also i see no sense in having two sites, providing the same.
> The site will be up for a while until all the themes
Gustavo wrote:
> On Sun, Jul 20, 2008 at 8:58 PM, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
>
>> Gustavo Sverzut Barbieri schrieb:
>>
>>> On Sun, Jul 20, 2008 at 8:29 PM, Peter Wehrfritz <[EMAIL PROTECTED]>
>>>
Peter wrote:
> Jose Gonzalez schrieb:
>> (4) Extensions to the current rectangle obj api:
>> ***
>>
>> void evas_object_rectangle_corner_radius_set(obj, float r);
>> void evas_object_rectangle_corne
Vincent wrote:
>
> On Sun, 20 Jul 2008, Jose Gonzalez wrote:
>
>> I agree that discussion on this important aspect of
>> "e-and-the-web" would
>> be excellent, and it's something I tried to mention several times.
>> But what's
morlenxus wrote:
> On Sun, Jul 20, 2008 at 04:01:11AM -0400, Jose Gonzalez wrote:
>
>>Vincent wrote:
>>
>>
>>> On Sun, 20 Jul 2008, Jose Gonzalez wrote:
>>>
>>>
>>>> This is actually damn nice. It's a g
Vincent wrote:
>
> On Sun, 20 Jul 2008, Jose Gonzalez wrote:
>
>> This is actually damn nice. It's a great example of having e
>> become more
>> "web-connected", and could yet become something bigger and better. I
>> suppose
>> get-e
Sthithaprajna wrote:
> For themes, you get a lot more information, that could be useful
> depending on what you are looking for..
> for example, if you dont like the look of your shelf and want to try
> something else, you could go here:
> http://exchange.enlightenment.org/themeGroup/show/2664
Or rather, what to do with "edc" and its use for representing gfx
components in both edje and evolve... that's the real question here.
Right now, evolve has no direct 'gfx' representations other than via
edje/edc, and the latter is limited to what has been available in evas so far.
Edj
Just a couple of other remarks on these two (parts I, II) proposals:
Like the proposed gradient obj api function that sets an (affine)
"fill_transform",
there would be a similar one to set such on an image object:
void evas_object_image_fill_transform_set(obj, Evas_Transform *t);
Ok, now for a proposed api for evas "vgfx objects" -- a very simple one,
but
general enough to allow for the overwhelming majority of vgfx uses (and
certainly
ones for most 'real-time' use in evas).
Again, by evas "vgfx objects" we mean evas objects that can be "filled
and/or
stroke
As the subject states, let me make a (relatively) short summary of some
proposed changes and additions to the evas gfx api -- and I'll deal with only
gradients and a possible vgfx-objs api, leaving transforms (mostly) and filters
for later.
First, changes to the current gradient api. T
Sevcsik András wrote:
> On Wed, Jul 16, 2008 at 9:20 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>
>>Sevcsik András wrote:
>>
>>>
>>>> Hi list,
>>>>
>>>> What's the purpose of esmar
Vincent wrote:
>
> On Wed, 16 Jul 2008, Jose Gonzalez wrote:
>
>> Nathan wrote:
>>
>>> I also think it would be a good idea to add student blogs to Planet E
>>> to give their work more exposure.
>>
>> What's "Planet E
101 - 200 of 342 matches
Mail list logo
