data from access to excel
PHP Database Access Through Arrays 0.7.0
PHP Database Access Through Arrays project can be used to access data stored in MySQL tables like accessing arrays. more>>
Examples:
$DB[test_table][] = array(
name => first,
value => the first row
);
foreach ($DB[test_table] as $i => $row) {
...
}
$DB[test_table][first][value] = 1st;
unset($DB[test_table][first]);
AnyData::Format::XML 0.10
AnyData::Format::XML is a Perl module for tiedhash and DBI access to XML. more>>
SYNOPSIS
# access XML data via a multi-dimensional tied hash
# see AnyData.pod for full details
#
use AnyData;
my $table = adTie( XML, $file, $mode, $flags );
OR
# convert data to and from XML
# see AnyData.pod for full details
#
use AnyData;
adConvert( XML, $file1, $any_other_format, $file2, $flags );
adConvert( $any_other_format, $file1, XML, $file2, $flags );
OR
# access the data via DBI and SQL
# see DBD::AnyData.pod for full details
#
use DBI;
my $dbh = DBI->connect( dbi:AnyData );
$dbh->func(mytable,XML,$file,$flags,ad_catalog);
See below for a description of the optional flags that apply to all of these examples.
This module allows you to create, search, modify and/or convert XML data and files by treating them as databases without having to actually create separate database files. The data can be accessed via a multi-dimensional tiedhash using AnyData.pm or via DBI and SQL commands using DBD::AnyData.pm. See those modules for complete details of usage.
The module is built on top of Michel Rodriguezs excellent XML::Twig which means that the AnyData interfaces can now include information from DTDs, be smarter about inferring data structure, reduce memory consumption on huge files, and provide access to many powerful features of XML::Twig and XML::Parser on which it is based.
Importing options allow you to import/access/modify XML of almost any length or complexity. This includes the ability to access different subtrees as separate or joined databases.
Exporting and converting options allow you to take data from almost any source (a perl array, any DBI database, etc.) and output it as an XML file. You can control the formating of the resulting XML either by supplying a DTD listing things like nesting of tags and which columns should be output as attributes and/or you can use XML::Twig pretty_print settings to generate half a dozen different levels of compactness or whitespace in how the XML looks.
The documentaion below outlines the special flags that can be used in either of the interfaces to fine-tune how the XML is treated.
The flags listed below define the relationship between tags and attributes in the XML document and columns in the resulting database. In many cases, you can simply accept the defaults and the database will be built automatically. However, you can also fine tune the generation of the database by specifying which tags and attributes you are interested in and their relationship with database columns.
Sowa Data Capacitor 0.0.0_dev0
Sowa Data Capacitor is a unified Java API for accessing data in several different forms, such as XML, memory, or database. more>>
Installation:
Sowa Data Capacitor now not need any dependences (except ant), but itll propably have.
To build it you have to have:
* Apache Ant
* JDK of Java 2
To use it you have to have:
* JVM of Java 2
To build it just run build in base catalogue.
Version Convention
First noumber(maior) is api version, except 0 and 1 which is maturity change.
Itll change only if api is completly rewritten.
Second(minor) means small api(especcially adds) changes, which could break(but
not have to) plugins but not applications.
Third(patch) means some improvement, which not change api.
Dev means version for developer(of plugins optionally applications), Alpha
and Beta test release.
Last noumber mark order of releases.
Hierarchical Data Format 1.8.0 Beta 3
Hierarchical Data Format is a general purpose library and file format for storing scientific data. more>>
HDF5 can store two primary objects: datasets and groups. A dataset is essentially a multidimensional array of data elements, and a group is a structure for organizing objects in an HDF5 file. Using these two basic objects, one can create and store almost any kind of scientific data structure, such as images, arrays of vectors, and structured and unstructured grids. You can also mix and match them in HDF5 files according to your needs.
Efficient storage and I/O.
HDF5 was created to address the data management needs of scientists and engineers working in high performance, data intensive computing environments. As a result, the HDF5 library and format emphasize storage and I/O efficiency. For instance, the HDF5 format can accommodate data in a variety of ways, such as compressed or chunked. And the library is tuned and adapted to read and write data efficiently on parallel computing systems.
Software.
NCSA maintains a suite of free, open source software, including the HDF5 I/O library and several utilities. The HDF5 user community also develops and contributes software, much of it freely available. Unlike HDF4, there is little commercial support for HDF5 at this time, but we are successfully working with vendors to change this.
Emphasis on standards.
Data can be stored in HDF5 in an endless variety of ways, so it is important for communities of users to standardize on how their data is to be organized in HDF5. This makes it possible to share data easily, and also to build and share tools for accessing and analyzing data stored in HDF5. The NCSA HDF team works with users to encourage them to organize HDF5 files in standard ways.
Large and varied user community.
HDF5 users range across a variety of engineering and scientific fields, and even some non-technical fields. Data stored in HDF5 is used for a wide range of applications, from computational fluid dynamics to film making.
Main features:
- Parallel HDF5 - Information on installing and using Parallel HDF5
- SZIP Compression - Information about SZIP Compression in HDF5
- Thread Safe HDF5 - Information on thread-safe capabilities of HDF5 and how to install
- The High Level HDF5 APIs, previously distributed separately, are now distributed as part of the main HDF5 Library:
- High Level HDF5 APIs - Information on installing and using the High Level HDF5 APIs
Applications:
- HDF Java Products - HDF4/HDF5 Java interfaces and viewer, HDFView.
- HDF Web-browser Plug-in - The HDF Web-browser plug-in is a windowed browser plug-in that is launched from a web browser to display HDF4 and HDF5 files.
- netCDF-4 - The NCSA and NetCDF groups are collaborating on a version of NetCDF built on top of HDF5.
- HDF5 XML Information Page - DTD and tools for using HDF5 with XML
- HDF5 WRF I/O Module - I/O module that reads HDF5 datasets for the Weather Research and Forecasting Model
- HDF5 Mesh API (prototype) - API for storing and retrieving structured and unstructured mesh data
Enhancements:
- The default Fortran was switched to G95 when using GCC.
- The autoconf build tools were updated. Fortran interfaces were added for the Image, Table, and Lite APIs.
- A Dimension Scale API (H5DS) was added.
- FreeBSD is now supported on AMD64 with GNU C and Fortran compilers.
- Support for sequential and parallel libraries was added for Intel 64 Linux clusters.
- Several bugs with writing fill values for datasets that have a variable-length datatype or component datatype were fixed.
Quasar Accounting 1.4.7
Quasar is a full function, stand-alone business accounting package more>>
Or, you may elect to purchase our commercial license for a nominal fee. To ensure timely access to support you will need to purchase one of our support packages.
With Quasar it is extremely easy to set up remote access to multiple servers from multiple workstations. You can run Quasar on both Windows and/or Linux on the same network. For example, you can maintain a Linux server and access the data from a Windows workstation.
Quasar Retail contains all of the features available in Quasar Accounting plus it contains the Quasar Point-of-Sale driver which allows Quasar Accounting to communicate with the Quasar Point-of-Sale application. Quasar Retail is only available with our commercial license.
In a mission critical environment such as retail you will need to purchase one of our support packages for timely access to support . Resellers and customers who wish a copy of the Quasar Retail source code can obtain it by purchasing annual source code access.
Main features:
international ready
- Quasars new international ready features include the ability to define your monetary symbol, monetary format, date format, time format, number format and percentage format. Any and all text can be translated or changed to suit your specific requirements. In addition Quasar has a standard Canadian format and a standard United States format.
graphical user interface
- Quasar is a new product designed with a graphical interface. It is not an older text based package with a graphical interface add-on. It was designed using Qt which is the same library used for the KDE user interface and other Linux projects. For more information on Qt 3.0 please see the Trolltech web page at http://www.trolltech.com.
fast/easy data entry
- The Quasar main window, icons, menus, lookups, and search functions have all been designed with you, the user, in mind. Screens were kept simple with instant access to advanced functions and superior access to supporting data.
quick error correction
- Existing transactions are easy to find and easy to edit. Quasar has a find transaction screen that allows you to find a transaction very quickly using a variety of selection criteria.
backup and restore
- Backup your company to a backup file and restore it as and when the need arises.
recurring transactions
- Define recurring transactions for recurring journal entries, recurring cheques, recurring customer invoices, recurring vendor invoices and recurring vendor payments.
on-line help
- On-line help is available for every screen. A table of contents provides the ability to move around and view several help screens in succession.
preferences
- Set your style, font and color preferences.
multiple companies
- Create and manage multiple companies within the same application.
import data
- Quasar makes maximum use of XML files for importing. Using XML files you can import data such as the chart of accounts, inventory, customer information, vendor information, opening balances, journal entries, purchase orders and packing slips. new data imports
drill down feature
- From most Quasar information screens you can drill down and view the detail of the actual transactions. This will be limited only by the user security access.
mailing labels
- Print mailing labels for customers, vendors, employees and personal acquaintances. Select labels from one of our supported forms.
work shift control
- Every transaction includes date, time, work station, employee and shift. After a each work shift, you can close the shift, complete cash reconciliations, do tender adjustments and report on the results.
MySpace Data Mining Tools 1.1
MySpace Data Mining Tools are a set of Java classes designed to mine information from MySpace profile and blog pages. more>>
Enhancements:
- Direct database connectivity via JDBC was implemented for data storage.
- A basic user profile class was created to handle both user data compression and database access.
- Minor bugs were fixed for some of the raw data accessing routines.
GData Java Client 1.13.0
GData Java Client provides a library and source code that make it easy to access data through Google Data APIs. more>>
The Google data APIs ("GData" for short) provide a simple standard protocol for reading and writing data on the web. GData combines common XML-based syndication formats (Atom and RSS) with a feed-publishing system based on the Atom publishing protocol, plus some extensions for handling queries.
Google also provides a set of client libraries for interacting with GData-enabled services, in a variety of programming languages. Using these libraries, you can construct GData requests, send them to a service, and receive responses.
Data::Locations 5.4
Data::Locations is a virtual file manager which allows to read/write data to and from virtual files. more>>
Did you already encounter the problem that you had to produce some data in a particular order, but that some piece of the data was still unavailable at the point in the sequence where it belonged and where it should have been produced?
Did you also have to resort to cumbersome and tedious measures such as storing the first and the last part of your data separately, then producing the missing middle part, and finally putting it all together?
In this simple case, involving only one deferred insertion, you might still put up with this solution.
But if there is more than one deferred insertion, requiring the handling of many fragments of data, you will probably get annoyed and frustrated.
You might even have to struggle with limitations of the file system of your operating system, or handling so many files might considerably slow down your application due to excessive file input/output.
And if you dont know exactly beforehand how many deferred insertions there will be (if this depends dynamically on the data being processed), and/or if the pieces of data you need to insert need additional (nested) insertions themselves, things will get really tricky, messy and troublesome.
In such a case you might wonder if there wasnt an elegant solution to this problem.
This is where the "Data::Locations" module comes in: It handles such insertion points automatically for you, no matter how many and how deeply nested, purely in memory, requiring no (inherently slower) file input/output operations.
(The underlying operating system will automatically take care if the amount of data becomes too large to be handled fully in memory, though, by swapping out unneeded parts.)
Moreover, it also allows you to insert the same fragment of data into SEVERAL different places.
This increases space efficiency because the same data is stored in memory only once, but used multiple times.
Potential infinite recursion loops are detected automatically and refused.
In order to better understand the underlying concept, think of "Data::Locations" as virtual files with almost random access: You can write data to them, you can say "reserve some space here which I will fill in later", and continue writing data.
And you can of course also read from these virtual files, at any time, in order to see the data that a given virtual file currently contains.
When you are finished filling in all the different parts of your virtual file, you can write out its contents in flattened form to a physical, real file this time, or process it otherwise (purely in memory, if you wish).
You can also think of "Data::Locations" as bubbles and bubbles inside of other bubbles. You can inflate these bubbles in any arbitrary order you like through a straw (i.e., the bubbles object reference).
Note that this module handles your data completely transparently, which means that you can use it equally well for text AND binary data.
You might also be interested in knowing that this module and its concept have already been heavily used in the automatic code generation of large software projects.
Enhancements:
- Fixed test file "02___refcount.t" to auto-adjust the offset dealing with self-ties not incrementing
- the refcount in some Perl versions.
- Added a warning to "Makefile.PL" that Perl versions including and between v5.6.1 and v5.7.0 are not fully supported (test file "11_______dump.t" dumps core).
MillScript-Excel 0.1
MillScript-Excel project is a Java library for reading and writing Excel spreadsheets. more>>
Performance Co-Pilot 2.5.0
Performance Co-Pilot is a performance monitoring toolkit and API. more>>
The services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.
Safe and SafeDesktop 2.2.6
Safe and SafeDesktop project are created so that a user need not remember all her login names and passwords. more>>
What is Safe?
Nowadays, every person is forced to remember lots of sensitive data to interact with machines during daily life. For instance, automatic teller machines ask for numerical passwords and email accounts are protected by using loginnames and passwords. For many good reasons passwords should be difficult to guess and every password should be used for one account only. In reality, this makes it quite difficult for the average person to remember all the different passwords. Hence, people tend to choose easy to remember passwords and many persons re-use their passwords in such a way that the same password is used for many accounts. Even worse, it is quite common to write down passwords and stick the note to a screen frame. All these facilitations of remembrance lower the burden for hackers to get access to sensitive data and abuse computers.
The idea behind Safe is that a user must not remember all her loginnames and passwords. Instead, the user utilizes her cell phone to store sensitive data in an encrypted way. Only one root password is required to be remembered to get access to the data.
This concept works pretty well, because nowadays, cell phones are ubiquitous. Usually, cell phone owners carry the phones in their pocket regardless where they are going. So, running Safe on a cell phone means that passwords have no longer be to remembered and can be chosen as difficult as it can be. The only requirement is that the cell phone in question supports J2ME applications.
What is SafeDesktop?
SafeDesktop provides the same features as Safe does but it runs on desktop machines. Java is also used for the implementation of SafeDesktop. This allows SafeDesktop to be executed on almost all modern desktop operating systems (e.g., Microsoft Windows, Linux).
A synchronization mechanism is part of SafeDesktop to keep the data synchronized between Safe and SafeDesktop.
How does it work?
First, a MD5 hash of the root password is stored and compared with the users input, that is requested at applications startup. If the hash of the users input is equal with the stored hash, the user input is used as key to decrypt the data.
Second, a IDEA cipher is used in CBC mode (of operation) to store data in an encrypted way. The password that the user entered at startup, is used as a key for the IDEA cipher.
Version restrictions:
- Safe and SafeDesktop have their limits. The limits are inherent - they came from the IDEA cipher, the hardware, the operating system and all the other parts that are used as a blackbox.
- But remember, there are things you can do to push the limits: review the source code of Safe and SafeDesktop. Even more security relevant: Select a difficult to remember, long and random root password. With Safe and SafeDesktop you have only to remember one password, so, make it difficult for the opposer to get access to your sensitive data.
Enhancements:
- An IPv6 problem has been fixed (no exception will be thrown when the machine uses IPv6).
- Exception handling has been improved (error messages provide hints as to what went wrong).
- A minor bug has been fixed (mainly how and when Alerts are shown).
Class::DataStore 0.07
Class::DataStore is a Perl module for generic OO data storage/retrieval. more>>
SYNOPSIS
my %values = ( one => 1, two => 2 );
my $store = Class::DataStore->new( %values );
# using get/set methods
$store->set( three, 3 );
my $three = $store->get( three );
# using AUTOLOAD method
$store->four( 4 );
my $four = $store->four;
my @four = $store->four; # returns a list
my $exists = $store->exists( three ); # $exists = 1
my $data_hashref = $store->dump;
$store->clear;
Class::DataStore implements a simple storage system for object data. This data can be accessed via get/set methods and AUTOLOAD. AUTOLOAD calls are not added to the symbol table, so using get/set will be faster. Using AUTOLOAD also means that you will not be able to store data with a key that is already used by a instance method, such as "get" or "exists".
This module was written originally as part of a website framework that was used for the Democratic National Committee website in 2004. Some of the implementations here, such as get() optionally returning a list if called in array context, reflect the way this module was originally used for building web applications.
Class::DataStore is most useful when subclassed. To preserve the AUTOLOAD functionality, be sure to add the following when setting up the subclass:
use base Class::DataStore;
*AUTOLOAD = &Class::DataStore::AUTOLOAD;
This module is also a useful add-on for modules that need quick and simple data storage, e.g. to store configuration data:
$self->{_config} = Class::Datastore->new( $config_data );
sub config { return $_[0]->{_config}; }
my $server = $self->config->server;
my $sender = $self->config->get( sender );
Xephyrus Data Structures Tag Library 1.5
Xephyrus Data Structures Tag Library is a tag library to provide access to common data-structures. more>>
Enhancements:
- The library was polished up.
- Several improvements were made and a few bugs were fixed.
- This version is aimed at Java 5 and JSP 2.0.
Google Data Objective-C Client 1.1.0
Google Data Objective-C Client provides a framework and source code that make it easy to access data through Google Data APIs. more>>
The Google data APIs provide a simple protocol for reading and writing data on the web. Many Google services provide a Google data API.
Each of the following Google services provides a Google data API:
- Base
- Blogger
- Calendar
- Spreadsheets
- Picasa Web Albums
- Notebook
Additional services with Google data APIs that are not yet supported by the Objective-C Client Library:
- Code Search
- Google Apps Provisioning
LastPass Password Manager (beta) 1.36
LastPass is the last password you will ever need. It allows you to: Create strong passwords, knowing you only have to remember one. Log into your favorite sites with a single click. Only fill forms out once. Access and manage your data from multiple computers seamlessly. Share logins with friends and let others share logins with you. Supports IE & Firefox, Windows, Mac and Linux more>>
LastPass Password Manager (beta) - LastPass is a free password manager that makes your web browsing easier and more secure and supports IE and Firefox, allows you to import from every major password storage vendor and export too, captures passwords that other managers wont including many AJAX forms, and allows you to make strong passwords easily.
LastPass is the last password you will ever need. It allows you to:
- Create strong passwords, knowing you only have to remember one.
- Easily fill in form data
- Log into your favorite sites with a single click
- Access and manage your data from multiple computers seamlessly
- Share logins with friends and let others share logins with you
- Supports IE as well, so if you switch browsers youre always in sync, as well as when you switch computers
- Supports importing passwords from other password managers such as Roboform, Keepass, PasswordSafe, MyPasswordSafe, Firefox and IEs built in password manager
- Exporting your data always available in plugin and website.
- In windows, helps you recover lost passwords stored on your computer
- Capture passwords that other password managers will not capture like those done in AJAX logins, and multi-step logins like Bank Of America, and frustrating sites like ING bank.
- Make moving to a new computer or using multiple computers much easier
- Works with any platform that has Firefox plus IE on Windows
- Has a USB/Thumb drive portable version for Windows, Mac and Linux
- http://m.lastpass.com for mobile access
Your sensitive data is encrypted locally with AES, then uploaded to allow syncing with other computers or browsers. IE is also supported as well as
Enhancements:
Version 1.36
Save any form support
Version 1.34
Improved homepage, bug fixes
Version 1.33
Built-in fast homepage, bug fixes
Version 1.32
French, Hebrew, bug fixes with basic auth, Pocket for Mac and Linux
Version 1.31
Local Site Search, HotKeys, Secure Notes
System Requirements:233 MHz, 128MB ram<<less