Though I am programming on BeOS since 1999, only in recent years I have slowly become more comfortable with various multithreading related issues in my programs. So I thought I'd like to share some of my experiences here for beginning programmers or programmers skeptical about multithreading. I hope to be extending this as a series of articles to help learn the benefits and pitfalls of multithreading. All with an emphasis on programming for the Haiku API.
Body: Following Deskbar redesign proposal is based on discussion in the 3D-Accelerated Haiku Desktop RFC comment thread. One problem that came up was that current menu designs do not support good organization.
Only ways to organize a cascading menu (or variant like Deskbar and Windows start menu) is to use subcategories and separator lines. One good thing about subcategories is that you have a short description (i.e., folder name) attached to the group of items in the category, but those items are hidden most of the time and inefficient to use.
Body: First of all, apologize me for my English, I know it not quite good but Im improving. I have posted before but they have been deleted (I dont know why).
Quality / Stability, Kernel I wish that Haiku before have been or sooner if possible BeOS clone. Have some security and quality features, i propose that this OS have a memory execution protection, just to make the life easier and secure, just to enforce to make best programming practices.
Body: One Desktop to Rule Them All For the purposes of the novice user, Tracker is Haiku. Many people don't even know -- or care -- what an operating system is. As I have said many times before, the average person just wants to get his work done. This makes Tracker's interface crucial to user productivity because it is the main way for someone to use the computer. Many different kinds of people use Tracker.
Thank you very much for showing your support for Haiku. A receipt for your donation has been sent to your mailbox.
Being a project comprised of volunteers that work on Haiku in their spare time, contributions like yours make a great difference in advancing our cause of creating a free operating system for all to use. Your donation will be put to good use.
We look forward for your continued support.
This document outlines the team structure of the Documentation Team. It will describe how the privileges and duties are distributed between the three main entities: Contributors, Members and the Coordinator. It will also describe how the advancement system works.
