Linked by Thom Holwerda on Mon 20th Mar 2006 23:07 UTC, submitted by Tako Lansbergen
Studio33 has released part II [part I] in its series of articles looking at the current state of Haiku. "In the previous part I talked about the achievements of the Haiku Team since the project was first started, this time I will go deeper into the work that has been done lately and which parts need serious attention in the coming months." Screenshots o'plenty, boys and girls.
Thread beginning with comment 106445
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
underthebridge wrote:
> If you want your old BeOS apps, STICK TO BEOS. Leave Haiku alone.
Actually, the whole reason the Haiku team is sticking with their original goal of binary compatibility is so you can indeed run your old BeOS apps on Haiku.
And, BTW, I think what alexorizor is implying is correct: if I want to run an app on one machine but have it display on a different machine, I want a simple GUI dialog box with checkboxes and text fields specifying which machine the program will run on, which machine it will display on, which user it will be running as on the remote machine, which user it will be displaying as on the local machine (with a help box describing how the permission issues are handled), and big "run" and "stop" buttons at the bottom. And maybe color-coding so I can immediately tell when a window is from an app running on a remote machine. The worst thing about X11 is fiddling with its config files trying to get it to do what you want. And it looks like programming for it is no picnic either.