• Protein Database files(*.pdb)
  
• Hyper-Chem files (*.hin)
  
• *.mld
  
• *.mol
  

• Can save image as BMP/PNG/JPG/PCX/JPEG2000/ICO/GIF/TGA format.
  
• Stereo View Mode
  
• User definable atom definition file
  

Molecule Spatioplotter ver 1.02 [kwmsp102.zip (644 KB)]

Solid Sphere	Line+Label	Sphere and Line
Sphere and Cylinder	Translucent Sphere and line	Volume Rendering

• Borland C++ version 5.02J
  
• Microsoft Visual C++ 2005
  
• jpeg-6b
  This software is based in part on the work of the Independent JPEG Group.
  
• libpng: version 1.2.5
  
• zlib: version 1.2.1
  
• libtiff: version 3.5.7
  
• JasPer: IMAGE POWER JPEG-2000
  
• CxImage: version 5.99c
  

• PDB: Protein Data Bank (*.pdb)
  http://www.rcsb.org/pdb/
  
• HIN: HyperChem package has *.HIM files.
  It used to have lots of data in the trial version package. I don't know current version, but maybe.
  http://www.hyper.com/
  
• MOL :
  
• MLD: MOLDA package comes with tons of molecule data file (*.mld).
  MOLDA for Windows
  
• Protein Explorer proteinexplorer.org
  

• George Spencer-Brown, Laws of Form. 1994. ISBN:0-9639899-0-1
  
• Boundary Institute for the Study of Foundations http://www.boundaryinstitute.org/
  
• Dr. William Bricken's Homepage http://wbricken.com/index.html
  

• Cooper, Alan. About Face: The Essentials of User Interface Design. (Foster City, CA: IDG Books Worldwide, 1995)
  
• Norman, Donald A. The Design of Everyday Things. (New York: Doubleday, 1990)
  

• A software design must be based not on features but on the user's tasks. To achieve this purpose, I think we should describe the task-function relationship. All functions have to belong to at least one task.
  
• We should provide several methods to complete a task. I agree with the point that within a flow of functions, an operation should produce one result.
  
• I agree with Raskin's view, "A well-designed and humane interface doesn't have to be split into beginner and expert subsystems." (Raskin, 2000, p.70) Providing several methods to do a task will help a user transit from beginner to expert.
  
• I think we also have to have a measure to quantify the distance between a user's goal and a presented goal provided by a program.
  

• Time to perform
  
• A structure and steps to perform
  
• A proper report
  
• A distance between goal and implementation
  

1. To indicate to users that there are functions in the program.
   
2. To give a guide to performing the task and the flow of functions.
   

1. Affordance (Norman, 1999)
   "The required information was in the world: the appearance of the device could provide the critical clues required for its proper operation."(Norman, 1999) The Affordance is a natural property that the object has in the physical world. In this sense, there is no real Affordance in software.
   
2. Constraint (Norman, 1999)
   There are three constraints. Physical constraint limits the user's behavior physically. Logical constraint limits the user's behavior by indicating a user clue which makes user logically aware of the limitation. Cultural constraint is formed in the culture. It provides many conventions to the user.
   
3. Convention (Norman, 1999)
   This is cultural constraint. "There is nothing inherent in the devices or design that requires the system to act in this way." (Norman, 1999) That is, every interface is artificial. If it becomes easier and easier, it becomes natural and intuitive. "The term natural equates to very easy to learn." (Raskin, 2000, p.150)
   

1. Users should be able to control the operation
   
2. A program must not interrupt a user's operation
   
3. The steps must be predictable
   
4. The task should be a skill that can be acquired through practice.
   

• It requires users to keep current Mode. But human being can't do things simultaneously; a user will lose current Mode. This causes operation error.
  
• Even if a program makes a proper feedback of mode, when users are concentrating on their task, they will make a mis-operation.
  
• The more the numbers of mode increase, the more users have to remember the meaning of gesture in each mode. This will increase user's effort to use a program.
  

• The way to describe an interface as combination of atoms, which are defined as basic unit of interface. This is based on the principle from the statement that "any objects that look the same are the same." (Raskin, 2000, p.102)
  
• The method to quantify the quality of a user interface.
  
• The mechanism that how GUI and a language can help each other. This is based on the statement that "We need tools that are driven by language and abstraction, not by touch." (Bricken, 2000) I believe that every application program should have a language (i.e. scripting) to communicate with users. A language and a graphical user interface should be reciprocal.
  

• Cooper, Alan. About Face: The Essentials of User Interface Design. (Foster City, CA: IDG Books Worldwide, 1995)
  ==> About Face 3: The Essentials of Interaction Design (Paperback) ISBN:0470084111
  
• Mullet, Kevin. Sano, Darrell. Designing Visual Interfaces: Communication Oriented Techniques. (Mountain View, CA: SunSoft Press, 1995) ISBN:0133033899
  
• Norman, Donald A. The Design of Everyday Things. (New York: Doubleday, 1990) ISBN:0465067107
  
• Raskin, Jef. The Humane Interface. (Stoughton, MA: ACM Press, 2000) ISBN:0201379376
  
• Vicente, Kim J. "A Few Implications of an Ecological Approach to Human Factors" Human Factors Society Bulletin 33:11, pp.1-4 (Nov. 1990)
  

1. All functions are implemented by myself.
   I'm not using any 3D library, such as DirectX-3D or Open-GL.
   
2. Uses Z-Buffering as hidden surface removal method.
   
3. Based on the KWLib class library.
   

• Shapes: Point, Line, Triangle, Rectangle, Box, Sphere, Cylinder, Prism, Ring, Circle
  
• Various types of Mesh: Mesh, Mesh with color
  
• Regular polygon generator.
  
• Rendering: Z-Buffer, Flat/Phong shading
  
• Only view point can change the location.
  
• Translucent. (using Z-Buffer and Z-Sort.)
  
• Texture mapping to sphere/plane.
  
• Stereo view mode.
  
• Volume Rendering.
  
• 3D Turtle Graphics.
  
• 140,000 polygons per second. (At Celeron 550MHz)
  

• The Net Equation: Electron Orbitals, Quantum Numbers, and Orbital Filling
  
• Orbital Viewer Software: Atomic Orbitals
  From the site, you can download really nice software and document which includes a complete explanation and equations.
  
• Wikipedia: Electron orbital
  

• To study mechanism of framework class library.
  
• To experiment various implementation method.
  
• To experiment various user interfaces.
  
• To study various algorithms.
  

• Classes to extend C++
  
  • KStr: String Class
    
  • Container Classes
    
  • FunctionClasses
    
• Numerical Computation
  
  • Multiple-Precision Arithmetic.
    
• Process and Thread control
  
  • KProcess, KThread, KMutex
    
• Scripting Engine (KWLib-sh)
  
• Classes to develop windows application
  
  • Windows Class
    
  • Window's objects (GDI,DIB,etc.)
    
  • GUI Objects
    
  • KWLib-GUI Widgets (Button, Menu, Scrollbar, etc.)
    These controls are not wrapper class of existing window's class, but my original controls created from scratch. The reason why I developed them from scratch is to experiment various user interface requirement, which is beyond just modification of existing controls.
    
  • Print/Preview Component
    
• UI Description Language
  
  • Menu/Toolbar definition
    
  • Dialog definition
    
• Classes expanding the ability of KWLib
  
  • Image manipulation Class
    
  • 3D-Graphics Engine (KWLib-3D)
    

void KwTree_001(K3DTurtle kt,float w,int ct)
{
  if(ct<0) return;
  float w1=w/4.0, w2=w1*3.;
  kt.Move(w1);    // Draw line only 1/4 length.
  K3DTurtle kt2;
  int i,n=4;
  float a=30, b=360/n;
  for(i=0;i<n;i++){
    kt2=kt; kt2.TurnUp(a);
    // Recursive Call. Change the length slightly by random.
    KwTree_001(kt2,w2*(1.0+0.05*(rand()%10-5)),ct-1);
    kt.RotateRight(b*(i+1));
  }
}

KwTree_001(k3t,w,4);  // Main Call

• Both Recursive Call and Iteration to simulate growing.
  
• Genetic information and its realization mechanisms to simulate a generation of body.
  

• Calculate the nine planets' location and show how they are seen from space.
  
• Planisphere
  

The Earth	The Moon
The Venus
The Mars	The Jupiter

• Data Center
  
  • The Strasbourg astronomical Data Center (CDS)(CDS)
    
• Star Catalogs
  
  • Yale Bright Star Catalogue, 5th Revised Ed. (Hoffleit, Warren 1991) (V/50)
    
  • Sixth Catalogue of Fundamental Stars (FK6) (Wielen+ 2000) FK6(I/264)
    
  • Third Reference Cat. of Bright Galaxies (RC3) (de Vaucouleurs+ 1991) RC3(VII/155)
    

• Calculation of the position of the planets.
  
  • How to compute planetary positions by Paul Schlyter, Stockholm, Sweden
    
  • Planetary Orbital Elements by Solar System Dynamics Group of the Jet Propulsion Laboratory.
    
  • Precession & mean orbital elements
    
  • ELP2000-82 (orbital theory of Moon)
    
  • VSOP87 (orbital theories of planets)
    
  • Astronomy and numerical software source codes
    
• Space-related images and programs: A Space Library
  
• Students for the Exploration and Development of Space (SEDS)
  
• The Nine planets by Bill Arnett
  

• GLOBAL LAND and OCEANS: tbase.bin: TerrainBase Global Terrain Model.
  
• Global 30 Arc Second Elevation Data Set (GTOPO30)
  

• Maple Applications: Maps
  by Ross Taylor and Richard Baur, Department of Chemical Engineering, Clarkson University and by John Oprea, Department of Mathematics, Cleveland State University
  

• A C version of GCTP (FTP site)
  GCTP(General Cartographic Transformation Package) was developed by EROS Data Center and is one of the oldest systems.
  

• CIA World Data Bank II map database
  
• Shoreline / Coastline Databases World Data Center for Marine Geology & Geophysics, Boulder