
|
[openbeos]
||
[Date Prev]
[08-2002 Date Index]
[Date Next]
||
[Thread Prev]
[08-2002 Thread Index]
[Thread Next]
[openbeos] Re: state-keeping app
- From: "Jonas Sundstrom" <kirilla@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 02 Aug 2002 20:01:23 CEST (+0200)
"Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
...
> > > - a B_LOAD_STATE app launch message
> > >
> > > - a B_SAVE_STATE shutdown message
> > > (probably a B_QUIT_REQUESTED with a "save_state" field)
>
> Actually I would provide the application programmer with a little bit
> more comfortable interface. E.g. two new BApplication hook methods
>
> status_t StoreState(BDataIO *state);
> status_t RestoreState(BDataIO *state);
>
> A BDataIO should be better than a BMessage, as applications with a
> greater amount of data to be saved/loaded certainly don't want to put
> it into a BMessage first, whereas the others are free to internally
> use
> a BMessage and just Flatten() it to/Unflatten() it from the BDataIO.
Hook methods would be nice, but I didn't mean fullblown BMessages,
just the "what" constants, asking the application to take action.
I don't see the point of the BDataIO object.
/Jonas Sundstrom. ~ www.kirilla.com ~ www.kioki.com
|

|