[chimera-dev] savepos

[Tom Goddard]

Hi Matt,

  One idea is use the Chimera note pad that lets you write any text notes and they are saved in the session, menu Tools / Utilities / Notepad.  You could put position names and notes about those positions in using note pad.

  If you don’t like that I’d say the real issue is user interface, how will you type the notes in and how will you view them.  If you plan on providing that user interface in your own dialog then I’d suggest you can just keep a Python dictionary mapping names to notes and your tool will save these in sessions.

  Using the iPad to control Chimera so it can be passed around during a group visualization session is cool.  When I show Chimera stereo visualization to visiting students I usually pass around a wireless space navigator so they can change the view point.  I wonder what they would do if the controller allowed them to change molecule display styles, clip the model, change colors.  Seems like changing view points (flying around) is the main interesting thing.  Probably the second most interesting capability would be to blow things up!

	Tom


> On Jun 10, 2015, at 5:05 PM, Dougherty, Matthew T wrote:
> 
> This relates to a previous email exchange.
> 
> I would like to add a description parameter to the import of midas positions.  The reason is that I would like to keep the position names brief when I am doing scripting, but would like to put detailed information in the description, for example a flag indicating that the research group has picked particular positions to be used in an animation after proofing through a pool of 50 saved positions.  I would also like to use the field to indicate other things such as which animation is is to be used in, number of seconds I should hold the position before moving on, date it was created, etc.
> 
> I think there are two ways to add a description field into position
> 1) something in the chimera build that I could access with python, 
> 2) something I would add through my python code.  If I did this I would have concern that the description parameter gets included in the session save, or could create incompatibilities in the session files down the road on later chimera builds.
> 
> Which method would you recommend?
> 
> 
> In a related s/w dev comment, I am now connecting an ipad via wifi, to my laptop.  This is allows me to pass the ipad around as a control surface in a collaborative conference room/dome environment.  As the conductor of the collaborative viz, I would have buttons on the laptop that would alter the gui on the ipadbased on the needs of the moment (e.g., color, stereo3D, threshold).  This part of overall HID toolbox of multiple gamespads, contour shuttle dialbox, 3dconnection, and master control button boxes, where I am remapping variables (e.g., translation/rotation) to an HID such that a user can make a preference as to which HID is more intuitive.
> 
> 
> 
> Matthew Dougherty
> National Center for Macromolecular Imaging
> Baylor College of Medicine
> ===========================================================================
> _______________________________________________
> Chimera-dev mailing list
> Chimera-dev at cgl.ucsf.edu <mailto:Chimera-dev at cgl.ucsf.edu>
> http://www.rbvi.ucsf.edu/mailman/listinfo/chimera-dev <http://www.rbvi.ucsf.edu/mailman/listinfo/chimera-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://plato.cgl.ucsf.edu/pipermail/chimera-dev/attachments/20150611/c56a4c77/attachment.html>