Fair enough.

Looking at the latest version of it, it's much clearer in it's intent...
I'm sure it wasn't like this.

What do you think about things like a right mouse click context menu
that allows you to "create file" or "add file from..." where it then
brings the file in from some other place on the file system?

I think the browser gives an impression that it can do stuff like this,
but at hte moment doesn't.



> The original intent for the current tool was as a project browser.
> 
> Prior to the Task 2.0 rewrite, this got extended to serve dual
> purpose. But I was never a huge fan of this double-purposing. I'd be
> quite happy to see a seperate directory tool.
> 
> As for the "Add file to project" type thing, it has always been
> intended that this should not be required, and that the editor should
> automatically intuit which files are in the project, and which are
> not.
> 
> Adam K
> 
> On 6 November 2010 09:55, Peter Lavender <pla...@internode.on.net> wrote:
> > 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
> >
> >
> _______________________________________________
> Padre-dev mailing list
> Padre-dev@perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev


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

Reply via email to