Yeah I remember it seemed cool at one point, but it's just seems kind of scary to have the text content mixed in with the child views.
On Tue, Sep 14, 2010 at 6:33 PM, P T Withington <[email protected]>wrote: > The simple fix, which I think is much more readable is to move the text out > of the body into the attribute: > > <tabpane text="Insecticides"> > <simple... > <radio ... > ... > </tabpane> > > but if you think that is going to offend too many people, we can keep the > old way. It just seems messy and hard to read. > > On 2010-09-14, at 15:38, Henry Minsky wrote: > > > When I put in a warning about mixing LZX and HTML content, all of these > > components > > give warnings, because they intermix text and lzx content quite happily. > > > > <tabpane>Insecticides > > <simplelayout spacing="10" inset="10"/> > > <radiogroup> > > <radiobutton>Yes, I want to know > more</radiobutton> > > <radiobutton>No, I prefer to remain blissfully > > unaware</radiobutton> > > <radiobutton>Please tell my neighbor, who may tell > > me</radiobutton> > > </radiogroup> > > </tabpane> > > > > These components declare their text attribtute as > > > > <attribute name="text" value="tab" type="text" /> > > > > Maybe we really do need to have a distinct type "html" for text, which is > > different from plain "text", and if that is the type then the compiler > > issues a warning about mixing HTML tags and LZX tags? In that case, the > > compiler could pass through the entire body > > verbatim to the runtime, which is what we've been shooting for as the > goal, > > right? > > > > > > > > > > > > -- > > Henry Minsky > > Software Architect > > [email protected] > > -- Henry Minsky Software Architect [email protected]
