|
Boost : |
Subject: Re: [boost] Thoughts for a GUI (Primitives) Library
From: Yakov Galka (ybungalobill_at_[hidden])
Date: 2010-09-08 14:33:52
Fine.
Then clarify some more details please.
On Wed, Sep 8, 2010 at 18:17, Gwenio <urulokiurae_at_[hidden]> wrote:
> Low level: the part the allow interaction with the system and cannot be
> replaced without knowing what the system is.
>
According to your definition the low-level part should implement the
controls with system independent interface. Consider a grid control (aka
list-view with details style). What interface should it have? Should it
store the data (with list_view::set_item_data()) or ask the owner to provide
the data when needed by a callback?
> The event handling components should translate the system messages,
> determine which control they are for, and pass it on to where ever the
> application or library as indicated it should be sent.
>
Recall message capturing/bubbling phases discussed before. Should the
low-level event handling component implement them or perhaps it'll be broken
into low-level component that merely captures system messages and a
high-level component that actually transfers them to their destination
(implementing capturing/bubbling and non-system events on the way)?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk