Re: print preview screenshot

From: Alan Horkan (horkana@tcd.ie)
Date: Tue Aug 27 2002 - 08:51:44 EDT

  • Next message: Alan Horkan: "Re: print preview screenshot"

    On Tue, 27 Aug 2002, [iso-8859-1] Andrew Dunbar wrote:

    > Argh! Yes but fonts which don't respect Unicode
    > encoding *always* require special case code. This

    if we are already working around it then i guess it is not a big deal.

    > But I'm a bit hesitant to do it this way because it's
    > so intensive - you have to load and render up every
    > font in the system. That makes lots of processor and
    > disk work. But I'm not against it either really...

    yet another option. if it was done right and done well i cant say i am
    aginst it either.

    > > This would be less of a problem if changing the font
    > > did not cause Abiword to lose the selection. I
    > > would have sworn there was a bug for this but i
    > > have not found it.
    >
    > Really? That's not good and does need a bug.

    need to file one then dont i!

    or i could just change this bug report as the selection not being kept
    affects various places, more than just fonts.
    http://bugzilla.abisource.com/show_bug.cgi?id=615

    there are a few other bugs that might be relevant but that i dont feel
    like checking right now.

    > > i would really like to see this tho'
    > >

    http://matrix.netsoc.tcd.ie/~horkana/dev/abi/ui/microsoft-word97_fonts_fonttoolbarMostRecentlyUsed_003.png

    http://bugzilla.abisource.com/show_bug.cgi?id=1765
    Most recently used fonts
    >
    > Me too! I always use this feature in Word.
    > But we shouldn't limit it to fonts. The Word language
    > selection tool does the same - which I also use.

    If i was doing a multilingual document it would be very useful to have
    a drop down menu for language on the toolbar, with the 5 MRU used
    languages even if i am unlikely to ever use more than 2 languages in a
    document.

    I definately think there are a loads of things that could be done to the
    toolbars for Abiword, like make more of them (Tables, Plugins toolbar,
    user specified toolbars etc), break the exsiting
    toolbars into smaller toolbars. make sure that there are
    only N icons per toolbar where N is as many as will fit on a small
    display.

    Doing of stuff like Zoom would of course be very silly.

    From Joelonsoftware (paraphrased sorry no link)
    Any drop down menu that is not editable should be clickable

    [Zoom [v]

    example, currently on the [v] bit is the clickable target, but the user
    should be offered a bigger clickable target the whole [Zoom [v].

    In the case of something like the font dialog you might want to manually
    type in the font name rather than scrolling for it (unlikely but possible) so you would
    have to leave the menu section editable rather than making the whole menu
    the target.
    Is this clear? i hope so, but i doubt it.
    is this relevant? not really but we were talking about usability.

    > I think we need a nice new GUI component that we can
    > use in both these places - and maybe there's other
    > places where it makes sense.
    >
    > Andrew Dunbar.

    > > > To do it in GTK 2 would require modification of
    > > > the combo box widget I think. Seth Nichol thinks
    > > > this would be "rather easy" :-)

    > > Sincerely
    > > Alan Horkan
    > >
    > > http://abisource.com
    > > http://gnome.org
    > > http://mozilla.org

    http://linguaphile.sourceforge.net/cgi-bin/translator.pl
    http://www.abisource.com



    This archive was generated by hypermail 2.1.4 : Tue Aug 27 2002 - 08:56:05 EDT