MantisBT - ParaView
View Issue Details
0010966ParaViewFeaturepublic2010-07-08 17:092010-10-18 13:14
Ken Moreland 
Sebastien Jourdain 
normalminorhave not tried
closedfixed 
 
 
0010966: What's the point of the Directory View tab in Python Shell
The Python Shell has a Directory View tab that contains a very sub-par file browser. This tab seems to do nothing other than confuse the GUI. Two simple things should be done:

1. Add an "Add" button to the Macros tab. When clicked, it opens the file browser to select a Python script on the local directory.
2. Get rid of the Directory View tab and everything in it.
No tags attached.
related to 0009672closed Sebastien Jourdain Separate Python tracing/macros from Python shell dialog 
Issue History
2010-07-08 17:09Ken MorelandNew Issue
2010-07-08 17:10Ken MorelandRelationship addedrelated to 0009672
2010-07-14 11:06Pat MarionNote Added: 0021391
2010-07-14 11:26Ken MorelandNote Added: 0021392
2010-09-01 11:18Utkarsh AyachitTarget Version3.10 => 3.10.shortlist
2010-09-20 14:32Utkarsh AyachitStatusbacklog => tabled
2010-09-20 14:32Utkarsh AyachitAssigned To => Sebastiennn Jourdain
2010-09-27 10:37Sebastien JourdainNote Added: 0022367
2010-09-27 10:37Sebastien JourdainStatustabled => @80@
2010-09-27 10:37Sebastien JourdainResolutionopen => fixed
2010-10-15 20:29Alan ScottNote Added: 0022501
2010-10-15 20:29Alan ScottStatus@80@ => closed
2010-10-18 13:14Ken MorelandNote Added: 0022523
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature

Notes
(0021391)
Pat Marion   
2010-07-14 11:06   
Hi Ken,

I agree with you that this tab is confusing. Let me just explain the intent of this tab-

The text entry allows you to define a script directory. Next to the text entry there is a button to open a native choose-directory dialog. The 'script directory' is a place where you can save all your paraview related scripts. The directory view shows only .py files and subfolders of the script directory.

You can double click on the scripts in the directory view to open them in a text editor. The text editor is another very sub-par widget, but it is somewhat convenient for making quick on-the-fly changes to scripts, such as changing a reader's filename property. Then you can quickly re-run the script by clicking the 'run selected' button. Without this button, you have to open a file-chooser dialog each time you want to run the script again.

Also, in a fresh installation of paraview the script directory defaults to a 'demo' directory. Unfortunately paraview ships with only one not-very-impressive demo script.


Honestly, I use the directory view tab quite a bit, but that's not surprising since I put it there :) Now that you point it out, I see how tedious it is to navigate the directory view in order to locate a script to add as a macro. I've just never needed to navigate with the directory view because I always save my scripts to the same location. Anyway, I have no problems with removing this tab completely.
(0021392)
Ken Moreland   
2010-07-14 11:26   
Thanks for the description Pat. I would still advocate getting rid of the Directory tab. Instead, I would just migrate this functionality to the Macros tab. The point, as I understand it, is to provide quick editing/running functionalities for a set of python scripts. They make a lot of sense for the selection of scripts bound to macros, but a bit more dubious for scripts in some arbitrary directory.
(0022367)
Sebastien Jourdain   
2010-09-27 10:37   
Fixed provided inside the commit 8d67360bcc130352b75f5ff8c334ca09b729cf74

- The graphical panel that was on the right of the python shell has been removed
- All the features have been integrated inside the ParaView menu itself
-- Creation of a macro is inside the Macro menu itself
(0022501)
Alan Scott   
2010-10-15 20:29   
Very nice.
(0022523)
Ken Moreland   
2010-10-18 13:14   
Agreed. The new interface is way cool.