Free advance stock tracker 0.2.8 software for linux

Advanced Stock Tracking System provides the individual investor with a powerful set of tools for making financial decisions and tracking securities.

This project features a portfolio with dividend tracking, worksheet to keep track of prospects, a stock comparison utility, a search engine for the stock market and an alert engine to email you about key events in your securities.

Asset Tracker provides an inventory management system.
Asset Tracker is an inventory management system that allows flexibility in choosing column names and types and contains a plugin system, an access control system, filtering and sorting in the list view, and bookmarkable pages and views.
Main features:
- Suitable for tracking any kind of physical object.
You can create multiple asset databases containing any information you wish to keep track of. Some examples: put all your IT infrastructure into the database, or if you are a building manager, put all your facilities equipment in the database.
- Designed with flexibility in mind.
This means that you can add or remove any columns from the database at any time. Each column can have whatever name youd like to give it. Currently, columns can contain numbers, dates, free-form text, or drop-down lists (to be used if there are a range of valid items that could go into that field).
- Contains a plugin system
This allows you to add any custom functionality that youd like. A plugin is included with the default distribution to enable a connection with RT2 and RT3 databases (I have verified that it works with RT3, but have not updated the documentation to reflect this yet). RT is Request Tracker, an incident management and response system available from http://www.bestpractical.com/rt/. If you have created a plugin youd like to share with everyone, please email me at assettracker@yoderhome.com so I can upload your plugin to the sourceforge download area.
- Contains an access control system
This allows you to decide who can view, add, modify, and delete items from any of the tables. The access control system is administered from within Asset Tracker.
- Comprehensive filters and sorting in the list view
This allows you to choose only to see the data you want to see. For example, a facilities manager might want to see items that were installed 1 year ago, and whose expected lifetime is 365 days. This is easy to manage with the filtering interface. It becomes particularly powerful when coupled with external database connections such as RT2 (see above). If a particular asset keeps generating repair orders within RT2, there will be a high number of RT2 links associated with the asset; this can easily be identified using the sorting and filtering interface.
- All asset list views are bookmarkable
If you create a view with a particular sort order and filters, you can bookmark the search and return to it easily (of course, if the contents of the database change, the view will reflect the updated database). In fact, all operations within Asset Tracker are handled this way, so you can easily bring up any previous page or view.

ttrk (tektracker) is a console MIDI sequencer with a tracker-style step editor.I was annoyed by the bad step editors found on pretty much all MIDI sequencers I could find, and since I was big fan of the tracker interface, I used the user interface ideas behind a tracker in my design.
There are five main goals for creating ttrk:
1. Tracker-style step editor, think ScreamTracker3.
2. Pattern based sequencer per track, more like Sonic Foundrys ACID.
3. Big, accessable track mute buttons, think Alesis MMT8.
4. Realtime editing, never need to push stop.
5. All functions directly accessable from the keyboard for rapid editing.
Main features:
- Tracker-style step editor.
- 256 channels, each with 256 patterns.
- Songs up to 4096 patterns long.
- Pattern copy and paste.
- Sync to external MIDI.
- Sends MIDI sync.
- Convenient channel mute buttons for live play.

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

TimeTracker is an application loosely based on TimeKeeper, a Windows application used to track the time you spent on a task.

Being a Linux user and not willing to install Wine, I decided to hack my own version.