MobileRead Forums - View Single Post - Why PalmSource May Be Right About Multitasking

surur · 06-25-2005, 10:45 PM

I noted an interesting fact which Dianne alluded to. It will be possible, under cobalt, to write the whole app (including the GUI) to run as a thread in the background. If this is simple, it would save a programmer a lot of work in the other parts of the program to save state properly and enable messaging between the parts of the program.

Could this be a way to shoe-horn multi-tasking into Cobalt for ALL apps, by hook or by crook?

BTW, I still have not see anybody address the disadvantages of Saved State vs multi-tasking yet. Isn't this what the whole thread is all about?

Surur

06-25-2005, 10:45 PM	#19
surur Enthusiast Posts: 30 Karma: 2258 Join Date: Jun 2005 Device: Loox 720	I noted an interesting fact which Dianne alluded to. It will be possible, under cobalt, to write the whole app (including the GUI) to run as a thread in the background. If this is simple, it would save a programmer a lot of work in the other parts of the program to save state properly and enable messaging between the parts of the program. Could this be a way to shoe-horn multi-tasking into Cobalt for ALL apps, by hook or by crook? BTW, I still have not see anybody address the disadvantages of Saved State vs multi-tasking yet. Isn't this what the whole thread is all about? Surur