On Wed, 2004-06-30 at 10:32, martyn 2 russell bt com wrote: > > * the way I'd handle bolding of the main text, is that > > > > - If we aren't using markup for the main text and > > the secondary text should be should be displayed > > in bold > > > > - If we are using markup for the main text, we leave > > it unmodified. > > I thought the idea of the GtkMessageDialog was to hold a certain format > when displaying information, i.e. the primary text is a certain > format, and the secondard is another format. Using markup allows this > format to be changed and I would argue if the developer wants a > particular format (which is outside the guidelines of the HIG), why > not create their own unique dialog? From the point of view of "what application developer's should do", perhaps. I'm just trying to work out the cases from the perspective of API completeness. If the application uses markup for the main text of GtkMessageDialog and sets secondary text, then we need to do *something*. The question is, what is most useful and most expected. > > Two other possibilities are: > > > > - We should implicitly add a <b></b> around > > the main text in the case where the main text > > has markup. > > I think this is slightly messy. What happens if the developer doesn't want bold text, > but instead, just larger text? They have no choice then. > > Perhaps the solution is the only allow tags like <u> and <i>? That way the developer > can place emphasis on text still, but the actual sizing and boldness of the text is > limited to the HIG? Limiting to only a certain set of tags would be tricky to implement. And anyways, that's the implicit effect of putting the default attributes on a span surrounding all the user implied markup. <b>foo <b>blah</b> blargh</b> is the same as <b>foo blah blargh</b> The tradeoff is basically: - Not doing the default markup when the user specifies markup is conceptually simpler and gives the user more flexibility. - Doing the default + the user specified makes it a lot easier to get the right effect for "A <i>coup d'etat</i> has occurred" > For most the message dialogs I have created, I am not interested in the formatting, > I just expect the primary to be bold or bigger, and the secondary to be smaller and > to have less emphasis. For me, using arguments when setting the label text was my > biggest beef :) If the user doesn't use markup for the main text, then it clearly just works as you want. > > > > - We should have > > > > gtk_message_dialog_set_title_text() > > > > instead and use the current text as the main text. > > But that strikes me as making the code read backwards > > from the display and hence bad. > > I thought the HIG says to use an empty title for a dialog/alert? Sorry, that was confusing, I was just searching for a more intuitive term for "main_text". Regards, Owen
Attachment:
signature.asc
Description: This is a digitally signed message part