Re: questions about features
- From: tpgww@xxxxxxxxxxx
- To: emelfm2@xxxxxxxxxxxxx
- Date: Thu, 2 Feb 2006 15:14:03 +1100
> > > In the filelists we distinguish, by colour, 6 broad categories of
> > > item. That seems a reasonable compromise between ease-of-use and
> > > speed (which is a priority, I work with dirs that contain up to
> > > 2,000 items, and I know that some e2 users have slow hardware).
> > > There is currently no infrastructure (and in particular, fast
> > > infrastructure) in e2 for distinguishing items in finer detail e.g.
> > > mime-type.
> >
> > I think you're going into a premature optimization.
> The application has been in use for almost 2 years, and quite stable for
> over a year.
>
> My self-patched mc
> > with file type coloring has no problem with 2000 file directories. And
> > this is VERY important from UI viewpoint. In fact this is MORE
> > important than coloring file categories. I very rarely use sockets or
> > hard links, so coloring them is scarcely helpful. But I want to be
> > able to tell my images from my XML and C++ files at once, they are
> > always before my eyes and coloring them differently is way more
> > important. I consider this a major can't-live-without feature.
> Well, it's worth a try. But I have to say, IMO current e2 filelist
> refreshing is bordering on unacceptably slow, for large directories.
> Gtk2 is going to make things a lot slower than mc
I put together a test-rig which supports setting a color for each category of
filetype and/or each extension, among the 'regular' items. That is, the ones
which now currently show in your default text colour (not dirs, links, sockets
etc). Seems to work ok, though the UI for setting the colors is rudimentary
bordering on disgusting. Such is life, until we understand all the wrinkles.
On reflection, my big directories are mostly system-related, and full of dirs,
links, executables etc not impacted by the coloring. Is that common ?
Regards
Tom
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts: