Thanks for the response. I've tried to digest all you've said.
errol wrote:
Hello,
If you are using the current Gnome desktop environment you have set your system to login to a set user account and also start up an application. I have done this in the past to automatically run video projections for a theatre show.
Under the Gnome 3 desktop select System Settings then User Accounts. From there you can select which user account you want to use for automatic login.
Under Systems Tools then Startup Applications you can then add your application to be started when you login.
You may need to install some of these applications to set-up auto loading. Once this is done all should be easy and with out you needing to mess around with scripts
The first part worked great and I can login without the login screen, however I have seen many forums reference the Startup Applications, but I just can't find it. I believe it has to do with updating. I originally started with Ubuntu 10.04 using unity and now have 12.04 using Gnome, and I've heard that buntu just does not update well and becomes unstable after numerous upgrades.
Anyway after more research I found that Ubuntu isn't the right distribution for what I'm doing anyway. I need a real time operating system.
Paul Childs wrote:
You've got all the answer you need out of Errol,
I'd back up what he is saying. As GTK and your application is going to use a large amount of what is loaded by default I wouldn't stop the boot sequence but instead just disable whatever functionality you don't need. You can do this in Ubuntu, but if you have the time you might want to investigate setting up an OS that is more designed for customisation, e.g. Gentoo or Arch.
I looked at Gentoo and Arch and they have their merits, but I realized I need a real time operating system. My boss is willing to pay for Red Hat which I think will save time over using a free distribution. Also the drivers I need were tested in Red Hat which takes out some guess work.
Paul Childs wrote:
I've done a fair bit of instrumentation work; though probably not as much as yourself. Yes, it was a hatred for LabVIEW licencing practices that drove me to GTK and other things free & open source. I might be able to add a few pointers. Maybe some things will be new to you and useful.
I hate Labview as well, and not just the licensing. I don't like the design and the overhead is ridiculous. It uses c format strings so I started calling it C--
Paul Childs wrote:
* One of the good things about GTK is it is cross-platform in terms of software and hardware. If you write an application, there is a good chance that it will work on Windows, Linux or BSD as well as different architectures, e.g. x86, ARM or SPARC. If you are working in instrumentation this is very useful as you can readily transfer an app you have developed on your desktop to a microcontroller with a reduced instruction set. I recently bought a raspberry pi (a rather impressive $30 ARM microcomputer) and was able to port my software over to it seamlessly. I'd recommend it for tinkering around with (looks a lot cooler and more serious than using a laptop in a prototype system for showcasing your work).
This sounds incredible, and quite unbelievable actually. Could you maybe expand on this? Did this microcomputer use GTK+ to produce a user interface or for calculation with glib? I realized that the GTK+ portion of my code can be ported as is, which is the reason I've focused on learning GTK+ instead of Win Api or some other api in the first place. Most of the C calls are the same, but the threading is a little different, and I'll be fighting the drivers for awhile.
Paul Childs wrote:
* There is a project 'comedi' looking at providing drivers for a lot of commercial DAQ cards etc. If they don't have the driver you're after, get in contact with them. They might be able to help and your experiences would provide valuable feedback for the project. Comedi requires itself to be compiled into the kernel so it might be something to think of earlier rather than later. (though if you go down the gentoo path recompiling the kernel is an everyday task; bit more daunting as an Ubuntu user).
I looked at their website, but could not find the card I'm using. I'll try contacting them though.
Paul Childs wrote:
* Gtk builds upon glib to provide cross-platform support. Try to exploit the glib function calls as much as possible as every included header you can eliminate will make your application more portable, stable and future-proof. (e.g. stdio.h, stdlib.h and string.h are all unnecessary when using glib)
I've seen many references to these functions in the tutorials, but always used the functions in the standard c library. I had assumed that anywhere I would use GTK+, I would be using a compiler with the standard C library. Could you maybe give an example of an instance that you could use glib but now the standard C library?