Hi Everyone,

Given the issues raised about the directory tree widget in Padre at the
moment, I'd like to raise an idea or two.

To me, the directory tree always causes me some confusion in its
intended use.  Is it a convenient  file system browser or is meant to be
bound to the "project"?

I think in many ways this can be a problem for others as well when they
find the directory tree doesn't do what they expected.

I've been using Visual Studio a fair bit, and the concept of the project
browser is a good one.  You know it's bound to the project at hand
( basically because that's all I work in I guess ) because it doesn't
offer any visual indication that you can move up a directory level in
the file system  ( as you see in the directory tree ).  The root of the
tree is the project root.

Now, I'm wondering if we don't have a separate widget for each idea
here, one the convenient file system browser, with context menus for
open file, create new file etc, and one for projects that has it's root
as the project root and with it additional menus such as "Import file"
or "Add file to project", making it more clear in it's terminology that
this is indeed a project specific widget.

I think there is room for both widgets, even in use at the same time
( maybe... ).


Just a thought or two...

Peter.


_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to