2009/6/25 Stephen George <steve_geo@...>:
> Benny Malengier wrote:
>> I know we all support GRAMPS to be cross platform, but without
>> specific requirements that new features are tested in another platform
>> before release, it is not honest to our users to say that platform is
>> Eg, as far as I know spell check does not work in windows
>> although it should be easy to make work,
> My experience with spell check on windows is similar, however I don't
> believe it's easy to work as I have yet to find a binary version of GTKSpell
> for windows available on the net.
> Goggling returns a lot of people asking where the binaries are, but no
> binaries that I can find.
> Until such a binary is readily available I believe that spell checking will
> continue to be hard for non-developer windows users.
> I must admit I haven't tried to build GTKSpell for myself under windows, but
> I don't believe it's up to GRAMPS to provide/distribute the GTKSpell binary.
You are right. It is just that GTKSpell is 2 c files and one header
file, with only enchant and gtk, glib dependencies, and then the
python module in pygtk is a wrapper around that. Really strange nobody
has interest to package that for windows.
> Having said all that, I have a working python script that looks like
> GtkSpell to GRAMPS, but talks directly to pyEnchant [which does have binary
> installers for windows]
> This method bypasses the GTKSpell layer entirely and allows me to perform
> Spell checking on windows.
> The script needs a bit of spit and polish to clean it up, but I don't know
> if it's the correct way to provide spell checking support to windows users.
If via import platform, the methods can coexist easily, then I see no
reason not to include it. I must admit that spell check is not the
killer feature that is needed in genealogy
>> the automatic bug reporting has never functioned, ... .
> Strong words, as that was never my recollection, this is the 2nd time I've
> heard this on the list in the last few months. .. has someone fixed it since
> these posts?
> I just tested automatic bug reporting with Gramps 3.1.2 on two different
> Windows XP systems .... works OK. - Is the error only present on other
> versions of Windows?
Ah, without windows it is hard for me to know. I just repeated words
that I heard from others on the mailing list.
> On last page of the reporting wizard there are two buttons.
> First one copied the text to the clip board - which I verified by pasting
> into notepad.
> Second one launched my preferred browser (firefox) and opened the GRAMPS bug
> tracking web page (I had to log in manually) - and set up the bug report
> manually which I thought was standard.
Yes, this is how it works now. I don't know who changed it from the
automatic mails to the bug list (which is what was not working I
believe). Bug list is essentially dead for some months due to this
change. Perhaps it was changed by someone due to windows problems, I
really don't know. I'm not sure the link to webpage is a good service
to the users, but it does reduce the workload in the bug list
Anyway, The main thing for support is that:
1. any issues are documented on the wiki somehow, with a status and a
decision. Eg, now that you mention your enchant work, the discussion
of gtkspell on windows comes back to me, and I remember we already had
the discussion and you decided not to do it. This should be put on the
wiki, so anybody can first look there before starting another round of
2. a patch should be provided to add to GRAMPS. At a minimum the
resolution on eg Win should be in the doc path, preferentially, use of
the platform module is made to create a seperate codepath that is
clear. Eg, for spellchecking, in Spell.py:
if platform.system() in const.WINDOWS:
HAVE_ENCHANT = False
HAVE_GTKSPELL = False
LOG.warn(_("The windows version does not support spell check"))
HAVE_ENCHANT = True
HAVE_ENCHANT = False
HAVE_GTKSPELL = True
HAVE_GTKSPELL = False
if not HAVE_GTKSPELL:
LOG.warn(_("Spelling checker is not installed"))
These patches allow a search on const.WINDOWS to see all that is
different in Windows.
It also makes sure we know that we do not expect spell check to work.
This is the kind of thing I would like to see in the code for