Mercurial > traipse_dev
view upmana/ReadMe.txt @ 191:a3d7e05085da beta
Traipse Beta 'OpenRPG' {100201-00}
Traipse is a distribution of OpenRPG that is designed to be easy to
setup and go. Traipse also makes it easy for developers to work on code
without fear of sacrifice. 'Ornery-Orc' continues the trend of 'Grumpy'
and adds fixes to the code. 'Ornery-Orc's main goal is to offer more
advanced features and enhance the productivity of the user.
Update Summary (Beta)
New Features:
New Bookmarks Feature
New 'boot' command to remote admin
New confirmation window for sent nodes
Miniatures Layer pop up box allows users to turn off Mini labels, from
FlexiRPG
New Zoom Mouse plugin added
New Images added to Plugin UI
Switching to Element Tree
New Map efficiency, from FlexiRPG
New Status Bar to Update Manager
New TrueDebug Class in orpg_log (See documentation for usage)
New Portable Mercurial
New Tip of the Day, from Core and community
New Reference Syntax added for custom PC sheets
New Child Reference for gametree
New Parent Reference for gametree
New Gametree Recursion method, mapping, context sensitivity, and
effeciency..
New Features node with bonus nodes and Node Referencing help added
New Dieroller structure from Core
New DieRoller portability for odd Dice
New 7th Sea die roller; ie [7k3] = [7d10.takeHighest(3).open(10)]
New 'Mythos' System die roller added
New vs. die roller method for WoD; ie [3v3] = [3d10.vs(3)]. Included for
Mythos roller also
New Warhammer FRPG Die Roller (Special thanks to Puu-san for the
support)
New EZ_Tree Reference system. Push a button, Traipse the tree, get a
reference (Beta!)
New Grids act more like Spreadsheets in Use mode, with Auto Calc
Fixes:
Fix to allow for portability to an OpenSUSE linux OS
Fix to mplay_client for Fedora and OpenSUSE
Fix to Text based Server
Fix to Remote Admin Commands
Fix to Pretty Print, from Core
Fix to Splitter Nodes not being created
Fix to massive amounts of images loading, from Core
Fix to Map from gametree not showing to all clients
Fix to gametree about menus
Fix to Password Manager check on startup
Fix to PC Sheets from tool nodes. They now use the tabber_panel
Fix to Whiteboard ID to prevent random line or text deleting.
Fixes to Server, Remote Server, and Server GUI
Fix to Update Manager; cleaner clode for saved repositories
Fixes made to Settings Panel and now reactive settings when Ok is
pressed
Fixes to Alternity roller's attack roll. Uses a simple Tuple instead of
a Splice
Fix to Use panel of Forms and Tabbers. Now longer enters design mode
Fix made Image Fetching. New fetching image and new failed image
Fix to whiteboard ID's to prevent non updated clients from ruining the
fix.
default_manifest.xml renamed to default_upmana.xml
author | sirebral |
---|---|
date | Mon, 01 Feb 2010 09:57:07 -0600 |
parents | 52f6a38f8885 |
children |
line wrap: on
line source
Welcome to Update Manager 0.6.7!!! This is the first isntallment of Update Manager for the OpenRPG Virtual Game Table. The package includes several files that allow users to install Update Manager as a package into other softwares that use Mercurial. The package itself includes updatemana.py ## The Update Manager manfiest.py ## A clone of the Plugin Database file (plugindb.py) from the OpenRPG Project validate.py ## Currently unused but it is here for future packaging, from the OpenRPG Project xmltramp.py ## From the OpenRPG Project __init__.py ## So you can copy the upmana folder and import updatemana.py anywhere tmp folder ## Used to protect files during a repository update default_ignorelist.txt ## An empty txt, needed in case users cannot create their own ignorelist.txt default_manifest.xml ## A nearly empty XML file. Used to hold Update Manager information. The code is incomplete in this version, but the pieces that are missing have notes in remarks on how to complete them. So what can you do with Update Manager? If you have a project that you want to serve to users and user Mercurial as a way to deliver updates, Update Manager allows you to deliver those updates without the fear of creating a problem with user sentiment. Users will be able to (when completed) access their Control tab and update to any revision or any branch that has been served via a repoistory. Users also have the option to protect files from being overwritten during updates, or not update at all! If you have a development team you can use Update Manager as a speedy way to surf through your branches and revisions.