Thread: [Bashburn-info] new filemanager
Brought to you by:
bashburn
From: Markus K. <mar...@on...> - 2008-10-13 14:36:42
|
I think the filemanager is a great idea since it is not easy to explain someone why he had to give in bash commands to define data - and in other bashburn menus not. Good work, Anders. I suggest to include this in bashburn 3.1 - but we have to improve it to make it easy usable: * color directories in another color as the files * list files/dirs also horizontal to use display space better * cut list of large data to a "page" and provide a simple page selection * provide also removing of files in the burn-dir in the same usage as adding files * as a future function we could also provide burn-data saving, which allows users to define data once - and store it in a file for future use. One may say the filemanager is not so powerful like the method now to define data. This may be true for experienced users. But since we also welcome all users and give each the ability to easy burn cd, we should think of that (we could provide the old data definition method in future, too). Markus |
From: Steven W. O. <st...@sy...> - 2008-10-13 17:37:01
|
On Monday, Oct 13th 2008 at 10:37 -0000, quoth Markus Kollmar: =>I think the filemanager is a great idea since it is not easy to explain =>someone =>why he had to give in bash commands to define data - and in other =>bashburn menus not. =>Good work, Anders. => =>I suggest to include this in bashburn 3.1 - but we have to improve it to =>make it easy usable: => =>* color directories in another color as the files =>* list files/dirs also horizontal to use display space better =>* cut list of large data to a "page" and provide a simple page selection =>* provide also removing of files in the burn-dir in the same usage as =>adding files =>* as a future function we could also provide burn-data saving, which =>allows users to => define data once - and store it in a file for future use. => =>One may say the filemanager is not so powerful like the method now to =>define data. =>This may be true for experienced users. But since we also welcome all =>users and give each the ability =>to easy burn cd, we should think of that (we could provide the old data =>definition method in future, too). I like the idea of the file manager, but there are already so many file managers out there that we really don't want to write a new one that might prevent the user from selecting one that he already likes (e.g., mc, konqueror, etc...) * The use could have an BBFILEMGR to override the default one that we could supply. * I'm leary of the whole color thing because it currently makes the presumption about running with a black background/white foregound. We need to implement themes so that people can define things the way they want. And if we do it right then users will be able to contribute themes to us for distribution. * The last suggestion about burn-data saving is something I very much like. k3b has the same notion, so if you regularly burn the same data over an over, you might just select a predefineable project and your burndir would automagically populate. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
From: Anders L. <and...@gm...> - 2008-10-13 20:30:09
|
On Monday 13 October 2008 16:37:39 Markus Kollmar wrote: > I think the filemanager is a great idea since it is not easy to explain > someone > why he had to give in bash commands to define data - and in other > bashburn menus not. > Good work, Anders. > Thanks. It was just an idea I wanted to try out. I always felt the linking of files, while not difficult didn't really fit into the rest of BashBurn. > I suggest to include this in bashburn 3.1 - but we have to improve it to > make it easy usable: > > * color directories in another color as the files That's an idea. Or maybe some sort of indicator (<Dir>) to show that it's a directory and not a file. > * list files/dirs also horizontal to use display space better Good idea. > * cut list of large data to a "page" and provide a simple page selection Also a good idea. Maybe show like 25 files/directories by page and the user can press 'n' to go to the next page and maybe 'p' to go to the previous. > * provide also removing of files in the burn-dir in the same usage as > adding files > * as a future function we could also provide burn-data saving, which > allows users to > define data once - and store it in a file for future use. > Why not. > One may say the filemanager is not so powerful like the method now to > define data. > This may be true for experienced users. But since we also welcome all > users and give each the ability > to easy burn cd, we should think of that (we could provide the old data > definition method in future, too). > We could perhaps add a new variable where the user can select to use the old way, this file manager or some external one. -- Anders Lindén http://bashburn.dose.se |
From: Anders L. <and...@gm...> - 2008-10-13 22:10:11
|
I committed a new version of the file manager that displays files in three columns, marked with [d] or [f] depending on whether they are files or directories. I also added a delete mechanism that works the same way as the file linking one. The difference is that the delete function is 'locked' to BBBURNDIR. Anyone has a good idea on how to implement a page system? Let's say we want to show a maximum of 16 entries per page (Three columns, four rows). Anyway, try it out and let me know what you think. -- Anders Lindén http://bashburn.dose.se |
From: Nick W. <ni...@uk...> - 2008-10-14 07:29:00
|
On Mon, 13 Oct 2008 23:40:28 +0200 Anders Lindén <and...@gm...> wrote: > I committed a new version of the file manager that displays files in > three columns, marked with [d] or [f] depending on whether they are > files or directories. I also added a delete mechanism that works the > same way as the file linking one. The difference is that the delete > function is 'locked' to BBBURNDIR. > > Anyone has a good idea on how to implement a page system? Let's say > we want to show a maximum of 16 entries per page (Three columns, four > rows). > > Anyway, try it out and let me know what you think. > I have added a small fix - the column count logic was wrong, and every 4th file/dir wasn't being printed to stdout. Another issue is trying to delete directories. rm <filename> doesn't work here, of course. ==== File(s): 12 rm: cannot remove `/home/nick/burn/test': Is a directory 12 -> /home/nick/burn/test deleted. Files deleted from /home/nick/burn ==== One way is to check if dir is emtpy and use 'rmdir', or the real dangourous way if it isn't empty is 'rm -[r]f'. Perhaps it easier to ask used to empty the directory first, as I wouldn't like to see 'rm -[r]f' in the code. Nick -- Free Software Foundation Associate Member 5508 |