MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009672ParaViewFeaturepublic2009-10-07 11:242010-10-27 20:48
ReporterKen Moreland 
Assigned ToSebastien Jourdain 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.10 
Project
Topic Name
Type
Summary0009672: Separate Python tracing/macros from Python shell dialog
DescriptionRight now when you open the Python shell dialog, the dialog has attached a bunch of widgets concerning macros and Python tracing. This is too much stuff for this dialog box. The Python shell dialog should go back to being just a shell. The tracing and macro widgets should be moved to their own separate dialog box.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0011251closed Sebastien Jourdain Mechanisms to distribute macros with Paraview 
related to 0010966closed Sebastien Jourdain What's the point of the Directory View tab in Python Shell 
related to 0011068closed Sebastien Jourdain toolbar that calls macros 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-10-07 11:24Ken MorelandNew Issue
2010-04-16 11:11Utkarsh AyachitTarget Version3.8 => 3.10
2010-04-20 17:09Pat MarionNote Added: 0020298
2010-07-08 17:10Ken MorelandRelationship addedrelated to 0010966
2010-09-01 11:17Utkarsh AyachitRelationship addedrelated to 0011068
2010-09-01 11:17Utkarsh AyachitTarget Version3.10 => 3.10.shortlist
2010-09-20 14:06Utkarsh AyachitStatusbacklog => tabled
2010-09-20 14:06Utkarsh AyachitAssigned To => Sebastiennn Jourdain
2010-09-20 14:08Utkarsh AyachitRelationship addedrelated to 0011251
2010-09-20 14:12Pat MarionNote Added: 0022283
2010-09-20 15:00Ken MorelandNote Added: 0022284
2010-09-27 10:35Sebastien JourdainNote Added: 0022366
2010-09-27 10:35Sebastien JourdainStatustabled => @80@
2010-09-27 10:35Sebastien JourdainFixed in Version => 3.10
2010-09-27 10:35Sebastien JourdainResolutionopen => fixed
2010-10-15 20:37Alan ScottNote Added: 0022502
2010-10-15 20:37Alan ScottStatus@80@ => @20@
2010-10-15 20:37Alan ScottResolutionfixed => reopened
2010-10-22 10:02Sebastien JourdainNote Added: 0022659
2010-10-22 10:02Sebastien JourdainStatus@20@ => @80@
2010-10-22 10:02Sebastien JourdainResolutionreopened => fixed
2010-10-27 20:48Alan ScottNote Added: 0022719
2010-10-27 20:48Alan ScottStatus@80@ => closed
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature

Notes
(0020298)
Pat Marion   
2010-04-20 17:09   
If it makes any difference... the widgets to the side of the python shell can be collapsed using the horizontal slider, so they are not shown at all. This is remembered between sessions.
(0022283)
Pat Marion   
2010-09-20 14:12   
If you click "show trace" and "trace state" in the trace tab, there is output that is printed to the console. If these tabs are separated from the console, maybe there should be a new text area to display the text?
(0022284)
Ken Moreland   
2010-09-20 15:00   
Showing the trace in the console seems really odd in the first place, because it is never executed even though it looks like commands. The only real reason to put it there is programmer convenience.

So, yes, there should be some other text area to display the text. That text area could appear on demand. For example, pop up that Python editor with the text in it.
(0022366)
Sebastien Jourdain   
2010-09-27 10:35   
Fixed provided inside the commit 8d67360bcc130352b75f5ff8c334ca09b729cf74

- Start/Stop trace are available inside the menu now.
- Edit/Save trace are available inside the menu now.
- A text message keep showing in the status bar while the recording is ON.
(0022502)
Alan Scott   
2010-10-15 20:37   
I really like what has been done so far.

Questions:
* Why not add a "run trace" or "run memory trace" button to tools? That way, user doesn't have to write it to a file, then run it.
* Why not allow a user to "run macro" in Macros, without adding? What if user wants to do this once?
(0022659)
Sebastien Jourdain   
2010-10-22 10:02   
commit d37a8cd2233b59747c285a4a348ef4952997768e
Merge: f5f9a47 2d052f1
Author: Sebastien Jourdain <sebastien.jourdain@kitware.com>
Date: Fri Oct 22 09:52:11 2010 -0400

    Merge topic 'python-trace-ui'
    
    2d052f1 Change strategy around Python trace usage

commit 2d052f1d9ba54bbdee6cc9b89bbb8f01095adf39
Author: Sebastien Jourdain <sebastien.jourdain@kitware.com>
Date: Fri Oct 22 09:43:19 2010 -0400

    Change strategy around Python trace usage
    
    Now the user can only start/stop trace. When the user stop a trace,
    the Python editor Popup with the content of the trace. The user has
    to choose what he wants to do with it. He can discard it, save it as
    a file or save it as a Macro.
    
    Caution: As only one editor is used for Python code editing inside
             ParaView. If the user do not save its trace and re-run
         another one, when it stop it, the editor will be reset
             to the later trace content. The same thing happen when
             you try to edit a Macro while the editor is open.
(0022719)
Alan Scott   
2010-10-27 20:48   
Excellent. Tested local server, Windows, trunk.