Free royal bank software for linux

Main features:
Scheduled Transactions
- You can now create recurring transactions, including automatic reminders when a transaction is due, the ability to postpone a scheduled transaction without canceling it, and the ability to specify only a limited number of transactions.
Mortgage & Loan Repayment Druid
- A guided dialogue for setting up loan payments as scheduled transactions.
Small Business Accounting Features
- Simplify managing a small business with Customer and Vendor tracking, Invoicing and Bill Payment, and Tax and Billing Terms.
OFX Import
- GnuCash is the first free software application to support the Open Financial Exchange protocol that many banks and financial services are starting to use.
HBCI Support
- GnuCash is the first free software application to support the German Home Banking Computer Information protocol, allowing German users to perform statement download and initiate bank transfers and direct debits.
Improved Import Transaction Matching
- The development of OFX and HBCI support has also resulted in an improved transaction matching system that more accurately recognizes duplicate transactions during file import.
New User Manual and Help
- A new help subsystem that focuses on how to do tasks is now available, in addition to a Tutorial and Concepts guide that gives the user background information on accounting principles and how they are reflected in GnuCash.
New Multi-Currency Transaction Handling
- GnuCash no longer requires separate currency exchange accounts to handle multiple currency transfers. Transactions can be made directly between accounts denominated in different currencies.
Redesigned Menus
- The GnuCash menus have been redesigned to conform more with the new GNOME Human Interface Guidelines.

Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files.

Puppets simple declarative specification language provides powerful classing abilities for drawing out the similarities between hosts while allowing them to be as specific as necessary, and it handles dependency and prerequisite relationships between objects clearly and explicitly.

Puppet is a system configuration tool. Puppet project has a library for managing the system, a language for specifying the configuration you want, and a set of clients and servers for communicating the configuration and other information.

The library is entirely responsible for all action, and the language is entirely responsible for expressing configuration choices.

Everything is developed so that the language operations can take place centrally on a single server (or bank of servers), and all library operations will take place on each individual client. Thus, there is a clear demarcation between language operations and library operations, as this document will mention.

Setup

The vast majority of Puppet architectures will look like a star, with a central server running puppetmasterd, and each client node running puppetd, contacting that central server.

Your central manifest, which contains the configuration for all of your nodes, needs to be on the central server, most likely at /etc/puppet/manifests/site.pp.

Start the puppetmasterd daemon, and then tell your clients to contact that server by specifying -s < servername > as arguments to puppetd, replacing "< servername >" with the name of the server. Alternatively, puppetd defaults to looking for a server named "puppet", so you can just create a CNAME for your server, so that it answers to "puppet".

It is a good idea to run both the server and client in verbose mode, enabled with the -v flag, until you are sure everything is working. As each new client connects, you will need to run puppetca --list to list the certificates waiting to be signed, and then puppetca --sign < name >, replacing "< name >" with the name of the client whose certificate you want to sign. You can turn on autosigning by creating /etc/puppet/autosign.conf and put the hosts, domains, or IP addresses or ranges that you want to sign in there.

ATutor is an Open Source Web-based Learning Content Management System (LCMS) designed with accessibility and adaptability in mind.
Administrators can install or update ATutor in minutes, and develop custom templates to give ATutor a new look. Educators can quickly assemble, package, and redistribute Web-based instructional content, easily retrieve and import prepackaged content, and conduct their courses online. Students learn in an adaptive learning environment.
ATutor is the first fully inclusive LCMS, complying with the W3C WCAG 1.0 accessibility specifications at the AA+ level, allowing access to all potential learners, instructors, and administrators, including those with disabilities who may be accessing the system using assistive technologies. Conformance with W3C XHTML 1.0 specifications ensures that ATutor is presented consistently in any standards compliant technology.
ATutor has also adopted the IMS/SCORM Content Packaging specifications, allowing content developers to create reusable content that can be swapped between different e-learning systems. Content created in other IMS or SCORM comformant systems can be imported into ATutor, and visa versa. ATutor also includes a SCORM 1.2 Runtime Environment (LMS RTE3) for playing and managing SCORM based Sharable Content Objects (SCOs).
ATutors base in Open Source technology makes it a cost effective tool for both small and large organizations presenting their instructional materials on the Web, or delivering fully independent online courses. Comprehensive help is available through the ATutor HowTo documentation, through a number of support services, or through the public forums, and full language support is available through the ATutor Translation Site.
ATutor 1.5.4 Demo:
http://www.atutor.ca/atutor/demo.php
Main features:
- Forum Upgrades: Shared forums for communication across courses. Create communities around groups of course forums, or around an entire ATutor course server. Alumi participation in course forums. Subscribe to shared forums or course forums, or subscribe to specific topic threads to receive messages by email. Quickly access current forum messages through the Forum Posts menu module.
- File Manager Upgrades: Create new text and html files, move individual files or batches of files, and use the file manager while editing ATutor content pages. Use the Insert function to create links to files within course content pages and test questions.
- Enrollment Manager Overhaul: Create, import, and export course enrollment lists, and manage enrolled students or alumni. New tabbed display for managing student information, managing course lists, managing roles and privileges, as well as creating and managing groups.
- Language Overhaul: Language management has been completely re-designed. Translate, import, and export language from within an ATutor installation. Support for the UTF-8 character set. ATutor is avalable in more than 30 languages.
- Backup Manager: Administrator and Instructor Backup Manager. Create master copies of courses. Manage multiple backups per course and restore only material you specify into existing and newly created courses.
- Question Bank: Create tests by adding questions to, and retrieving questions from, a test item respository.
- Test/Survey Manager Upgrade: New ability to create image based test items, arrange multiple choice questions vertically or horizontally, assign tests to a class, to groups, or to individual students.
- Theme Manager: Easily copy, import, and export ATutor themes.
- RSS Feeds: Syndicate course announcements with RSS 1.0, or RSS 2.0 feeds, to display them on remote Web sites.
- New Feedback and Error Handling: Redesigned, modular, user feedback system. Improved logging, tracking, and presentation of system errors for debugging and troubleshooting ATutor installations.
- Embed ACollab: Embed ACollab into ATutor, or open it in a new window to participate in group activities.
- System Announcements: Administrators can send email announcements to all instructors and/or students registered on an ATutor system.
- Easy Enrollment: Students can now enroll in courses through the Browse Courses screen.

CK-ERP is an accounting/ERP/CRM system that runs on top of eGroupWare.

CK-ERP project provides admin, contact management, customer relationship, customer self service, vendor relationship, ledger, bank reconciliation, inventory, service, AR, AP, SO, PO, quotation, POS for cashiers, POS for managers, HR, staff self service, and payroll functions.

Whats New in This Release:

1.Connector for MirrorMed
2.Connector for ClearHealth
3.Connector for OpenEMR
4.Connector for osCMax
5.Connector for XOOPS updated to provide group-module ACL control
6.locale-aware monetary figure printing
7.Improvement to sample cheque
8.Bug fixes to rectify,
- Error when searching for untranslated phrases (aTutor)
- Error when converting TIPs into translated phrases
- orphaned temp tables
- wrong official quotation (with tax) when bulk despatched
- error in ck-bank control report (suspense item total)
- error implementing ck-bank bulk update

GPS Tracker project allows someone to track a GPS enabled cell phone using Google maps. For this project I used a Motorola i355 cell phone on the Sprint/Nextel network.
You need to have a data plan so that you can make updates to your website from the cellphone. Please read the ReadMe.txt file in the download for installation instructions. I hope you enjoy the project. If you have any questions, feel free ask them in the forum.
There are two projects available. The first project is built with .NET and Microsoft SQL Server. The second project is built with PHP and MySQL. If you have any suggestions, please feel free to let me know. Both projects use java (J2ME) on the phone.
How It Works:
None of the code for this project is very difficult, but it does span a number of tiers and languages which may be unfamiliar to some. Figure 1 shows the data flow from phone to Google map.
Phone
Lets start with the code on the phone. This app is written in java using Java 2 Micro Edition (J2ME). Java is very similar to C#. As you look through the code, the only thing that might confuse a C# coder is the vector. A java vector is pretty much a C# ArrayList, a dynamic array. There are 2 classes in the app, LBSMidlet7 and Qworker. A midlet is an app that runs on cell phones. Take a look at the class definition. It extends the MIDlet class and implements a LocationListener interface. That means that we need to put all the method definitions of that interface into our class. Well get to that in a bit, right now lets look at the constructor.
We do 2 things in the constructor. We create a QWorker object and pass it "this" and the website that we will be uploading to. The getAppProperty method gets attributes out of the JAD file. Open the JAD file in your favorite text editor and there youll see the webpage that youll be sending GPS data to. Notice how were passing "this" to the GWorker object? Thats the LBSMidlet7 object. Take a quick look at the QWorker class, it extends the Thread class. Thats why we call worker.start() in the LBSMidlet7 constructor. We want to start our worker thread.
When you start a thread, what you are doing is creating an object and then running that objects run() method. Take a look at the run method. It has an endless loop and in the loop the first thing it does is call queue.wait(). Look at the definition of the queue. The queue is an abstract data type (ADT), it just like a queue at a bank, enter the queue at the back of the line and leave the queue when you get to the front of the line. Look at the definition of the queue, its our vector (dynamic array). When you call wait() on an object within a class that extends the Thread class, it puts that object to sleep. Think about that a little. When we hit that line, our QWorker object is now waiting... Whats it waiting for? Well get to that in a minute. Before we do that, take a look at the synchronized keyword. Notice that its wrapping the queue. What that does is it puts a lock on the queue and tells all other processes not to touch the queue until that little block of code is done with it.
Ok, so now weve started a worker thread and put it to sleep. Lets now go back to the LBSMidlet7 class and take a look at the startApp() method. In the lifecycle of a midlet, the constructor is called once and then the startApp() method is called next. In fact it can be called several times, like for instance when you close a flip phone and then open it again. What happens is that the app is suspended and when you flip the phone open again, startApp() is called again. In startApp(), we get our display and then we create a LocationProvider if one hasnt already been created and we create another thread... Why are we creating all these threads? Good question. When a midlet (app) is suspended, the backgroud threads that are created keep running. That allows us to get our GPS data and send it to our webserver while we do other important stuff, like make phone calls.
The LocationProvider is what gets our GPS data. First we create a criteria, were using the default, but you can set stuff like accuracy, response time etc. Next we create our Location Listener. Its pretty much just what it sounds like. Here you can set the interval for how often you want to get GPS data. Its currently set to 60 which is in seconds. When data comes in, the locationUpdated() method is called. This is another one of the required methods in the LocationListener interface. Here we create yet another thread and call getLocation(). The getLocation() method gets the GPS coordinates, creates a queryString which we will send to the web server a little later and then calls worker.addToQueue in the QWorker class.
Lets go back over to the QWorker class and see what happens in that method. It add the queryString to the queue and then calls queue.notify(). Guess what queue.notify() does? It wakes up our sleeping QWorker thread and tells it to get to work! Notice that our calls to the queue are once again wrapped in a synchronized block. Please practice safe threading... When notify() is called on a thread, what it does is go back to the run() method and execute the next line of code right after where we told the queue to wait(). So now we are just about ready to send the GPS data to the web server. We have a couple of interesting lines of code there. First we call peekInQueue() which gets the queryString out of the queue but leaves it there for now. Then it sends the queryString to the getUrl method which attempts to send the queryString to our web server. If its successful, we can remove the queryString from the queue. If not, we leave the queryString in the queue and try to send it to the webserver again later.
Why in the world do we have this complicated queue here? Im glad you asked. There may be times when you are receiving GPS data but are not actually in an area that has a cell phone connection. If we dont have a cell phone connection, we cant send our GPS data to our web server. So we stick our queryString in our queue and wait until we get back into an area with cell phone connectability. Can you hear me now?
Well, weve spent a pretty fair bit of time explaining the phone code. Its a little complicated but its important to know whats going on if you want to take the code and make modifications to it to suit your needs. Heres a good article on the Sun website to let you know about more capabilities of the Location Based Services API. Right about now, our queryString should be arriving at our website, lets catch up to it and see what happens.
Enhancements:
- Added comments to code

Barcode Writer in Pure Postscript is an award-winning open source project, as used by NASA, that facilitates the printing of all major barcode symbologies entirely within level 2 PostScript.
Hence the process of generating a printed barcode representing a given input is performed entirely within the printer (or print system) so that it is no longer the responsibility of your application or a library.
There is no need for any barcode fonts and the flexibility gained by using direct PostScript allows you to avoid re-implementing barcode generator code, or migrating to new libraries, whenever your project language needs change.
Barcode Writer in Pure Postscript project makes including any barcode within a PostScript document as simple as inserting the following directive:
(1-86074-271) (includetext) isbn barcode
The project generates all of the major types of one-dimensional barcode supported by the vast majority of barcode scanners.
The current list of supported symbologies includes: EAN-13, EAN-8, UPC-A, UPC-E, EAN-5 & EAN-2 (EAN/UPC add-ons), ISBN (including ISBN-13), Code 128 (A, B & C, including EAN-128), Code 39 Extended, Code 93 Extended, Interleaved 2 of 5 (including ITF-14), Code 2 of 5, Codabar, MSI, Plessey, PostNet, Royal Mail (RM4SCC), FIM symbols.
This list is growing all the time. If it doesnt contain the format you are looking for then make a request via the mailing list and check back soon.
Since this resource is written in PostScript and interpretted within the virtual machine of a printer it is compatible with virtually any operating system and hardware platform, for example Windows 95/XP on i386, Mac OS X/Linux on Power PC, Solaris on SPARC, and OpenVMS on Alpha AXP.
Enhancements:
- Support for the MaxiCode 2D barcode was added.