Free libgist 2.0.2 software for linux

libzdt is a free general library aimed at anyone who wants to use it.

Some people may wonder why we need another software library. The answer is simple: What others dont offer, were trying to provide.

This basically meaning, while some of the things included in libzdt are included in other libraries, either we think the implementation isnt perfect, or we just feel it would make a great compliment to what were trying to do which is make life easier for those who want to write software.

While libzdt does not contain any graphical user interface API, it may later (please keep in mind that libzdt is still very pliable in a GUI application depending on what it is, and what the application does).

Anyway, libzdt is just a collection of functions Ive wrote over the years, or someone else has written and Ive just picked em up (you can see the list of people to whom I owe thanks for their code in the Documentation/Authors file). libzdts primary use will be in ZerOS, the operating system myself and a few friends are designing and developing (well, Im doing the development), right now however, its primary use is in custom commercial software my company writes. This version however, is not used in any commercial software, please see further into this document for more information on libzdt itself.

Little note on our coding style, at least myself, I go by the Linux kernel coding standards (which are included in the Documentation/CodingStyle file).

Anyway, back to libzdt itself... Its being rewritten for one reason, and one simple reason only. The version of libzdt that I use myself (not to say I dont use this one, because I do) is private, closed source. Its a library written in Objective-C++ anyway, so only a few platforms can use it (MacOS X, NeXTSTEP/OpenStep are the only platforms that I know have a working ObjC++ compiler), and besides, the code is ugly looking.

To compile libzdt, all you have to do is go into the main directory, which you are no doubt in right now reading this file, and type: make. This will build both the static library and shared library files and place them in the $LIBZDT_ROOT/Objects.x86 directory. In previous versions you had to type: make depend shared static, or something of the such to build all that you can now with just the make command without any arguments. To install libzdt, you must be root (or a user who has permissions to run ldconfig) in order to complete the install process. Simply type: make install.

ftplib++ contains a c++ class providing ftp client functionality. ftplibpp library supports all basic ftp functionality plus some advanced features like resuming, fxp, ssl/tls encryption, large file support, or logging to fit todays standards.
The very base of ftplib++ is the nice code of Thomas Pfaus ftplib c library. Every ftp session is represented by an ftplib object, whose methods are called to communicate with the ftp server.
The ftp sessions should begin with a call to myftp.Connect("myftp.org:21") (and maybe myftp.NegotiateEncryption()), be followed with myftp.Login("myuser","mypass") and ended by myftp.Quit(); For the magic in between, read the class methods documentation.
Most methods have their tasks yet explained from their name. ftplib++ uses the openssl library for encryption functionality, if you dont need it you can use the "NOSSL" flag, when compiling ftplib.cpp (g++ -c ftplib.cpp -DNOSSL).
If your system does not feature large file support you can use the "NOLFS" flag (g++ -c ftplib.cpp -DNOLFS).
Enhancements:
- fixed a bug in the upload routine

Clipmarks is a Firefox Extension and its about breaking down the web into pieces instead of pages.

When you find something in a web page that interests you, clip it.

By adding tags to clipmarks, youre able to create your own searchable collection of things youve clipped from the web.

Clipmarks is also about seeing and discussing things that other people are clipping.

pBeans project is a Object/Relational (O/R) database mapping layer. It is designed to be simple to use and automated.
The idea is that you save time and effort by simply focusing on writing Java classes, and not worrying about maintenance of matching SQL scripts, schema evolution, XML based schemas, or generating code. The pBeans framework takes care of persisting JavaBeans with little assistance from the developer.
Main features:
- Automatic Table Creation and Schema Evolution- Tables corresponding to JavaBean classes are created on demand. Field types are based, by default, on JavaBean compile-time types. Field type changes and new fields are detected. Manually changing tables (user-managed mode) is also supported.
- Based on Annotated JavaBeans- You define a getter and setter for each bean property. Persisent bean classes only need to be tagged with a @PersistentClass annotation.
- Transitive Persistence- If object A is persisted and it refers to Persistent object B, then object B is automatically persisted. If Persistent object C also refers to B, and C is also persisted, the record for object B in the database is not duplicated.
- Instance Consistency- If you retrieve an object from persistent storage that is already known to exist in main memory, you get a reference to the object in main memory. (Garbage collection is allowed to happen via weak references.)
- Near-Zero Configuration- There is no need to define schemas or anything of the sort in a language other than Java, and there are no code generation steps of any kind. No XML or SQL need to be written, except the necessary to create a database and grant user permissions. However, you can instruct pBeans to let you manage database modifications manually.
- Database features- Transactions and auto-increment IDs (MySQL only) are now supported.
- Flexibility- Via annotations users are allowed to define their own table and field names, the name of the primary key, whether fields are nullable, whether tables are user-managed (not automatically modified), table indexes, unique or otherwise, whether unused fields should be deleted, whether a field is nullable, whether it is renamed from another field (to prevent loss of data when a property is renamed), etc.
- Servlet support- A pBeans store may be easily configured using servlet context parameters (see ServletAccess.)

svk is a decentralized version control system written in Perl. svk project uses the Subversion filesystem but provides additional, powerful features. svk was originally developed by ChiaLiangKao, with the help from SVKPeople and generous SVKSponsors.
Main features:
- svk uses the subversion fs library. the SVN::XD module is a svn_wc (working copy) replacement (XD is character increment of WC).
- SVN::XD does not use the .svn for checkout meta-data. it uses Data::Hierarchy for storing per-directory meta-data in a compact way. Read about WhyXD.
- svk uses svm (svn mirror) for retrieving remote repositories (via ra) to a certain point of the local repository. There are plans to integrate svm and vcp so we have instant ability to branch remote cvs or perforce.
- the depot spec is like : . ~/.svk/config holds a depotmap hash for mapping depotname (which could be empty) to a path containing a subversion repository.
- when committing (or merging) into the mirrored directory, svm provides a commit editor for svk to use. the merge brings changes from local to remote repository if theres no conflict.
- using a local repository holding the subversion tree for benchmark, svk checkout time is 3 times faster than svn.
Enhancements:
- Perl 5.9.5 compatibility, various fixes in the merge subsystem, and some Win32 fixes.

Stencil is a library for developing web-based applications in C++.
It includes request and response objects, a skinnable template engine, server api abstraction, and facilities for load balancing, browser jogging, security and catching runaway CGIs.
Stencil library also includes some useful Javascripts and images.
Stencil is the successor to Groundwork.
Enhancements:
- Fixes a multipart form processing bug.
- All methods use (u)int(16|32|64)_t types rather than (unsigned )(short|long|long long) types.

DPML SDK is a management platform for Java-based component development, resource management, and deployment.
DPML SDK is composed of the Transit resource management layer, the Depot multi-project build system, the Metro component management runtime engine, and the Station application management console.
Enhancements:
- New features and enhancements added since version 2.0.1 include the addition of support for component composition via reference to nested parts within the internal structure of a component using part URIs as the construction mechanisms.
- This version also includes numerous code and documentation quality enhancements and updates to the checkstyle task involving migration from Checkstyle 4.1 to 4.3.