Probably the best resource for a description of the inner workings of BFS is the book "Practical File System Design with the Be File System" written by Dominic Giampaolo and published by Morgan Kaufmann Publishers. Although that book is out of -print, it's available as a free download from -Dominic's web site. +print, it's available at the Haiku web site. -
If you prefer to see how it works in code, please have a look at Haiku's BFS -implementation - you can find that in the SVN repository under -src/add-ons/kernel/file_systems/bfs/. This code is not mature yet, but is considered -to be fairly stable. +
If you prefer to see how it works in code, please have a look at Haiku's BFS +implementation.
If you are interested in the Haiku file system API, please refer to its documentation as part of the Haiku book. diff --git a/docs/develop/kits/app/usecases/BClipboardUseCases.html b/docs/develop/kits/app/usecases/BClipboardUseCases.html index 2322c88871..0baf129394 100644 --- a/docs/develop/kits/app/usecases/BClipboardUseCases.html +++ b/docs/develop/kits/app/usecases/BClipboardUseCases.html @@ -23,7 +23,7 @@ The document has the following sections:
The BClipboard class provides an interface to a named, system-wide, temporary storage resource. Access to the system clipboard is provided by the be_clipboard variable provided by a BApplication object (or by constructing a clipboard with the name "system"). The best source of information for the BClipboard interface can be found -here in the Be Book. +here in the Be Book.
The BCursor class is a simple class used to represent a mouse cursor as an object instead of an array of pixel data. The best source of information for the BCursor interface can be found -here in the Be Book. +here in the Be Book.
Construction 1: The first BCursor constructor requires a pointer to the pixel data. The format for the pixel data is described -here in the Be Book. +here in the Be Book. This pixel data is used to initialize the BCursor, but BCursor does not take ownership of the data, therefore you are responsible for freeing the memory after construction.
Construction 2: The second BCursor constructor requires a BMessage as an archive, however BCursor does not currently support archiving. Do not use this constructor.
The BMessageFilter class is a simple class for processing incoming BMessage's before they are dispatched to a BLooper. The best source of information for the BMessageFilter interface can be found -here in the Be Book. +here in the Be Book.
The BMessageQueue class is a simple class for managing a queue of BMessages. The best source of information for the BMessageQueue interface can be found -here in the Be Book. +here in the Be Book.
The BPropertyInfo class is a simple class for describing the scripting interface which a BHandler provides. It makes implementing the ResolveSpecifier() hook function easier to implement. One source of information for the BPropertyInfo interface can be found -here in the Be Book. +here in the Be Book. Unfortunately, details of some changes to this interface introduced in BeOS 4 does not seem to have made it into the BeBook. For the latest, refer to the -PropertyInfo.h header file or the -BeOS 4 Developer Release Notes. +PropertyInfo.h header file or the +BeOS 4 Developer Release Notes.
The BDeskbar class is a simple class for getting information from the deskbar and for modifying it from your application. The best source of source of information for the BDeskbar interface can be found -here in the Be Book. +here in the Be Book.
Add Item 1: The AddItem() member function can be used to take a passed in pointer to a BView and send it to the deskbar for inclusion in its shelf. This BView must be archivable and must be exported by the application (for details on how to do this, -this article +this article may help). The item will be added and the id of the new item will be passed back to the caller through a pointer to an int32.
Internally, the BDeskbar uses a BMessenger to communicate with the deskbar itself. -The source code from the OpenTracker project will be used as a reference for this effort. -You can find the deskbar source code here:
- --http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/opentracker/opentracker/deskbar/ -- -
Specifically, the code which handles communicating with the BDeskbar class can be found -here:
- --http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/opentracker/opentracker/deskbar/BarWindow.cpp?rev=1.2&content-type=text/vnd.viewcvs-markup -- -
The following describes the messages used to communicate between BDeskbar and the deskbar -itself.
+Internally, the BDeskbar uses a BMessenger to communicate with the deskbar itself.
+The code which handles communicating with the BDeskbar is described below.
Note that in both cases, the deskbar does not set the what code of the reply. Checking the source code for -TBarWindow::AddItem() +TBarWindow::AddItem() confirms this. @@ -200,7 +185,7 @@ theMsg.AddBool("exists", IDorNameExists()); // This is a true/false value whi
Note that the deskbar does not set the what code of the reply. Checking the source code for -TBarWindow::ItemExists() +TBarWindow::ItemExists() confirms this.
@@ -227,7 +212,7 @@ theMsg.AddInt32("id", theID); // This is the id corresponding to the namNote that the deskbar does not set the what code of the reply. Checking the source code for -TBarWindow::ItemInfo() +TBarWindow::ItemInfo() confirms this.
diff --git a/docs/develop/kits/interface/usecases/BPolygonUseCases.html b/docs/develop/kits/interface/usecases/BPolygonUseCases.html index 826c138876..211b2ac41a 100644 --- a/docs/develop/kits/interface/usecases/BPolygonUseCases.html +++ b/docs/develop/kits/interface/usecases/BPolygonUseCases.html @@ -23,8 +23,8 @@ The document has the following sections:The BPolygon class is used to hold information about a shape composed of a series of straight lines (ie a polygon). On its own, it just describes the shape and can only be drawn by passing -it to a BView. The best source of source of information for the BPolygon interface can be found -here in the Be Book. +it to a BView. The best source of source of information for the BPolygon is +the Be Book page about it.