Skip to content

Releases: evought/VCard-Tools

v0.9.4.3

30 Aug 04:44
Compare
Choose a tag to compare

Updated abandoned dependency rhumsaa/uuid to new project/namespace ramsey/uuid.

v0.9.4.2

29 Aug 23:25
Compare
Choose a tag to compare

Updated to work with PHP 7 and more recent dependencies. Changed continuous integration testing environment to drop PHP 5.5, require 5.6 (no longer optional), and add 7.0. HHVM was not changed.

Also minor tweaks to documentation re: dependencies and database privileges.

Switch to Packagist data-uri component.

04 Feb 00:42
Compare
Choose a tag to compare

Intermediate release along the 0.9.5 milestone. Switches to using the Packagist data-uri component just made available to remove the need for a VCS-repository and simplify packaging/install.

Cleanup and Stabilization

23 Jan 08:09
Compare
Choose a tag to compare
Pre-release

This release concentrated on security, stabilization, error-handling, testing, documentation, and other fit-and-finish tasks to work toward a 1.0 release (milestone 0.9.4 issues). It was also a checkpoint for planning the remaining milestones working toward a 1.0 stable release (currently 3 milestones to a pre-1.0 release).

0.9.3

09 Jan 05:43
Compare
Choose a tag to compare
0.9.3 Pre-release
Pre-release

Release incorporating major refactorings of VCard Property types to make them first-class objects and exploit polymorphism to manipulate different types of properties/parameters, getting this closer to a production-quality API. The refactoring of VCard allowed significant cleanup throughout the rest of the API, particularly cleaner logic in VCardDB and more consistent handling of different property types. File/raw data parsing has been separated out from VCard into its own class, making VCard proper simpler, allowing legacy properties with embedded VCards and multiple VCard imports to be handled cleanly, and opening up the possibility of future customization of parsing by client code. Exception reporting and iteration APIs have also been greatly improved.

All RFC 6350 (VCard 4.0) properties are now represented in VCard, X-tended properties are handled (relatively) gracefully. Data-type properties (LOGO, PHOTO, SOUND, KEY) now handle encoding and media-type, including VCard 2.1/3.0 compatibility. Embedded binary data from legacy VCards is automatically encapsulated in a data URI. A utility class for validating/creating/parsing data URIs has been incorporated. Comma-properties such as CATEGORIES are now imported correctly. The VALUE parameter is now parsed and retained, along with default values according to the spec, allowing the caller to determine the format of a Property's data (e.g. TEXT vs. URI).

The JohnDoe sample VCard now imports from a file, translating legacy features to VCard 4.0. It can be written back out, stored to and fetched from the database.

Functionality of VCardDB and Template has not caught up to new VCard features. In other words, it is now possible to import and represent VCards which cannot be faithfully stored by VCardDB nor output faithfully by Template. This will be improved in the following pre-1.0 milestones.

0.9.2

15 Dec 20:06
Compare
Choose a tag to compare
0.9.2 Pre-release
Pre-release

Release with more complete round-trip VCard support (model, RDBMS, and output(file, html)), especially of TYPES, and VCard 4.0 Parameters.

0.9.1

09 Dec 18:14
Compare
Choose a tag to compare
0.9.1 Pre-release
Pre-release

First 'usable' release.

Utilities have been refactored into separate classes/files encapsulated within a namespace, project management has been set up (though not perfect), unit tests exist and have reasonable coverage, and API documentation is usable. Should set a decent foundation for moving forward.