Woopsi /

Filename Size Date modified Message
Pics
Woopsi
34.5 KB
1.5 KB
8.0 KB
1.4 KB
892 B
* Copyright (c) 2007-2008, Antony Dzeryn
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions are met:
*     * Redistributions of source code must retain the above copyright
*       notice, this list of conditions and the following disclaimer.
*     * Redistributions in binary form must reproduce the above copyright
*       notice, this list of conditions and the following disclaimer in the
*       documentation and/or other materials provided with the distribution.
*     * Neither the names "Woopsi", "Simian Zombie" nor the
*       names of its contributors may be used to endorse or promote products
*       derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY Antony Dzeryn ``AS IS'' AND ANY
* EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL Antony Dzeryn BE LIABLE FOR ANY
* DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

  
Woopsi
------

  Woopsi is a windowing system for the Nintendo DS, written in C++.  The aim of
  the project is to create a windowing system that other programmers can use for
  their applications, decreasing the tedious amount of GUI code that they have
  to write.
  
  The system itself is loosely based on the Commodore Amiga's "Intuition"
  windowing system.  The look-and-feel of the system intentionally resembles the
  old Amiga system.  There are several reasons for this:
  
  - It gives me a template to work from, reducing the amount of work I need to
    do;
  - Intuition was designed for low-power, low-resolution hardware;
  - It seemed like a good idea at the time.
  
  The windowing system is *not* intended to be a complete desktop environment.
  It is *not* going to be a DS version of GNOME, KDE or Windows Explorer.  It
  will simply provide a system for rapidly building window and gadget-based
  interfaces.
  

Features
--------

  - Multiple screen support;
  - A full set of user interface components:
    - Text buttons with text alignment functionality;
    - Image buttons;
    - Animated buttons;
    - Radio buttons and radio button groups;
    - Check boxes;
    - Single-line textboxes;
    - Multi-line text boxes;
    - Screens;
    - Windows;
    - Gradient backgrounds;
    - SuperBitmap, for persistent drawing and displaying large bitmaps in small
      gadgets;
    - Scrolling panels, for containing graphics or gadgets within regions that
      are larger than the parent container;
    - Scroll bars;
    - Slider bars;
    - Context-sensitive menu;
    - List boxes;
    - Progress bars;
    - Requesters;
    - File requesters;
    - Cycle buttons.
  - Skinnable screens and windows;
  - Draggable gadgets, including draggable windows and screens;
  - Borderless gadgets, including borderless windows;
  - Built-in debug console;
  - All gadgets can become modal;
  - Intelligent, optimised gadget drawing and erasing;
  - Event system;
  - Depth sorting;
  - Automatic gadget garbage collection;
  - Complete API for constructing new gadgets:
    - Extensible font system that supports:
      - Fixed-width, bit-packed monochrome fonts;
      - Fixed-width, 16-bit colour bitmap fonts;
      - Compressed proportional fonts (monochrome and 16-bit).
    - Text manipulation, including wrapping functions and width calculation;
    - Animation class with support for variable framerates and standard/pingpong
      looping;
    - GraphicsPort class providing depth-sorted, clipped, hardware-accelerated
      drawing functions:
      - Pixel plotting;
      - Optimised horizontal/vertical lines;
      - Bresenham omni-directional lines;
      - Filled and unfilled rectangles;
      - Filled and unfilled circles;
      - Bitmap blitting;
      - Bitmap blitting with transparent colour key;
      - XOR horizontal/vertical lines and pixel plotting;
      - Flood fill.
    - Linked list, dynamic array and hashmap template container classes and
      iterator classes.
  - Object-orientated design for easy integration into other C++ software;
  - Simple API for rapid GUI creation;
  - Simplistic "multitasking" - each window runs simultaneously;
  - Uses 16-bit framebuffer display mode;
  - Multiple build options:
    - With/without PALib support;
    - SDL layer to facilitate native compilation on non-DS platforms and
      aid porting;
    - libwoopsi.a library build.


Requirements
------------

  To run the project you will need either a DS emulator or a real DS and a flash
  cart.
  
  To compile the project you need devKitPro and an IDE of some sort.  This
  archive contains a VC++ 2005 Express project.
  
  To use Woopsi with PALib:
  
   - Replace the "Makefile" with "Makefile.palib".
   
  To use Woopsi with libnds:
  
   - Replace the "Makefile" with "Makefile.libnds".
   
  To build a library version of Woopsi:
  
   - Open a CLI;
   - Navigate to the Woopsi directory that contains the makefiles;
   - Type "make -f Makefile.lib", sans quotes.
   
  Woopsi has been developed using devkitPro r20, VC++ 2005 Express, and the last
  official version of PALib (070323).  It has been tested with devkitPro r23.
  

SDL Compatibility
-----------------

  Woopsi has been designed to be portable.  Thanks to this, Woopsi comes
  equipped with an optional SDL layer that replaces libnds and allows the code
  to be compiled for any platform with an SDL port.  To create an SDL build of
  Woopsi:
  
   - Create a new SDL project in your dev environment of choice;
   - Copy the "woopsi" source folder into your SDL project;
   - Copy the contents of the "sdl" folder from this archive into your copy of
     the "woopsi" folder.
     
  Assuming you set up the initial project correctly, you can now develop Woopsi
  applications using SDL.
  
  Note that you should not use the Woopsi makefiles, as these are only relevant
  to DS builds of Woopsi.
  
  
Credits and Acknowlegements
---------------------------

 - Coding and design                                - Antony Dzeryn
 - Testing, technical advice, other contributions   - Jeff Laing
 - PALib independence                               - Steve
 - More testing and suggestions						- John Buxton
 - Simian Zombie logo                               - John Clay
 - Thanks to                                        - The devKitPro team
                                                    - The PALib team
                                                    - Nintendo
                                                    - R. J. Michal


Links
-----

 - http://ant.simianzombie.com/blog                 - Woopsi development blog
 - http://ant.simianzombie.com/forum                - Woopsi forum
 - http://www.sourceforge.net/projects/woopsi       - Woopsi SourceForge page


Email
-----

  Contact me at spam_mail250@yahoo.com.


Licencing and Contributions
---------------------------

  Any contributions of bugfixes or new features will be gratefully received.
  Any such contributions must follow the style guidelines laid out in Woopsi's
  documentation.  They must also be of sufficient general usefulness and quality
  to qualify for inclusion in the main code base.
  
  Please don't be offended if I reject or tidy up submissions that don't meet
  these criteria.
  
  All code will continue to be distributed under the BSD licence, so do not
  contribute code if you are unwilling to release it under that licence.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.