Re: [boost] Re: Re: Re: Re: [gui] GUI Taxonomy

From: Alan Gutierrez (alan-boost_at_[hidden])
Date: 2004-12-31 15:16:18

* Andy Little <andy_at_[hidden]> [2004-12-31 13:36]:
> 
> "Alan Gutierrez" <alan-boost_at_[hidden]> wrote in message
> news:20041231150348.GA20515_at_maribor.izzy.net...
> >* Andy Little <andy_at_[hidden]> [2004-12-31 07:37]:
> >>
> >> "Alan Gutierrez" <alan-boost_at_[hidden]> wrote
> >
> >> >    Are we talking about the same thing? Interface and implentation
> >> >    are overloaded terms.
> >
> >> // text
> >> struct text_element : graphics_element {..}
> >
> >> // edit box
> >> struct active_text : text_element,user_action_handler,
> >> draw_handler{..};
> >
> >    Except that on PlamOS, when using resource files, I don't need a
> >    draw function for my text boxes. I know they are draw somehow,
> >    but not by the Boost.GUI library.
> >
> >    Could this be what I'm saying?
> 
> Hmm  I see what you are saying ... The os privately owns the draw function
> for some (system) elements. So it doesnt need to be part of the interface
> except for user drawn elements

    Or library drawn elements (a nit).

    Also, I'm not creating boundries across applications, or
    platforms, such specialization might occur within a single
    application on a single platform.
    
    I might write a bitty spread sheet for Palm OS that uses Boost
    rendered elements on a grid, but still use resource bound
    elements for all other forms.
    
    Even though I've pulled the logic in for the spread sheet, it is
    going to be unused in Palm OS rendered forms.

--
Alan Gutierrez - alan_at_[hidden]