gc invoicer
Simple Invoicer 1.0b2
Simple Invoicer - Project management application more>>
I typically work on multiple projects at a time for a small number of clients and wanted a program to track my time on a project basis, rather than on a client basis.
At some point, I may re-write this using Core Data and Cocoa Bindings to make a more robust and user-friendly application, but for now caveat emptor.
Enhancements:
- Corrected a problem with the "review unsaved documents" functionality where the application would terminate before the user could review their documents.
GCViewer 1.21
GCViewer is a free open source tool to visualize data produced by the Java VM options -verbose:gc and -Xloggc: more>>
Supported Formats
Sun JDK 1.4/1.5 with the options -Xloggc: [-XX:+PrintGCDetails]
Sun JDK 1.2.2/1.3.1/1.4 with the option -verbose:gc
IBM JDK 1.3.1/1.3.0/1.2.2 with the option -verbose:gc
Best results are achieved with: -Xloggc: -XX:+PrintGCDetails
Data Export
GCViewer can also export the data in CSV (comma separated values) format, which may easily be imported into spreadsheet applications for further processing.
Miscellaneous
GCViewer has been developed with J2SE 1.4 and is licensed under LGPL.
GCStatistic 1.5.1
Geocaching statistic tool. more>>
GCStatistic 1.5.1 is a simple to use, yet sophisticated geocaching statistic tool which can choose between the generation af a standalone html file or an automated upload to your geocaching.com profile.
Major Features:
- Simply select the gpx file with your finds from gc and select the statistic section you would like to see in the output.
- Just some available find statistics are:
- Finds by year/month and weekday
- Finds by distance and countries
- Finds by cache size, type, owner or difficulty
- Maps of the countries cached in
- A lot of additional interesting statistics
Enhancements:
- New section added that divides the finds in 5 levels acc. D/T
- New World66 map for canadian provinces added.
- If the gpx file is created with BuildGPX (no premium) the 3 stats about log-length are hidden now as these information is missing in the gpx file.
- The time lag column in the special cache section can be hidden now.
- The settings for the cachetype section is back.
- The entry in the FTF statistic for the first cache should be fixed now.
with your finds from gc and select the statistic section you would like to see in the output. JustLicense:Freeware
xvidEncoder 1.1.5
xvidEncoder has come as a smart and useful program for you to download. more>>
xvidEncoder 1.1.5 has come as a smart and useful program for you to download. Xvid and libavcodec based QuickTime Media Compressor component . Support xvid, another MPEG-4 SP/ASP Video Media. Support some MPEG-4 ASP features, including B-frame with Open/Closed GOP.
Source codes are included, and free software under GPL V2. Uses libxvidcore.a, libavcodec.a and others from xvid release build and ffmpeg SVN.
Enhancements:
- Fix incompatibility with GC-only Apps.
- Other minor fix.
- Includes 64bit CoreVFPrefPane.
- Sync core to xvidcore CVS-20090917 and ffmpeg SVN-20125.
x264Encoder 1.1.5
x264Encoder offers you a smart and flexible x264 and libavcodec based QuickTime Media Compressor component that supports avc1, H.264/MPEG-4 AVC Video Media. more>>
x264Encoder 1.1.5 offers you a smart and flexible x264 and libavcodec based QuickTime Media Compressor component that supports avc1, H.264/MPEG-4 AVC Video Media. Support some MPEG-4 AVC features, including Main/High Profile up to Level 5.1.
Source codes are included, and free software under GPL V2. Uses libx264.a, libavcodec.a and others from x264 git and ffmpeg SVN. (Universal Binary)
Enhancements:
- Fix incompatibility with GC-only Apps.
- Other minor fix.
- Includes 64bit CoreVFPrefPane.
- Sync core to x264 git-1271 and ffmpeg SVN-20125.
mp4vEncoder 1.1.5
mp4vEncoder provides you with a handy and useful libavcodec based QuickTime Media Compressor component which can deal with mp4v, MPEG-4 Video Media. more>>
mp4vEncoder 1.1.5 provides you with a handy and useful libavcodec based QuickTime Media Compressor component which can deal with mp4v, MPEG-4 Video Media. Support some MPEG-4 ASP features, including B-frame with Open/Closed GOP.
Source codes are included, and free software under GPL V2. Uses libavcodec.a and others from ffmpeg SVN. (Universal Binary)
Enhancements:
- Fix incompatibility with GC-only Apps.
- Other minor fix.
- Includes 64bit CoreVFPrefPane.
- Sync core to ffmpeg SVN-20125.
Snap2GC 1.1
Snap2GC - Take screen snapshot and paste it into GraphicConverter more>>
Sends keystroke to the application to achieve this. There is an Applescript function built-in to GC that loads the clipboard but the keystroke technique may be useful for other "non-scriptable" apps.
AstroGC 5.7
AstroGC - Gives an astrological character description more>>
The "Astro" files are based on a friends astrology notes.
Enhancements:
- Universal Binary.
Legacy BCD2000 MIDI Driver 20070111
Free BCD2000 midi driver for your Mac more>> If youre in business - small, medium, or large - you need invoice software thats easy to set up and easy to use. CG Invoicer is a marvel of simplicity; our users say its "well thought out", "simple to grasp", and "intuitive."
Track Orders: Keep tabs on your sales orders so that you get paid in a timely manner. Provide better customer service with the ability to view a history of products and services rendered at a glance.
Create Sales Reports: Run a report of all invoices 30 days or more overdue. Year-to-date sales reports so that you can capture, measure and improve your performance.
Control Overdue Accounts: Our invoice software allows you to quickly access and act upon unpaid invoices. Maintain buying patterns and sales volumes for customers so you sell them what they need when they need it.<<less
Toms Graphing Calculator 1.0
Toms Graphing Calculator - 3D graphing calculator more>>
It includes a stereo 3D mode for use with red/cyan glasses
Main features:
- Plotting of curves as a function of x or a function of y
- Plotting of surfaces as functions of x and y, either as points, a wireframe or a surface (surface sucks)
- Plotting of vector fields as a function of R (the < x,y,z> vector)
- Functions: sin, cos, tan, ln, *, +, /, -, ^ (* and / are dot and cross respectively between vectors), v(a,b,c) to make a vector of a,b and c
- Stereogram graph drawing, but it needs some 3D glasses to look through to see this.
F-Script 2.0
F-Script is such an effective open-source scripting layer which is specifically designed for the Mac OS X object system (i.e. Cocoa). more>>
F-Script 2.0 is such an effective open-source scripting layer which is specifically designed for the Mac OS X object system (i.e. Cocoa). F-Script provides scripting and interactive access to Cocoa frameworks and custom Objective-C objects. It aims to be a useful and fun tool for both beginners and experts, allowing interactively exploring, testing and using Cocoa-based objects and frameworks.
Major Features:
- The F-Script shell provides an interactive command line interface for manipulating Objective-C objects.
- Use a fully featured object-oriented shell.
- Manipulate objects interactively or write scripts.
- Save and load objects easily.
- Express complex object manipulations quickly and easily with a high-level programming model.
- Access the Cocoa frameworks as well as your own Objective-C objects.
- The object browser lets you graphically find, explore and manipulate objects.
- Explore objects and methods.
- Browse Objective-C instances and Objective-C classes.
- Quickly locate attributes and methods with the search field.
- Graphically Invoke methods.
- Navigate Cocoa bindings.
- Explore Core Data objects graphs.
- Select objects on screen with the "Select and browse" magic button.
- Add custom actions to the browser.
- Powerful tools let you inspect objects.
- Query Core Data interactively.
- Explore Cocoa collections (arrays, dictionaries, etc.)
- Edit and run scripts.
- Inspect Cocoa objects.
Enhancements:
- Garbage collection
-
- New in F-Script 2.0 is a fast, concurrent, generational garbage collector. It was a lot of work to implement. Fortunately, Apple did all of it, as F-Script 2.0 uses the new Objective-C garbage collector. As with Objective-C, when you run F-Script in GC mode you no longer have to manage retain counts and to care for cyclic references. You can still use F-Script in non-GC mode, which is needed if you want to interact with non-GC capable frameworks or libraries. A new option in the F-Script preference panel let you choose your memory management model. Finally, you can embed F-Script in GC or non-GC applications.
- Garbage collection is performed concurrently, on its own thread. Another notable aspect is that it works both for objects and for raw memory buffers. Actually, for raw memory buffers, you can either use managed or unmanaged memory. F-Script 2.0 lets you use unmanaged memory as usual (i.e., with the malloc: method) and introduces new methods, in the FSPointer class, for dealing with managed memory. Features such as weak references, explicit GC control, etc. are all available from F-Script using the standard methods provided by Cocoa.
- 64-bit: F-Script 2.0 provides 64-bit support. Benefits include:
-
- Very large virtual address space
- New Objective-C runtime (optimized message dispatching, zero-cost setup model for exceptions, etc.)
- Ability to load 64-bit frameworks in F-Script and to embed F-Script in 64-bit applications
- You can still run in 32-bit mode and you can use the F-Script framework in 64-bit and 32-bit applications. The F-Script API itself now exposes both 64-bit and 32-bit capable interfaces, using Cocoa's NSInteger, NSUInteger and CGFloat macros.
- New object browser: The graphical object browser gains a new look and a number of enhancements. This includes:
-
- Introspection of Objective-C 2.0 properties
- Improved introspection of bindings
- Direct access to the view hierarchy
- Visual feedback when selecting graphical components on screen
- Additional information about standards Cocoa objects
- And more...
- Dynamic Cocoa class creation: F-Script 2.0 makes it very easy to dynamically define new classes. At run-time, these dynamically generated classes are regular Cocoa classes that happen to execute F-Script code instead of compiled Objective-C code. They can be used from both F-Script and Objective-C. You can subclass existing Cocoa classes in F-Script and, as in Objective-C, define instance variables, instance methods and class methods. In addition, F-Script also supports defining class instance variables.
- System-wide scripting: F-Script 2.0 is able to control scriptable applications and graphically browse and interact with the applications scripting interfaces. This major new feature is based on the MAC OS X Scripting Bridge technology. For example, here is how you can connect to iTunes
- Updated embedding and injecting capabilities: F-Script can be easily embedded into your own applications or dynamically injected at runtime into any running Cocoa application. Embedding is great for adding scripting or interactive object querying/manipulation capabilities to your applications, as well as for implementing parts of your apps with F-Script. Injecting is incredibly powerful when it comes to debugging or exploring the innards of applications. F-Script 2.0 comes with full support for the new plugin model of Interface Builder 3, allowing drag and drop of F-Script graphical components right into your application. F-Script 2.0 also includes a developer version of F-Script Anywhere 2.0, which allows injecting F-Script into any Cocoa application.
- Refined syntax and class library
-
- F-Script is a Smalltalk dialect. As such, its syntax is well suited to the manipulation of Objective-C objects, since Objective-C itself borrowed its messaging syntax from Smalltalk. F-Script 2.0 introduces several syntax refinements, including a handy notation for specifying dictionaries. Here is how an NSMutableDictionary instance with two entries looks like:
- There are other syntax enhancements including support for Unicode in string literals and a hexadecimal notation for numbers. Besides, the base class library has been refined, with new methods for dealing with collections, new globals for easy access to the standards IO streams, a new facility for comparing objects with the special nil value and some changes in the way test for object equality is performed. It is also worth noting the introduction of a new public class, FSAssociation, which represents associations between two objects, a "key" and a "value", and is primarily used for specifying dictionary entries.
- If you are not familiar with the F-Script syntax and fundamental elements, the two articles referenced below will get you up to speed in a breeze.
- Direct access to the latest Mac OS X technologies: F-Script 2.0 lets you directly access a number of the latest Mac OS X frameworks. And other ones are just a simple loading instruction away.
- New project infrastructure: The source code for F-Script is now available at Github
Requirements: Requires Mac OS X 10.5 or later
ZODB3 3.9.0 Beta 1
A free set of tools for using the Zope Object Database (ZODB) more>> A free set of tools for using the Zope Object Database (ZODB)
The Zope Object Database provides an object-oriented database for Python that provides a high-degree of transparency.
Applications can take advantage of object database features with few, if any, changes to application logic. ZODB includes features such as a plugable storage interface, rich transaction support, and undo.
The components you get with the ZODB release are as follows:
- Core ZODB, including the persistence machinery
- Standard storages such as FileStorage
- The persistent BTrees modules
- ZEO, for scalability needs
- documentation (needs more work)
ZODBs primary development platforms are Mac OS X, Linux, and Windows XP.
System requirements:
-
Enhancements
New Features (in more or less reverse chronological order):
- The Database class now has an xrefs keyword argument and a corresponding allow-implicit-cross-references configuration option. which default to true. When set to false, cross-database references are disallowed.
- As a convenience, the connection root method for returning teh root object can now also be used as an object with attributes mapped to the root-object keys.
- Databases have a new method, transaction, that can be used with the Python (2.5 and later) with statement
- This uses a private transaction manager for the connection. If control exists the block without an error, the transaction is committed, otherwise, it is aborted.
- Convenience functions ZODB.connection and ZEO.connection provide a convenient way to open a connection to a database. They open a database and return a connection to it. When the connection is closed, the database is closed as well.
- The ZODB.config databaseFrom... methods now support multi-databases. If multiple zodb sections are used to define multiple databases, the databases are connected in a multi-database arrangement and the first of the defined databases is returned.
The zeopack script has gotten a number of improvements:
- Simplified command-line interface. (The old interface is still supported, except that support for ZEO version 1 servers has been dropped.)
- Multiple storages can be packed in sequence.
- This simplifies pack scheduling on servers serving multiple databases.
- All storages are packed to the same time.
- You can now specify a time of day to pack to.
- The script will now time out if it cant connect to s storage in 60 seconds.
- The connection now estimates the object size based on its pickle size and informs the cache about size changes.
- The database got additional configurations options (cache-size-bytes and historical-cache-size-bytes) to limit the cache size based on the estimated total size of cached objects. The default values are 0 which has the interpretation "do not limit based on the total estimated size". There are corresponding methods to read and set the new configuration parameters.
- Connections now have a public opened attribute that is true when the connection is open, and false otherwise. When true, it is the seconds since the epoch (time.time()) when the connection was opened. This is a renaming of the previous _opened private variable.
- FileStorage now supports blobs directly.
- You can now control whether FileStorages keep .old files when packing.
- POSKeyErrors are no longer logged by ZEO servers, because they are really client errors.
- A new storage interface, IExternalGC, to support external garbage collection, http://wiki.zope.org/ZODB/ExternalGC, has been defined and implemented for FileStorage and ClientStorage.
- As a small convenience (mainly for tests), you can now specify initial data as a string argument to the Blob constructor.
- ZEO Servers now provide an option, invalidation-age, that allows quick verification of ZEO clients less than a given age even if the number of transactions the client hasnt seen exceeds the invalidation queue size. This is only recommended if the storage being served supports effecient iteration from a point near the end of the transaction history.
- The FileStorage iterator now handles large files better. When iteratng from a starting transaction near the end of the file, the iterator will scan backward from the end of the file to find the starting point. This enhancement makes it practical to take advantage of the new storage server invalidation-age option.
- Previously, database connections were managed as a stack. This tended to cause the same connection(s) to be used over and over. For example, the most used conection would typically be the onlyt connection used. In some rare situations, extra connections could be opened and end up on the top of the stack, causing extreme memory wastage. Now, when connections are placed on the stack, they sink below existing connections that have more active objects.
- There is a new pool-timeout database configuration option to specify that connections unused after the given time interval should be garbage colection. This will provide a means of dealing with extra connections that are created in rare circumstances and that would consume an unreasonable amount of memory.
- The Blob open method now supports a new mode, c, to open committed data for reading as an ordinary file, rather than as a blob file. The ordinary file may be used outside the current transaction and even after the blobs database connection has been closed.
- ClientStorage now provides blob cache management. When using non-shared blob directories, you can set a target cache size and the cache will periodically be reduced try to keep it below the target size.
- The client blob directory layout has changed. If you have existing non-shared blob directories, you will have to remove them.
- ZODB 3.9 ZEO clients can connect to ZODB 3.8 servers. ZODB ZEO clients from ZODB 3.2 on can connect to ZODB 3.9 servers.
- When a ZEO cache is stale and would need verification, a ZEO.interfaces.StaleCache event is published (to zope.event). Applications may handle this event and take action such as exiting the application without verifying the cache or starting cold.
- Theres a new convenience function, ZEO.DB, for creating databases using ZEO Client Storages. Just call ZEO.DB with the same arguments you would otherwise pass to ZEO.ClientStorage.ClientStorage.
- Object saves are a little faster
- When configuring storages in a storage server, the storage name now defaults to "1". In the overwhelmingly common case that a single storage, the name can now be ommitted.
- FileStorage now provides optional garbage collection. A gc keyword option can be passed to the pack method. A false value prevents garbage collection.
- The FileStorage constructor now provides a boolean pack_gc option, which defaults to True, to control whether garbage collection is performed when packing by default. This can be overridden with the gc option to the pack method.
- The ZConfig configuration for FileStorage now includes a pack-gc option, corresponding to the pack_gc constructor argument.
- The FileStorage constructor now has a packer keyword argument that allows an alternative packer to be supplied.
- The ZConfig configuration for FileStorage now includes a packer option, corresponding to the packer constructor argument.
- MappingStorage now supports multi-version concurrency control and iteration and provides a better storage implementation example.
DemoStorage has a number of new features:
- The ability to use a separate storage, such as a file storage to store changes
- Blob support
- Multi-version concurrency control and iteration
- Explicit support dfor demo-storage stacking via push and pop methods.
- Wen calling ZODB.DB to create a database, you can now pass a file name, rather than a storage to use a file storage.
Added support for copying and recovery of blob storages:
- Added a helper function, ZODB.blob.is_blob_record for testing whether a data record is for a blob. This can be used when iterating over a storage to detect blob records so that blob data can be copied. In the future, we may want to build this into a blob-aware iteration interface, so that records get blob file attributes automatically.
- Added the IBlobStorageRestoreable interfaces for blob storages that support recovery via a restoreBlob method.
- Updated ZODB.blob.BlobStorage to implement IBlobStorageRestoreable and to have a copyTransactionsFrom method that also copies blob data.
- New ClientStorage configuration option drop_cache_rather_verify. If this option is true then the ZEO client cache is dropped instead of the long (unoptimized) verification. For large caches, setting this option can avoid effective downtimes in the order of hours when the connection to the ZEO server was interrupted for a longer time.
- Cleaned-up the storage iteration API and provided an iterator implementation for ZEO.
- Versions are no-longer supported.
- Document conflict resolution (see ZODB/ConflictResolution.txt).
- Support multidatabase references in conflict resolution.
- Make it possible to examine oid and (in some situations) database name of persistent object references during conflict resolution.
- Moved the transaction module out of ZODB. ZODB depends upon this module, but it must be installed separately.
- ZODB installation now requires setuptools.
- Added offset information to output of fstail script. Added test harness for this script.
- Added support for read-only, historical connections based on datetimes or serials (TIDs). See src/ZODB/historical_connections.txt.
- Removed the ThreadedAsync module.
- Now depend on zc.lockfile
Bugs Fixed:
- fixed Python 2.6 compatibility issue with ZEO/zeoserverlog.py
- using hashlib.sha1 if available in order to avoid DeprecationWarning under Python 2.6
- made runzeo -h work
- The monitor server didnt correctly report the actual number of clients.
- Packing could return spurious errors due to errors notifying disconnected clients of new database size statistics.
- Undo sometimes failed for FileStorages configured to support blobs.
- Starting ClientStorages sometimes failed with non-new but empty cache files.
- The history method on ZEO clients failed.
- Fix for bug #251037: Make packing of blob storages non-blocking.
- Fix for bug #220856: Completed implementation of ZEO authentication.
- Fix for bug #184057: Make initialisation of small ZEO client file cache sizes not fail.
- Fix for bug #184054: MappingStorage used to raise a KeyError during load instead of a POSKeyError.
- Fixed bug in Connection.TmpStore: load() would not defer to the backend storage for loading blobs.
- Fix for bug #181712: Make ClientStorage update lastTransaction directly after connecting to a server, even when no cache verification is necessary.
- Fixed bug in blob filesystem helper: the isSecure check was inversed.
- Fixed bug in transaction buffer: a tuple was unpacked incorrectly in clear.
- Bugfix the situation in which comparing persistent objects (for instance, as members in BTree set or keys of BTree) might cause data inconsistency during conflict resolution.
- Fixed bug 153316: persistent and BTrees were using int for memory sizes which caused errors on x86_64 Intel Xeon machines (using 64-bit Linux).
- Fixed small bug that the Connection.isReadOnly method didnt work after a savepoint.
- Bug #98275: Made ZEO cache more tolerant when invalidating current versions of objects.
- Fixed a serious bug that could cause client I/O to stop (hang). This was accomonied by a critical log message along the lines of: "RuntimeError: dictionary changed size during iteration".
- Fixed bug #127182: Blobs were subclassable which was not desired.
- Fixed bug #126007: tpc_abort had untested code path that was broken.
- Fixed bug #129921: getSize() function in BlobStorage could not deal with garbage files
- Fixed bug in which MVCC would not work for blobs.
- Fixed bug in ClientCache that occurred with objects larger than the total cache size.
- When an error occured attempting to lock a file and logging of said error was enabled.
- FileStorages previously saved indexes after a certain number of writes. This was done during the last phase of two-phase commit, which made this critical phase more subject to errors than it should have been. Also, for large databases, saves were done so infrequently as to be useless. The feature was removed to reduce the chance for errors during the last phase of two-phase commit.
- File storages previously kept an internal object id to transaction id mapping as an optimization. This mapping caused excessive memory usage and failures during the last phase of two-phase commit. This optimization has been removed.
- Refactored handling of invalidations on ZEO clients to fix a possible ordering problem for invalidation messages.
- On many systems, it was impossible to create more than 32K blobs. Added a new blob-directory layout to work around this limitation.
- Fixed bug that could lead to memory errors due to the use of a Python dictionary for a mapping that can grow large.
- Fixed bug #251037: Made packing of blob storages non-blocking.
- Fixed a bug that could cause InvalidObjectReference errors for objects that were explicitly added to a database if the object was modified after a savepoint that added the object.
- Fixed several bugs that caused ZEO cache corruption when connecting to servers. These bugs affected both persistent and non-persistent caches.
- Improved the the ZEO client shutdown support to try to avoid spurious errors on exit, especially for scripts, such as zeopack.
- Packing failed for databases containing cross-database references.
- Cross-database references to databases with empty names werent constructed properly.
- The zeo client cache used an excessive amount of memory, causing applications with large caches to exhaust available memory.
Fixed a number of bugs in the handling of persistent ZEO caches:
- Cache records are written in several steps. If a process exits after writing begins and before it is finishes, the cache will be corrupt on restart. The way records are writted was changed to make cache record updates atomic.
- There was no lock file to prevent opening a cache multiple times at once, which would lead to corruption. Persistent caches now use lock files, in the same way that file storages do.
- A bug in the cache-opening logic led to cache failure in the unlikely event that a cache has no free blocks.
- When using ZEO Client Storages, Errors occured when trying to store objects too big to fit in the ZEO cache file.
- Fixed bug in blob filesystem helper: the isSecure check was inversed.
- Fixed bug in transaction buffer: a tuple was unpacked incorrectly in clear.
- Fixed bug in Connection.TmpStore: load() would not defer to the backend storage for loading blobs.
- Fixed bug #190884: Wrong reference to POSKeyError caused NameError.
- Completed implementation of ZEO authentication. This fixes issue 220856.
- Page: 1 of 1
- 1
