On Thu, 10 Jan 2013 12:04:19 +0200 Dominik Röttsches
said:
disabled now with:
https://phab.enlightenment.org/rEFL5adb2f1ae6766fb0880aba5a92fff4fa52d1402f
(yes we've moved to git now for efl - will move more and more from svn to git..
and we're not using phabricator not trac... this allows u to
On Mon, 11 Feb 2013 22:46:32 +0100 Davide Andreoli
said:
i fixed it. :)
> Hi guys,
> I think I found 2 bugs in edje (trunk):
>
> edje_color_class_list() and edje_text_class_list() always return nothing...
>
> see a super simple example at:
> http://pastebin.com/8dAiaFzR
>
> looking at the cod
+1 I strongly agree.
Commit id title is inconvenient.
2013. 2. 18. 오후 1:04에 "Daniel Juyung Seo" 님이 작성:
> And it'll be great if the title includes the first line of commit message.
> That should be way more useful.
> Thanks.
>
> Daniel Juyung Seo (SeoZ)
>
> On Mon, Feb 18, 2013 at 10:14 AM, ChunEon
On Mon, Feb 18, 2013 at 1:02 PM, Daniel Juyung Seo wrote:
> And it'll be great if the title includes the first line of commit message.
> That should be way more useful.
Indeed.
--
Cedric BAIL
--
The Go Parallel Website,
And it'll be great if the title includes the first line of commit message.
That should be way more useful.
Thanks.
Daniel Juyung Seo (SeoZ)
On Mon, Feb 18, 2013 at 10:14 AM, ChunEon Park wrote:
> By the way, Daniel,
>
> Could it possible to make git mail title messages to be more meaningful?
>
On Fri, 15 Feb 2013 11:30:25 + Nathan Baxter
said:
> On 15/02/13 10:45, Carsten Haitzler (The Rasterman) wrote:
> > On Fri, 15 Feb 2013 13:41:59 +0300 المسالم المسالمة
> > said:
> >
> >>> what? do what gnome did? :) ie lose users. :) seriously. the old fashioned
> >>> look
> >>> is what e is
On Fri, 15 Feb 2013 11:43:21 + (GMT) Rajeev Ranjan
said:
> Hi,
> > --- Original Message ---
> > Sender : Carsten Haitzler
> > Date : Feb 15, 2013 20:15 (GMT+09:00)
> >Title : Re: [E-devel] [Query] Controlling further eventing on an edje
> >draggable part programmatically
> >
> > On F
On Sat, 16 Feb 2013 14:33:05 +0100 Cedric BAIL said:
> Hello,
>
> Our current build system is currently in a bad state and there was no
> improvements in the past week. So here is I think a TODO that everyone
> will agree with.
>
> - siginfo is not a portable API. There was a test and proper #i
I will have to check with the company I work for if I may release the
code. Won't happen till I'm back home from ELC though.
//Peter
> -Original Message-
> From: Tom Hacohen [mailto:t...@stosb.com]
> Sent: 17 February 2013 14:29
> To: e
> Subject: Re: [E-devel] One mail/commit (was: RE:
By the way, Daniel,
Could it possible to make git mail title messages to be more meaningful?
i.e) [core/efl] xxxmaster updated. f27ff2fbf31a01c2f8d98e773bed6cc4298749bd
-> [core/efl/evas] xxxmaster updated. f27ff2fbf31a01c2f8d98e773bed6cc4298749bd
If the title shows any detailed core lib name t
P Purkayastha wrote:
> On 02/17/2013 01:15 PM, المسالم المسالمة wrote:
>
>>> I've already commented at length about the only aspect to this
>>> that merits any serious discussion - perhaps you missed that?
>>>
>>> But since you seem to want some serious critical feedback:
>>>
>>> Think you there
Your patches seem to be coming with DOS newlines.
Please fix your editor to avoid that.
On Sat, Feb 16, 2013 at 1:32 AM, Paulo C. A. Cavalcanti Jr
wrote:
> pca...@zytor.com (Paulo C. A. Cavalcanti Jr) writes:
>
>> Just follow a patch that fixes a bug with
>> evas_object_precise_is_inside_set() us
Assuming that setting font_size=666 doesn't make hell break loose on it's
own (by summoning satan to earth) it should "just work", yes.
On Sun, Feb 17, 2013 at 2:50 PM, Iván Briano wrote:
> On Sun, Feb 17, 2013 at 11:48 AM, Iván Briano wrote:
> > On Sun, Feb 17, 2013 at 11:30 AM, Tom Hacohen
That's why I sent the email, because there was more to comment, just not
something that should go into the commit log.
That's why I've asked all the questions in this mail, and what I've just
repeated was said in my initial mail here.
Commit logs are not blogs, and I shouldn't tell a sad story or
On Sun, Feb 17, 2013 at 11:48 AM, Iván Briano wrote:
> On Sun, Feb 17, 2013 at 11:30 AM, Tom Hacohen wrote:
>> That's why I do what I do, that instead of actually setting the font, I
>> multiply it by a scaling factor, so for example:
>> size: 10
>> size_range: 5 20
>>
>> Will let *all* the fonts
On Sun, Feb 17, 2013 at 11:30 AM, Tom Hacohen wrote:
> That's why I do what I do, that instead of actually setting the font, I
> multiply it by a scaling factor, so for example:
> size: 10
> size_range: 5 20
>
> Will let *all* the fonts to be anywhere between half to twice the size,
> even if the
That's why I do what I do, that instead of actually setting the font, I
multiply it by a scaling factor, so for example:
size: 10
size_range: 5 20
Will let *all* the fonts to be anywhere between half to twice the size,
even if the actual font used in textblock is of
size 50.
The problem is, that
On Sun, Feb 17, 2013 at 11:14 AM, Tom Hacohen wrote:
> You are correct. Next time I'll include complete documentation about Evas,
> Edje and textblock,
> how they work together, what fonts exactly are, when one should use
> textblock vs. animated gifs with text
> and some related code examples.
>
You are correct. Next time I'll include complete documentation about Evas,
Edje and textblock,
how they work together, what fonts exactly are, when one should use
textblock vs. animated gifs with text
and some related code examples.
What would you have expected to see in the commit message?
On S
On Sun, Feb 17, 2013 at 10:56 AM, Tom Hacohen wrote:
> Planet alignment? Heck no, it uses a proprietary formula of which it's
> details I can't disclose.
>
> Seriously though, you don't expect me to rewrite the docs in every commit
> message, do you? Just read the docs,
> text.fit and text.size_ra
On Sun, 17 Feb 2013 13:56:36 +
Tom Hacohen wrote:
> Planet alignment? Heck no, it uses a proprietary formula of which it's
> details I can't disclose.
>
> Seriously though, you don't expect me to rewrite the docs in every commit
> message, do you? Just read the docs,
> text.fit and text.size
Planet alignment? Heck no, it uses a proprietary formula of which it's
details I can't disclose.
Seriously though, you don't expect me to rewrite the docs in every commit
message, do you? Just read the docs,
text.fit and text.size_range are documented already. This is just adding
support for them
On Sun, Feb 17, 2013 at 10:40 AM, Tom Hacohen wrote:
> No idea...
>
> If I have to guess, I'd say it controls the range of which textblock fonts
> are being sized.
>
Randomly? Based on container size? Under specific conditions depending
on planet alignment?
--
No idea...
If I have to guess, I'd say it controls the range of which textblock fonts
are being sized.
On Sun, Feb 17, 2013 at 1:30 PM, Iván Briano wrote:
> On Fri, Feb 15, 2013 at 4:11 PM, Tom Hacohen
> wrote:
> >
> > At the moment, the API is kinda quirky:
> > Because we don't really know t
I didn't even know this was broken, forwardport it!
On 17 Feb 2013 12:21, "Michael Blumenkrantz"
wrote:
> if the gods of text approve, this should probably be forwardported
>
> On Sun, 17 Feb 2013 04:16:01 -0800
> "Enlightenment SVN" wrote:
>
> > Log:
> > finally fix damn edje entry anchor click
On Fri, Feb 15, 2013 at 4:11 PM, Tom Hacohen wrote:
>
> At the moment, the API is kinda quirky:
> Because we don't really know the current textblock font size, I had to
> set a value.
> So at the moment you actually need to set
> text.size: 20;
> text.size_range: 10 60;
>
> Which means textblock w
May we have your script then? It'll be easier than writing our own and
solving issues you've already solved.
--
Tom.
On 17 Feb 2013 10:59, "Peter Kjellerstedt"
wrote:
> > -Original Message-
> > From: Tom Hacohen [mailto:t...@stosb.com]
> > Sent: 16 February 2013 17:43
> > To: e
> > Subje
On Sun, 17 Feb 2013 13:10:48 +0100 Andreas Volz said:
> Hello,
>
> while developing I reviewed again the evas module loader.
>
> quote file/evas_module.c:
>
>/* 1. ~/.evas/modules/ */
>path = eina_module_environment_path_get("HOME", "/.evas/modules");
>evas_module_paths = _evas_mod
if the gods of text approve, this should probably be forwardported
On Sun, 17 Feb 2013 04:16:01 -0800
"Enlightenment SVN" wrote:
> Log:
> finally fix damn edje entry anchor click signals: this fixes anchor clicking
> in elm_entry widgets when using a desktop profile which has been broken for
>
Hello,
while developing I reviewed again the evas module loader.
quote file/evas_module.c:
/* 1. ~/.evas/modules/ */
path = eina_module_environment_path_get("HOME", "/.evas/modules");
evas_module_paths = _evas_module_append(evas_module_paths, path);
/* 2. $(EVAS_MODULE_DIR)/evas/mod
Before I complained about this, but I'm stopping doing so now.
On Saturday, February 16, 2013, Cedric BAIL wrote:
> Hello,
>
> Our current build system is currently in a bad state and there was no
> improvements in the past week. So here is I think a TODO that everyone
> will agree with.
>
> - si
Am Thu, 14 Feb 2013 09:03:44 +0900 schrieb Cedric BAIL:
> Yop,
>
> On Thu, Feb 14, 2013 at 7:41 AM, Andreas Volz
> wrote:
> > I just found out that now all modules (I checked Evas/Ecore_Evas) in
> > EFL are linked static into the libs.
>
> Not all, only the core one that every one will use. Thi
> -Original Message-
> From: Tom Hacohen [mailto:t...@stosb.com]
> Sent: 16 February 2013 17:43
> To: e
> Subject: Re: [E-devel] [EGIT] [core/efl] branch master updated.
> 04e660c5c76fa9168be08de1f979a1684c464154
>
> At the moment it's one mail per changeset, that can be changed if
> deci
On 02/17/2013 01:15 PM, المسالم المسالمة wrote:
>> I've already commented at length about the only aspect to this
>> that merits any serious discussion - perhaps you missed that?
>>
>> But since you seem to want some serious critical feedback:
>>
>> Think you there's any shortage of people out ther
Oh and btw, the problem that I see with using e's current
notion of "profile" as a means to define such a shell-skin
bundle, is that the current notion of a profile is either too small
if you mean just the config data file, or too big if you mean
the entire directory.
As Cedric succinctly
2013/2/17 Daniel Juyung Seo
> Hello, thanks for the patch but this looks wrong.
>
> Genlist item has two types of elements:
> 1. Text
> "Text" is a text data that can be set to TEXT or TEXTBLOCK part of
> genlist item.
> The text is retrieved by text_get callback and set in
> _item_text_reali
36 matches
Mail list logo