Re: Milestones document



[snip]
> I'll probably try again with Mozilla

I think you'll prob. find it too pre alpha at the moment. It'll be great,
but It currently spends a lot of time spitting out debuging information.

> > 2.  switch from E, first to blackbox and now sawmill
> > 3.  use a sensible gtk theme  (ThinIce is a good one)
>
> I guess I don't understand how the gtk themes and the E themes interact.

GTK themes and E themes are completely seperate. gtk themes effect all gtk
programs and (I think at the moment) the gtk theme is loaded for each gtk
app, increasing memory usage more with every app. E themes basicly effect
the window borders and all sorts of other enligtenment features.

> Should
> one of them be disabled?

You can't run E without a theme (you can but it's unusable) so you can't
disable that without changing WMs. If you are having issues with gtk stuff
being slow, try the thin ice theme or a derivative (or any "engine" theme
for that matter). Mem. usage aside, think how much extra computation goes
into resizing a graphic when the scrollbar gets smaller. non-pixmap engine
themes are way faster and way lighter on the system.

[snip]

> 2)I launched gnomepad+ with nothing else running it could not keep up with
> my typing its was 5-10 characters behind. I'm pretty sure I was not memory
> limited
> in this case.

Yikes! That's not right. try running top in a terminal while you'r doing
that. what's the cpu load, mem usage and swap usage?  (before this computer
I had a P100, 40MB that always kept running onto swap space and comming to a
grinding halt. As much as I try to convince myself otherwise, Linux seems to
be less happy than windows when it runs low on RAM.


--Ben



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]