From: Peter L. <pet...@te...> - 2009-10-26 08:05:55
|
Hi, How come I only see one Gramplet (Record) when I run Gramps in Swedish. If I run in English or French I see all! /Peter |
From: Benny M. <ben...@gm...> - 2009-10-26 10:12:16
|
2009/10/26 Peter Landgren <pet...@te...>: > Hi, > > How come I only see one Gramplet (Record) when I run Gramps in Swedish. > If I run in English or French I see all! I can think of no reason for this. No output on command line about failed register of some files? Add some print statements to understand what is registered. So open src/gen/plug/_pluginreg.py and in the scan_dir function add at the end: for x in self.__plugindata: print x.id to know what is registered (you should see it in the plugin status window also of course). If all are registered, it would mean something is going wrong later. If not registered, add print statements in eg the newplugin and register functions to know if they are having issues. With LANG=sv I see all plugins, so it must be related to your locale installation. Benny > /Peter > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2009-10-26 11:30:17
|
> can think of no reason for this. No output on command line about > failed register of some files? No, nothing on the console. There is only one gramplet registered. > Add some print statements to understand what is registered. So open > > src/gen/plug/_pluginreg.py > > and in the scan_dir function add at the end: > > for x in self.__plugindata: > print x.id It seems to me that it finds 119 plugings. I can see all names. > to know what is registered (you should see it in the plugin status > window also of course). If all are registered, it would mean something > is going wrong later. Only one gramplet is registered. And that is Records.py which is in the /plugins direcory. None of the Gramplets in the gramplet directory seems to be registered. > If not registered, add print statements in eg the newplugin and > register functions to know if they are having issues. There are 153 runs of newplugin function and 85 runs of register function. I get the same number when I run English Gramps. But now all 25 Gramplets are shown in the Plugin Status and in the Gramplte view. /Peter |
From: Doug B. <dou...@gm...> - 2009-10-26 11:56:08
|
Peter, If you move the .gramps/gramplet.ini file, do you then see gramplets? Can you create a gramplet by right-clicking on the gramplet view? Does that create one? Does it reload after a restart? -Doug On Mon, Oct 26, 2009 at 7:29 AM, Peter Landgren <pet...@te...> wrote: >> can think of no reason for this. No output on command line about >> failed register of some files? > No, nothing on the console. > There is only one gramplet registered. > >> Add some print statements to understand what is registered. So open >> >> src/gen/plug/_pluginreg.py >> >> and in the scan_dir function add at the end: >> >> for x in self.__plugindata: >> print x.id > It seems to me that it finds 119 plugings. I can see all names. > > >> to know what is registered (you should see it in the plugin status >> window also of course). If all are registered, it would mean something >> is going wrong later. > Only one gramplet is registered. And that is Records.py which is in the /plugins direcory. > None of the Gramplets in the gramplet directory seems to be registered. > > >> If not registered, add print statements in eg the newplugin and >> register functions to know if they are having issues. > > There are 153 runs of newplugin function and 85 runs of register function. > I get the same number when I run English Gramps. But now all 25 Gramplets are shown in the Plugin > Status and in the Gramplte view. > > /Peter > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2009-10-26 15:35:48
|
> Peter, > > If you move the .gramps/gramplet.ini file, do you then see gramplets? I see only Records Gramplet. If I delete the plugins/gramplet directory I see the same. > Can you create a gramplet by right-clicking on the gramplet view? Does > that create one? Does it reload after a restart? And I can activate it and it runs OK. And no reload button. However, if I start gramps with: LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py in stead of: python src/gramps.py (which should be enough) Everything is OK even the Reload button. /Peter > -Doug > > On Mon, Oct 26, 2009 at 7:29 AM, Peter Landgren <pet...@te...> wrote: > >> can think of no reason for this. No output on command line about > >> failed register of some files? > > > > No, nothing on the console. > > There is only one gramplet registered. > > > >> Add some print statements to understand what is registered. So open > >> > >> src/gen/plug/_pluginreg.py > >> > >> and in the scan_dir function add at the end: > >> > >> for x in self.__plugindata: > >> print x.id > > > > It seems to me that it finds 119 plugings. I can see all names. > > > >> to know what is registered (you should see it in the plugin status > >> window also of course). If all are registered, it would mean something > >> is going wrong later. > > > > Only one gramplet is registered. And that is Records.py which is in the > > /plugins direcory. None of the Gramplets in the gramplet directory seems > > to be registered. > > > >> If not registered, add print statements in eg the newplugin and > >> register functions to know if they are having issues. > > > > There are 153 runs of newplugin function and 85 runs of register > > function. I get the same number when I run English Gramps. But now all 25 > > Gramplets are shown in the Plugin Status and in the Gramplte view. > > > > /Peter > > > > > > ------------------------------------------------------------------------- > >----- Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Benny M. <ben...@gm...> - 2009-10-26 15:11:39
|
2009/10/26 Peter Landgren <pet...@te...>: >> can think of no reason for this. No output on command line about >> failed register of some files? > No, nothing on the console. > There is only one gramplet registered. > >> Add some print statements to understand what is registered. So open >> >> src/gen/plug/_pluginreg.py >> >> and in the scan_dir function add at the end: >> >> for x in self.__plugindata: >> print x.id > It seems to me that it finds 119 plugings. I can see all names. > > >> to know what is registered (you should see it in the plugin status >> window also of course). If all are registered, it would mean something >> is going wrong later. > Only one gramplet is registered. And that is Records.py which is in the /plugins direcory. > None of the Gramplets in the gramplet directory seems to be registered. Ok, so or in swedish locale the os.walk command does not enter the plugins/gramplet directory, or reading the gpr.py file there fails in a way that does not show output. To know the first, in _manager.py, add in method reg_plugins a: print dirparth in the for loop over os.walk If it does enter the file, then in _pluginreg, the execfile command runs, but errors always lead to a print of something on command line, see the exept ValueError and except branches, so no id what could be happening there Are you running with python -O or just python? Benny > > >> If not registered, add print statements in eg the newplugin and >> register functions to know if they are having issues. > > There are 153 runs of newplugin function and 85 runs of register function. > I get the same number when I run English Gramps. But now all 25 Gramplets are shown in the Plugin > Status and in the Gramplte view. > > /Peter > > |
From: Peter L. <pet...@te...> - 2009-10-26 15:35:49
|
> 2009/10/26 Peter Landgren <pet...@te...>: > >> can think of no reason for this. No output on command line about > >> failed register of some files? > > > > No, nothing on the console. > > There is only one gramplet registered. > > > >> Add some print statements to understand what is registered. So open > >> > >> src/gen/plug/_pluginreg.py > >> > >> and in the scan_dir function add at the end: > >> > >> for x in self.__plugindata: > >> print x.id > > > > It seems to me that it finds 119 plugings. I can see all names. > > > >> to know what is registered (you should see it in the plugin status > >> window also of course). If all are registered, it would mean something > >> is going wrong later. > > > > Only one gramplet is registered. And that is Records.py which is in the > > /plugins direcory. None of the Gramplets in the gramplet directory seems > > to be registered. > > Ok, so or in swedish locale the os.walk command does not enter the > plugins/gramplet directory, or reading the gpr.py file there fails in > a way that does not show output. > > To know the first, in _manager.py, add in method reg_plugins a: > print dirparth in the for loop over os.walk > > If it does enter the file, then in _pluginreg, the execfile command > runs, but errors always lead to a print of something on command line, > see the exept ValueError and except branches, so no id what could be > happening there > > Are you running with python -O or just python? I found it: If get into trouble if I start with -O /Peter > Benny > > >> If not registered, add print statements in eg the newplugin and > >> register functions to know if they are having issues. > > > > There are 153 runs of newplugin function and 85 runs of register > > function. I get the same number when I run English Gramps. But now all 25 > > Gramplets are shown in the Plugin Status and in the Gramplte view. > > > > /Peter -- Peter Landgren Talken Hagen 671 94 BRUNSKOG 0570-530 21 070-635 4719 pet...@te... Skype: pgl4820.2 |
From: Peter L. <pet...@te...> - 2009-10-26 15:39:23
|
Correction: However, if I start gramps with: LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py in stead of: python -O src/gramps.py (which should be enough) I didn't notice that the long comman was without -O and the short was with -O /Peter |
From: Benny M. <ben...@gm...> - 2009-10-26 19:28:25
|
2009/10/26 Peter Landgren <pet...@te...>: > Correction: > > However, if I start gramps with: > LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py > in stead of: > python -O src/gramps.py > (which should be enough) > > I didn't notice that the long comman was without -O and the short was with -O svn up, should be fixed now, default for register is UNSTABLE, which only shows without -O flag. Added to almost all gramplets that they are STABLE Benny |
From: Peter L. <pet...@te...> - 2009-10-26 19:45:33
|
Den Monday 26 October 2009 20.28.04 skrev Benny Malengier: > 2009/10/26 Peter Landgren <pet...@te...>: > > Correction: > > > > However, if I start gramps with: > > LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py > > in stead of: > > python -O src/gramps.py > > (which should be enough) > > > > I didn't notice that the long comman was without -O and the short was > > with -O > > svn up, should be fixed now, default for register is UNSTABLE, which > only shows without -O flag. Added to almost all gramplets that they > are STABLE > > Benny OK. Now I see all gramplets and they work. But, there us no "Load" button and no "Reload" button when I start with -O. /Peter |
From: Benny M. <ben...@gm...> - 2009-10-26 19:54:56
|
2009/10/26 Peter Landgren <pet...@te...>: > Den Monday 26 October 2009 20.28.04 skrev Benny Malengier: >> 2009/10/26 Peter Landgren <pet...@te...>: >> > Correction: >> > >> > However, if I start gramps with: >> > LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py >> > in stead of: >> > python -O src/gramps.py >> > (which should be enough) >> > >> > I didn't notice that the long comman was without -O and the short was >> > with -O >> >> svn up, should be fixed now, default for register is UNSTABLE, which >> only shows without -O flag. Added to almost all gramplets that they >> are STABLE >> >> Benny > OK. Now I see all gramplets and they work. > > But, there us no "Load" button and no "Reload" button when I start with -O. Yes, users don't see this. Why would they, they cannot code, so there is no need to load or reload a plugin. It is just confusing for them. This is a developers only functionality. The 'Loaded Plugins' tab is present, because it allows us to ask what the error is when they say on bug list that a plugin does not start after selection in the menu. It will appear there with 'Fail'. Benny |
From: Peter L. <pet...@te...> - 2009-10-26 21:13:31
|
Den Monday 26 October 2009 20.54.42 skrev Benny Malengier: > 2009/10/26 Peter Landgren <pet...@te...>: > > Den Monday 26 October 2009 20.28.04 skrev Benny Malengier: > >> 2009/10/26 Peter Landgren <pet...@te...>: > >> > Correction: > >> > > >> > However, if I start gramps with: > >> > LANGUAGE=sv_SE.UTF-8:sv LANG=sv_SE.UTF-8:sv python src/gramps.py > >> > in stead of: > >> > python -O src/gramps.py > >> > (which should be enough) > >> > > >> > I didn't notice that the long comman was without -O and the short was > >> > with -O > >> > >> svn up, should be fixed now, default for register is UNSTABLE, which > >> only shows without -O flag. Added to almost all gramplets that they > >> are STABLE > >> > >> Benny > > > > OK. Now I see all gramplets and they work. > > > > But, there us no "Load" button and no "Reload" button when I start with > > -O. > > Yes, users don't see this. Why would they, they cannot code, so there > is no need to load or reload a plugin. It is just confusing for them. > This is a developers only functionality. > > The 'Loaded Plugins' tab is present, because it allows us to ask what > the error is when they say on bug list that a plugin does not start > after selection in the menu. It will appear there with 'Fail'. > > Benny Sounds logical. I came to think something like that after I sent the previous mail. /Peter |