Thread: [Screem-devel] File Browser Discussion
Status: Inactive
Brought to you by:
davek
From: Sven S. <sv...@mo...> - 2004-06-16 12:51:47
|
Hi, when using screem, I'm mostly working in one directory at a time and don't need the treeview based file browser. The treeview based file browser very unhandy for me, because i have files and folders in one view at the same time, but not much space to display all. This causes a lot of scrolling and finding files isn't very easy. Another app that I use is gthumb, which implements this part of file browing better, in my opinion. So, what I'd like to suggest is, that the files get splitted out of the tree into a separate list below of the directories, like gthumb does it. Also, only displaying one directory in the directory browser would use much less space and would make it much more handy, but a treeview with only directories would help much. For the filesystem a multirooted treeview would help a lot too. Well, what do you think of the current implementation and this suggestion? Regards, Sven |
From: David A K. <da...@sc...> - 2004-06-21 15:42:05
|
On Wed, 2004-06-16 at 14:52 +0200, Sven Salzwedel wrote: > So, what I'd like to suggest is, that the files get splitted out of the > tree into a separate list below of the directories, like gthumb does it. > Also, only displaying one directory in the directory browser would use > much less space and would make it much more handy, but a treeview with > only directories would help much. For the filesystem a multirooted > treeview would help a lot too. I'm not sure if making it a split view is a good idea, it would introduce yet another pane which would make the interface look more complex. The problem of lots of scrolling around is why there are the top level Images, Scripts, and Stylesheet nodes, so you can access them quickly without expanding possible deep directory structures. I have at times thought about adding html/php nodes as well, so you can access all your html files from expanding the one node. This does have a problem in that there would probably still be lots of scrolling if you have a large site. If a split view were to be used I would be thinking of something a little different from gthumb, which from screenshots seems to just show the current directory + path, then the files below. I'm thinking the top pane would be a tree of directories, much like is currently present, just without any files showing, then have the bottom frame show the files for whatever directory is double clicked, or perhaps just selected. For anyone feeling adventurous EggTreeModelFilter from libegg would probably be the foundation for implementing this. David -- Make your website SCREEM - Site Creating & Editing EnvironMent URL: http://www.screem.org/ Mail: da...@sc... |
From: Sven S. <sv...@mo...> - 2004-06-21 16:34:40
|
Am Mo, den 21.06.2004 schrieb David A Knight um 17:41: > I'm not sure if making it a split view is a good idea, it would > introduce yet another pane which would make the interface look more > complex. Yes, that's (sadly) true, but I think it would be better than scrolling and searching in a webproject with all folders expanded and files below folders in the same treeview. > The problem of lots of scrolling around is why there are the top level > Images, Scripts, and Stylesheet nodes, so you can access them quickly > without expanding possible deep directory structures. I have at times > thought about adding html/php nodes as well, so you can access all your > html files from expanding the one node. This does have a problem in > that there would probably still be lots of scrolling if you have a large > site. Well, I mostly have to scroll a lot when I open a lot of folders in a site and don't close them. This wouldn't be such a big problem if the files were splitted out into an own listview, because normally you have more files than folders :) > If a split view were to be used I would be thinking of something a > little different from gthumb, which from screenshots seems to just show > the current directory + path, then the files below. I'm thinking the > top pane would be a tree of directories, much like is currently present, > just without any files showing, then have the bottom frame show the > files for whatever directory is double clicked, or perhaps just > selected. Yes, that would be (after reconsideration) the best possible option, IMHO. The files should appear in the bottom frame when selected, I think. Regards, Sven |
From: David A K. <da...@sc...> - 2004-07-13 15:57:38
|
On Mon, 2004-06-21 at 16:41 +0100, David A Knight wrote: > If a split view were to be used I would be thinking of something a > little different from gthumb, which from screenshots seems to just show > the current directory + path, then the files below. I'm thinking the > top pane would be a tree of directories, much like is currently present, > just without any files showing, then have the bottom frame show the > files for whatever directory is double clicked, or perhaps just > selected. I've been playing around with monodevelop which uses a split view like gthumb does, and I definitely don't like it so the above would seem to be my prefered method of implementing a split view. Here's a few more thoughts, feel free to add to them / comment on them. split view pros + cons. Pro - files are listed separately from folders, so you don't have to scroll through past lots of folders to get to the files Pro - it isn't a tree, the HIG says trees are bad, although you do still have the tree structure with the file system. Con - can't show files from 2 different folders at once, e.g. an images folder so you can drag / drop images into the editor to insert <img> tags can't be open at the same time as another folder containing the html files you plan to work on. Con - gthumb style can only drag files to folders in the same folder as the file already is Con - can't glance at the file tree to see the file system structure of the site. David -- Make your website SCREEM - Site Creating & Editing EnvironMent URL: http://www.screem.org/ Mail: da...@sc... |
From: Sven S. <sv...@mo...> - 2004-07-21 12:25:33
|
Am Di, den 13.07.2004 schrieb David A Knight um 17:57: > split view pros + cons. >=20 > Pro - files are listed separately from folders, so you don't have to > scroll through past lots of folders to get to the files In my opinion _the_ reason to switch over and then finding solutions for problems :) > Con - can't show files from 2 different folders at once, e.g. an images > folder so you can drag / drop images into the editor to insert <img> > tags can't be open at the same time as another folder containing the > html files you plan to work on. A possibility would be a second tab with images and css files besides the html/php/whatever files, but this would clutter up the UI a lot. > Con - gthumb style can only drag files to folders in the same folder as > the file already is That wouldn't be a problem if the folders would stay a tree and only files were in an own list. So this is not relevant if the file browser would be splitted to treeview for folders and a flat file view of the currently selected folder. > Con - can't glance at the file tree to see the file system structure of > the site. With the folders in tree you can at least see the folders which should indicate by it's name what type of files it is containing. Also less relevant. Regards, Sven |
From: David A K. <da...@sc...> - 2005-03-04 00:06:57
|
The 2 pane version will be going into screem, I've been suffering from the problem of scrolling myself recently, where I have too many files to be able to copy one to another folder. The implementation is done, but is currently suffering from what I think is a GTK bug so isn't yet checked into cvs. David --=20 Make your website SCREEM - Site Creating & Editing EnvironMent URL: http://www.screem.org/ Mail: da...@sc... |