Re: [Gramps-devel] Capitalization of Window Headers

[Raphael A. <rap...@gm...>]

One way is to look at one window title, then search for it in the
gramps sources. E.g., search for "Undo history warning" and you'll see
it in two files. src/PluginUtils/_Tool.py and
src/PlugUtils/DbLoader.py. It is the first argument in the call to the
class QuestionDialog2 in the file QuestionDialog.py. This file has
many Dialog classes and they all take a string as argument which they
will display. Searching for all the places in the code where one of
these Dialog Classes is called would be a good start to find some
window headers in a systematic way.

To make it easier in the future, and to remove redundancy/duplication,
it might make sense to have a class with constants for all the windows
title and whenever a window title is needed one could check whether
one should reuse an existing one or add a new one to this class with
constants and then reference the constant when calling e.g.,
QuestionDialog2(...)

Raphael

On Jan 29, 2008 11:39 PM, James G. Sack (jim) <jg...@sa...> wrote:
> Duncan Lithgow wrote:
> > I will continue looking for window headers which are not yet
> > capitalized. But there are a lot of windows, so please let me know if
> > you find one which needs capitalization.
> >
> > Duncan
> >
> > PS. Or is there some automated way of seeing _all_ the windows without
> > clicking through everything?
>
> Don't know, but..
> ..if you discover a good way to do that, be sure to document it so that
> it can be repeated on every release, as a QC step!
>
> Regards,
> ..jim
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>