Hello,
Clemens Eisserer wrote:
> I do not think a P100 should be taken as a serious benchmarking
> machine anymore, however a P2-350 or a P3-500 should be able to handle
i think the source of these issues is that developers usually have PCs in mind.
In my opinion a ~200MHz machine is a good one f
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Petr Tomasek
> Sent: 25 October 2005 11:56
> To: gtk-list@gnome.org
> Subject: Re: so,is this claim about pango still true? or does
> nobody actually care?
>
> On Fri,
On Fri, Oct 14, 2005 at 08:47:38AM +0300, Tommi Komulainen wrote:
> On 10/14/05, Paul Davis <[EMAIL PROTECTED]> wrote:
> >
> > is this still true? does anybody care? is there a way to avoid pango
> > entirely and still get AA fonts inside GTK2? will this ever be fixed
> > before everyone is using h
Hello,
> So far I've only been using Sysprof:
>
> http://primates.ximian.com/~federico/news-2005-07.html#26
>
> Federico
Its really great to actually see something happen, since also on my
more or less modern system GTK2 based gui programs feel much slower
than compareble widget sets li
On Mon, 2005-10-17 at 11:10 +0200, Emmanuel Briot wrote:
> I have read your very interesting blog, but haven't found out what tools
> you are using to profile an application. I would love to use them on my
> own tools using gtk+!
So far I've only been using Sysprof:
http://primates.xim
Federico Mena Quintero wrote:
Many people care. The problem is that up until now, we have not had
good/friendly tools to profile complex apps like GNOME's. Now that we
have them, we can do something about our performance problems.
I have read your very interesting blog, but haven't found ou
Russell Shaw wrote:
Daniel Kasak wrote:
Russell Shaw wrote:
...
I'm using a pentium 166 as a dedicated mozilla machine among a few other
things.
Correction: 266MHz (with 64MB ram)
But that is very sluggish because of ram swapping when running mozilla.
In a typical gtk window with a dozen
Daniel Kasak wrote:
Russell Shaw wrote:
I don't care how much tedious rendering pango does; if a gui isn't
lightning fast on a 100MHz pentium (or 25MHz 386 for that matter),
it's fundamentally broken in either or both design and implementation.
Oh come on!
A pentium 100?
That's what you're us
Russell Shaw wrote:
I don't care how much tedious rendering pango does; if a gui isn't
lightning fast on a 100MHz pentium (or 25MHz 386 for that matter),
it's fundamentally broken in either or both design and implementation.
Oh come on!
A pentium 100?
That's what you're using, right? Sure? Rea
On Thu, 2005-10-13 at 23:30 -0400, Paul Davis wrote:
> concerns on GTK+-2.x. As a reference the perf issue I was having was
> most evident when updating a textual label (reporting some ADC value)
> at a rapid rate (10x per second or so).
This will cause the label to queue a resize on itself, s
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Paul Davis
> Sent: 14 October 2005 04:30
> To: gtk-list@gnome.org
> Subject: so,is this claim about pango still true? or does
> nobody actually care?
>
> We are about 60% of the way through porting Ar
On 10/14/05, Paul Davis <[EMAIL PROTECTED]> wrote:
>
> is this still true? does anybody care? is there a way to avoid pango
> entirely and still get AA fonts inside GTK2? will this ever be fixed
> before everyone is using h/w acceleration to print button labels?
If you don't actually need any of t
[EMAIL PROTECTED] wrote:
is this still true? does anybody care? is there a way to avoid pango
entirely and still get AA fonts inside GTK2? will this ever be fixed
before everyone is using h/w acceleration to print button labels?
the issue raised here will *kill* ardour dead, and would force us t
Paul Davis ([EMAIL PROTECTED]):
> [...] As a reference the perf issue I was having was most evident when
> updating a textual label (reporting some ADC value) at a rapid rate
> (10x per second or so). Updating 5-10 labels at h the above rate
> (this was reporting data for an outside slow-speed da
> is this still true? does anybody care? is there a way to avoid pango
> entirely and still get AA fonts inside GTK2? will this ever be fixed
> before everyone is using h/w acceleration to print button labels?
>
> the issue raised here will *kill* ardour dead, and would force us to
> also have to
15 matches
Mail list logo