Re: [Fwd: Re: find dialog]

[Steve H. <dig...@mi...>]

From: Elias Pschernig, Mar 9, 2004 5:09 AM
> On Tue, 2004-03-09 at 05:57, Steve Hall wrote:
> >
> > That flakiness is due to several factors:

	[snip]

> > o Cream generally remembers tons of settings (last word searched
> >   for, states of wrap, invisibles, margins, tab expansion,
> >   indention, file positions, color schemes, etc.) Since Cream is
> >   script, and not binary, it takes some time to run through it
> >   all.
> > 
> > o GNOME/GTK/X window rendering are slower than Windows. Granted
> >   they are doing about 10 times more, but the net effect feels a
> >   bit slower. Can't wait to try kernel 2.6.
> 
> Yeah, the above two together must be what I'm seeing. But for me, I
> prefer not remembering the window position at all, to remembering
> it, but having to do it after the gvim window was already mapped.

This was an early feature, but looking back, it may have been better
to make the default off rather than on. Perhaps that could change.


> > Be happy to get some help identifying places where we could gain
> > some speed, feel free to offer suggestions on what tradeoffs you'd
> > rather see.
> 
> Well, I'd probably be happy if I could just disable it :) I.e. - I
> don't think I ever had any special or help file or even multiple
> files open in cream - rather I open one cream window per text file,
> and use the gnome task bar for navigation between them. Mostly I
> also maximize them all/leave at their assigned positions. So in my
> case, I'd like cream to start as fast as gvim, without doing
> anything besides remapping the keyboard, including useful things
> like ctrl-t and so on. Never had to touch the font settings as well,
> since I use the Gnome default font for everything. Window
> position/fonts and so on is all ok in gvim for me already. But I can
> see that some users may want the additional features. Maybe, if it's
> easy to do, there could be some setting somewhere (without having to
> edit config files), which parts of cream should get active.
> Something like:
> 
> [ ] Remove vim modes and remap to sane keyboard shortcuts
> [ ] Cream menu
> [ ] Cream statusbar
> [ ] Cream search dialog
> [ ] Save font changes
> [ ] Remap window on startup
> 
> Then I would, as my personal preference, only check the first 3 - but
> not the last 3. I can of course see how the other features are useful -
> just they cause that unwanted side-effect of re-opening every cream
> window at startup, which I don't like, since I seem to be opening and
> closing cream windows a lot these days :)

Since the beginning, Cream has been a wholesale approach to usability.
But it has been designed with modular components, so the selections
you mention wouldn't be that difficult to implement. It would be
pretty simple to provide these options through the cream-config file,
the back end just needs to be written.

We've got some major architectural changes in the works right now, but
I'll consider looking over the speed ToDo items following.


-- 
Steve Hall  [ dig...@mi... ]

Cream... the Vim text editor in sheep's clothing!
  http://cream.sourceforge.net