Mark Phalan writes:
> I've been watching E development recently and I've notices that EFM's
> replacement hasn't even been started (well apart from the UML).
Quite the contrary; evidence is fully functional and after some
final touches will be released RSN. At the time, I also intend
to freeze the API.
> I think that evas2 would be a great place to start a filemanager
evidence builds against evas2. It can also build against
gnome-canvas, but you miss all the sexiness then.
evas2 is used for a fully themable icon-view (where all engines
are shared objects, so you can easily extend functionality without
anyone crying bloat).
evidence also has the mandatory tree-view, and a browser-view a la
NeXT/Step or Mac OS X which has proved invaluable in handling for
> and I was intensly impressed with EFM (mmm.. typebuffer).
evidence features a typebuffer which will likely get more integrated
with Escreen over time -- as in, start a text-mode app from typebuffer,
send output to a tab in Eterm.
> EFSD is just sitting in CVS waiting to be used and I was wondering
Like about everything else, file-backends are pluggable shared
objects in evidence. evidence doesn't much mind if meta-data come
from a POSIX backend or whatever, so adding a backend for your
favourite file-system abstraction (gnome-vfs, efsd, kio, ...)
should not be an issue. I am contemplating adding an efsd-backend
after the gnome-vfs one, unless of course you want to jump the gun. ; )
> if anyone had any plans to go ahead and restart development on the
Been there, done that.
Additional coders welcome.
> is it e18?
Man, we haven't even released e17. : (
> Is there anyone else interested in EFM or is it dead?
Far from it.
"If you don't like what you see, make a better theme!"
cvs -z3 -d:pserver:anonymous@... login
(There's also RPM-download, but since I've been keeping busy, that's not up-to-date
most of the time)