GRAMPS › GRAMPS - Dev

trunk/ 3.5.0 problems

Classic

List

Threaded

13 messages Options

robhealey1

trunk/ 3.5.0 problems

Greetings:

Since Jerome made the change to trunk to 3.5.0, I have NOT opened a
database until now!

All of the *.gpr.py files in the plugins directory need to be updated
from 'gramps_target_version="3.4"' to 3.5 because you get a TON of
messages on the screen!

There will also need to be added a gramps35 to gramps-addons, and copy
all of trunk into the new gramps35 directory with the above change
also to their *.gpr.py files...

--
Sincerely yours,
Rob G. Healey

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

jerome

Re : trunk/ 3.5.0 problems

Rob,

The change was related to behavior pointed out by you.

"I have just realized something of a strange nature!

1) deleted the whole gramps34 directory...
2) deleted the whole .gramps directory this time
3) checkout gramps34
4) compiled and installed gramps34
5) imported my database into gramps34
6) clicked on Geography View from the left navigation bar...
7) it worked, and all five views

8) closed gramps34
0) opened trunk, and geography view was already selected
10) it works, and all five views are working!

It appears that gramps34 has GEOGRAPHY PATH already set and trunk was able to see it and use it..."

'trunk' and 'gramps34' have used the same config files (.ini, plugins).
All branches are still sharing 'report_options.xml' and 'tool_options.xml'.

By adding new features on trunk, which do not exist on 3.4, we are generating strange config files. As you want, I can revert the change but we need to keep in mind that 'trunk' is more '3.4' and some strange things might happen!

Jérôme

--- En date de : Mar 10.4.12, Rob Healey <[hidden email]> a écrit :

> De: Rob Healey <[hidden email]>
> Objet: [Gramps-devel] trunk/ 3.5.0 problems
> À: "Gramps Development List" <[hidden email]>
> Date: Mardi 10 avril 2012, 4h33
> Greetings:
>
> Since Jerome made the change to trunk to 3.5.0, I have NOT
> opened a
> database until now!
>
> All of the *.gpr.py files in the plugins directory need to
> be updated
> from 'gramps_target_version="3.4"' to 3.5 because you get a
> TON of
> messages on the screen!
>
> There will also need to be added a gramps35 to
> gramps-addons, and copy
> all of trunk into the new gramps35 directory with the above
> change
> also to their *.gpr.py files...
>
> --
> Sincerely yours,
> Rob G. Healey
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes
> to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

jerome

Re : trunk/ 3.5.0 problems

> that 'trunk' is more '3.4'

is no more ...

--- En date de : Mar 10.4.12, jerome <[hidden email]> a écrit :

> De: jerome <[hidden email]>
> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
> À: "Gramps Development List" <[hidden email]>, "Rob Healey" <[hidden email]>
> Date: Mardi 10 avril 2012, 8h03
> Rob,
>
>
> The change was related to behavior pointed out by you.
>
> "I have just realized something of a strange nature!
>
> 1) deleted the whole gramps34 directory...
> 2) deleted the whole .gramps directory this time
> 3) checkout gramps34
> 4) compiled and installed gramps34
> 5) imported my database into gramps34
> 6) clicked on Geography View from the left navigation
> bar...
> 7) it worked, and all five views
>
> 8) closed gramps34
> 0) opened trunk, and geography view was already selected
> 10) it works, and all five views are working!
>
> It appears that gramps34 has GEOGRAPHY PATH already set and
> trunk was able to see it and use it..."
>
> 'trunk' and 'gramps34' have used the same config files
> (.ini, plugins).
> All branches are still sharing 'report_options.xml' and
> 'tool_options.xml'.
>
> By adding new features on trunk, which do not exist on 3.4,
> we are generating strange config files. As you want, I can
> revert the change but we need to keep in mind that 'trunk'
> is more '3.4' and some strange things might happen!
>
>
> Jérôme
>
> --- En date de : Mar 10.4.12, Rob Healey <[hidden email]>
> a écrit :
>
> > De: Rob Healey <[hidden email]>
> > Objet: [Gramps-devel] trunk/ 3.5.0 problems
> > À: "Gramps Development List" <[hidden email]>
> > Date: Mardi 10 avril 2012, 4h33
> > Greetings:
> >
> > Since Jerome made the change to trunk to 3.5.0, I have
> NOT
> > opened a
> > database until now!
> >
> > All of the *.gpr.py files in the plugins directory need
> to
> > be updated
> > from 'gramps_target_version="3.4"' to 3.5 because you
> get a
> > TON of
> > messages on the screen!
> >
> > There will also need to be added a gramps35 to
> > gramps-addons, and copy
> > all of trunk into the new gramps35 directory with the
> above
> > change
> > also to their *.gpr.py files...
> >
> > --
> > Sincerely yours,
> > Rob G. Healey
> >
> >
> ------------------------------------------------------------------------------
> > Better than sec? Nothing is better than sec when it
> comes
> > to
> > monitoring Big Data applications. Try Boundary
> one-second
> > resolution app monitoring today. Free.
> > http://p.sf.net/sfu/Boundary-dev2dev
> > _______________________________________________
> > Gramps-devel mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >
>

Serge Noiraud-2

Re: Re : trunk/ 3.5.0 problems

Hi,

At each times we change the version we must change all *.gpr.py files.
perhaps it should be better to use a global variable for this.

Serge

Le 10/04/2012 08:05, jerome a écrit :

>> that 'trunk' is more '3.4'
> is no more ...
>
> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :
>
>> De: jerome<[hidden email]>
>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>
>> Date: Mardi 10 avril 2012, 8h03
>> Rob,
>>
>>
>> The change was related to behavior pointed out by you.
>>
>> "I have just realized something of a strange nature!
>>
>> 1) deleted the whole gramps34 directory...
>> 2) deleted the whole .gramps directory this time
>> 3) checkout gramps34
>> 4) compiled and installed gramps34
>> 5) imported my database into gramps34
>> 6) clicked on Geography View from the left navigation
>> bar...
>> 7) it worked, and all five views
>>
>> 8) closed gramps34
>> 0) opened trunk, and geography view was already selected
>> 10) it works, and all five views are working!
>>
>> It appears that gramps34 has GEOGRAPHY PATH already set and
>> trunk was able to see it and use it..."
>>
>> 'trunk' and 'gramps34' have used the same config files
>> (.ini, plugins).
>> All branches are still sharing 'report_options.xml' and
>> 'tool_options.xml'.
>>
>> By adding new features on trunk, which do not exist on 3.4,
>> we are generating strange config files. As you want, I can
>> revert the change but we need to keep in mind that 'trunk'
>> is more '3.4' and some strange things might happen!
>>
>>
>> Jérôme
>>
>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>> a écrit :
>>
>>> De: Rob Healey<[hidden email]>
>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>>> À: "Gramps Development List"<[hidden email]>
>>> Date: Mardi 10 avril 2012, 4h33
>>> Greetings:
>>>
>>> Since Jerome made the change to trunk to 3.5.0, I have
>> NOT
>>> opened a
>>> database until now!
>>>
>>> All of the *.gpr.py files in the plugins directory need
>> to
>>> be updated
>>> from 'gramps_target_version="3.4"' to 3.5 because you
>> get a
>>> TON of
>>> messages on the screen!
>>>
>>> There will also need to be added a gramps35 to
>>> gramps-addons, and copy
>>> all of trunk into the new gramps35 directory with the
>> above
>>> change
>>> also to their *.gpr.py files...
>>>
>>> --
>>> Sincerely yours,
>>> Rob G. Healey
>>>
>>>
>> ------------------------------------------------------------------------------
>>> Better than sec? Nothing is better than sec when it
>> comes
>>> to
>>> monitoring Big Data applications. Try Boundary
>> one-second

jerome

Re: Re : trunk/ 3.5.0 problems

If so, do not need to use a target, isn't it?

To load gramps.py/const.py (or where the version is set), will load plugins whatever version !!! :(

Note, I will create the 3.4 branch into addons repository.
Some issues were pending. I will rebuild packages (download) after SVN copy (trunk -> 3.4). ie. start to test addons into a clean environment.
Then, to also change version number for trunk (addons).

--- En date de : Mer 11.4.12, Serge Noiraud <[hidden email]> a écrit :

> De: Serge Noiraud <[hidden email]>
> Objet: Re: [Gramps-devel] Re : trunk/ 3.5.0 problems
> À: "jerome" <[hidden email]>
> Cc: "Gramps Development List" <[hidden email]>, "Rob Healey" <[hidden email]>
> Date: Mercredi 11 avril 2012, 9h35
> Hi,
>
> At each times we change the version we must change all
> *.gpr.py files.
> perhaps it should be better to use a global variable for
> this.
>
> Serge
>
> Le 10/04/2012 08:05, jerome a écrit :
> >> that 'trunk' is more '3.4'
> > is no more ...
> >
> > --- En date de : Mar 10.4.12, jerome<[hidden email]>
> a écrit :
> >
> >> De: jerome<[hidden email]>
> >> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
> >> À: "Gramps Development List"<[hidden email]>,
> "Rob Healey"<[hidden email]>
> >> Date: Mardi 10 avril 2012, 8h03
> >> Rob,
> >>
> >>
> >> The change was related to behavior pointed out by
> you.
> >>
> >> "I have just realized something of a strange
> nature!
> >>
> >> 1) deleted the whole gramps34 directory...
> >> 2) deleted the whole .gramps directory this time
> >> 3) checkout gramps34
> >> 4) compiled and installed gramps34
> >> 5) imported my database into gramps34
> >> 6) clicked on Geography View from the left
> navigation
> >> bar...
> >> 7) it worked, and all five views
> >>
> >> 8) closed gramps34
> >> 0) opened trunk, and geography view was already
> selected
> >> 10) it works, and all five views are working!
> >>
> >> It appears that gramps34 has GEOGRAPHY PATH already
> set and
> >> trunk was able to see it and use it..."
> >>
> >> 'trunk' and 'gramps34' have used the same config
> files
> >> (.ini, plugins).
> >> All branches are still sharing 'report_options.xml'
> and
> >> 'tool_options.xml'.
> >>
> >> By adding new features on trunk, which do not exist
> on 3.4,
> >> we are generating strange config files. As you
> want, I can
> >> revert the change but we need to keep in mind that
> 'trunk'
> >> is more '3.4' and some strange things might
> happen!
> >>
> >>
> >> Jérôme
> >>
> >> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
> >> a écrit :
> >>
> >>> De: Rob Healey<[hidden email]>
> >>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
> >>> À: "Gramps Development List"<[hidden email]>
> >>> Date: Mardi 10 avril 2012, 4h33
> >>> Greetings:
> >>>
> >>> Since Jerome made the change to trunk to 3.5.0,
> I have
> >> NOT
> >>> opened a
> >>> database until now!
> >>>
> >>> All of the *.gpr.py files in the plugins
> directory need
> >> to
> >>> be updated
> >>> from 'gramps_target_version="3.4"' to 3.5
> because you
> >> get a
> >>> TON of
> >>> messages on the screen!
> >>>
> >>> There will also need to be added a gramps35 to
> >>> gramps-addons, and copy
> >>> all of trunk into the new gramps35 directory
> with the
> >> above
> >>> change
> >>> also to their *.gpr.py files...
> >>>
> >>> --
> >>> Sincerely yours,
> >>> Rob G. Healey
> >>>
> >>>
> >>
> ------------------------------------------------------------------------------
> >>> Better than sec? Nothing is better than sec
> when it
> >> comes
> >>> to
> >>> monitoring Big Data applications. Try Boundary
> >> one-second
>

Serge Noiraud-2

Re: Re : trunk/ 3.5.0 problems

In reply to this post by Serge Noiraud-2

Le 11/04/2012 09:35, Serge Noiraud a écrit :
> Hi,
>
> At each times we change the version we must change all *.gpr.py files.
> perhaps it should be better to use a global variable for this.
>
> Serge
We could use something like the folllowing in each gpr.py delivered with the standard gramps tree
Not in other plugins.

from const import VERSION_TUPLE
MODULE_VERSION="%1d.%1d" % (VERSION_TUPLE[0], VERSION_TUPLE[1])

then we can use :
...
gramps_target_version = MODULE_VERSION,
...

Serge

>
> Le 10/04/2012 08:05, jerome a écrit :
>>> that 'trunk' is more '3.4'
>> is no more ...
>>
>> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :
>>
>>> De: jerome<[hidden email]>
>>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>
>>> Date: Mardi 10 avril 2012, 8h03
>>> Rob,
>>>
>>>
>>> The change was related to behavior pointed out by you.
>>>
>>> "I have just realized something of a strange nature!
>>>
>>> 1) deleted the whole gramps34 directory...
>>> 2) deleted the whole .gramps directory this time
>>> 3) checkout gramps34
>>> 4) compiled and installed gramps34
>>> 5) imported my database into gramps34
>>> 6) clicked on Geography View from the left navigation
>>> bar...
>>> 7) it worked, and all five views
>>>
>>> 8) closed gramps34
>>> 0) opened trunk, and geography view was already selected
>>> 10) it works, and all five views are working!
>>>
>>> It appears that gramps34 has GEOGRAPHY PATH already set and
>>> trunk was able to see it and use it..."
>>>
>>> 'trunk' and 'gramps34' have used the same config files
>>> (.ini, plugins).
>>> All branches are still sharing 'report_options.xml' and
>>> 'tool_options.xml'.
>>>
>>> By adding new features on trunk, which do not exist on 3.4,
>>> we are generating strange config files. As you want, I can
>>> revert the change but we need to keep in mind that 'trunk'
>>> is more '3.4' and some strange things might happen!
>>>
>>>
>>> Jérôme
>>>
>>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>>> a écrit :
>>>
>>>> De: Rob Healey<[hidden email]>
>>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>>>> À: "Gramps Development List"<[hidden email]>
>>>> Date: Mardi 10 avril 2012, 4h33
>>>> Greetings:
>>>>
>>>> Since Jerome made the change to trunk to 3.5.0, I have
>>> NOT
>>>> opened a
>>>> database until now!
>>>>
>>>> All of the *.gpr.py files in the plugins directory need
>>> to
>>>> be updated
>>>> from 'gramps_target_version="3.4"' to 3.5 because you
>>> get a
>>>> TON of
>>>> messages on the screen!
>>>>
>>>> There will also need to be added a gramps35 to
>>>> gramps-addons, and copy
>>>> all of trunk into the new gramps35 directory with the
>>> above
>>>> change
>>>> also to their *.gpr.py files...
>>>>
>>>> --
>>>> Sincerely yours,
>>>> Rob G. Healey
>>>>
>>>>
>>> ------------------------------------------------------------------------------
>>>> Better than sec? Nothing is better than sec when it
>>> comes
>>>> to
>>>> monitoring Big Data applications. Try Boundary
>>> one-second
>>>

robhealey1

Re: Re : trunk/ 3.5.0 problems

In reply to this post by jerome

Jerome and Serge:

Thank you so much for everything that you do!

I will be anxiously awaiting your confirmation that it is completed
and ready for use...

Sincerely yours,
Rob G. Healey

On Wed, Apr 11, 2012 at 12:48 AM, jerome <[hidden email]> wrote:

> If so, do not need to use a target, isn't it?
>
> To load gramps.py/const.py (or where the version is set), will load plugins whatever version !!! :(
>
> Note, I will create the 3.4 branch into addons repository.
> Some issues were pending. I will rebuild packages (download) after SVN copy (trunk -> 3.4). ie. start to test addons into a clean environment.
> Then, to also change version number for trunk (addons).
>
>
>
> --- En date de : Mer 11.4.12, Serge Noiraud <[hidden email]> a écrit :
>
>> De: Serge Noiraud <[hidden email]>
>> Objet: Re: [Gramps-devel] Re : trunk/ 3.5.0 problems
>> À: "jerome" <[hidden email]>
>> Cc: "Gramps Development List" <[hidden email]>, "Rob Healey" <[hidden email]>
>> Date: Mercredi 11 avril 2012, 9h35
>> Hi,
>>
>> At each times we change the version we must change all
>> *.gpr.py files.
>> perhaps it should be better to use a global variable for
>> this.
>>
>> Serge
>>
>> Le 10/04/2012 08:05, jerome a écrit :
>> >> that 'trunk' is more '3.4'
>> > is no more ...
>> >
>> > --- En date de : Mar 10.4.12, jerome<[hidden email]>
>> a écrit :
>> >
>> >> De: jerome<[hidden email]>
>> >> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>> >> À: "Gramps Development List"<[hidden email]>,
>> "Rob Healey"<[hidden email]>
>> >> Date: Mardi 10 avril 2012, 8h03
>> >> Rob,
>> >>
>> >>
>> >> The change was related to behavior pointed out by
>> you.
>> >>
>> >> "I have just realized something of a strange
>> nature!
>> >>
>> >> 1) deleted the whole gramps34 directory...
>> >> 2) deleted the whole .gramps directory this time
>> >> 3) checkout gramps34
>> >> 4) compiled and installed gramps34
>> >> 5) imported my database into gramps34
>> >> 6) clicked on Geography View from the left
>> navigation
>> >> bar...
>> >> 7) it worked, and all five views
>> >>
>> >> 8) closed gramps34
>> >> 0) opened trunk, and geography view was already
>> selected
>> >> 10) it works, and all five views are working!
>> >>
>> >> It appears that gramps34 has GEOGRAPHY PATH already
>> set and
>> >> trunk was able to see it and use it..."
>> >>
>> >> 'trunk' and 'gramps34' have used the same config
>> files
>> >> (.ini, plugins).
>> >> All branches are still sharing 'report_options.xml'
>> and
>> >> 'tool_options.xml'.
>> >>
>> >> By adding new features on trunk, which do not exist
>> on 3.4,
>> >> we are generating strange config files. As you
>> want, I can
>> >> revert the change but we need to keep in mind that
>> 'trunk'
>> >> is more '3.4' and some strange things might
>> happen!
>> >>
>> >>
>> >> Jérôme
>> >>
>> >> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>> >> a écrit :
>> >>
>> >>> De: Rob Healey<[hidden email]>
>> >>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>> >>> À: "Gramps Development List"<[hidden email]>
>> >>> Date: Mardi 10 avril 2012, 4h33
>> >>> Greetings:
>> >>>
>> >>> Since Jerome made the change to trunk to 3.5.0,
>> I have
>> >> NOT
>> >>> opened a
>> >>> database until now!
>> >>>
>> >>> All of the *.gpr.py files in the plugins
>> directory need
>> >> to
>> >>> be updated
>> >>> from 'gramps_target_version="3.4"' to 3.5
>> because you
>> >> get a
>> >>> TON of
>> >>> messages on the screen!
>> >>>
>> >>> There will also need to be added a gramps35 to
>> >>> gramps-addons, and copy
>> >>> all of trunk into the new gramps35 directory
>> with the
>> >> above
>> >>> change
>> >>> also to their *.gpr.py files...
>> >>>
>> >>> --
>> >>> Sincerely yours,
>> >>> Rob G. Healey
>> >>>
>> >>>
>> >>
>> ------------------------------------------------------------------------------
>> >>> Better than sec? Nothing is better than sec
>> when it
>> >> comes
>> >>> to
>> >>> monitoring Big Data applications. Try Boundary
>> >> one-second
>>

--
Sincerely yours,
Rob G. Healey

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

robhealey1

Re: Re : trunk/ 3.5.0 problems

In reply to this post by Serge Noiraud-2

Dear Serge:

I believe that this is a wonderful idea!

Lets suggest it to the entire list???

Sincerely yours,
Rob G. Healey

On Wed, Apr 11, 2012 at 12:54 AM, Serge Noiraud <[hidden email]> wrote:

> Le 11/04/2012 09:35, Serge Noiraud a écrit :
>> Hi,
>>
>> At each times we change the version we must change all *.gpr.py files.
>> perhaps it should be better to use a global variable for this.
>>
>> Serge
> We could use something like the folllowing in each gpr.py delivered with the standard gramps tree
> Not in other plugins.
>
> from const import VERSION_TUPLE
> MODULE_VERSION="%1d.%1d" % (VERSION_TUPLE[0], VERSION_TUPLE[1])
>
> then we can use :
> ...
> gramps_target_version = MODULE_VERSION,
> ...
>
> Serge
>>
>> Le 10/04/2012 08:05, jerome a écrit :
>>>> that 'trunk' is more '3.4'
>>> is no more ...
>>>
>>> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :
>>>
>>>> De: jerome<[hidden email]>
>>>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>>>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>
>>>> Date: Mardi 10 avril 2012, 8h03
>>>> Rob,
>>>>
>>>>
>>>> The change was related to behavior pointed out by you.
>>>>
>>>> "I have just realized something of a strange nature!
>>>>
>>>> 1) deleted the whole gramps34 directory...
>>>> 2) deleted the whole .gramps directory this time
>>>> 3) checkout gramps34
>>>> 4) compiled and installed gramps34
>>>> 5) imported my database into gramps34
>>>> 6) clicked on Geography View from the left navigation
>>>> bar...
>>>> 7) it worked, and all five views
>>>>
>>>> 8) closed gramps34
>>>> 0) opened trunk, and geography view was already selected
>>>> 10) it works, and all five views are working!
>>>>
>>>> It appears that gramps34 has GEOGRAPHY PATH already set and
>>>> trunk was able to see it and use it..."
>>>>
>>>> 'trunk' and 'gramps34' have used the same config files
>>>> (.ini, plugins).
>>>> All branches are still sharing 'report_options.xml' and
>>>> 'tool_options.xml'.
>>>>
>>>> By adding new features on trunk, which do not exist on 3.4,
>>>> we are generating strange config files. As you want, I can
>>>> revert the change but we need to keep in mind that 'trunk'
>>>> is more '3.4' and some strange things might happen!
>>>>
>>>>
>>>> Jérôme
>>>>
>>>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>>>> a écrit :
>>>>
>>>>> De: Rob Healey<[hidden email]>
>>>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>>>>> À: "Gramps Development List"<[hidden email]>
>>>>> Date: Mardi 10 avril 2012, 4h33
>>>>> Greetings:
>>>>>
>>>>> Since Jerome made the change to trunk to 3.5.0, I have
>>>> NOT
>>>>> opened a
>>>>> database until now!
>>>>>
>>>>> All of the *.gpr.py files in the plugins directory need
>>>> to
>>>>> be updated
>>>>> from 'gramps_target_version="3.4"' to 3.5 because you
>>>> get a
>>>>> TON of
>>>>> messages on the screen!
>>>>>
>>>>> There will also need to be added a gramps35 to
>>>>> gramps-addons, and copy
>>>>> all of trunk into the new gramps35 directory with the
>>>> above
>>>>> change
>>>>> also to their *.gpr.py files...
>>>>>
>>>>> --
>>>>> Sincerely yours,
>>>>> Rob G. Healey
>>>>>
>>>>>
>>>> ------------------------------------------------------------------------------
>>>>> Better than sec? Nothing is better than sec when it
>>>> comes
>>>>> to
>>>>> monitoring Big Data applications. Try Boundary
>>>> one-second
>>>>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel

Benny Malengier

Re: Re : trunk/ 3.5.0 problems

This is not a good idea.

The idea is that gramplets are tested for the new version, and explicitly indicate they work in the new version. This is like firefox or other software that uses plugins.

It is just as easy to write a sed script to do what you want if one is too lazy to open and test.

Forcing plugins to be by hand changed to the new versions also guarantees somebody still cares about the plugin.
I agree however that some plugins are less suited for this than others, but can't think of a way to have some plugins allow to circumvent it, while others don't.

Benny

2012/4/11 Rob Healey <[hidden email]>

Dear Serge:

I believe that this is a wonderful idea!

Lets suggest it to the entire list???

Sincerely yours,
Rob G. Healey

On Wed, Apr 11, 2012 at 12:54 AM, Serge Noiraud <[hidden email]> wrote:
> Le 11/04/2012 09:35, Serge Noiraud a écrit :
>> Hi,
>>
>> At each times we change the version we must change all *.gpr.py files.
>> perhaps it should be better to use a global variable for this.
>>
>> Serge
> We could use something like the folllowing in each gpr.py delivered with the standard gramps tree
> Not in other plugins.
>
> from const import VERSION_TUPLE
> MODULE_VERSION="%1d.%1d" % (VERSION_TUPLE[0], VERSION_TUPLE[1])
>
> then we can use :
> ...
> gramps_target_version = MODULE_VERSION,
> ...
>
> Serge
>>
>> Le 10/04/2012 08:05, jerome a écrit :
>>>> that 'trunk' is more '3.4'
>>> is no more ...
>>>
>>> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :
>>>
>>>> De: jerome<[hidden email]>
>>>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>>>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>
>>>> Date: Mardi 10 avril 2012, 8h03
>>>> Rob,
>>>>
>>>>
>>>> The change was related to behavior pointed out by you.
>>>>
>>>> "I have just realized something of a strange nature!
>>>>
>>>> 1) deleted the whole gramps34 directory...
>>>> 2) deleted the whole .gramps directory this time
>>>> 3) checkout gramps34
>>>> 4) compiled and installed gramps34
>>>> 5) imported my database into gramps34
>>>> 6) clicked on Geography View from the left navigation
>>>> bar...
>>>> 7) it worked, and all five views
>>>>
>>>> 8) closed gramps34
>>>> 0) opened trunk, and geography view was already selected
>>>> 10) it works, and all five views are working!
>>>>
>>>> It appears that gramps34 has GEOGRAPHY PATH already set and
>>>> trunk was able to see it and use it..."
>>>>
>>>> 'trunk' and 'gramps34' have used the same config files
>>>> (.ini, plugins).
>>>> All branches are still sharing 'report_options.xml' and
>>>> 'tool_options.xml'.
>>>>
>>>> By adding new features on trunk, which do not exist on 3.4,
>>>> we are generating strange config files. As you want, I can
>>>> revert the change but we need to keep in mind that 'trunk'
>>>> is more '3.4' and some strange things might happen!
>>>>
>>>>
>>>> Jérôme
>>>>
>>>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>>>> a écrit :
>>>>
>>>>> De: Rob Healey<[hidden email]>
>>>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>>>>> À: "Gramps Development List"<[hidden email]>
>>>>> Date: Mardi 10 avril 2012, 4h33
>>>>> Greetings:
>>>>>
>>>>> Since Jerome made the change to trunk to 3.5.0, I have
>>>> NOT
>>>>> opened a
>>>>> database until now!
>>>>>
>>>>> All of the *.gpr.py files in the plugins directory need
>>>> to
>>>>> be updated
>>>>> from 'gramps_target_version="3.4"' to 3.5 because you
>>>> get a
>>>>> TON of
>>>>> messages on the screen!
>>>>>
>>>>> There will also need to be added a gramps35 to
>>>>> gramps-addons, and copy
>>>>> all of trunk into the new gramps35 directory with the
>>>> above
>>>>> change
>>>>> also to their *.gpr.py files...
>>>>>
>>>>> --
>>>>> Sincerely yours,
>>>>> Rob G. Healey
>>>>>
>>>>>
>>>> ------------------------------------------------------------------------------
>>>>> Better than sec? Nothing is better than sec when it
>>>> comes
>>>>> to
>>>>> monitoring Big Data applications. Try Boundary
>>>> one-second
>>>>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel

--
Sincerely yours,
Rob G. Healey

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

jerome

Re: Re : trunk/ 3.5.0 problems

In reply to this post by robhealey1

I did not get a chance to test trunk, I just saw that I missed some *.gpr.py files...

Serge fixed the special 'geography' group.

I understand why these files exist:

src/plugins/tool/toolsdebug.gpr.py
src/plugins/gramplet/bottombar.gpr.py

But I wonder why there is some extra files:

src/plugins/view/htmlrenderer.gpr.py
src/plugins/view/fanchartview.gpr.py
src/plugins/view/placetreeview.gpr.py

It looks like feature added during developement.
Maybe the content of these files could be added into the main one for views?

Jérôme

--- En date de : Mer 11.4.12, Benny Malengier <[hidden email]> a écrit :

De: Benny Malengier <[hidden email]>
Objet: Re: [Gramps-devel] Re : trunk/ 3.5.0 problems
À: "Rob Healey" <[hidden email]>
Cc: "Gramps Development List" <[hidden email]>, "Serge Noiraud" <[hidden email]>
Date: Mercredi 11 avril 2012, 10h26

This is not a good idea.

The idea is that gramplets are tested for the new version, and explicitly indicate they work in the new version. This is like firefox or other software that uses plugins.

It is just as easy to write a sed script to do what you want if one is too lazy to open and test.

Forcing plugins to be by hand changed to the new versions also guarantees somebody still cares about the plugin.
I agree however that some plugins are less suited for this than others, but can't think of a way to have some plugins allow to circumvent it, while others don't.

Benny

2012/4/11 Rob Healey <[hidden email]>

Dear Serge:

I believe that this is a wonderful idea!

Lets suggest it to the entire list???

Sincerely yours,

Rob G. Healey

On Wed, Apr 11, 2012 at 12:54 AM, Serge Noiraud <[hidden email]> wrote:

> Le 11/04/2012 09:35, Serge Noiraud a écrit :

>> Hi,

>>

>> At each times we change the version we must change all *.gpr.py files.

>> perhaps it should be better to use a global variable for this.

>>

>> Serge

> We could use something like the folllowing in each gpr.py delivered with the standard gramps tree

> Not in other plugins.

>

> from const import VERSION_TUPLE

> MODULE_VERSION="%1d.%1d" % (VERSION_TUPLE[0], VERSION_TUPLE[1])

>

> then we can use :

> ...

> gramps_target_version = MODULE_VERSION,

> ...

>

> Serge

>>

>> Le 10/04/2012 08:05, jerome a écrit :

>>>> that 'trunk' is more '3.4'

>>> is no more ...

>>>

>>> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :

>>>

>>>> De: jerome<[hidden email]>

>>>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems

>>>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>

>>>> Date: Mardi 10 avril 2012, 8h03

>>>> Rob,

>>>>

>>>>

>>>> The change was related to behavior pointed out by you.

>>>>

>>>> "I have just realized something of a strange nature!

>>>>

>>>> 1) deleted the whole gramps34 directory...

>>>> 2) deleted the whole .gramps directory this time

>>>> 3) checkout gramps34

>>>> 4) compiled and installed gramps34

>>>> 5) imported my database into gramps34

>>>> 6) clicked on Geography View from the left navigation

>>>> bar...

>>>> 7) it worked, and all five views

>>>>

>>>> 8) closed gramps34

>>>> 0) opened trunk, and geography view was already selected

>>>> 10) it works, and all five views are working!

>>>>

>>>> It appears that gramps34 has GEOGRAPHY PATH already set and

>>>> trunk was able to see it and use it..."

>>>>

>>>> 'trunk' and 'gramps34' have used the same config files

>>>> (.ini, plugins).

>>>> All branches are still sharing 'report_options.xml' and

>>>> 'tool_options.xml'.

>>>>

>>>> By adding new features on trunk, which do not exist on 3.4,

>>>> we are generating strange config files. As you want, I can

>>>> revert the change but we need to keep in mind that 'trunk'

>>>> is more '3.4' and some strange things might happen!

>>>>

>>>>

>>>> Jérôme

>>>>

>>>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>

>>>> a écrit :

>>>>

>>>>> De: Rob Healey<[hidden email]>

>>>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems

>>>>> À: "Gramps Development List"<[hidden email]>

>>>>> Date: Mardi 10 avril 2012, 4h33

>>>>> Greetings:

>>>>>

>>>>> Since Jerome made the change to trunk to 3.5.0, I have

>>>> NOT

>>>>> opened a

>>>>> database until now!

>>>>>

>>>>> All of the *.gpr.py files in the plugins directory need

>>>> to

>>>>> be updated

>>>>> from 'gramps_target_version="3.4"' to 3.5 because you

>>>> get a

>>>>> TON of

>>>>> messages on the screen!

>>>>>

>>>>> There will also need to be added a gramps35 to

>>>>> gramps-addons, and copy

>>>>> all of trunk into the new gramps35 directory with the

>>>> above

>>>>> change

>>>>> also to their *.gpr.py files...

>>>>>

>>>>> --

>>>>> Sincerely yours,

>>>>> Rob G. Healey

>>>>>

>>>>>

>>>> ------------------------------------------------------------------------------

>>>>> Better than sec? Nothing is better than sec when it

>>>> comes

>>>>> to

>>>>> monitoring Big Data applications. Try Boundary

>>>> one-second

>>>>

>

> ------------------------------------------------------------------------------

> Better than sec? Nothing is better than sec when it comes to

> monitoring Big Data applications. Try Boundary one-second

> resolution app monitoring today. Free.

> http://p.sf.net/sfu/Boundary-dev2dev

> _______________________________________________

> Gramps-devel mailing list

> [hidden email]

> https://lists.sourceforge.net/lists/listinfo/gramps-devel

--

Sincerely yours,

Rob G. Healey

------------------------------------------------------------------------------

Better than sec? Nothing is better than sec when it comes to

monitoring Big Data applications. Try Boundary one-second

resolution app monitoring today. Free.

http://p.sf.net/sfu/Boundary-dev2dev

_______________________________________________

Gramps-devel mailing list

[hidden email]

https://lists.sourceforge.net/lists/listinfo/gramps-devel

-----La pièce jointe associée suit-----

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
-----La pièce jointe associée suit-----

_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

Serge Noiraud-2

Re: Re : trunk/ 3.5.0 problems

Le 13/04/2012 09:56, jerome a écrit :

> I did not get a chance to test trunk, I just saw that I missed some *.gpr.py files...
>
> Serge fixed the special 'geography' group.
>
> I understand why these files exist:
>
> src/plugins/tool/toolsdebug.gpr.py
> src/plugins/gramplet/bottombar.gpr.py
>
> But I wonder why there is some extra files:
>
> src/plugins/view/htmlrenderer.gpr.py

For the htmlrenderer, I think it's the same problem as the geography module.
This gpr.py is only used to load the module if one of the following library is present :
gtkmozembed or/and webkit.

I can make the same modification as the geography module for this htmlrenderer.gpr.py.

> src/plugins/view/fanchartview.gpr.py
> src/plugins/view/placetreeview.gpr.py
>
> It looks like feature added during developement.
> Maybe the content of these files could be added into the main one for views?
>
>
> Jérôme
>
>
>
> --- En date de : Mer 11.4.12, Benny Malengier<[hidden email]> a écrit :
>
> De: Benny Malengier<[hidden email]>
> Objet: Re: [Gramps-devel] Re : trunk/ 3.5.0 problems
> À: "Rob Healey"<[hidden email]>
> Cc: "Gramps Development List"<[hidden email]>, "Serge Noiraud"<[hidden email]>
> Date: Mercredi 11 avril 2012, 10h26
>
> This is not a good idea.
>
> The idea is that gramplets are tested for the new version, and explicitly indicate they work in the new version. This is like firefox or other software that uses plugins.
>
> It is just as easy to write a sed script to do what you want if one is too lazy to open and test.
>
>
> Forcing plugins to be by hand changed to the new versions also guarantees somebody still cares about the plugin.
> I agree however that some plugins are less suited for this than others, but can't think of a way to have some plugins allow to circumvent it, while others don't.
>
>
> Benny
>
> 2012/4/11 Rob Healey<[hidden email]>
>
> Dear Serge:
>
>
>
> I believe that this is a wonderful idea!
>
>
>
> Lets suggest it to the entire list???
>
>
>
> Sincerely yours,
>
> Rob G. Healey
>
>
>
>
>
> On Wed, Apr 11, 2012 at 12:54 AM, Serge Noiraud<[hidden email]> wrote:
>
>> Le 11/04/2012 09:35, Serge Noiraud a écrit :
>>> Hi,
>>> At each times we change the version we must change all *.gpr.py files.
>>> perhaps it should be better to use a global variable for this.
>>> Serge
>> We could use something like the folllowing in each gpr.py delivered with the standard gramps tree
>> Not in other plugins.
>> from const import VERSION_TUPLE
>> MODULE_VERSION="%1d.%1d" % (VERSION_TUPLE[0], VERSION_TUPLE[1])
>> then we can use :
>> ...
>> gramps_target_version = MODULE_VERSION,
>> ...
>> Serge
>>> Le 10/04/2012 08:05, jerome a écrit :
>>>>> that 'trunk' is more '3.4'
>>>> is no more ...
>>>> --- En date de : Mar 10.4.12, jerome<[hidden email]> a écrit :
>>>>> De: jerome<[hidden email]>
>>>>> Objet: Re : [Gramps-devel] trunk/ 3.5.0 problems
>>>>> À: "Gramps Development List"<[hidden email]>, "Rob Healey"<[hidden email]>
>
>>>>> Date: Mardi 10 avril 2012, 8h03
>>>>> Rob,
>>>>> The change was related to behavior pointed out by you.
>>>>> "I have just realized something of a strange nature!
>>>>> 1) deleted the whole gramps34 directory...
>>>>> 2) deleted the whole .gramps directory this time
>>>>> 3) checkout gramps34
>>>>> 4) compiled and installed gramps34
>>>>> 5) imported my database into gramps34
>>>>> 6) clicked on Geography View from the left navigation
>>>>> bar...
>>>>> 7) it worked, and all five views
>>>>> 8) closed gramps34
>>>>> 0) opened trunk, and geography view was already selected
>>>>> 10) it works, and all five views are working!
>>>>> It appears that gramps34 has GEOGRAPHY PATH already set and
>>>>> trunk was able to see it and use it..."
>>>>> 'trunk' and 'gramps34' have used the same config files
>>>>> (.ini, plugins).
>>>>> All branches are still sharing 'report_options.xml' and
>>>>> 'tool_options.xml'.
>>>>> By adding new features on trunk, which do not exist on 3.4,
>>>>> we are generating strange config files. As you want, I can
>>>>> revert the change but we need to keep in mind that 'trunk'
>>>>> is more '3.4' and some strange things might happen!
>>>>> Jérôme
>>>>> --- En date de : Mar 10.4.12, Rob Healey<[hidden email]>
>>>>> a écrit :
>>>>>> De: Rob Healey<[hidden email]>
>>>>>> Objet: [Gramps-devel] trunk/ 3.5.0 problems
>>>>>> À: "Gramps Development List"<[hidden email]>
>>>>>> Date: Mardi 10 avril 2012, 4h33
>>>>>> Greetings:
>>>>>> Since Jerome made the change to trunk to 3.5.0, I have
>>>>> NOT
>>>>>> opened a
>>>>>> database until now!
>>>>>> All of the *.gpr.py files in the plugins directory need
>>>>> to
>>>>>> be updated
>>>>>> from 'gramps_target_version="3.4"' to 3.5 because you
>>>>> get a
>>>>>> TON of
>>>>>> messages on the screen!
>>>>>> There will also need to be added a gramps35 to
>>>>>> gramps-addons, and copy
>>>>>> all of trunk into the new gramps35 directory with the
>>>>> above
>>>>>> change
>>>>>> also to their *.gpr.py files...
>>>>>> --
>>>>>> Sincerely yours,
>>>>>> Rob G. Healey
> -- Sincerely yours, Rob G. Healey

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

Nick Hall-6

Re: Re : trunk/ 3.5.0 problems

In reply to this post by jerome

On 13/04/12 08:56, jerome wrote:
> I understand why these files exist:
>
> src/plugins/tool/toolsdebug.gpr.py
> src/plugins/gramplet/bottombar.gpr.py

There is no real reason why the bottombar entries are in a separate
file. I am happy for it to be merged into the main file, if this is
more convenient.

> But I wonder why there is some extra files:
>
> src/plugins/view/htmlrenderer.gpr.py
> src/plugins/view/fanchartview.gpr.py
> src/plugins/view/placetreeview.gpr.py
>

The place tree view is in a separate file because it started life as an
experimental view. It can also be moved into the main file. I think
that the fan chart view was originally a third party plugin which would
explain the separate gpr file.

Nick.

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

jerome

Re: Re : trunk/ 3.5.0 problems

Thanks!

done on rev19325:

http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=19325

Jérôme.

Nick Hall a écrit :

> On 13/04/12 08:56, jerome wrote:
>> I understand why these files exist:
>>
>> src/plugins/tool/toolsdebug.gpr.py
>> src/plugins/gramplet/bottombar.gpr.py
>
> There is no real reason why the bottombar entries are in a separate
> file. I am happy for it to be merged into the main file, if this is
> more convenient.
>
>
>> But I wonder why there is some extra files:
>>
>> src/plugins/view/htmlrenderer.gpr.py
>> src/plugins/view/fanchartview.gpr.py
>> src/plugins/view/placetreeview.gpr.py
>>
>
> The place tree view is in a separate file because it started life as an
> experimental view. It can also be moved into the main file. I think
> that the fan chart view was originally a third party plugin which would
> explain the separate gpr file.
>
> Nick.
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>