
|
[haiku-doc]
||
[Date Prev]
[09-2007 Date Index]
[Date Next]
||
[Thread Prev]
[09-2007 Thread Index]
[Thread Next]
[haiku-doc] Re: Messaging Introduction
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-doc@xxxxxxxxxxxxx
- Date: Sun, 30 Sep 2007 14:56:43 +0200 CEST
Hi Niels,
"Niels Reedijk" <niels.reedijk@xxxxxxxxx> wrote:
> I just finished the first version of the messaging introduction of
> the
> application kit
> (http://factory.haiku-os.org/documentation/Haiku_Book_doxygen/html/app_messaging.html).
> > It's not completely finished, but I think that finishing it only
> makes
> sense after the individual classes have been documented. If there is
> anyone willing to pick up a messaging class from the application kit,
> please claim it. You can use my schematic display as a starting point
> (http://haiku-os.org/files/screenshots/Messaging_0.png).
I'm currently reading through the introduction. It looks nice overall,
but I have the following comments:
* the last sentence of the first paragraph could be reworded, maybe
like this: "The framework allows inter-application messaging as well as
intra-application messaging, and it will always use the most effective
mechanism for the communication automatically."
* The classes titles in the classes overview should probably be links
to the respective class
* Typo in the BMessage overview FindBook() -> FindBool()
* With scripting, maybe also hint to the drag&drop protocol?
* In the BLooper introduction in the first paragraph, maybe it should
be mentioned that a BLooper can have any number of BHandlers (and is a
BHandler itself) before writing that it would choose a BHandler to
handle the message.
* Also all methods mentioned in the text (like AddBool(), AddHandler(),
...) should be links to make the documentation more usable.
* The warning in BHandler "baseclassMessageReceived()" looks messed up.
Nice work, anyway!
Bye,
Axel.
|

|