pax_global_header 0000666 0000000 0000000 00000000064 11577342641 0014524 g ustar 00root root 0000000 0000000 52 comment=30892579541332ae1df40dbcc3a7bb386dc06cc4 vitables-2.1/ 0000775 0000000 0000000 00000000000 11577342641 0013177 5 ustar 00root root 0000000 0000000 vitables-2.1/ANNOUNCE.txt 0000664 0000000 0000000 00000003533 11577342641 0015152 0 ustar 00root root 0000000 0000000 ======================= Announcing ViTables 2.1 ======================= After a long period retired from development activities I'm happy to come back and present ViTables 2.1, the latest release of this viewer for PyTables/HDF5 files. As it happens with the entire PyTables family, the main strength of ViTables is its ability to manage really large datasets in a fast and comfortable manner. For example, with ViTables you can open a table with one thousand million rows in a few tenths of second, with very low memory requirements. Also important is the fact that it is designed to be a multiplatform application, i.e., it runs flawlessly in Unix (and hence, GNU/Linux), Mac OS X and Windows. The fact that it runs on top of PyTables ensures its speed and memory efficiency. In this release you will find some bug fixes and usability enhancements. New features include: - improved queries. They are faster and eat much less memory - a simple but flexible plugins framework - human friendly formatting of times and dates for PyTables native Time fields and also for time series created via scikits.timeseries package - datasets can be imported/exported from/to files with CSV format Platforms --------- At the moment, ViTables has been fully tested only on GNU/Linux and Windows platforms, but as it is made on top of Python, PyQt and PyTables, its portability should be really good and it should work just fine in other Unices. How to get it ------------- Visit: http://www.vitables.org/download and click the link 'downloads area' to find the available packages. Share your experience --------------------- I'm very interested in your feedback about ViTables. Please send your opinions, suggestions, bugs, etc. to the ViTables Users Group at http://tech.groups.yahoo.com/group/vitables-users. Thank you! Enjoy Data with ViTables, the troll of the PyTables family! vitables-2.1/ChangeLog.txt 0000664 0000000 0000000 00000166163 11577342641 0015604 0 ustar 00root root 0000000 0000000 ViTables ChangeLog ================== ** February 09, 2011 ** Issues specific to Windows Vista have been reworked in the NSIS installer script. ** February 05, 2011 ** Fixed a minor issue (specific to Windows Vista) in the NSIS installer script. ** February 02, 2011 ** Fixed a minor issue in the NSIS installer script. Fixed a minor issue in the setup.py module. The Users' Guide has been updated. Packaging procedure changed accordingly to recent changes in timeseries plugin. ** February 01, 2011 ** The timeseries and menu plugins have been enhanced. ** January 28, 2011 ** Fixed a bug introduced in the CSV plugin in r220. ** January 27, 2011 ** Fixed a bug in the initial configuration setup. ** January 26, 2011 ** Fixed a small drag & drop issue. Python strings and Unicode strings have been revisited. The Makefile file for building the MSWindows installer has changed. ** January 25, 2011 ** Several files (mainly example scripts) have been updated. ** January 24, 2011 ** Fixed a bug in the startup settings of ViTables. ** January 22, 2011 ** The process for building documentation has been refined. ** January 20, 2011 ** The copyright statement has been updated. The setup.py script has changed. Applied a workaround to a PyQt4 4.8.2 bug. Fixed some minor bugs regarding plugins. ** January 18, 2011 ** Fixed some minor issues in the creation of the Windows installer. ** January 17, 2011 ** Fine tuning the building process of the Windows installer. Updated several files required for building the Windows installer. ** December 18, 2010 ** More advances in the migration path to Python 3.0. ** December 11, 2010 ** More advances in the migration path to Python 3.0. ** December 09, 2010 ** String formatting is done via .format() method now. ** December 08, 2010 ** Moved to Python 2.6 :-) and preparing the migration path to Python 3.0. ** December 07, 2010 ** The project documentation has been updated. And now it is built via Sphinx. ** December 03, 2010 ** The node selection behavior of the tree of databases has been improved. ** December 01, 2010 ** Fixed some small problems in several files. ** November 30, 2010 ** Customised models have been debugged and fine tuned using modtest.py. ** November 28, 2010 ** The docstrings of the whole package have been updated. ** November 24, 2010 ** super() is used now in the ctor of all classes derived from PyQt4. The csv plugin has been debugged and refactored. ** November 20, 2010 ** The module vtapp.py has been split into 2 modules. ** November 17, 2010 ** Qt properties of QActions set via keyword arguments at creation time. ** November 16, 2010 ** Some improvements applied to vtapp.py module. Some small improvements have been made to several modules. Several methods renamed to shorter names. Fixed a small bug. Some minimal changes made to a several modules. ** November 15, 2010 ** Some improvements applied to the docBrowser subpackage. The logger.py module has been refactored. ** November 14, 2010 ** All old-style signal/lot connections replaced with new-style connections. ** November 05, 2010 ** Several modules refactored. Code for querying tables has been debugged. ** November 04, 2010 ** The Preferences dialog has been debugged and refactored. Signals and slots are connected via setUi method in several modules. ** November 03, 2010 ** The Preferences dialog has been improved. ** November 02, 2010 ** A couple of pure Python modules have been split in a Python part and a ui part. ** October 30, 2010 ** The utils.py module has been simplified. Some unwanted directories have been removed from the repository. Copyright statements updated in every source file. The method used for dynamically load UI files has been simplified. ** October 26, 2010 ** Information about version number and copyright has been updated. ** December 29, 2009 ** Module nodePropDlg.py has been refactored and simplified. Some code dealing with PyTables datatypes and numpy datatypes has been cleaned. ** December 28, 2009 ** Rows insertion/deletion in the tree view has been simplified and debugged. ** December 27, 2009 ** The import_csv and export_csv plugins have been improved. ** December 23, 2009 ** Inconsistencies in the spacing between lines have been fixed. Tree view usability improved. ** December 21, 2009 ** Added the new plugins_menu.py plugin. It show info about the loaded plugins. ** December 20, 2009 ** The code dealing with application setup has been debugged and refactored. ** December 19, 2009 ** The plugins framework has been debugged and refactored and has a new ui. ** December 15, 2009 ** The deprecated (in Python 2.6) sets module is not used anymore. ** December 14, 2009 ** The code dealing with the tree view has been debugged and simplified. ** December 11, 2009 ** Fixed a subtle bug in the automatic sync between tree view pane and workspace. ** December 10, 2009 ** In the tree view fixed a bug in the cut node + paste node sequence. ** December 09, 2009 ** The logger module has been refactored and simplified. Fixed a bug in the context menu of the logger. Fixed a couple of minor bugs. ** December 05, 2009 ** The documentation browser subpackage has been simplified. Several question like message boxes have been customised. ** December 04, 2009 ** Removed wild imports and other minor annoyances common to most modules. The time series plugin has been refactored. pluginsManager module has been refactored to improve some bizarre behavior. Usability of csv_import plugin has been improved with better dialog texts. ** December 03, 2009 ** Autodetection of tables headers has been added to the import csv plugin. ** December 02, 2009 ** Support for tables headers has been added to the import/export csv plugins. ** November 30, 2009 ** The import_csv.py plugin has been debugged, refactored and enhanced. ** November 28, 2009 ** New version of import_csv.py plugin added to repository. ** November 25, 2009 ** Minor problems introduced in recent changes have been fixed. ** November 24, 2009 ** Import capabilities added to the CSV plugin. vtapp.py module changed to make easier interaction with plugins. ** November 23, 2009 ** Layout of csv plugin changed to allow future additions; modules, icons,... Plugin export_csv.py enhanced: better code, reduced memory footprint. ** November 22, 2009 ** Memory footprint greatly reduced. ** November 20, 2009 ** Fixed a bug in the datasheet.py module apparent with pyqt < 4.6. ** November 13, 2009 ** Support for queries has been updated. dataSheet.py module has been refactored. leafView.py module has been refactored. Plugins have been updated. Querying functionality has been moved from vtapp.py to queriesManager.py. dataSheet.py module has been refactored. Circular references have been removed. Fixed a bug in the Preferences dialog. ** November 10, 2009 ** Fixed a bug in the Preferences dialog. ** November 08, 2009 ** Fixed a bug in the tree of databases that was not apparent in PyQt <=4.4.4. The path of the config. file on Unix systems now adheres to the Qt standards. ** September 25, 2009 ** Fixed a minor bug in the code for opening files via drag and drop. ** September 22, 2009 ** Last improvements in the documentation style applied to Windows platforms. Fixed an annoyance in the creation of PDF documentation. ** September 21, 2009 ** The User's Guide has been updated (and its custom layer has been recovered). ** September 20, 2009 ** Fixed a compatibility problem XP/Vista in the Windows installer. ** September 19, 2009 ** Applied several minor simplifications to styles management code. ** September 18, 2009 ** Windows installer upgraded for the next release. ** September 15, 2009 ** Fixed some minor bugs. Prepare things for the next release. ** August 24, 2009 ** Some icons have been updated. The zoomCell module has been debugged and refactored. ** August 22, 2009 ** The plugins framework has been debugged and its usability has been improved. The time_series plugin has been debugged and refactored. ** August 21, 2009 ** The examples directory has been reworked. ** August 20, 2009 ** A couple of modules have been sanitised (bad variable names changed). ** August 15, 2009 ** The docBrowser package has been reworked a little bit. Splash screen has been updated. ** August 13, 2009 ** Icons have been updated. About ViTables dialog enhanced with a Thanks To page. Fixed a bug introduced when the use of Qt resources was dropped. ** August 07, 2009 ** Makefile files and other unneeded stuff have been removed. ** August 06, 2009 ** The plugins framework has been made more robust. Fixed some small problems in the new build system. ** August 05, 2009 ** Last 2 commits backed out + Dima's patches merged + backed out commits restored ** July 29, 2009 ** Added support for packages to the plugins framework. ** July 28, 2009 ** A simple plugin framework has been implemented. ** July 21, 2009 ** The "Node properties" dialog is generated automatically (via Qt Designer) now. ** May 01, 2009 ** Added missing licensing information to several files. Sources of Users Guide are now distributed in the ViTables tarball. Procedure for generating the usersguide has been updated. INSTALL.txt and setup.py have been updated. HTML documentation uses utf-8 encoding now. ** March 11, 2009 ** Code for creating DBDoc objects was confusing and has been refactored. Added a couple of (subtle) usability improvements. ** March 10, 2009 ** The Preferences subpackage has been updated. Fixed a small bug in the "Select a file for opening" dialog. ** March 08, 2009 ** New utility function added to utils.py module. Table queries are done in a separated execution thread now. ** March 05, 2009 ** The "New query" dialog is generated automatically (via Qt Designer) now. ** March 04, 2009 ** Some subpackages have been reorganised. ** March 02, 2009 ** __tr method has changed. Attributes editing has been debugged and simplified. Unneeded encoding/decoding of strings has been removed. ** March 01, 2009 ** The main menu bar has been reorganised. ** Feb 26, 2009 ** New feature added: export a dataset to plain text file with CSV format. Fixed a unicode bug in the queries manager. ** Feb 24, 2009 ** The resources module has been added to the repository. A couple of Makefile files have been changed. ** Feb 23, 2009 ** setup.py has been updated. Code dealing with formatting time series has been refactored. **Feb 21, 2009** License files and license notes have been updated. Fixed a little bug in the time_series plugin. The examples foder has been reorganized. Support for unicode filenames has been improved. Fixed a silly bug in the time_series plugin. Focus indicators for the logger and the tree panel have been improved. The support for time series has been fixed and improved. ** Feb 11, 2009** An ubiquitous misuse of the Python unicode() built-in has been fixed. The recent fix to the windows installer is now in the repository. ** Jan 21, 2009** Fixed a bug in the support for unicode filenames in Windows. A better support for unicode filenames has been added. ** Jan 19, 2009** Fixed a small bug in the support for date/time. ** Jan 17, 2009** Date/time information is displayed now as legal time. ** Jan 16, 2009** Fixed a bug in the zoom cell feature. ** Jan 10, 2009** More improvements to installer for Windows. Fixed a serious bug in the installer for Windows. ** Jan 07, 2009** Code style of the vitables package has been improved. ** Jan 02, 2009** Code style of the h5db and docBrowser subpackages has been improved. Code style of the preferences, nodes and nodeProperties subpackages has been improved. Code style of the vtWidgets and vtTables subpackages has been improved. ** Jan 01, 2009** PyQt4 imports changed to remove unnecessary code verbosity. ** Dec 27, 2008** Fixed bug 014953. Strings are managed via unicode strings with utf-8 encoding. ** Dec 22, 2008** The User's Guide has been updated. Every str() call as been replaced by a unicode() call. ** Dec 19, 2008** Fixed a couple of minor problems. Fixed a bug that made impossible to open files by drag and drop in Windows. Fixed a bug introduced in the previous commit. The node copy/cut/paste mechanism has changed. Now it is much more efficient and simpler. ** Dec 18, 2008** The Copy Node operation has been greatly optimized. Fixed an encoding related problem in the file opening procedure. Fixed a minor issue with the vertical header of large tables. The procedure for creating a Windows installer has been changed in order to deal properly with PyQt4. ** Dec 16, 2008** Fixed some bugs regarding portability between different platforms ** Dec 15, 2008** Fixed a problem in setup.py. Applied several simplifications derived from the use of Qt resources system. Fixed some bugs regarding portability between different platforms. ** Dec 13, 2008** Project clean-up and final changes. ** Dec 12, 2008** The preferences package has been refactored. ** Dec 11, 2008** Zooming cells with string content has been fixed. Fixed an annoying bug introduced in changeset 184e748db458. ** Dec 10, 2008** A context menu has been added to the workspace. The User's Manual has been updated. The documentation browser has been updated. The module in charge of application configuration has been updated. Fixed a small bug in the Properties dialog. Changed the trigger for in-place renaming of nodes in the tree of databases pane. The Properties dialog has been debugged and improved. ** Dec 09, 2008** ANNOUNCE.txt and setup.py have been updated. Fixed a bug in scripts/vitables. Fixed a small l10n problem. ** Dec 08, 2008** Fixed a small bug in insertion of nodes in the tree of databases pane. ** Dec 05, 2008** Fixed a subtle bug in the datasets access process. A small bug has been fixed. File Save As... operation has been debugged. Enhanced the render of datasets with just one row/column. Fixed a small bug in the synchronisation of the workspace with the tree of databases pane. ** Dec 04, 2008** A minor problem found in tables queries have been fixed. The content of just created filtered tables is now automatically displayed. Fixed a bug in the access to datasets with two or more dimensions. Nodes copying has been updated: leaves whose dataset is not readable are not copied Deletion of views tied to overwritten nodes has been implemented. The status bar is properly updated now when a node is renamed in the Tree of databases pane. ** Dec 03, 2008** The 'Recover last session' feature is fully implemented now. Fixed a small bug in the splash screen. Added a label in the status bar for displaying info about the node currently selected in the Tree of databases pane. ** Dec 02, 2008** Implemented the capability for zooming cell contents. Dynamic entries under the Windows menu are now checkable and exclusive. ** Nov 30, 2008** Fixed a bug in the navigation of huge datasets. Now displayed data is properly updated when a slider drag ends and when the table is wheeled. ** Nov 13, 2008 ** Navigation of huge datasets is now fully implemented. Every navigation device (vertical scrollbar, keyboard and mouse wheel) seems to work fine and to update displayed data when a buffer fault occurs. ** Nov 04, 2008 ** Navigability of huge datasets has been enhanced. The selected cell is now properly updated when a buffer fault occurs. It means that navigating the table with the keyboard works fine now. ** Oct 31, 2008 ** Huge datasets can be displayed and navigated. Several things remain to be done (usability enhancements) but the feature seems usable and stable. ** Oct 24, 2008 ** Opening files by dropping their icons in the databases tree panel is fully implemented. Some annoying problems that arised when nodes were moved around in the databases tree panel have been fixed. I've started to implement the support for huge datasets. ** Oct 23, 2008 ** Opening files by dropping their icons in the databases tree panel has been partially implemented. Fixed a couple of bugs in the Properties dialog: data types are correctly shown now. In-place renaming of nodes has been debugged. Fixed a little problem with groups expansion in the tree view pane that was rather annoying: now pasting a node (or creating a new group) expands the parent group if it was closed. So user can see that the node has really been added. ** Oct 22, 2008 ** More progresses in the datasets displaying: - the workspace and the tree of databases are synchronized now: if a leaf with a view is selected in the tree then the view becomes active in the workspace. And viceversa, if a view is activated in the workspace its leaf is automatically selected in the tree - when a node with views is overwritten (because a group has been created, a node has been renamed or a node has been pasted/dropped) the views are closed - the drag and drop behavior has been debugged ** Oct 21, 2008 ** Fixed a bug in the application quitting process: the temporary database wasn't properly deleted. ** Oct 20, 2008 ** The Windows menu has been reimplemented. ** Oct 19, 2008 ** Datasets can now be displayed in the workspace. Still importants things remain to be done, mainly to add support for quickly navigate huge datasets. ** Oct 17, 2008 ** The buffer.py module has been refactored and modified. ** Oct 16, 2008 ** Fixed a bug in the node rename and file save as operations. A node/file cannot overwrite itself. ** Oct 13, 2008 ** Fixed a subtle bug in the code for renaming nodes. Fixed a bug in the dialog for entering the name of a node when a group is being created or a node is being renamed: empty strings are not valid names now :-) ** Oct 11, 2008 ** The code for renaming nodes has been refactored. Affected modules are vtapp.py, utils.py, inputNodeName.py and renameDlg.py. The setup.py has been updated. ** Sep 26, 2008 ** Fixed some minor bugs regarding the enabled/disabled state of toolbar buttons and menu items. Added new module inputNodeName.py. It is used instead of renameDlg.py for creating groups and entering the initial name in renaming operations. ** Sep 25, 2008 ** The behavior of the Open Recent File submenu is now a little bit more user friendly. ** Sep 24, 2008** Fixed a bug in the file opening procedure. Files with no PyTables/HDF5 format are properly managed now. Some code in the vtapp.py module has been reorganized to make it more readable. ** Aug 02, 2008 ** Fixed a couple of bugs in the File menu: * the Close All action wasn't enabled/disabled properly * the Save As... action didn't work ** Jul 23, 2008 ** The porting of the nodeProperties subpackage has finished. ** Jul 21, 2008 ** Merged r1054 and r1055 from trunk. Every modified file has been merged but VERSION. ** Jul 18, 2008 ** The nodeProperties subpackage is being ported. At the moment the GUI part has been ported. Next step will be porting the code for attributes validation. ** Jul 15, 2008 ** Fixed a nasty bug that crashed the application every time a node was expanded in the tree viewer. The reported Qt4 error was: QObject: Do not delete object during its event handling! I've been unable to locate exactly where the bug was. Apparently it was produced by a strange interaction between VTApp and VTGUI classes so I've embedded VTGUI in VTApp and removed the vtgui.py module. It seems to fix the bug. ** Jul 07, 2008 ** The porting of the nodeProperties subpackage has started. A new module, nodeDoc.py, has been added. It is in charge of the information collection about a given PyTables node. This module makes unnecessary the following ones: nodeDoc.py, tableDoc.py, arrayDoc.py, unimplementedDoc.py and groupDoc.py. All those modules have been removed from the project. ** Jul 03, 2008 ** The behavior of the Preferences dialog has been tuned. ** Jul 01, 2008 ** The porting of the documentation browser has been done. The behavior of the documentation browser has been tuned. ** Jun 26, 2008 ** Added svn:keyword property to dbsTreeModel.py leafNode.py nodeItemDelegate.py groupNode.py dbsTreeView.py rootGroupNode.py ** Apr 18, 2008 ** Added contextual menus to the tree of databases view. Also a couple of menu items in the Help menu are working now. Functionality for configuring the application has been reimplemented. ** Apr 16, 2008 ** Added code for enable/disable actions depending on the selected node in the tree of databases view. ** Apr 15, 2008 ** Thre new icons have been added. Command 'Delete All Queries' has been reimplemented. The Query toolbar has been added. Tables queries have been reimplemented. ** Apr 11, 2008 ** A couple of methods have been refactored and now have a new signature. Calls to these methods have been updated. The dbDoc.py module has been refactored. The nodeItemDelegate.py module has been moved to the h5db subpackage. ** Apr 08, 2008 ** Added support for renaming nodes inplace. The code for node editing operations has been refactored. ** Apr 07, 2008 ** Implemented Node --> Rename command with overwriting support. ** Apr 03, 2008 ** Fixed a bug in the algorithm for recovering last session. Now if a given node doesn't exist then the application reports it and doesn't crash. Implemented Node --> New Group command with overwriting support. ** Apr 02, 2008 ** The overwriting feature has been implemented in the drag and drop of nodes. Splash screen readability improved. Fixed a bug in DBDoc.pasteNode method of dbDoc.py module. The overwriting feature has been implemented in the Node Paste... command. The overwriting feature has been implemented in the File Save as... command. Added code for setting the application icon. ** Mar 31, 2008 ** Processing command line fetaure has been ported. The last session recovering feature has been ported. ** Mar 28, 2008 ** Splash screen module has been debugged: now messages are drawn at the proper position. The following files have been updated: INSTALL.txt, README.txt, setup.py and Makefile. Version number has changed to 2.0. A note has been attached to the start of every source file of ViTables. In this note it is specified how the ViTables program is licensed. ** Mar 27, 2008 ** Copyright statement of source files has been updated. ViTables logo has changed: now it doesn't contain the Carabos logo. I've done this because now ViTables is not developed by Carabos Coop. V.. Instead it is a free software project maintained by myself. The ViTables source code license has changed. From now on it has a GPLv3 license. ** Mar 26, 2008 ** Creating a branche for porting ViTables to PyQt4. Fixed a little problem in the drag and drop support of the tree of databases model/view. The treeEditor subpackage has been removed. The functionality of the File menu has been implemented. Only overwritting files during a File --> Save as... operation remains unimplemented. Fixed a couple of bugs in the tree of databases model: - the close database operation didn't remove the node from the tree view. - when opening a database fails the returned value was no specified. The configuration module has been rewritten. The configuration module has been rewritten. Small changes introduced in several modules: the name of some attributes has changed and some imports have been slightly modified. Small changes introduced in several modules: the name of some attributes has changed and some imports have been slightly modified. ** Mar 20, 2008 ** The vtgui.py module has been refactored and some small problems have been fixed: the size of the toolbars icons, the WhatsThis action setup, and the setup of the menu with entries for the toolbars. The vtgui.py module porting is done. The result is a module much shorter and clearer thant it was before. ** Mar 19, 2008 ** The porting of the vtgui.py module has started. It has been greatly simplified. The drag and drop behavior of the tree of databases view has been debugged a little bit. PyQt4.QtXXX libraries are now imported as QtCore and QtGui instead of qtCore and qtGui. In addition a couple of modules have some minor changes. ** Mar 18, 2008 ** Copy, cut, paste and delete operations have been implemented in the tree of databases model. Overwriting has not been considered yet. ** Mar 05, 2008 ** Basic drag and drop of the tree of databases model/view works! Nodes can be moved from one location to another (even in a different file). Nodes that belong to files opened in read-only mode cannot be dragged. Lazy population of the model works fine too. ** Mar 03, 2008 ** The basic model/view implementation for the tree of opened databases is done. Databases can be opened and closed. The object tree of a given database is populated in a lazy way so that performance is guaranteed when opening files with a large number of nodes. Finally, icons are tied to nodes in the tree view. ** Feb 29, 2008 ** Drag and drop support is being implemented. ** Feb 27, 2008 ** Added basic support for renaming nodes in-place. ** Feb 26, 2008 ** Added support for custom context menus to the tree of databases view. Some modules have been changed in order to keep internal consistency. Minor modifications made in several modules. ** Feb 22, 2008 ** The h5db subpackage has been updated. Calls to Qt3 methods have been moved to Qt4 equivalent methods. nodes subpackage has been updated. Calls to Qt3 methods has been replaced by calls to Qt4 methods. ** Feb 20, 2008 ** createIcons function changed: removed a line that was commented out. The nodes subpackage migration has started. Calls to Qt functions/methods have been adapted to Qt4. ** Feb 18, 2008 ** The following modules have been ported: * scripts/vitables * vitables/utils.py * vitables/vtsplash.py * vitables/vtSite.py * vitables/vtgui.py This module has been split in two modules: logger class is defined in a new module now. * vitables/logger.py The whole preferences subpackage has been ported: * vitables/preferences/vtconfig.py * vitables/preferences/preferences.py * vitables/preferences/configException.py The following tests have been ported: * vitables/preferences/preferencesGUI.py * tests/preferences/test_vtconfig.py * tests/preferences/test_preferences.py ** Dec 16, 2007 ** The Spanish translation has been updated. WhatsThis help texts and some About... texts have been reformatted in order to improve the code readability. ** Dec 14, 2007 ** The previous bug fix in the editing of the TITLE system attribute was incomplete. It has been corrected now (hopefuly). ** Dec 13, 2007 ** Fixed a bug in the editing of the TITLE system attribute (accents raised errors). Some trivial enhancements have been done. The editing of user attributes has been improved. Overflow cases are now properly detected and a ValueError is raised. Although this is not the default behavior of numpy arrays (which are silently converted to the apropriate dtype when an overflow occurs) it seems more adequated for an end user application as ViTables. ** Nov 29, 2007** Drag and drop of nodes has been debugged. Cut and paste has been improved. I hope that editing nodes is now implemented in a quite robust way. ** Nov 28, 2007** The behaviour of the documentation browser has been improved. A couple of bugs have been fixed: - canceling the Open File... command works fine now - opening a new documentation browser doesn't give errors due to not found documents - trying to open a document that doesn't exist don't shows a blank page but a page with the message 'Document Not found' A mess due to the use of backslashes still happened on Windows platforms, specially in the list of recent files and in the navigation browser history and bookmarks. This problem has been hopefully solved. The copy and paste operation has been enhanced. Now a node can be copied and pasted in its parent group. The overwrite dialog is raised, giving you the chance to rename the pasted node. If you decide to overwrite, the operation fails (a PyTable exception is raised) because a node cannot be overwritten by itself. ** Nov 27, 2007** The template script that generates the Windows installer has been updated. Now it takes care of the available translations. Unittests have been updated. The search method for locating the application settings has been improved on Mac OS X platforms. ** Nov 26, 2007** Spanish translation added. A couple of minor problems have been fixed: - the .vitables directory is not created on Mac OS X platforms anymore - the message raised when a directory is dropped on the tree viewer is now clearer The User's Guide has been updated. ** Nov 23, 2007** Displaying of objects in tables widgets has been enhanced. Now cell contents are dynamically adapted to the available room. It means that how the content of a given cell is displayed depends on the column width. As a consequence, the displaying of multidimensional objects has been greatly improved. Some changes aimed to improve the i18n have been done. ** Nov 21, 2007** Fixed a bug in the creation of user attributes with dtype float32. Errors raised during user attributes editing are displayed in the attributes editing dialog, not in the logger. This make easier to user to realise that an error has been raised. ** Nov 19, 2007** The release version has been updated. The User's Guide source has been updated. The DocBrowser behavior has been enhanced. Opening a file for the very first time in the DocBrowser uses the home directory as a working directory. Before it used the installation directory which was ugly. ** Nov 02, 2007** Fixed a bug in the access to VLArrays elements. The bug avoided the creation of views for VLArrays. VERSION has been updated in vtSite.py. This is required in order to run properly on Mac OS X platforms because on these platforms the module is NOT overwritten by setup.py. The temporary database is not removed when quitting ViTables because on Windows platforms a Permission denied error is raised. **Oct 31, 2007** Explicit support for addressing 64 bit space has been added. Now ViTables can display tables with more than 2**32 rows with no problem. A small bug has been fixed (hopefully) in the node paste operation: pasting a node on an expanded group doesn't refresh the object tree i.e. the pasted node is not visible. The whole unittest directory has been updated/refactored/debugged. I forgot to update tests/test_all.py in the previous commit :-( Fixed a small bug in the File Save As... procedure. The file extension of the new file was generated in a wrong way because the full filepath was used to determine the extension. The right thing is to use the filename. **Oct 30, 2007** The Users' Guide has been updated. A specific icons has been given to the toobar button in charge of opening files so that users can appreciate that it can show a popup menu now. Fixed a bug in File --> Close All and Query --> Delete All. Closing a set of non selected nodes caused a wrong update of the QAction in charge of closing all open files. Deleting a set of non selected filtered tables caused a wrong update of the QAction in charge of deleting all filtered tables. Fixed a bug in the procedure used to close a database. A race condition has been removed. A new icon has been added. Fixed a bug in the updating of query QActions. The bug couldn't be appreciated by users because it happened when the application was about to exit. **Oct 26, 2007** The VERSION file has been updated. A new usability enhancement has been added. The Open button of the File toolbar is able now to open the file of Recent files too. **Oct 22, 2007** Fixed a bug in the initial setup of the application. Fixed a bug in the Properties dialog of empty groups. Creating and renaming node operations have been made more robust. Fixed a small problem of name qualification when accessing to a couple of PyQt attributes. **Oct 19, 2007** Usability of Properties dialog has been improved by fixing the visual behavior of attributes editing. The format given to catched errors has changed again. Now the readability of Syntax Errors is better. In the Filter Table dialog ValueErrors are explicitely catched now. **Oct 18, 2007** Some classes still were instantiated via apply(qt.QSomeWidget.__init__, (self,args)). Now qt.QSomeWidget.__init__(self, args) is used. The behavior of tables shown in the Properties dialog has been improved. Tables have been resized so that they occupy all the available horizontal space leaving no (anoying) gaps. **Oct 17, 2007** Fixed a small bug in the console that produced a wrong color update in some situations. Wild imports have been completely removed. The examples directory has been updated. **Oct 16, 2007** The management of application preferences and configuration has been improved. The code has been simplified and a small bug has been fixed. Fixed a bug in the Preferences dialog that made the Cancel button useless. Some error and warning messages have been changed in order to ensure that all of them have a consistent format. **Oct 15, 2007** The resize mode of the Tree Viewer widget has been fixed so that the widget's header resizes properly its sections when the widget is resized. A subtle bug has been fixed in the setup of the default configuration of the application. **Oct 11, 2007** Some logger messatges have been changed in order to make them self-explanatories. The installer template script has been modified. The name of the installer includes the kind of license now. Fixed a small bug in the File Save As... command. It avoided open files overwriting on Windows platforms. The format used for display catched exceptions has changed. Now it is more readable (although provides less information). **Oct 10, 2007** The format of docstrings has been updated. Now every docstring has a restructured text format. Docstrings of every module have been updated. In particular the updated sections are those that listed the names of classes, methods, functions and global variables contained in the modules. Code for moving a node from one location to a different one has been changed in order to improve the performance. **Oct 04, 2007** Fixed a bug in the paste node procedure. **Oct 03, 2007** The behavior of the Query results node of the tree view has been setup accordingly to its aim. A subtle bug has been fixed in the dbView.py module. When dealing with nodepaths os.path.join should be avoided in favour of tables.utils.joinPath. The reason: in Windows platforms os.path.join can produce paths with a mix of slashes and backslashes. A small bug in the template installer script has been fixed. The uninstaller didn't remove completely the ViTables entry from the Start menu. Fixed a bug in the opening file process. When the open file dialog was called for the first time (i.e. application startup) and the dialog was cancelled then later calls of this dialog were unusable. The procedure for saving a file with a different name has been slightly changed to avoid a nasty HDF5 error. The error was raised when the new file name was filename (with no extension) and a filename.h5 file already existed. **Oct 02, 2007** As no evaluation versions are going to be distributed the dbManager template is not needed now. That's why it has been renamed to dbManager.py Unneeded and obsolete files have been removed. A small bug has been fixed in vitables/nodes/leafView.py. The bug was raised by a bug in the underlying PyTables 2.0.1 The ViTables configuration has been updated. The Startup option `start in current directory` is now `start in home directory` to avoid opening unexpected directories in Windows and Mac OS X when ViTables is launched by double clicking its desktop icon. Fixed a small bug that prevented to start ViTables in the home directory (when configured to do it) in Windows platforms. The template script for generating installers has been modified to add more items to the Start menu: links to documentation (in both PDF and HTML4 formats) and to the examples directory. **Oct 01, 2007** The users' guide has been updated. A check has been added to several methods in vtapp.py, to ensure that filepaths do not contain backslashes because they produce a real mess in the Windows registry and the list of recent files. **Sep 30, 2007** Added a button for group creation to the Node toolbar. **Sep 29, 2007** Fixed a bug in the drag and drop of a node from a read-only file to a read-write one. **Sep 28, 2007** QActions updating and synchronizating panels strikes back! The last approache has been discarded because it didn't encompass every possible case. The new approache seems to work better and it is simpler. Fixed a bug that prevented empty nodes to be added to the object tree when the tree was expanded. Fixed a bug in the creation of new groups. Now the new group can overwrite any node with the same name placed in its parent group. Before only groups could be overwriten. **Sep 27, 2007** The Help Browser history and bookmarks are now stored in the configuration file instead of in their own files. Fixed a bug in the updating of the QActions state. **Sep 26, 2007** The list of recent files is now stored in the configuration file (or in the Windows registry) instead of in its own file. The last session is now stored in the configuration file (or in the Windows registry) instead of in its own file. unittests have been updated. **Sep 25, 2007** The configuration file lastdir, used to store the last opened directory has been removed. Now this information is stored in the application configuration file (or in the Windows registry). **Sep 24, 2007** Fixed a small bug in the recovering last session process. **Sep 23, 2007** Unittests have been updated. **Sep 22, 2007** Added a new usability improvement: the tree view pane and the workspace keep now their selection state synchronized. Several keyboard accelerators added. **Sep 21, 2007** A couple of small usability improvements has been added. The action Node-->New group has a keyboard accelerator now. **Sep 20, 2007** The dialog raised when a node editing leads to a naming problem is now more readable a.k.a useful. Added permission to create groups under the Query results root node. Fixed a bug that appeared when a node was moved from one file to a different one. Fixed a bug that appeared when a node was copied from one file and pasted into a different one. **Sep 18, 2007** A small bug has been fixed in the renameDlg.py module. Fixed a bug in the implementation of tables queries. The bug caused wrong values to be displayed in the query indices field (if requested) when the range of rows to be queried was other than (start=1, stop=n, step=1).. **Sep 17, 2007** A small bug has been fixed in the dbView.py module. The unittests under tests/h5db have been updated. **Sep 13, 2007** The dialog raised when a naming problem appears has been enhanced. Now, detailed information about the operation being executed is displayed and buttons text is self-explanatory. Fixed a small bug that affected the File Save as... operation. Added support for overwriting nodes when a new group is being created. Docstrings of dbMananger_template have been updated. Fixed a small bug in renameDlg.py. **Aug 09, 2007** Fixed a serious bug in node deletions procedure. **Aug 08, 2007** New, clearer descriptions are used in the Properties dialog, in help texts and in buttons text. Unneeded messages are not passed to the logger anymore. Management of filenames extensions has been improved. The Query menu has been simplified. The HelpBrowser toolbar layout has changed. It is clearer now. **Aug 03, 2007** All unittest modules have been refactored and debugged. __init__.py files have been added to the tests directory and its subdirectories. test_all.py module has been added so that all unittests can be executed easily. testingHOWTO.txt has been updated and moved to the tests directory. **Jul 31, 2007** Unittest module test_query.py has been added. The tables query implementation has been modified in order to make it more suitable for testing it with unittests. Fixed a bug that was hitting every module in the tests/nodes directory. Unittests in the tests/preferences directory have been updated. Unittest module root_package/test_commandLine.py updated. **Jul 25, 2007** Updated Mac packaging instructions to avoid linking sip/PyQt against wrong Python. **Jul 24, 2007** INSTALL.txt and ChangeLog.txt have been updated. VTApp.slotHelpAbout method changed. The info displayed in the About tab has been updated. Support for VLArrays has been enhanced. VLArrays with pseudo-atom of kind vlunicode are now supported. Module zoomCell.py has been updated accordingly to the recoded cell formatting methods of utils.py **Jul 23, 2007** Use a `make.sh` script instead of `make` to build Mac OS X DMG images. The process is not complete yet, since the license is not shown on opening the DMG image. That's why the `SLA.*` files are still in place. Makefile_windows and the template NSIS installer script have been updated. Now they take care of the LICENSE.html file. Makefile for unix has been simplified. Added RTF readme to DMG image with important details for Mac OS X. Removed the files for the Mac OS X DMG resource fork. The license file in the DMG root is enough and easier to place. ;) The Linux packaging system has been updated so that licenses are properly managed. **Jul 21, 2007** Fix the Mac OS X app not finding the `qt.so` extension in the appdir. Thanks to Doug Anderson from the PythonMac-SIG list for the solution. **July 19, 2007** Added a bunch of tests for testing that the actions of menu items if File, Node and Query menus are properly enabled/disabled depending on the kind and number of selected nodes in the tree viewer. **July 12, 2007** The way of saving settings in the windows registry has changed. Now settings are stored under the key Carabos/Vitables/Version/PythonXX. No changes have been introduced for Unix and Mac OS X platforms. The management of application settings has been improved. Some annoyances regarding the geometry of the main window and viewer panels have been fixed. **July 06, 2007** Module subprocess.py has been removed. Since no packages for Python 2.3 are built now the module is not required. Bug fixed in scripts/vitables. The order of the import sentences was wrong. **July 03, 2007** Screenshots for the User's Guide have been updated. Support for personal and site licenses has been added. **July 02, 2007** Makefile_windows slightly modified to ensure that del behaves like rm. hpViewport.py module has been changed in order to fix the speed problem hitting PyQt >=3.16. The PNG file vitables_wm.png has changed. It has been converted from RGB to indexed mode. This way transparency is properly handled in Windows boxes. **June 28, 2007** The 3rd_party_licenses directory has been removed. The MANIFEST.in, LICENSE.txt and utils.py files have been modified accordingly. The User's Guide includes now a copyright notice for Qt and PyQt. **June 27, 2007** Package Mac OS X app as a semi-standalone application (incomplete). The PNG used in ViTables windows as application icon has been updated. References to the evaluation version have been removed from ANNOUNCE.txt and README.txt. **June 25, 2007** The docBrowser subpackage has been refactored and debugged. The script used to generate the treeSymbols.png image has been updated. The icon for compressed arrays has been included in the script. The image treeSymbols.png itself has been updated too. The xml source of the User's Guide has been updated. **June 20, 2007** The mingwm10.dll library must be included in the installed ViTables because qt and pyqt have been compiled dinamically with the MinGW compiler. The Makefile mswindows/Makefile_windows and the template NSIS script mswindows/vitables.nsi.in have been modified to take care of this dependency. **June 15, 2007** Added a Confirm Uninstall page to the template NSIS script. Several changes intended to allow for generating user's guide in a Windows box have been introduced. **June 14, 2007** A small inconsistency in the ViTables behavior has been fixed: files are now open in read-write mode by default. The template NSIS script for the Windows installer has been updated and refactored. **June 13, 2007** A working version of the new Windows installer is ready. Refactoring will start in brief :-) **May 29, 2007** A new set of unittests has been added to the h5db subpackage. **May 27, 2007** Some minor changes introduced in the h5db subpackage. **May 26, 2007** Unittests for the h5db subpackage has been refactored and debugged. **May 24, 2007** Unittests for the h5db subpackage has been rewritten from scratch. **May 21, 2007** The Windows installer making process is being updated. Compilation is done with MinGW. **May 18, 2007** The Properties dialog for files has been slightly enhanced: the access mode is shown now in the database groupbox. A small bug has been fixed in the dataspace groupbox. The bug produced bad dataspace groupboxes when the number of children of the group was zero. Class NodeDoc and its descendants have a new, simpler signature. The preferences subpackage has been slightly refactored. Unittests are being updated. **May 17, 2007** The operations Node Rename and File Save as... have been enhanced and debugged. The dialogs involved in node renaming and file saving have been modified to make them more suitable for the new behavior of those operations. **May 15, 2007** The File Save as... operation has been refactored. We have got rid of the `h5file` attribute of root nodes in the tree view pane. It is not needed anymore due to the recent changes in the code. We have got rid of the parent widget argument in most of the application dialog ctors because this widget uses to be the application main widget, which is always accessible through the qt.qApp.mainWidget method. **May 14, 2007** The methods for iterating over tree views have been refactored. The mechanism for querying tables has been refactored and reorganized. Some modules have moved to different locations, some methods have moved to different modules, etc. The result is much more consistent than the previous implementation. Functionality provided by the xxxEditor modules of the treeEditor subpackage has been moved to other modules. The xxxEditor modules have been removed from the project. **May 12, 2007** Fixed an annoying bug that produced lots of error messages when a new database was created/open. It was caused by a bad interaction between VTApp.slotUpdateActions and DBManager.openDB methods. Several internal operations have been simplified. The code of the whole application is now clearer. **May 11, 2007** The utils.py module has changed. The function getNode has been moved to dbDoc.py module. Several modules are affected by this change. A bug has been fixed in the NodeDoc.move method. The bug caused that views of small tables werent properly displayed after a drag and drop operation. The way of accessing the DBDoc instance tied to a given item of the tree view item (i.e tied to a TreeNode instance) has been simplified. **May 10, 2007** Node editing reimplementation has finished. After a new refactorisation everything seems to work fine now. **May 09, 2007** Drag and drop of nodes has been reimplemented. Now it takes care of properly overwriting nodes and updating views. **May 08, 2007** Node editing refactoring is still on. Delete and paste operations have been reimplemented. **May 05, 2007** The mechanism for renaming and deleting nodes has been enhanced and debugged. A translate method has been added to some modules that (due to recent changes) need it now. The mechanism for cutting and copying nodes has been reimplemented. Now it is simpler and more stable. **May 04, 2007** The coupling between leavesManager.py and dbManager.py modules has been removed. Started a heavy refactorisation of the treeEditor subpackage. The group creation and renaming of tree view items in-place have been completely recoded. **May 02, 2007** Fixed a bug in node deletion: deleting a group with views didn't close the views. Module nameConflictDlg.py strongly refactored. **Apr 30, 2007** Drag and drop management is now simpler: we have got rid of the nodeDrag module information about drags is now encoded via QTextDrag method **Apr 27, 2007** Some methods of treeView module have been moved to the utils module. The vtInputBox module has a changed. Now it can be called more easily and used in a more consistent way. The implementation of the model-view-controller in the leaves manager has been fixed for renaming and dropping operations. Some minor changes have been done to descendants of NodeDoc class. **Apr 23, 2007** The queries management has been enhanced in several ways. On the one hand performance of the filling of the result table has been increased when a column for selected indices is required by user. On the other hand usability of the query dialog has been improved in some aspects. **Apr 20, 2007** Added a help system to the user's attributes page of the node properties dialog. Also the query dialog has been enhanced with a help system. The splash screen has been updated. Management of configuration exceptions has been simplified by reducing the number of classes to deal with. **Apr 19, 2007** The support for complex queries has been enhanced. Now columns whose names contain blanks can be queried too. **Apr 18, 2007** The preferences subpackage has been refactored and simplified. **Apr 15, 2007** Added support for complex queries. **Apr 14, 2007** A couple of bugs have been fixed: - the action Close view is inactive when the selected item is a group. However there was a LeavesManager.closeGroup method designed for closing every opened view under the selected group when the Close view action was launched. - the icons dictionary was recreated every time an icon was required by the application. It caused the openRecentFile action not to work at all. On the other hand the nodeProperties subpackage has been refactored and simplified. **Apr 11, 2007** The nodes subpackage has been refactored and simplified. **Apr 10, 2007** The h5db subpackage has been refactored and simplified. **Apr 09, 2007** The application exiting code has been refactored. Applied a workaround to a bug that hangs the application during the quit process: calls to methods Table.where and Table.whereAppend have been replaced by calls to Table.readWhere. **Apr 07, 2007** The queryDlg.py module has been heavily refactored. **Apr 06, 2007** The management of tables queries is still under revision. **Apr 03, 2007** The tables query syntax has changed in PyTables 2.0. Methods involved in querying tables have been updated. **Mar 31, 2007** The module resources.py has been renamed to utils.py. **Mar 30, 2007** Management of the application icons have been simplified. **Mar 29, 2007** The code for opening a node from the tree view has been refactored and simplified. Management of empty datasets has been improved. **Mar 28, 2007** Added support for CArrays. Until now CArrays were managed as regular Arrays: they shared the same icon and looked the same in Properties dialogs. Now an icon has been created for CArrays and they are explicitely identified in Properties dialogs. The attributes editing stuff have been refactored and simplified. **Mar 27, 2007** The editing code of the TITLE system attribute has been simplified. The directory vtBoxes has been renamed to vtWidgets. It is aimed to contain widgets specifically designed for ViTables and widely used for it. The following modules have been moved to this directory: - zoomCell.py - vtTableItem.py **Mar 26, 2007** The VTTableItem class has been refactored. The getNodeInfo method has been changed in classes derived from NodeDoc. As a consequence a more convenient way to access the info returned by this method is achieved. It means that the code that use the returned info is now simpler. Several modules are affected by this change. The copyright line at top section of every python module of the project has been updated. The General page of the Properties dialog has been slightly refactored. **Mar 24, 2007** Most of calls to vitables.resources.getAttr have been changed. The simpler form, object.attribute, is preferred unless the attribute name is stored in a variable. In this case only the first form can be used. A bunch of modules is affected by these changes. vitables.resources.getNode function rewritten. The methods for dinamically building the object tree (tree view) of a given database have been refactored and greatly simplified. zoomCell.py module refactored. The management of empty databases has been debugged. Fixed a bugg in the management of UnImplemented datasets. **Mar 23, 2007** In PyTables 2.0 some Table attributes have been renamed, other have disappeared and other have been added. In order to see if a Table has nested field the colnames attribute cannot be used anymore. One can use the colpathnames attribute for that purpose. zoomCell.py and buffer.py modules refactored. **Mar 22, 2007** zoomCell.py and buffer.py modules refactored. The methods for painting cells in a table widget have been updated and optimised. Debugged management of VLArrays with vlstring and object atoms. **Mar 21, 2007** The properties dialog of leaves has been updated. Several issues concerning with PyTables 2.0 have been fixed. Management of PyTables scalar arrays improved in the buffer.py module. **Mar 20, 2207** Fixed several minor issues in some help texts. ViTables dependencies on numarray package are being removed. The numarray functionality is now provided by numpy. As a consequence numarray will not be included anymore in the ViTables installer for Windows. Instead numpy will be included so the numarray license has been substituted by the numpy one in the 3rd_party_licenses directory. The examples directory has been updated. Most of the .h5 files are now PyTables 2.0 files. **Mar 19, 2007** ViTables dependencies on numarray package are being removed. Management of PyTables user and system attributes has been updated. At the moment only PyTables.2.0 attributes are supported. The names of the supported data types are still outdated. **Mar 17, 2006** Ensure that both PyTables format version 1.x and 2.x are supported in the case of VLArrays. zoomCell.py module has been heavily refactored and debugged. **Mar 16, 2007** Starts the adaptation to PyTables 2.0. buffer.py module refactored. **June 01, 2006** Solved a couple of bugs that were apparent only on Mac OS X. Several usability enhancements added: warning messages are highlighted in orange color, files with read-only access permissions are automatically opened in read-only mode, improved bookmarks management in the documentation browser... **May 23, 2006** New splash screen behavior. Now it provides the users with feedback that the application is loading. **May 19, 2006** Application geometry is now kept between sessions. It includes the position and size of the application window and the sizes of the components of the viewing area, i.e. the tree viewer, the workspace and the logger. **May 18, 2006** A new indicator has been added to the status bar. The indicator permanently shows the path of the item currently selected (if any) in the tree viewer. **May 16, 2006** A view for the selected leaf (if any) of the tree viewer can be opened/closed by pressing the plus/minus keys, in the very same way that group nodes can be expanded/collapsed. **May 15, 2006** Keyboard focus indicators have been added to the tree viewer and the logger in order to improve the application usablility, specially if you are moving around using the keyboard instead of the mouse. **April 28, 2006** Added in-place node renaming capabilities. Now a selected node of a given object tree can be renamed in-place as well as via Rename dialog. **April 27, 2006** Several contextual menus enhanced and debugged. **April 26, 2006** Added support for the cut node operation. **April 19, 2006** A PDF version of the User's Guide has been added. **April 07, 2006** Files opening has been made easier. Now, a file can be opened by dragging it into the tree viewer. **March 14, 2006** The query dialog has been improved. Now it remembers the last entered query and uses it to set the initial values of the query if it applies. **March 10, 2006** Added support for any file extension to the File Browser. When a table is queried, if the result table is empty, a suitable message is logged. **March 08, 2006** Implemented a mechanism to ensure that, if an error occurs when a dataset is being accessed, the application cursor will not remain frozen in its clock shape. The tables query dialog has been debugged. Empty strings are not valid names for the column of indices. **March 01, 2006** Node renaming has been debugged. User's Guide has been updated. vitables-2.1/INSTALL.txt 0000664 0000000 0000000 00000004237 11577342641 0015054 0 ustar 00root root 0000000 0000000 System requirements ------------------- ViTables 2.1 has been tested against Python 2.6 and 2.7 and the latest versions of PyTables and PyQt4 (you can try older versions at your own risk :). Installation on Windows platforms --------------------------------- Just double click the installer icon and follow the wizard instructions. If you prefer to launch ViTables from the command line then install it following the instructions given in the next section. Installation on Linux platforms ------------------------------- The Python Distutils are used to build and install ViTables. Provided your system fulfills the requirements listed in the above section, installing the package is really easy. Just uncompress it, change to the distribution directory and execute (as root) $ python setup.py install If you are doing this on a MacOS X platform, please make sure that the DYLD_LIBRARY_PATH environment variable has been setup properly. By default ViTables will be installed in the system-protected area where your system installs third party Python packages so you will need superuser privileges. If you prefer to install the package in a different location (for instance, your home directory) so that the installation can be done by non privileged users, you can do it using the --prefix (or --home) tag $ python setup.py install --prefix=/home/myuser/mystuff Please, remember that installing Python modules in non-standard locations makes it necessary to setup properly the PYTHONPATH environment variable so that the Python interpreter can find the new modules. If you need further customizations, please have a look to the output of the command $python setup.py install --help to see all the available options. Complete information about them can be found in the Distutils documentation. Installation on MacOS X platforms --------------------------------- For getting a double-clickable application bundle do the following: - uncompress the tarball - change to the distribution directory - change to the macosxapp directory - execute the make.sh script If you prefer to launch ViTables from the command line then install it following the instructions given in the previous section. vitables-2.1/LICENSE.html 0000664 0000000 0000000 00000110617 11577342641 0015155 0 ustar 00root root 0000000 0000000
Copyright 2005-2007 by Carabos Coop. V. Copyright 2008-2011 by Vicent Mas
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
“This License” refers to version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based on the Program.
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
vitables-2.1/LICENSE.txt 0000664 0000000 0000000 00000104740 11577342641 0015030 0 ustar 00root root 0000000 0000000 Copyright Notice and License Agreement for ViTables Application Software Copyright 2005-2007 by Carabos Coop. V. Copyright 2008-2011 by Vicent Mas GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc.