Talk:Main Page: Difference between revisions

From PyMOLWiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:


=== Some Thoughts For Discussion ===
=== Some Thoughts For Discussion ===
* Would it be helpful to get rid of display of the somewhat awkward "Cmd" prefix for commands, and simply do a better job of separating the sections that cover concepts and ideas from those that discuss specific commands?   
* Would it be helpful to get rid of display of the somewhat awkward "Cmd" prefix for commands, and simply do a better job of separating the sections that cover concepts and ideas from those that discuss specific commands?   


Line 14: Line 13:


[[User:Warren|Warren]] (BTW: Please don't weight what I write too heavily here.  With respect to PyMolWiki, I am just another user -- and a clueless one at that).
[[User:Warren|Warren]] (BTW: Please don't weight what I write too heavily here.  With respect to PyMolWiki, I am just another user -- and a clueless one at that).
----
=====Begin Inchoate's Comments To Warren=====
First off, thanks for the post.  I always welcome better ways to work and organize information.  I don't claim to know any more than anyone else, I just took the initiative for PyMolWiki.


=== Hierarchy and Naming===
Warren, you're completely rightSomething needs to change, to make this more usable for people.  I tried to organize the PyMol information via the user manual and user commentsImposing a hierarchy on a system that doesn't really want one, isn't such a good idea, or my imposition was implemented incorrectlyThe link names need to be MUCH shorter: take a look at http://wikipedia.orgThey have 500,000+ pages and they have short link names. I tried to make a hierarchy so that if three such people come in and look up "rotate" that they go to the right pageThat is, there's "rotate," "cmd.rotate," and camera independent rotations and whatnot. We have name ambiguititiesDo we just make one big page with "rotate" and include all its information there, or do we make "rotate" a category and dole out the pages to the category?
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 wrongSo, 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 documentationMaybe we need a chatroom and a time to meet so we can hash this out w/folks.  Ideas, comments?
 
[[User:Tree|Tree]] 22:21, 20 Feb 2005 (CST)
 
=== Organizing PyMol Commands ===
 
==== New Simpler Rules ====
Our naming idea was stupid, tooAll commands are easily found under [[:Category:Commands|PyMol Commands]]We have something like 60 commands or so already documented!  All we require is that if you make a PyMol command page that you
* try to keep it simple like the ones we have up so far
* link it to the main PyMol Commands category by adding the text
<pre>[[Category:Commands|command_name_here]]</pre> Obviously replacing command_name_here with your command name.
* Make the see also's links as wellIt's real simple.  Just wrap the command in
<pre>[[Cmd command_name]]</pre> and that's it.  So, "center" becomes, <pre>[[Cmd center]]</pre>.  
 
==== Examples ====
See [[Cmd center|center]]
 
[[User:Tree|Tree]] 15:02, 19 Feb 2005 (CST)
 
== 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.
--[[User:Saper|Saper]] 22:54, 16 Feb 2005 (CST)
 
Saper, I had considered thatI 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. (?)
<br>
[[User:Tree|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?


[[User:Tree|Tree]]
I'm ambivalent towards empty links.  They remind me of what basic concepts that need filling, but are annoying if you're searching for info. and there's nothing there.


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.
As far as the comments on categories and subcategories, as I understand it, you can't use double ":"s in names. You have categories and then something is made a subcategory by claiming that is'a  category of a category. Kinda' strange.
--TheDude


=== Expanded Schema ===
I do think organization is good.  My way was seemingly obfuscated.  Don't you think PyMol commands should somehow be lumped into available categories?
Proposal to incorporate more than just a manual into this site:
Changes to be made from my POV:
* Much shorter link names
* Kill the hierarchy?
* How to use the Wiki Intro


# Manual
[[User:Inchoate|Inchoate]] 00:48, 6 May 2005 (CDT)
## GUI
----
## Command Script
## Python API
## Settings
## Miscellaneous
## Command Line
# Meta Manual
## Selections
## Colors
## Palettes
## Writing/Running Scripts
## Customizing PyMOL
# Discussions
## News
## Development
## Questions
# Special Topics
## Movies and Animation
## biochemical calculations
## NMR
## Crystallography
## DNA
## Stereo 3D

Revision as of 00:48, 6 May 2005

New

Some Thoughts For Discussion

  • Would it be helpful to get rid of display of the somewhat awkward "Cmd" prefix for commands, and simply do a better job of separating the sections that cover concepts and ideas from those that discuss specific commands?
  • Empty links discourage. Could we eliminate them sooner rather than later? Yes, they are helpful initially for maintaining some structure, but people do get bummed out when they follow a link for an interesting topic and end up with nothing. If there are too many of these, then they may quit and go home before finding the real content -- and that would be a shame since there is now plenty of real content.
  • For those coming into the Wiki for the first time, we should insure that the most useful content is out front and on top. Right now the TOC has an awful lot of blank links, so having it on top isn't so helpful as a starting point for nagivation. In contrast, the Categories, Script Library, and PyMOL Commands sections all seem like pretty good starting points.
  • For people (like me) who don't know the first thing about Wiki's, more "newbies click here to learn" links would help ease the transition...
  • Categories & subcategories confuse me. The resulting titles baffle. For example, Category: Using Pymol Objects and Selections Working with Objects. Shouldn't there be another colon in there? Category: Using Pymol Objects and Selections: Working with Objects Is this just a Wiki thing?

Warren (BTW: Please don't weight what I write too heavily here. With respect to PyMolWiki, I am just another user -- and a clueless one at that).


Begin Inchoate's Comments To Warren

First off, thanks for the post. I always welcome better ways to work and organize information. I don't claim to know any more than anyone else, I just took the initiative for PyMolWiki.

Warren, you're completely right. Something needs to change, to make this more usable for people. I tried to organize the PyMol information via the user manual and user comments. Imposing a hierarchy on a system that doesn't really want one, isn't such a good idea, or my imposition was implemented incorrectly. The link names need to be MUCH shorter: take a look at http://wikipedia.org. They have 500,000+ pages and they have short link names. I tried to make a hierarchy so that if three such people come in and look up "rotate" that they go to the right page. That is, there's "rotate," "cmd.rotate," and camera independent rotations and whatnot. We have name ambiguitities. Do we just make one big page with "rotate" and include all its information there, or do we make "rotate" a category and dole out the pages to the category?

I'm ambivalent towards empty links. They remind me of what basic concepts that need filling, but are annoying if you're searching for info. and there's nothing there.

As far as the comments on categories and subcategories, as I understand it, you can't use double ":"s in names. You have categories and then something is made a subcategory by claiming that is'a category of a category. Kinda' strange.

I do think organization is good. My way was seemingly obfuscated. Don't you think PyMol commands should somehow be lumped into available categories? Changes to be made from my POV:

  • Much shorter link names
  • Kill the hierarchy?
  • How to use the Wiki Intro

Inchoate 00:48, 6 May 2005 (CDT)