Free kaspersky int software for mac

XML-RPC Client is a free Cocoa-based developer tool for Mac OS X Tiger that allows you to access and debug XML-RPC web services from the comfort of your desktop.
Its not much? and its not very full-featured. Basically, the suitably-named "XML-RPC Client" allows you to point at an arbitrary XML-RPC service URL available on the network, specify a method and (limited) parameters, and view the response in a readable display. Its pretty much meant to be used as a handy, graphical debugger for developers setting up or accessing XML-RPC services. I kinda needed something like this at work, and was tired of using the command line for something for which there should be a nice little graphical tool. Theres still work to be done. At this point, you can only send arguments of some of XML-RPCs "primitve" types: string, int, double, and boolean are supported. structs, arrays, base64 and dateTime.iso8601 are not yet supported. That means that you may not access any service methods requiring parameters of those types using XML-RPC Client. Release early and release often, right?
Enhancements
- Now a Universal Binary.

BASh is a 4D component that provides extensive utility commands, especially for dynamically reusable variable space (DSS, Dynamic Stack Space, module), date-time stamps (DTS module), resources (RES module), encoding and decoding (CODEC module), encryption (CRYPT module), X4D module (record packing in XML), XML management, and much, much more.
The BASh component now consists of 477 methods across 32 modules of code.
Main features:
Modules currently available in the BASh component:
- ARR - Array sizing, management, and manipulation methods;
- BLOB - BLOB management and manipulation methods;
- CODEC - encoding and decoding support for common formats;
- CONV - conversion methods to handle data and type conversions;
- CRYPT - encryption and decryption routines;
- DATE - provides basic date manipulation routines;
- DSS - Dynamic Stack Space; reusable variable management system;
- DTS - Date-Time Stamps; generation and manipulation methods;
- ENV - environmental information (program, OS, CPU, etc.);
- FILE - path and file name utilities;
- FMAP - file mapping for document types, creator and type codes, and MIME types;
- IB - management and manipulation of indexed BLOBs;
- INIT - module and component initialization;
- INT - interruption manager;
- NULL - Variable clearing and initialization methods;
- NVP - named value pair utilities and management;
- PROS - process information accessors;
- PTEXT - parameter text replacement routines;
- QUIT - controlled clean up of BASh data structures;
- RES - resource management and utility methods;
- RW - read/write module for handling record access;
- SEM - Semaphore management methods;
- SEQ - flexible sequence number module;
- SERNO - serial number generation and confirmation methods;
- STR - string manipulation, formatting, and filtering methods;
- TIME - Time manipulation methods;
- TYPE - Variable type comparison methods;
- URL - URL creation and extraction routines;
- VAR - Variable utility methods;
- WORD - manipulators for non-native four-byte values;
- X4D - XML based record packing and unpacking methods;
- XML - Extensible Markup Lanugage parsing and retrieval code.

This Neverwinter Nights patch will brind several improvements and fixes to the previous versions of the game.
Note: Each patch contains all the fixes from the previous patches.
WARNING! AS OF THIS PATCH, ALL MODULES CREATED/SAVED WITH THE VERSION 1.67 TOOLSET ARE TAGGED AS REQUIRING VERSION 1.67 OR HIGHER OF NEVERWINTER NIGHTS GAME OR TOOLSET.
IF YOU DONT WANT TO BRAND YOUR MODULE AS 1.67 THEN DO NOT EDIT YOUR MODULE IN THE VERSION 1.67 TOOLSET.
Enhancements:
- Added visible cloaks to the game.
- Fixed an issue with the Monks Perfect Self feat not correctly reporting that the monk was immune when making saving throws against mind-affecting spells (was making Phantasmal Killer work on monks if they failed their saving throws).
Scripting-specific
- Fixed an issue with the sleep spell not being counted as a hostile action when cast (nw_s0_sleep.nss).
- Fixed range issue in spell "Mestils Acid Breath" (X2_S0_AcidBrth.nss).
Custom Content
- Added new scripting command:
- // Set oPlaceables useable object status.
- // Note: Only works on non-static placeables.
- void SetUseableFlag(object oPlaceable, int nUseableFlag);
- Added new nwnplayer.ini setting.
- [Game Options] Log Model Errors=0
- If turned on, some types of model errors will be logged out to the nwclientLog file and the AR_ERROR.LOG file while the game is running (in the NWN install directory). This would include some errors with setting invalid TileSet data, invalid use nodes set on placables, some placeable walkmesh errors, and some errors with the animrootnode not matching the name of other nodes in the model.
- Wings now use the ENVMAP setting from the new column in the WingModel.2da rather than using the ENVMAP setting from the appearance.2da. This fixes some issues with transparency on wings.
- Tails now use the ENVMAP setting from the new column in the TailModel.2da rather than using the ENVMAP setting from the appearance.2da. This fixes some issues with transparency on tails.

Bochs is a portable x86 PC emulation software package that emulates enough of the x86 CPU, related AT hardware, and BIOS to run Windows, Linux, *BSD, Minix, and other OSs, all on your workstation.
Bochs is a highly portable open source IA-32 (x86) PC emulator written in C++, that runs on most popular platforms.
Bochs includes emulation of the Intel x86 CPU, a custom BIOS and common I/O devices. Currently, Bochs can be compiled to emulate a 386, 486, Pentium/PentiumII/PentiumIII/Pentium4 or x86-64 CPU including optional SSEx, MMX, and 3DNow! instructions.
Bochs is capable of running most Operating Systems inside the emulation including Linux, Windows 95, DOS, and Windows NT 4. Bochs was written by Kevin Lawton and is currently maintained by this project.
Bochs can be compiled and used in a variety of modes, some which are still in development. The typical use of Bochs is to provide complete x86 PC emulation, including the x86 processor, hardware devices, and memory.
This allows you to run OSes and software within the emulator on your workstation, much like you have a machine inside of a machine. For instance, lets say your workstation is a Unix/X11 workstation, but you want to run Win95 applications.
Bochs will allow you to run Win 95 and associated software on your Unix/X11 workstation, displaying a window on your workstation, simulating a monitor on a PC.

Enhancements
- Fixed bunch of CPUID issues
- Bochs is now able to install and boot 64-bit Windows images!
- Several bugfixes in CPU emulation (mostly for x87 instructions)
- Fixed two critical deadlock bugs in the Win32 gui.
- Fixes related to the show ips feature
- Removed conflicting win32-specific alarm() functions (win32 and sdl gui)
- Feature now works in wx on win32
- Added support for gdb stub on big endian machine.
- Rewritten obsolete hash_map code in dbg symbols module.
- BIOS: implemented missing INT 15h/89h.

mlnet is a multi-network P2P client. Previously known as mldonkey, its been the heart inside some other packages, as mlMac and xDonkey.
mlnet core supports Mac OS X, Linux, BSD, Solaris, and Win32.
It works as a core, which can be accesed, managed and controlled via Telnet, Webb (with your favorite browser) or via a graphic interface.
Its multi-net support actually covers the following networks:
- eDonkey 2000
- Overnet
- Kademlia
- BitTorrent
- FastTrack (Kazaa)
- Gnutella
- G2 (Shareaza).
Enhancements:
- 5199: BT: Fix BT_client_uid changing between core start
- 5196: IP: Store IPs with two int values instead of four to save RAM
- 5195: BT: Log tracker error messages in UTF-8
- 5194: HTML: Print warning on opening page when enable_servers is set to false
- 5191: HTML: remove sysinfo on opening page & option motd_html
- 5192: Fix deactivation of verbosity "gui"
- 5163: Configure: CVS SCM support for Mac OS X 10.3
- 5158: HTML: Use table for printing buildinfo and runinfo data
- 5187: New option: BT_import_new_torrents_interval, ignore Thumbs.db & desktop.ini in directory lists
- 5186: GUI: Send only non-empty real_startup_message string
- 5156: HTML, improve Options output
- 5061: New option small_files_slot_limit to push release of small files. all files below the configured file size (default 10kb) are uploaded through one reserved slot
- 5144: Increase default max_upload_rate to 10
- 5177: HTML, Options: update display after changing options
- 5176: Swarming: Change error message text and verbosity for BAD WRITE. BAD WRITE is not really an error, MLDonkey just receives unwanted data
- 5175: GTK1 oldgui: Last compile fix for abstract verification bitmaps
- 5174: Abstract verification bitmaps: compile fixes for GTK1 GUIs, move generic code to CDK
- 5173: Swarmer: Small fix for merged downloads
- 5172: EDK: Log error which causes pausing a download
- 5171: New command group "Driver/Users", print help text for "Bad number of arguments" error message
- 5170: Fix default max_indirect_connections, minimum is 30
- 5169: HTML, Options: add description to option section buttons, remove save button
- 5168: Global module to abstract verification bitmaps
- 5167: Swarmer: Fix saving ini data for merged downloads
- 5166: Swarmer: New module to abstract verification bitmaps
- 5164: CommonSwarming: Pangos WIP5e
- 5063: EDK: remove duplicate entries in shared_files_new.ini
- 5160: Remove stale avifile.ml, clean commonMultimedia logging
- 5159: Compute magic values only when needed
- 5157: add some line breaks to option help text for shorter lines
- 5153: New command: force_web_infos to manually download web_infos URLs
- 5152: Do not connect friends from disabled networks
- 5151: Options: New stringvalue functions needed for multiuser support
- 5150: Log: Fix log when server list is empty in check_blocked_servers
- 5149: Log: Some additions for commonSwarming
- 5148: Mail: Fix for multiline SMTP responses
- 5143: HTML/Telnet: Country codes for servers
- 5147: G1/G2: Display proper filename (and therefore support rename)
- 5145: EDK: Fix md4 hashing when filesize is an exact multiple of edk chunk size, MLDonkey is now eMule-compatible
- 5141: Swarmer: New option swarming_block_selection_algorithm
- 5140: Update .cvsignore files
- 5138: Catch ip banned exception
- 5137: HTML: Fix display of file magic values with
- 5136: FileTP: fixes and enhancements
- 5131: New option gui_log_size: number of lines for GUI console messages
- 5129: HTML: Display client_bind_addr in options menu
- 5124: Log: Login messages can be disabled with verbosity "no-login"
- 5130: CommonSwarming: Pangos WIP4a. Thats a huge patch over CommonSwarming module (whose job is to select what data to ask from connected sources, and the merging of received data),
- 5121: EDK: Remove obsolete option emule_compression
- 5122: improve block_list output and runinfo ip blocking
- 5123: Fix Invalid_argument("UTF8.length") bug in HTML, down-/uploaders.

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.

The BDControl Framework supplies some of the useful functionality that used to be provided as part of EOFs EOControl framework.
Specifically, in version 1.0.5, BDControl provides qualifiers and sort orderings. No other EOF functionality is provided at this time.
The disk image contains both a binary release and the complete source code. The BDControl Framework is Open Source, covered by a BSD-style license.
HTML documentation is provided within the BDControl Framework. The BDQualifier and BDSortOrdering classes should be drop-in replacements for EOQualifier and EOSortOrdering in most cases.
Enhancements:
- Major Change: Now uses an install path of @executable_path/../Frameworks. This means the framework expects to be bundled into your application, rather than in /Library/Frameworks. You should still keep your development copy in /Library/Frameworks or in ~/Library/Frameworks of course.
- Major Change: Now built with MACOSX_DEPLOYMENT_TARGET set to 10.2. This means that the framework now expects to be run on Mac OS X 10.2 or later. You should still be able to build it for 10.1 if you need to though.
- Changed the signature of -[BDQualifier count] to return an usigned rather than an int. This matches -[NSArray count] and makes the compiler not complain about mismatched prototypes.
- Built with the December 2002 release of the Mac OS X Developer Tools, on Mac OS X 10.2.6.
- Added missing documentation on categories and exception.
- Changed sorting to use BSD mergesort(3) instead of -[NSArray sortedArrayUsingFunction:inContext:] and its mutable equivalent, because these sorts arent guaranteed to be stable. This shouldnt affect behavior but it may affect performance, since using mergesort(3) requires at least two copies.

Flickcurl is a C library for the Flickr API, handling creating the requests, signing, token management, calling the API, marshalling request parameters and decoding responses.
Flickcurl uses libcurl to call the REST web service and libxml2 to manipulate the XML responses. Flickcurl 1.0 or later supports 100% of the 2008-01-23 version of the API (see Flickcurl API coverage) including the functions for photo uploading, browsing,
Flickcurl also includes a program flickrdf to turn photo metadata, tags and machine tags into RDF descriptions of photos and tags.
NOTE: Flickcurl is released under LGPL 2.1 / GPL 2 / Apache 2.0.

System requirements:
- libcurl
- libxml2 2.6.8 or newer
- raptor 1.4.0 (optional), 1.4.14 recommended

Enhancements
- flickcurl_search_params structure now has an integer field woe_id for searching via Where On Earth IDs (WOEIDs). Forgot to add this earlier!
- The flickcurl utility was updated to support searching with the integer woeid parameter.
- Search results now decode more of the extras that can be returned in search queries when the extras field is set in the query to a comma-separated list of things to return. The additions with their extras names are: original dimensions (o_dims), photo views count (views), simple list of tags (tags), photo user information (owner), geo information (geo) and user buddy icons (icons),
- Added new flickcurl_photo fields for extras from search results: PHOTO_FIELD_original_height, PHOTO_FIELD_original_width, PHOTO_FIELD_owner_iconfarm, PHOTO_FIELD_owner_iconserver and PHOTO_FIELD_views
- Added donuthole support to shapes as announced 2009-05-06. The flicckurl_shapedata structure now has is_donuthole and has_donuthole boolean flag fields.
- Fix handling API calls return shape XML with slightly different names so that places.getShapeHistory and places.getInfo both work now (again?).
- Added function to get a user buddy icon URI for a given user: char* flickcurl_user_icon_uri(int farm, int server, char *nsid);
- Added function to get the user buddy icon URI from a users photo: char* flickcurl_photo_as_user_icon_uri(flickcurl_photo *photo);
- Added function to return the photo page URI of a photo: char* flickcurl_photo_as_page_uri(flickcurl_photo *photo);
- Added timezone field support to place (This has not yet been announced as an API change). The flickcurl_place structure now has a timezone string field.
- Make more attempts to reset the libcurl context between requests which should help in sequences of calls that mix GET (searches, get information) and POST (uploading, deletions etc.) This is intended to try to fix a hard-to-test report of crashes with multiple upload and API calls on Solaris/SPARC.
- Configuration via configure now uses pkg-config(1) to get the compile (CFLAGS) and link (LIBS) flags info for libxml, libcurl and raptor. This should work since those libraries have shipped the respective .pc file in releases for some time.
- Use pkg-config raptor configuration for checking raptor presence, versions, cflags and libs rather than the (deprecated) raptor-config program output.
- Added configure SHAVE support (git clone git://git.lespiau.name/shave ) to "make autotools output sane" which amounts to much less verbose messages when compiling. It is now enabled by default.
- Compiling from subversion (autogen.sh or configure --enable-maintainer-mode) requires Libtool V2 for consistency with my other projects.