Difference between revisions of "Talk:Main Page"

Revision as of 02:28, 22 February 2005

New

Hierarchy and Naming

Ok, the hierarchy is good, however the naming convention is foolish. Since the only hierarchy is based on how categories link to each other let's make all salient points in the hierarchy below it's own category and make the less prominent its own page. Yes/No?

I'm new at this and just want the best layout. I think I was wrong in my first design, I think began to realize it when I was typing the same thing over and over: in CS whenver you're doing that, you're doing something wrong. So, following others' suggestions, keep the page names short. I'll try to clean up the CmdScrip and API stuff tonight. I think the CmdScript stuff and API stuff should all be on page as Warren has them in the documentation. Maybe we need a chatroom and a time to meet so we can hash this out w/folks. Ideas, comments?

Tree 22:21, 20 Feb 2005 (CST)

Added Lotsa Commands

Took a little while a added a bunch of commands. Need more.

Old

User Comments

Should content from the User's and Reference manual be incorporated into this site? Then in the content pages, one could reference a section of Walter's manuals. --Saper 22:54, 16 Feb 2005 (CST)

Saper, I had considered that. I was going to strip out all the commands from PyMol and make a "commands" page where people could flush in some content. Maybe we'd be better off starting with page-by-page inserting PyMol commands into the wiki. (?)
Tree 00:12, 17 Feb 2005 (CST)

Nucleic Acids

From Luca Jovine: I apologize for being late, but... how about a section about nucleic acids? As in any other related program, they always end up being the poor siblings of proteins (I can't believe PyMOL's cartoon command still does not recognise the most common 5' and 3' nucleotides!), and I'm pretty sure people who work with them would benefit from such a section in the Wiki. Thanks,

Where should we put the Nucleic Acids Stuff?

Tree

For NA's - at the moment, the most appropriate location seems to be "Modeling and Editing". But perhaps we should add a special section devoted to types of molecules? ie/small molecules (like fatty acids, ligands, etc), nucleic acids, proteins, nucleic-acid/protein complexes, large macromolecules (ie/ribosome). I'm sure people have tips on how best to represent and work with each. Scale always seems to be an important factor when thinking of display details. --TheDude

Organizing PyMol Commands

Possibly Deprecated: Need Feedback

Our naming idea was stupid, too. All commands are easily found under PyMol Commands.

We have something like 60 commands or so already documented!

Examples

See CmdScript.center

See Cmd.center

Tree 15:02, 19 Feb 2005 (CST)

For CmdScript, would it make more sense to mirror the API style and do

 [[Category:CmdScript|Cmdscript]]
 [[Category:COMMANDNAME|COMMANDNAME]]

--Jcorn 18:20, 19 Feb 2005 (CST)

Yes, the CmdScript commands should all link back (be categorized in the CmdScript category.

Tree 22:21, 20 Feb 2005 (CST)

Expanded Schema

Proposal to incorporate more than just a manual into this site:

Manual
1. GUI
2. Command Script
3. Python API
4. Settings
5. Miscellaneous
6. Command Line
Meta Manual
1. Selections
2. Colors
3. Palettes
4. Writing/Running Scripts
5. Customizing PyMOL
Discussions
1. News
2. Development
3. Questions
Special Topics
1. Movies and Animation
2. biochemical calculations
3. NMR
4. Crystallography
5. DNA
6. Stereo 3D

@@ Line 37: / Line 37: @@
 ==== Possibly Deprecated: Need Feedback ====
-NEW: Tell me what you guys want!
-Due to the inherent ambiguity of wiki naming, we have come up with a way to categorize the naming/sorting of PyMol commands.
+Our naming idea was stupid, too.  All commands are easily found under [[:Category:Commands|PyMol Commands]].
-Since PyMol has two types of commands: command script as Warren calls it; and, the API we will separate the two by the following convention.
+We have something like 60 commands or so already documented!
-Command Script commands page names will be "CmdScript COMMANDNAME" and will be in the category called, "CmdScript".  The API naming will be similar, but we don't have to worry about namespace collisions b/c that's already been taken care of by Warren in that he has differen library names, viz "cmd" and "util" and whatnot.  So an API command will be "LIBRARYNAME.COMMANDNAME" and will be in the category "API COMMANDS".
-Lastly, make sure you add the category text at the bottom of each page as needed.  If you're adding to the CmdScript then put this at the bottom
-<pre>
- [[Category:CmdScript COMMANDNAME|COMMANDNAME]]
-</pre>
-If for some library put
-<pre>
- [[Category:API|API]]
- [[Category:LIBRARYNAME|FUNCTIONAME]]
-</pre>
-This will allow us to keep track of all CmdScripts in one category, and also allow us to keep categories of individual Libraries and ALL API commands as well.  Very cool.
 ==== Examples ====