From: Serge N. <Ser...@fr...> - 2011-01-31 19:54:13
|
Hi, Is there a way to set insensitive the navigation buttons ? example : in Geoview, when we show the geography view for events or places, the backward and forward buttons have no meaning. The same map is used. Do I need to create an issue ? Is there the same functionality for bars. GeoView create filters in the sidebar. if we show the geography view for one person or one family, the filters have no meaning has we have only one selected person or family. Do I need to create an issue ? One another question : If I drag the filter in the sidebar to the bottombar, If I remove it, I can't. I use : self.sidebar.remove_gramplet(self.active_filter) self.active_filter = 'Place Filter Gramplet' self.sidebar.add_gramplet(self.active_filter) The problem is on the remove_gramplet. Is there a better way to do this ? |
From: Nick H. <nic...@ho...> - 2011-02-01 14:44:36
|
Serge Noiraud wrote: > Hi, > > Is there a way to set insensitive the navigation buttons ? > example : in Geoview, when we show the geography view for events or places, > the backward and forward buttons have no meaning. > The same map is used. > Do I need to create an issue ? > In a Navigation View the forward and backward buttons are linked to a history object. The sensitivity of the buttons is set automatically, with the appropriate button set to insensitive when at either the beginning or end of the history. The Navigation View will also handle Bookmarks and the Jump to Gramps ID functionality. Would you want to disable all this functionality? Do you actually want to use a Navigation View? > Is there the same functionality for bars. > GeoView create filters in the sidebar. > if we show the geography view for one person or one family, > the filters have no meaning has we have only one selected person or family. > Do I need to create an issue ? > The filters are now gramplets. Each ListView has the appropriate filter gramplet loaded as a default. At the moment there is nothing to stop a user loading a filter gramplet that has no relevance for the view. This will not cause an error, but will not filter the view. The view also has programmatic control over the gramplets in a GrampsBar. The following public methods are available: add_gramplet(gramplet_name) remove_gramplet(gramplet_name) has_gramplet(gramplet_name) all_gramplets() where the gramplet name is the untranslated name or id of the gramplet. I think that the usage is self-explanatory. Note that add_gramplet will not allow a duplicate to be added and that remove_gramplet will not give an error if the gramplet does not exist. The all_gramplets method will return a list of both gramplets in tabs and detached gramplets. At the moment there is a restriction that it is not possible to remove a detached gramplet. Let me know if you need this functionality extending. > One another question : > If I drag the filter in the sidebar to the bottombar, If I remove it, I can't. > I use : > self.sidebar.remove_gramplet(self.active_filter) > self.active_filter = 'Place Filter Gramplet' > self.sidebar.add_gramplet(self.active_filter) > > The problem is on the remove_gramplet. > Is there a better way to do this ? > Each view creates two GrampsBars (the sidebar and bottombar). They are accessible from the self.sidebar and self.bottombar variables. Nick. > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |
From: Serge N. <Ser...@fr...> - 2011-02-01 18:01:46
|
Le 01/02/2011 15:44, Nick Hall a écrit : > > Serge Noiraud wrote: >> Hi, >> >> Is there a way to set insensitive the navigation buttons ? >> example : in Geoview, when we show the geography view for events or places, >> the backward and forward buttons have no meaning. >> The same map is used. >> Do I need to create an issue ? >> > In a Navigation View the forward and backward buttons are linked to a > history object. The sensitivity of the buttons is set automatically, > with the appropriate button set to insensitive when at either the > beginning or end of the history. > > The Navigation View will also handle Bookmarks and the Jump to Gramps ID > functionality. > > Would you want to disable all this functionality? Do you actually want > to use a Navigation View? I don't want to disallow the navigation. I use it. The problem is in geoview we have four possible maps depending on events, places, the family of the active person and the active person. I use navigation for the two last. For the two first, the navigation as no meaning. This is why I wanted to set the buttons insensitive for them. If it is not possible, it will works, but we will ask to geoview to recreate the html page. This can take a while for big databases. ( 4 minutes for 35000 places ). > >> Is there the same functionality for bars. >> GeoView create filters in the sidebar. >> if we show the geography view for one person or one family, >> the filters have no meaning has we have only one selected person or family. >> Do I need to create an issue ? >> > The filters are now gramplets. Each ListView has the appropriate filter > gramplet loaded as a default. At the moment there is nothing to stop a > user loading a filter gramplet that has no relevance for the view. This > will not cause an error, but will not filter the view. Yes it does. I use it in geoview which is not a listview but a pageview. > The view also has programmatic control over the gramplets in a > GrampsBar. The following public methods are available: > > add_gramplet(gramplet_name) > remove_gramplet(gramplet_name) > has_gramplet(gramplet_name) > all_gramplets() > where the gramplet name is the untranslated name or id of the gramplet. > > I think that the usage is self-explanatory. Note that add_gramplet will > not allow a duplicate to be added and that remove_gramplet will not give > an error if the gramplet does not exist. The all_gramplets method will > return a list of both gramplets in tabs and detached gramplets. If we can't have duplicate gramplets, I can remove it in the sidebar and the bottombar. It will solve my problem for drag and drop. > At the moment there is a restriction that it is not possible to remove a > detached gramplet. > > Let me know if you need this functionality extending. As geoview manage its filters, I think it needs to remove a detached gramplet too. > >> One another question : >> If I drag the filter in the sidebar to the bottombar, If I remove it, I can't. >> I use : >> self.sidebar.remove_gramplet(self.active_filter) >> self.active_filter = 'Place Filter Gramplet' >> self.sidebar.add_gramplet(self.active_filter) >> >> The problem is on the remove_gramplet. >> Is there a better way to do this ? >> > Each view creates two GrampsBars (the sidebar and bottombar). They are > accessible from the self.sidebar and self.bottombar variables. > > > Nick. |
From: Doug B. <dou...@gm...> - 2011-02-01 19:10:27
|
On Tue, Feb 1, 2011 at 2:00 PM, Nick Hall <nic...@ho...> wrote: > > > Serge Noiraud wrote: >> Le 01/02/2011 15:44, Nick Hall a écrit : >>> >>> Serge Noiraud wrote: >>>> Hi, >>>> >>>> Is there a way to set insensitive the navigation buttons ? >>>> example : in Geoview, when we show the geography view for events or >>>> places, >>>> the backward and forward buttons have no meaning. >>>> The same map is used. >>>> Do I need to create an issue ? >>>> >>> In a Navigation View the forward and backward buttons are linked to a >>> history object. The sensitivity of the buttons is set automatically, >>> with the appropriate button set to insensitive when at either the >>> beginning or end of the history. >>> >>> The Navigation View will also handle Bookmarks and the Jump to Gramps ID >>> functionality. >>> >>> Would you want to disable all this functionality? Do you actually want >>> to use a Navigation View? >> I don't want to disallow the navigation. I use it. >> The problem is in geoview we have four possible maps depending on >> events, places, >> the family of the active person and the active person. >> I use navigation for the two last. >> For the two first, the navigation as no meaning. >> This is why I wanted to set the buttons insensitive for them. >> If it is not possible, it will works, but we will ask to geoview to >> recreate the html page. >> This can take a while for big databases. ( 4 minutes for 35000 places ). > > OK. I can see why you want to do this. > > Unfortunately, I don't think it is as simple as making the buttons > insensitive. You will probably find that changing views, using > bookmarks or navigation in another view will cause the buttons to become > sensitive again. You could try it though, and see what happens. > > I suggest you create a feature request. > > >>> >>>> Is there the same functionality for bars. >>>> GeoView create filters in the sidebar. >>>> if we show the geography view for one person or one family, >>>> the filters have no meaning has we have only one selected person or >>>> family. >>>> Do I need to create an issue ? >>>> >>> The filters are now gramplets. Each ListView has the appropriate filter >>> gramplet loaded as a default. At the moment there is nothing to stop a >>> user loading a filter gramplet that has no relevance for the view. This >>> will not cause an error, but will not filter the view. >> Yes it does. I use it in geoview which is not a listview but a pageview. > > All the filter gramplets actually do is set the generic_filter variable > in the view to a filter, and then call the build_tree method. > > So you are correct, any view written to use a filter in the build_tree > can use a filter gramplet. I don't think that any other view apart from > GeoView and the ListViews use the generic_filter variable. > > >>> The view also has programmatic control over the gramplets in a >>> GrampsBar. The following public methods are available: >>> >>> add_gramplet(gramplet_name) >>> remove_gramplet(gramplet_name) >>> has_gramplet(gramplet_name) >>> all_gramplets() >> >>> where the gramplet name is the untranslated name or id of the gramplet. >>> >>> I think that the usage is self-explanatory. Note that add_gramplet will >>> not allow a duplicate to be added and that remove_gramplet will not give >>> an error if the gramplet does not exist. The all_gramplets method will >>> return a list of both gramplets in tabs and detached gramplets. >> If we can't have duplicate gramplets, I can remove it in the sidebar >> and the bottombar. >> It will solve my problem for drag and drop. > > It is actually possible to have duplicate gramplets. If you create a > gramplet in both the sidebar and bottombar, then you can drag one into > the other. > > I could disable drag and drop between the sidebar and bottombar. > > The Gramplet View allows duplicate gramplets though. I don't know how > useful this is. > > I think we need Doug's input here. Regarding duplicate gramplets: Yes, this is useful (given that we can configure gramplets). For example, the QuickView Gramplet allows you to run any Quick view of your choice. So, you might have one configured to run one QV, and another QuickView Gramplet to run another QV. We could make each one of those its own Gramplet, but that sounds like a lot of gramplets. I like the ability to drag gramplets between bars. This is looking very nice, Nick! -Doug > > >>> At the moment there is a restriction that it is not possible to remove a >>> detached gramplet. >>> >>> Let me know if you need this functionality extending. >> As geoview manage its filters, I think it needs to remove a detached >> gramplet too. > > I regard this as a bug so I'll look into it. I don't think that it > should be too difficult to fix. > > > Nick. > > >>> >>>> One another question : >>>> If I drag the filter in the sidebar to the bottombar, If I remove >>>> it, I can't. >>>> I use : >>>> self.sidebar.remove_gramplet(self.active_filter) >>>> self.active_filter = 'Place Filter Gramplet' >>>> self.sidebar.add_gramplet(self.active_filter) >>>> >>>> The problem is on the remove_gramplet. >>>> Is there a better way to do this ? >>>> >>> Each view creates two GrampsBars (the sidebar and bottombar). They are >>> accessible from the self.sidebar and self.bottombar variables. >>> >>> >>> Nick. >> >> > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2011-02-02 15:18:51
|
Rob Healey wrote: > Dear Nick: > > I also like using the QuickViews... I will make sure that the GrampsBar works with the QuickView gramplet. I need to think about how we change the tab label, and if we allow the user to do this. > > I also like having the ability of dragging gramplets from sidebar to > bottombar, so please do whatever it is possible to keep this... Thanks for your opinion. When I added this functionality I didn't know if it would be useful, or if users would like it. I thought that some gramplets would look better displayed horizontally and others vertically. I will keep it for the moment and see what other users think. > > I do not understand what the big deal is about having to have sidebar > or bottombar available in GeoView! We need to preserve the existing functionality, so the GeoView should be able to control the filter gramplets in the sidebar. If it is convenient to disable the bottombar we could consider that. Nick. > Simply disable it!!! Dp NOT give the user the option of doing so in > GeoView! > > Sincerely yours, > Rob G. Healey > > On Tue, Feb 1, 2011 at 11:10 AM, Doug Blank <dou...@gm... > <mailto:dou...@gm...>> wrote: > > On Tue, Feb 1, 2011 at 2:00 PM, Nick Hall <nic...@ho... > <mailto:nic...@ho...>> wrote: > > > > > > Serge Noiraud wrote: > >> Le 01/02/2011 15:44, Nick Hall a écrit : > >>> > >>> Serge Noiraud wrote: > >>>> Hi, > >>>> > >>>> Is there a way to set insensitive the navigation buttons ? > >>>> example : in Geoview, when we show the geography view for > events or > >>>> places, > >>>> the backward and forward buttons have no meaning. > >>>> The same map is used. > >>>> Do I need to create an issue ? > >>>> > >>> In a Navigation View the forward and backward buttons are > linked to a > >>> history object. The sensitivity of the buttons is set > automatically, > >>> with the appropriate button set to insensitive when at either the > >>> beginning or end of the history. > >>> > >>> The Navigation View will also handle Bookmarks and the Jump to > Gramps ID > >>> functionality. > >>> > >>> Would you want to disable all this functionality? Do you > actually want > >>> to use a Navigation View? > >> I don't want to disallow the navigation. I use it. > >> The problem is in geoview we have four possible maps depending on > >> events, places, > >> the family of the active person and the active person. > >> I use navigation for the two last. > >> For the two first, the navigation as no meaning. > >> This is why I wanted to set the buttons insensitive for them. > >> If it is not possible, it will works, but we will ask to geoview to > >> recreate the html page. > >> This can take a while for big databases. ( 4 minutes for 35000 > places ). > > > > OK. I can see why you want to do this. > > > > Unfortunately, I don't think it is as simple as making the buttons > > insensitive. You will probably find that changing views, using > > bookmarks or navigation in another view will cause the buttons > to become > > sensitive again. You could try it though, and see what happens. > > > > I suggest you create a feature request. > > > > > >>> > >>>> Is there the same functionality for bars. > >>>> GeoView create filters in the sidebar. > >>>> if we show the geography view for one person or one family, > >>>> the filters have no meaning has we have only one selected > person or > >>>> family. > >>>> Do I need to create an issue ? > >>>> > >>> The filters are now gramplets. Each ListView has the > appropriate filter > >>> gramplet loaded as a default. At the moment there is nothing > to stop a > >>> user loading a filter gramplet that has no relevance for the > view. This > >>> will not cause an error, but will not filter the view. > >> Yes it does. I use it in geoview which is not a listview but a > pageview. > > > > All the filter gramplets actually do is set the generic_filter > variable > > in the view to a filter, and then call the build_tree method. > > > > So you are correct, any view written to use a filter in the > build_tree > > can use a filter gramplet. I don't think that any other view > apart from > > GeoView and the ListViews use the generic_filter variable. > > > > > >>> The view also has programmatic control over the gramplets in a > >>> GrampsBar. The following public methods are available: > >>> > >>> add_gramplet(gramplet_name) > >>> remove_gramplet(gramplet_name) > >>> has_gramplet(gramplet_name) > >>> all_gramplets() > >> > >>> where the gramplet name is the untranslated name or id of the > gramplet. > >>> > >>> I think that the usage is self-explanatory. Note that > add_gramplet will > >>> not allow a duplicate to be added and that remove_gramplet > will not give > >>> an error if the gramplet does not exist. The all_gramplets > method will > >>> return a list of both gramplets in tabs and detached gramplets. > >> If we can't have duplicate gramplets, I can remove it in the > sidebar > >> and the bottombar. > >> It will solve my problem for drag and drop. > > > > It is actually possible to have duplicate gramplets. If you > create a > > gramplet in both the sidebar and bottombar, then you can drag > one into > > the other. > > > > I could disable drag and drop between the sidebar and bottombar. > > > > The Gramplet View allows duplicate gramplets though. I don't > know how > > useful this is. > > > > I think we need Doug's input here. > > Regarding duplicate gramplets: Yes, this is useful (given that we can > configure gramplets). For example, the QuickView Gramplet allows you > to run any Quick view of your choice. So, you might have one > configured to run one QV, and another QuickView Gramplet to run > another QV. We could make each one of those its own Gramplet, but that > sounds like a lot of gramplets. > > I like the ability to drag gramplets between bars. > > This is looking very nice, Nick! > > -Doug > > > > > > >>> At the moment there is a restriction that it is not possible > to remove a > >>> detached gramplet. > >>> > >>> Let me know if you need this functionality extending. > >> As geoview manage its filters, I think it needs to remove a > detached > >> gramplet too. > > > > I regard this as a bug so I'll look into it. I don't think that it > > should be too difficult to fix. > > > > > > Nick. > > > > > >>> > >>>> One another question : > >>>> If I drag the filter in the sidebar to the bottombar, If I remove > >>>> it, I can't. > >>>> I use : > >>>> self.sidebar.remove_gramplet(self.active_filter) > >>>> self.active_filter = 'Place Filter Gramplet' > >>>> self.sidebar.add_gramplet(self.active_filter) > >>>> > >>>> The problem is on the remove_gramplet. > >>>> Is there a better way to do this ? > >>>> > >>> Each view creates two GrampsBars (the sidebar and bottombar). > They are > >>> accessible from the self.sidebar and self.bottombar variables. > >>> > >>> > >>> Nick. > >> > >> > > > > > ------------------------------------------------------------------------------ > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > > Finally, a world-class log management solution at an even better > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > <mailto:Gra...@li...> > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > <mailto:Gra...@li...> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > ------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Rob H. <rob...@gm...> - 2011-02-03 01:26:20
|
Dear Nick: On Wed, Feb 2, 2011 at 7:18 AM, Nick Hall <nic...@ho...> wrote: > > > Rob Healey wrote: > >> Dear Nick: >> >> I also like using the QuickViews... >> > > I will make sure that the GrampsBar works with the QuickView gramplet. > I know that I appreciate it for sure... > > I need to think about how we change the tab label, and if we allow the user > to do this. > I am NOT sure what would need to be configured by the user when it comes to the label??? > > > >> I also like having the ability of dragging gramplets from sidebar to >> bottombar, so please do whatever it is possible to keep this... >> > > Thanks for your opinion. When I added this functionality I didn't know if > it would be useful, or if users would like it. I thought that some > gramplets would look better displayed horizontally and others vertically. > I truly agree with you! I believe that there are gramplets that look better by being either vertical or horizontal! For example, unless I was able to control how wide it is displayed, Image Metadata Gramplet does NOT look good horizontally! > > I will keep it for the moment and see what other users think. > > > >> I do not understand what the big deal is about having to have sidebar or >> bottombar available in GeoView! >> > > We need to preserve the existing functionality, so the GeoView should be > able to control the filter gramplets in the sidebar. If it is convenient to > disable the bottombar we could consider that. > You were able to exclude the bottombar of not being able to be activated in the GrampletView! So why would it be so hard... Sincerely yours, Rob G. Healey > > > Nick. > > > Simply disable it!!! Dp NOT give the user the option of doing so in >> GeoView! >> >> Sincerely yours, >> Rob G. Healey >> >> On Tue, Feb 1, 2011 at 11:10 AM, Doug Blank <dou...@gm...<mailto: >> dou...@gm...>> wrote: >> >> On Tue, Feb 1, 2011 at 2:00 PM, Nick Hall <nic...@ho... >> <mailto:nic...@ho...>> wrote: >> > >> > >> > Serge Noiraud wrote: >> >> Le 01/02/2011 15:44, Nick Hall a écrit : >> >>> >> >>> Serge Noiraud wrote: >> >>>> Hi, >> >>>> >> >>>> Is there a way to set insensitive the navigation buttons ? >> >>>> example : in Geoview, when we show the geography view for >> events or >> >>>> places, >> >>>> the backward and forward buttons have no meaning. >> >>>> The same map is used. >> >>>> Do I need to create an issue ? >> >>>> >> >>> In a Navigation View the forward and backward buttons are >> linked to a >> >>> history object. The sensitivity of the buttons is set >> automatically, >> >>> with the appropriate button set to insensitive when at either the >> >>> beginning or end of the history. >> >>> >> >>> The Navigation View will also handle Bookmarks and the Jump to >> Gramps ID >> >>> functionality. >> >>> >> >>> Would you want to disable all this functionality? Do you >> actually want >> >>> to use a Navigation View? >> >> I don't want to disallow the navigation. I use it. >> >> The problem is in geoview we have four possible maps depending on >> >> events, places, >> >> the family of the active person and the active person. >> >> I use navigation for the two last. >> >> For the two first, the navigation as no meaning. >> >> This is why I wanted to set the buttons insensitive for them. >> >> If it is not possible, it will works, but we will ask to geoview to >> >> recreate the html page. >> >> This can take a while for big databases. ( 4 minutes for 35000 >> places ). >> > >> > OK. I can see why you want to do this. >> > >> > Unfortunately, I don't think it is as simple as making the buttons >> > insensitive. You will probably find that changing views, using >> > bookmarks or navigation in another view will cause the buttons >> to become >> > sensitive again. You could try it though, and see what happens. >> > >> > I suggest you create a feature request. >> > >> > >> >>> >> >>>> Is there the same functionality for bars. >> >>>> GeoView create filters in the sidebar. >> >>>> if we show the geography view for one person or one family, >> >>>> the filters have no meaning has we have only one selected >> person or >> >>>> family. >> >>>> Do I need to create an issue ? >> >>>> >> >>> The filters are now gramplets. Each ListView has the >> appropriate filter >> >>> gramplet loaded as a default. At the moment there is nothing >> to stop a >> >>> user loading a filter gramplet that has no relevance for the >> view. This >> >>> will not cause an error, but will not filter the view. >> >> Yes it does. I use it in geoview which is not a listview but a >> pageview. >> > >> > All the filter gramplets actually do is set the generic_filter >> variable >> > in the view to a filter, and then call the build_tree method. >> > >> > So you are correct, any view written to use a filter in the >> build_tree >> > can use a filter gramplet. I don't think that any other view >> apart from >> > GeoView and the ListViews use the generic_filter variable. >> > >> > >> >>> The view also has programmatic control over the gramplets in a >> >>> GrampsBar. The following public methods are available: >> >>> >> >>> add_gramplet(gramplet_name) >> >>> remove_gramplet(gramplet_name) >> >>> has_gramplet(gramplet_name) >> >>> all_gramplets() >> >> >> >>> where the gramplet name is the untranslated name or id of the >> gramplet. >> >>> >> >>> I think that the usage is self-explanatory. Note that >> add_gramplet will >> >>> not allow a duplicate to be added and that remove_gramplet >> will not give >> >>> an error if the gramplet does not exist. The all_gramplets >> method will >> >>> return a list of both gramplets in tabs and detached gramplets. >> >> If we can't have duplicate gramplets, I can remove it in the >> sidebar >> >> and the bottombar. >> >> It will solve my problem for drag and drop. >> > >> > It is actually possible to have duplicate gramplets. If you >> create a >> > gramplet in both the sidebar and bottombar, then you can drag >> one into >> > the other. >> > >> > I could disable drag and drop between the sidebar and bottombar. >> > >> > The Gramplet View allows duplicate gramplets though. I don't >> know how >> > useful this is. >> > >> > I think we need Doug's input here. >> >> Regarding duplicate gramplets: Yes, this is useful (given that we can >> configure gramplets). For example, the QuickView Gramplet allows you >> to run any Quick view of your choice. So, you might have one >> configured to run one QV, and another QuickView Gramplet to run >> another QV. We could make each one of those its own Gramplet, but that >> sounds like a lot of gramplets. >> >> I like the ability to drag gramplets between bars. >> >> This is looking very nice, Nick! >> >> -Doug >> >> > >> > >> >>> At the moment there is a restriction that it is not possible >> to remove a >> >>> detached gramplet. >> >>> >> >>> Let me know if you need this functionality extending. >> >> As geoview manage its filters, I think it needs to remove a >> detached >> >> gramplet too. >> > >> > I regard this as a bug so I'll look into it. I don't think that it >> > should be too difficult to fix. >> > >> > >> > Nick. >> > >> > >> >>> >> >>>> One another question : >> >>>> If I drag the filter in the sidebar to the bottombar, If I remove >> >>>> it, I can't. >> >>>> I use : >> >>>> self.sidebar.remove_gramplet(self.active_filter) >> >>>> self.active_filter = 'Place Filter Gramplet' >> >>>> self.sidebar.add_gramplet(self.active_filter) >> >>>> >> >>>> The problem is on the remove_gramplet. >> >>>> Is there a better way to do this ? >> >>>> >> >>> Each view creates two GrampsBars (the sidebar and bottombar). >> They are >> >>> accessible from the self.sidebar and self.bottombar variables. >> >>> >> >>> >> >>> Nick. >> >> >> >> >> > >> > >> >> ------------------------------------------------------------------------------ >> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> > Finally, a world-class log management solution at an even better >> price-free! >> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> > February 28th, so secure your free ArcSight Logger TODAY! >> > http://p.sf.net/sfu/arcsight-sfd2d >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> <mailto:Gra...@li...> >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> <mailto:Gra...@li...> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> >> ------------------------------------------------------------------------ >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires February >> 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > |
From: Nick H. <nic...@ho...> - 2011-02-01 19:01:11
|
Serge Noiraud wrote: > Le 01/02/2011 15:44, Nick Hall a écrit : >> >> Serge Noiraud wrote: >>> Hi, >>> >>> Is there a way to set insensitive the navigation buttons ? >>> example : in Geoview, when we show the geography view for events or >>> places, >>> the backward and forward buttons have no meaning. >>> The same map is used. >>> Do I need to create an issue ? >>> >> In a Navigation View the forward and backward buttons are linked to a >> history object. The sensitivity of the buttons is set automatically, >> with the appropriate button set to insensitive when at either the >> beginning or end of the history. >> >> The Navigation View will also handle Bookmarks and the Jump to Gramps ID >> functionality. >> >> Would you want to disable all this functionality? Do you actually want >> to use a Navigation View? > I don't want to disallow the navigation. I use it. > The problem is in geoview we have four possible maps depending on > events, places, > the family of the active person and the active person. > I use navigation for the two last. > For the two first, the navigation as no meaning. > This is why I wanted to set the buttons insensitive for them. > If it is not possible, it will works, but we will ask to geoview to > recreate the html page. > This can take a while for big databases. ( 4 minutes for 35000 places ). OK. I can see why you want to do this. Unfortunately, I don't think it is as simple as making the buttons insensitive. You will probably find that changing views, using bookmarks or navigation in another view will cause the buttons to become sensitive again. You could try it though, and see what happens. I suggest you create a feature request. >> >>> Is there the same functionality for bars. >>> GeoView create filters in the sidebar. >>> if we show the geography view for one person or one family, >>> the filters have no meaning has we have only one selected person or >>> family. >>> Do I need to create an issue ? >>> >> The filters are now gramplets. Each ListView has the appropriate filter >> gramplet loaded as a default. At the moment there is nothing to stop a >> user loading a filter gramplet that has no relevance for the view. This >> will not cause an error, but will not filter the view. > Yes it does. I use it in geoview which is not a listview but a pageview. All the filter gramplets actually do is set the generic_filter variable in the view to a filter, and then call the build_tree method. So you are correct, any view written to use a filter in the build_tree can use a filter gramplet. I don't think that any other view apart from GeoView and the ListViews use the generic_filter variable. >> The view also has programmatic control over the gramplets in a >> GrampsBar. The following public methods are available: >> >> add_gramplet(gramplet_name) >> remove_gramplet(gramplet_name) >> has_gramplet(gramplet_name) >> all_gramplets() > >> where the gramplet name is the untranslated name or id of the gramplet. >> >> I think that the usage is self-explanatory. Note that add_gramplet will >> not allow a duplicate to be added and that remove_gramplet will not give >> an error if the gramplet does not exist. The all_gramplets method will >> return a list of both gramplets in tabs and detached gramplets. > If we can't have duplicate gramplets, I can remove it in the sidebar > and the bottombar. > It will solve my problem for drag and drop. It is actually possible to have duplicate gramplets. If you create a gramplet in both the sidebar and bottombar, then you can drag one into the other. I could disable drag and drop between the sidebar and bottombar. The Gramplet View allows duplicate gramplets though. I don't know how useful this is. I think we need Doug's input here. >> At the moment there is a restriction that it is not possible to remove a >> detached gramplet. >> >> Let me know if you need this functionality extending. > As geoview manage its filters, I think it needs to remove a detached > gramplet too. I regard this as a bug so I'll look into it. I don't think that it should be too difficult to fix. Nick. >> >>> One another question : >>> If I drag the filter in the sidebar to the bottombar, If I remove >>> it, I can't. >>> I use : >>> self.sidebar.remove_gramplet(self.active_filter) >>> self.active_filter = 'Place Filter Gramplet' >>> self.sidebar.add_gramplet(self.active_filter) >>> >>> The problem is on the remove_gramplet. >>> Is there a better way to do this ? >>> >> Each view creates two GrampsBars (the sidebar and bottombar). They are >> accessible from the self.sidebar and self.bottombar variables. >> >> >> Nick. > > |
From: Nick H. <nic...@ho...> - 2011-02-02 20:02:55
|
Nick Hall wrote: > Serge Noiraud wrote: > >> Le 01/02/2011 15:44, Nick Hall a écrit : >> >>> Serge Noiraud wrote: >>> >>>> Hi, >>>> >>>> Is there a way to set insensitive the navigation buttons ? >>>> example : in Geoview, when we show the geography view for events or >>>> places, >>>> the backward and forward buttons have no meaning. >>>> The same map is used. >>>> Do I need to create an issue ? >>>> >>>> >>> In a Navigation View the forward and backward buttons are linked to a >>> history object. The sensitivity of the buttons is set automatically, >>> with the appropriate button set to insensitive when at either the >>> beginning or end of the history. >>> >>> The Navigation View will also handle Bookmarks and the Jump to Gramps ID >>> functionality. >>> >>> Would you want to disable all this functionality? Do you actually want >>> to use a Navigation View? >>> >> I don't want to disallow the navigation. I use it. >> The problem is in geoview we have four possible maps depending on >> events, places, >> the family of the active person and the active person. >> I use navigation for the two last. >> For the two first, the navigation as no meaning. >> This is why I wanted to set the buttons insensitive for them. >> If it is not possible, it will works, but we will ask to geoview to >> recreate the html page. >> This can take a while for big databases. ( 4 minutes for 35000 places ). >> > > OK. I can see why you want to do this. > > Unfortunately, I don't think it is as simple as making the buttons > insensitive. You will probably find that changing views, using > bookmarks or navigation in another view will cause the buttons to become > sensitive again. You could try it though, and see what happens. > > I suggest you create a feature request. > > > >>>> Is there the same functionality for bars. >>>> GeoView create filters in the sidebar. >>>> if we show the geography view for one person or one family, >>>> the filters have no meaning has we have only one selected person or >>>> family. >>>> Do I need to create an issue ? >>>> >>>> >>> The filters are now gramplets. Each ListView has the appropriate filter >>> gramplet loaded as a default. At the moment there is nothing to stop a >>> user loading a filter gramplet that has no relevance for the view. This >>> will not cause an error, but will not filter the view. >>> >> Yes it does. I use it in geoview which is not a listview but a pageview. >> > > All the filter gramplets actually do is set the generic_filter variable > in the view to a filter, and then call the build_tree method. > > So you are correct, any view written to use a filter in the build_tree > can use a filter gramplet. I don't think that any other view apart from > GeoView and the ListViews use the generic_filter variable. > > > >>> The view also has programmatic control over the gramplets in a >>> GrampsBar. The following public methods are available: >>> >>> add_gramplet(gramplet_name) >>> remove_gramplet(gramplet_name) >>> has_gramplet(gramplet_name) >>> all_gramplets() >>> >>> where the gramplet name is the untranslated name or id of the gramplet. >>> >>> I think that the usage is self-explanatory. Note that add_gramplet will >>> not allow a duplicate to be added and that remove_gramplet will not give >>> an error if the gramplet does not exist. The all_gramplets method will >>> return a list of both gramplets in tabs and detached gramplets. >>> >> If we can't have duplicate gramplets, I can remove it in the sidebar >> and the bottombar. >> It will solve my problem for drag and drop. >> > > It is actually possible to have duplicate gramplets. If you create a > gramplet in both the sidebar and bottombar, then you can drag one into > the other. > > I could disable drag and drop between the sidebar and bottombar. > > The Gramplet View allows duplicate gramplets though. I don't know how > useful this is. > > I think we need Doug's input here. > > > >>> At the moment there is a restriction that it is not possible to remove a >>> detached gramplet. >>> >>> Let me know if you need this functionality extending. >>> >> As geoview manage its filters, I think it needs to remove a detached >> gramplet too. >> > > I regard this as a bug so I'll look into it. I don't think that it > should be too difficult to fix. > This is now fixed. The remove_gramplet method will now remove a gramplet from the GrampsBar even if it is detached. Nick. > > Nick. > > > >>>> One another question : >>>> If I drag the filter in the sidebar to the bottombar, If I remove >>>> it, I can't. >>>> I use : >>>> self.sidebar.remove_gramplet(self.active_filter) >>>> self.active_filter = 'Place Filter Gramplet' >>>> self.sidebar.add_gramplet(self.active_filter) >>>> >>>> The problem is on the remove_gramplet. >>>> Is there a better way to do this ? >>>> >>>> >>> Each view creates two GrampsBars (the sidebar and bottombar). They are >>> accessible from the self.sidebar and self.bottombar variables. >>> >>> >>> Nick. >>> >> > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Rob H. <rob...@gm...> - 2011-02-02 03:04:44
|
Dear Nick: I also like using the QuickViews... I also like having the ability of dragging gramplets from sidebar to bottombar, so please do whatever it is possible to keep this... I do not understand what the big deal is about having to have sidebar or bottombar available in GeoView! Simply disable it!!! Dp NOT give the user the option of doing so in GeoView! Sincerely yours, Rob G. Healey On Tue, Feb 1, 2011 at 11:10 AM, Doug Blank <dou...@gm...> wrote: > On Tue, Feb 1, 2011 at 2:00 PM, Nick Hall <nic...@ho...> wrote: > > > > > > Serge Noiraud wrote: > >> Le 01/02/2011 15:44, Nick Hall a écrit : > >>> > >>> Serge Noiraud wrote: > >>>> Hi, > >>>> > >>>> Is there a way to set insensitive the navigation buttons ? > >>>> example : in Geoview, when we show the geography view for events or > >>>> places, > >>>> the backward and forward buttons have no meaning. > >>>> The same map is used. > >>>> Do I need to create an issue ? > >>>> > >>> In a Navigation View the forward and backward buttons are linked to a > >>> history object. The sensitivity of the buttons is set automatically, > >>> with the appropriate button set to insensitive when at either the > >>> beginning or end of the history. > >>> > >>> The Navigation View will also handle Bookmarks and the Jump to Gramps > ID > >>> functionality. > >>> > >>> Would you want to disable all this functionality? Do you actually want > >>> to use a Navigation View? > >> I don't want to disallow the navigation. I use it. > >> The problem is in geoview we have four possible maps depending on > >> events, places, > >> the family of the active person and the active person. > >> I use navigation for the two last. > >> For the two first, the navigation as no meaning. > >> This is why I wanted to set the buttons insensitive for them. > >> If it is not possible, it will works, but we will ask to geoview to > >> recreate the html page. > >> This can take a while for big databases. ( 4 minutes for 35000 places ). > > > > OK. I can see why you want to do this. > > > > Unfortunately, I don't think it is as simple as making the buttons > > insensitive. You will probably find that changing views, using > > bookmarks or navigation in another view will cause the buttons to become > > sensitive again. You could try it though, and see what happens. > > > > I suggest you create a feature request. > > > > > >>> > >>>> Is there the same functionality for bars. > >>>> GeoView create filters in the sidebar. > >>>> if we show the geography view for one person or one family, > >>>> the filters have no meaning has we have only one selected person or > >>>> family. > >>>> Do I need to create an issue ? > >>>> > >>> The filters are now gramplets. Each ListView has the appropriate filter > >>> gramplet loaded as a default. At the moment there is nothing to stop a > >>> user loading a filter gramplet that has no relevance for the view. This > >>> will not cause an error, but will not filter the view. > >> Yes it does. I use it in geoview which is not a listview but a pageview. > > > > All the filter gramplets actually do is set the generic_filter variable > > in the view to a filter, and then call the build_tree method. > > > > So you are correct, any view written to use a filter in the build_tree > > can use a filter gramplet. I don't think that any other view apart from > > GeoView and the ListViews use the generic_filter variable. > > > > > >>> The view also has programmatic control over the gramplets in a > >>> GrampsBar. The following public methods are available: > >>> > >>> add_gramplet(gramplet_name) > >>> remove_gramplet(gramplet_name) > >>> has_gramplet(gramplet_name) > >>> all_gramplets() > >> > >>> where the gramplet name is the untranslated name or id of the gramplet. > >>> > >>> I think that the usage is self-explanatory. Note that add_gramplet will > >>> not allow a duplicate to be added and that remove_gramplet will not > give > >>> an error if the gramplet does not exist. The all_gramplets method will > >>> return a list of both gramplets in tabs and detached gramplets. > >> If we can't have duplicate gramplets, I can remove it in the sidebar > >> and the bottombar. > >> It will solve my problem for drag and drop. > > > > It is actually possible to have duplicate gramplets. If you create a > > gramplet in both the sidebar and bottombar, then you can drag one into > > the other. > > > > I could disable drag and drop between the sidebar and bottombar. > > > > The Gramplet View allows duplicate gramplets though. I don't know how > > useful this is. > > > > I think we need Doug's input here. > > Regarding duplicate gramplets: Yes, this is useful (given that we can > configure gramplets). For example, the QuickView Gramplet allows you > to run any Quick view of your choice. So, you might have one > configured to run one QV, and another QuickView Gramplet to run > another QV. We could make each one of those its own Gramplet, but that > sounds like a lot of gramplets. > > I like the ability to drag gramplets between bars. > > This is looking very nice, Nick! > > -Doug > > > > > > >>> At the moment there is a restriction that it is not possible to remove > a > >>> detached gramplet. > >>> > >>> Let me know if you need this functionality extending. > >> As geoview manage its filters, I think it needs to remove a detached > >> gramplet too. > > > > I regard this as a bug so I'll look into it. I don't think that it > > should be too difficult to fix. > > > > > > Nick. > > > > > >>> > >>>> One another question : > >>>> If I drag the filter in the sidebar to the bottombar, If I remove > >>>> it, I can't. > >>>> I use : > >>>> self.sidebar.remove_gramplet(self.active_filter) > >>>> self.active_filter = 'Place Filter Gramplet' > >>>> self.sidebar.add_gramplet(self.active_filter) > >>>> > >>>> The problem is on the remove_gramplet. > >>>> Is there a better way to do this ? > >>>> > >>> Each view creates two GrampsBars (the sidebar and bottombar). They are > >>> accessible from the self.sidebar and self.bottombar variables. > >>> > >>> > >>> Nick. > >> > >> > > > > > ------------------------------------------------------------------------------ > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > > Finally, a world-class log management solution at an even better > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |