From: Nick H. <nic...@ho...> - 2011-01-11 01:50:48
|
Devs, I have just committed a change which adds a new bottombar to Gramps. You can enable the bottom bar from the menu: View -> Bottombar. Each tab contains one gramplet. You can re-order them by drag-and-drop. There are three buttons on the right hand side of the bottombar. Use these to add or remove gramplets and also to close the bottombar. I have removed the normal gramplet controls. This creates more space and presents a cleaner interface to the user. The minimise button is not applicable for the bottom bar, and drag-and-drop functionality has moved to the tab. I have not implemented detaching of gramplets yet, but this could be achieved by dragging the tab out of the notebook (this is standard gtk functionality). I have written four example bottombar gramplets for the Person Views: 1. Details: This combines the primary picture, with parents, events and attributes to create a summary view for a person. 2. Gallery: This displays the pictures of a person in a scrollable list. Double-click to view the image with the default viewer application. 3. Residence: An example displaying a single event type. Double-click to edit an event. 4. Attributes: Just a GUI version of the existing Attributes gramplet. Double-click for the quick report. I was trying to make the gramplets look like they are part of core Gramps. Similar functionality is available in the person editor, but the bottom bar gramplets are intended to be optimised for viewing the data rather than editing it. I look forward to your feedback. Regards, Nick. |
From: Doug B. <dou...@gm...> - 2011-01-11 02:04:36
|
Nick, Having troubling running trunk: 22061: ERROR: gramps.py: line 142: Unhandled exception Traceback (most recent call last): File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, in view_changed self.__change_page(page_num) File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1214, in __change_page self.active_page.set_active() File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", line 220, in set_active ListView.set_active(self) File "/home/dblank/gramps/trunk/src/gui/views/listview.py", line 240, in set_active NavigationView.set_active(self) File "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", line 153, in set_active PageView.set_active(self) File "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line 379, in set_active self.bottombar.set_active() File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, in set_active title = get_title(self.notebook, page) File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, in get_title return notebook.get_tab_label_text(notebook.get_nth_page(page_num)) TypeError: Gtk.Notebook.get_tab_label_text() argument 1 must be gtk.Widget, not None 29382: ERROR: gramps.py: line 142: Unhandled exception Traceback (most recent call last): File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, in view_changed self.__change_page(page_num) File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1211, in __change_page self.__disconnect_previous_page() File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1241, in __disconnect_previous_page self.active_page.set_inactive() File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", line 228, in set_inactive self.uistate.viewmanager.tags.tag_disable() File "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, in tag_disable self.uistate.uimanager.remove_ui(self.tag_id) TypeError: Parameter 'merge_id' must be an int or a long I deleted my ~/.gramps/gramps33/*.ini files, but no avail. -Doug On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: > Devs, > > I have just committed a change which adds a new bottombar to Gramps. > > You can enable the bottom bar from the menu: View -> Bottombar. > > Each tab contains one gramplet. You can re-order them by drag-and-drop. > > There are three buttons on the right hand side of the bottombar. Use > these to add or remove gramplets and also to close the bottombar. > > I have removed the normal gramplet controls. This creates more space > and presents a cleaner interface to the user. The minimise button is > not applicable for the bottom bar, and drag-and-drop functionality has > moved to the tab. I have not implemented detaching of gramplets yet, > but this could be achieved by dragging the tab out of the notebook (this > is standard gtk functionality). > > I have written four example bottombar gramplets for the Person Views: > > 1. Details: This combines the primary picture, with parents, events and > attributes to create a summary view for a person. > > 2. Gallery: This displays the pictures of a person in a scrollable > list. Double-click to view the image with the default viewer application. > > 3. Residence: An example displaying a single event type. Double-click > to edit an event. > > 4. Attributes: Just a GUI version of the existing Attributes gramplet. > Double-click for the quick report. > > I was trying to make the gramplets look like they are part of core > Gramps. Similar functionality is available in the person editor, but > the bottom bar gramplets are intended to be optimised for viewing the > data rather than editing it. > > I look forward to your feedback. > > Regards, > > > Nick. > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2011-01-11 11:37:29
|
Doug, I'll look into it. Nick. Doug Blank wrote: > Nick, > > Having troubling running trunk: > > 22061: ERROR: gramps.py: line 142: Unhandled exception > Traceback (most recent call last): > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, > in view_changed > self.__change_page(page_num) > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1214, > in __change_page > self.active_page.set_active() > File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > line 220, in set_active > ListView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/listview.py", line > 240, in set_active > NavigationView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", > line 153, in set_active > PageView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line > 379, in set_active > self.bottombar.set_active() > File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, in set_active > title = get_title(self.notebook, page) > File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, in get_title > return notebook.get_tab_label_text(notebook.get_nth_page(page_num)) > TypeError: Gtk.Notebook.get_tab_label_text() argument 1 must be > gtk.Widget, not None > > 29382: ERROR: gramps.py: line 142: Unhandled exception > Traceback (most recent call last): > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, > in view_changed > self.__change_page(page_num) > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1211, > in __change_page > self.__disconnect_previous_page() > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1241, > in __disconnect_previous_page > self.active_page.set_inactive() > File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > line 228, in set_inactive > self.uistate.viewmanager.tags.tag_disable() > File "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, in > tag_disable > self.uistate.uimanager.remove_ui(self.tag_id) > TypeError: Parameter 'merge_id' must be an int or a long > > I deleted my ~/.gramps/gramps33/*.ini files, but no avail. > > -Doug > > On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: > >> Devs, >> >> I have just committed a change which adds a new bottombar to Gramps. >> >> You can enable the bottom bar from the menu: View -> Bottombar. >> >> Each tab contains one gramplet. You can re-order them by drag-and-drop. >> >> There are three buttons on the right hand side of the bottombar. Use >> these to add or remove gramplets and also to close the bottombar. >> >> I have removed the normal gramplet controls. This creates more space >> and presents a cleaner interface to the user. The minimise button is >> not applicable for the bottom bar, and drag-and-drop functionality has >> moved to the tab. I have not implemented detaching of gramplets yet, >> but this could be achieved by dragging the tab out of the notebook (this >> is standard gtk functionality). >> >> I have written four example bottombar gramplets for the Person Views: >> >> 1. Details: This combines the primary picture, with parents, events and >> attributes to create a summary view for a person. >> >> 2. Gallery: This displays the pictures of a person in a scrollable >> list. Double-click to view the image with the default viewer application. >> >> 3. Residence: An example displaying a single event type. Double-click >> to edit an event. >> >> 4. Attributes: Just a GUI version of the existing Attributes gramplet. >> Double-click for the quick report. >> >> I was trying to make the gramplets look like they are part of core >> Gramps. Similar functionality is available in the person editor, but >> the bottom bar gramplets are intended to be optimised for viewing the >> data rather than editing it. >> >> I look forward to your feedback. >> >> Regards, >> >> >> Nick. >> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any company >> that requires sensitive data to be transmitted over the Web. Learn how to >> best implement a security strategy that keeps consumers' information secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > > > |
From: jerome <rom...@ya...> - 2011-01-11 11:47:41
|
OK, it is only currently working into Person View... But this gives a good proof of concept :) It is possible to use (move or re-use) code from plugins/quickview on all views/objects. I suppose that the idea is the same: an active row on the listview. Jérôme --- En date de : Mar 11.1.11, Nick Hall <nic...@ho...> a écrit : > De: Nick Hall <nic...@ho...> > Objet: Re: [Gramps-devel] New Gramps bottombar > À: "Doug Blank" <dou...@gm...> > Cc: "Gramps developers" <gra...@li...> > Date: Mardi 11 janvier 2011, 12h37 > Doug, > > I'll look into it. > > Nick. > > > Doug Blank wrote: > > Nick, > > > > Having troubling running trunk: > > > > 22061: ERROR: gramps.py: line 142: Unhandled > exception > > Traceback (most recent call last): > > File > "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line > 1202, > > in view_changed > > self.__change_page(page_num) > > File > "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line > 1214, > > in __change_page > > self.active_page.set_active() > > File > "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > > line 220, in set_active > > ListView.set_active(self) > > File > "/home/dblank/gramps/trunk/src/gui/views/listview.py", line > > 240, in set_active > > > NavigationView.set_active(self) > > File > "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", > > line 153, in set_active > > PageView.set_active(self) > > File > "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line > > 379, in set_active > > self.bottombar.set_active() > > File > "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, > in set_active > > title = > get_title(self.notebook, page) > > File > "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, > in get_title > > return > notebook.get_tab_label_text(notebook.get_nth_page(page_num)) > > TypeError: Gtk.Notebook.get_tab_label_text() argument > 1 must be > > gtk.Widget, not None > > > > 29382: ERROR: gramps.py: line 142: Unhandled > exception > > Traceback (most recent call last): > > File > "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line > 1202, > > in view_changed > > self.__change_page(page_num) > > File > "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line > 1211, > > in __change_page > > > self.__disconnect_previous_page() > > File > "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line > 1241, > > in __disconnect_previous_page > > > self.active_page.set_inactive() > > File > "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > > line 228, in set_inactive > > > self.uistate.viewmanager.tags.tag_disable() > > File > "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, > in > > tag_disable > > > self.uistate.uimanager.remove_ui(self.tag_id) > > TypeError: Parameter 'merge_id' must be an int or a > long > > > > I deleted my ~/.gramps/gramps33/*.ini files, but no > avail. > > > > -Doug > > > > On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> > wrote: > > > >> Devs, > >> > >> I have just committed a change which adds a new > bottombar to Gramps. > >> > >> You can enable the bottom bar from the menu: > View -> Bottombar. > >> > >> Each tab contains one > gramplet. You can re-order them by > drag-and-drop. > >> > >> There are three buttons on the right hand side of > the bottombar. Use > >> these to add or remove gramplets and also to close > the bottombar. > >> > >> I have removed the normal gramplet controls. > This creates more space > >> and presents a cleaner interface to the > user. The minimise button is > >> not applicable for the bottom bar, and > drag-and-drop functionality has > >> moved to the tab. I have not implemented > detaching of gramplets yet, > >> but this could be achieved by dragging the tab out > of the notebook (this > >> is standard gtk functionality). > >> > >> I have written four example bottombar gramplets > for the Person Views: > >> > >> 1. Details: This combines the primary > picture, with parents, events and > >> attributes to create a summary view for a person. > >> > >> 2. Gallery: This displays the pictures of a > person in a scrollable > >> list. Double-click to view the image with > the default viewer application. > >> > >> 3. Residence: An example displaying a single > event type. Double-click > >> to edit an event. > >> > >> 4. Attributes: Just a GUI version of the > existing Attributes gramplet. > >> Double-click for the quick report. > >> > >> I was trying to make the gramplets look like they > are part of core > >> Gramps. Similar functionality is available > in the person editor, but > >> the bottom bar gramplets are intended to be > optimised for viewing the > >> data rather than editing it. > >> > >> I look forward to your feedback. > >> > >> Regards, > >> > >> > >> Nick. > >> > >> > >> > ------------------------------------------------------------------------------ > >> Gaining the trust of online customers is vital for > the success of any company > >> that requires sensitive data to be transmitted > over the Web. Learn how to > >> best implement a security strategy that keeps > consumers' information secure > >> and instills the confidence they need to proceed > with transactions. > >> http://p.sf.net/sfu/oracle-sfdevnl > >> _______________________________________________ > >> Gramps-devel mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > >> > > > > > > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the > success of any company > that requires sensitive data to be transmitted over the > Web. Learn how to > best implement a security strategy that keeps consumers' > information secure > and instills the confidence they need to proceed with > transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2011-01-11 15:41:28
|
jerome wrote: > OK, it is only currently working into Person View... > But this gives a good proof of concept :) > > It is possible to use (move or re-use) code from plugins/quickview on all views/objects. > I suppose that the idea is the same: an active row on the listview. > > Yes, the idea would be to create tabs for the other views that react to the currently active object. For example, the Family View could have a tab for the mother and another for the father that could look like the Details tab in the Person Views. The Event View could have a Gallery tab and a Participants tab. We could remove the image preview from the Media View and replace it with a tab in the bottombar. We could also have a Metadata tab in the Media View based upon Rob's existing metadata gramplet. Nick. > Jérôme > > --- En date de : Mar 11.1.11, Nick Hall <nic...@ho...> a écrit : > > >> De: Nick Hall <nic...@ho...> >> Objet: Re: [Gramps-devel] New Gramps bottombar >> À: "Doug Blank" <dou...@gm...> >> Cc: "Gramps developers" <gra...@li...> >> Date: Mardi 11 janvier 2011, 12h37 >> Doug, >> >> I'll look into it. >> >> Nick. >> >> >> Doug Blank wrote: >> >>> Nick, >>> >>> Having troubling running trunk: >>> >>> 22061: ERROR: gramps.py: line 142: Unhandled >>> >> exception >> >>> Traceback (most recent call last): >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line >> 1202, >> >>> in view_changed >>> self.__change_page(page_num) >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line >> 1214, >> >>> in __change_page >>> self.active_page.set_active() >>> File >>> >> "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> >>> line 220, in set_active >>> ListView.set_active(self) >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/views/listview.py", line >> >>> 240, in set_active >>> >>> >> NavigationView.set_active(self) >> >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", >> >>> line 153, in set_active >>> PageView.set_active(self) >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line >> >>> 379, in set_active >>> self.bottombar.set_active() >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, >> in set_active >> >>> title = >>> >> get_title(self.notebook, page) >> >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, >> in get_title >> >>> return >>> >> notebook.get_tab_label_text(notebook.get_nth_page(page_num)) >> >>> TypeError: Gtk.Notebook.get_tab_label_text() argument >>> >> 1 must be >> >>> gtk.Widget, not None >>> >>> 29382: ERROR: gramps.py: line 142: Unhandled >>> >> exception >> >>> Traceback (most recent call last): >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line >> 1202, >> >>> in view_changed >>> self.__change_page(page_num) >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line >> 1211, >> >>> in __change_page >>> >>> >> self.__disconnect_previous_page() >> >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line >> 1241, >> >>> in __disconnect_previous_page >>> >>> >> self.active_page.set_inactive() >> >>> File >>> >> "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> >>> line 228, in set_inactive >>> >>> >> self.uistate.viewmanager.tags.tag_disable() >> >>> File >>> >> "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, >> in >> >>> tag_disable >>> >>> >> self.uistate.uimanager.remove_ui(self.tag_id) >> >>> TypeError: Parameter 'merge_id' must be an int or a >>> >> long >> >>> I deleted my ~/.gramps/gramps33/*.ini files, but no >>> >> avail. >> >>> -Doug >>> >>> On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> >>> >> wrote: >> >>> >>> >>>> Devs, >>>> >>>> I have just committed a change which adds a new >>>> >> bottombar to Gramps. >> >>>> You can enable the bottom bar from the menu: >>>> >> View -> Bottombar. >> >>>> Each tab contains one >>>> >> gramplet. You can re-order them by >> drag-and-drop. >> >>>> There are three buttons on the right hand side of >>>> >> the bottombar. Use >> >>>> these to add or remove gramplets and also to close >>>> >> the bottombar. >> >>>> I have removed the normal gramplet controls. >>>> >> This creates more space >> >>>> and presents a cleaner interface to the >>>> >> user. The minimise button is >> >>>> not applicable for the bottom bar, and >>>> >> drag-and-drop functionality has >> >>>> moved to the tab. I have not implemented >>>> >> detaching of gramplets yet, >> >>>> but this could be achieved by dragging the tab out >>>> >> of the notebook (this >> >>>> is standard gtk functionality). >>>> >>>> I have written four example bottombar gramplets >>>> >> for the Person Views: >> >>>> 1. Details: This combines the primary >>>> >> picture, with parents, events and >> >>>> attributes to create a summary view for a person. >>>> >>>> 2. Gallery: This displays the pictures of a >>>> >> person in a scrollable >> >>>> list. Double-click to view the image with >>>> >> the default viewer application. >> >>>> 3. Residence: An example displaying a single >>>> >> event type. Double-click >> >>>> to edit an event. >>>> >>>> 4. Attributes: Just a GUI version of the >>>> >> existing Attributes gramplet. >> >>>> Double-click for the quick report. >>>> >>>> I was trying to make the gramplets look like they >>>> >> are part of core >> >>>> Gramps. Similar functionality is available >>>> >> in the person editor, but >> >>>> the bottom bar gramplets are intended to be >>>> >> optimised for viewing the >> >>>> data rather than editing it. >>>> >>>> I look forward to your feedback. >>>> >>>> Regards, >>>> >>>> >>>> Nick. >>>> >>>> >>>> >>>> >> ------------------------------------------------------------------------------ >> >>>> Gaining the trust of online customers is vital for >>>> >> the success of any company >> >>>> that requires sensitive data to be transmitted >>>> >> over the Web. Learn how to >> >>>> best implement a security strategy that keeps >>>> >> consumers' information secure >> >>>> and instills the confidence they need to proceed >>>> >> with transactions. >> >>>> http://p.sf.net/sfu/oracle-sfdevnl >>>> _______________________________________________ >>>> Gramps-devel mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>>> >>>> >>>> >>> >>> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the >> success of any company >> that requires sensitive data to be transmitted over the >> Web. Learn how to >> best implement a security strategy that keeps consumers' >> information secure >> and instills the confidence they need to proceed with >> transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > > > > > > |
From: Nick H. <nic...@ho...> - 2011-01-11 14:10:53
|
This should now be fixed. One of the last changes I made was to allow different default gramplets for each view. For all of the views, except for the person views, I specified no gramplets as the default. The empty bottombar was the cause of the problem. I'm sorry for not testing this change. Nick. Nick Hall wrote: > Doug, > > I'll look into it. > > Nick. > > > Doug Blank wrote: > >> Nick, >> >> Having troubling running trunk: >> >> 22061: ERROR: gramps.py: line 142: Unhandled exception >> Traceback (most recent call last): >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, >> in view_changed >> self.__change_page(page_num) >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1214, >> in __change_page >> self.active_page.set_active() >> File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> line 220, in set_active >> ListView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/listview.py", line >> 240, in set_active >> NavigationView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", >> line 153, in set_active >> PageView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line >> 379, in set_active >> self.bottombar.set_active() >> File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, in set_active >> title = get_title(self.notebook, page) >> File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, in get_title >> return notebook.get_tab_label_text(notebook.get_nth_page(page_num)) >> TypeError: Gtk.Notebook.get_tab_label_text() argument 1 must be >> gtk.Widget, not None >> >> 29382: ERROR: gramps.py: line 142: Unhandled exception >> Traceback (most recent call last): >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, >> in view_changed >> self.__change_page(page_num) >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1211, >> in __change_page >> self.__disconnect_previous_page() >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1241, >> in __disconnect_previous_page >> self.active_page.set_inactive() >> File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> line 228, in set_inactive >> self.uistate.viewmanager.tags.tag_disable() >> File "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, in >> tag_disable >> self.uistate.uimanager.remove_ui(self.tag_id) >> TypeError: Parameter 'merge_id' must be an int or a long >> >> I deleted my ~/.gramps/gramps33/*.ini files, but no avail. >> >> -Doug >> >> On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: >> >> >>> Devs, >>> >>> I have just committed a change which adds a new bottombar to Gramps. >>> >>> You can enable the bottom bar from the menu: View -> Bottombar. >>> >>> Each tab contains one gramplet. You can re-order them by drag-and-drop. >>> >>> There are three buttons on the right hand side of the bottombar. Use >>> these to add or remove gramplets and also to close the bottombar. >>> >>> I have removed the normal gramplet controls. This creates more space >>> and presents a cleaner interface to the user. The minimise button is >>> not applicable for the bottom bar, and drag-and-drop functionality has >>> moved to the tab. I have not implemented detaching of gramplets yet, >>> but this could be achieved by dragging the tab out of the notebook (this >>> is standard gtk functionality). >>> >>> I have written four example bottombar gramplets for the Person Views: >>> >>> 1. Details: This combines the primary picture, with parents, events and >>> attributes to create a summary view for a person. >>> >>> 2. Gallery: This displays the pictures of a person in a scrollable >>> list. Double-click to view the image with the default viewer application. >>> >>> 3. Residence: An example displaying a single event type. Double-click >>> to edit an event. >>> >>> 4. Attributes: Just a GUI version of the existing Attributes gramplet. >>> Double-click for the quick report. >>> >>> I was trying to make the gramplets look like they are part of core >>> Gramps. Similar functionality is available in the person editor, but >>> the bottom bar gramplets are intended to be optimised for viewing the >>> data rather than editing it. >>> >>> I look forward to your feedback. >>> >>> Regards, >>> >>> >>> Nick. >>> >>> >>> ------------------------------------------------------------------------------ >>> Gaining the trust of online customers is vital for the success of any company >>> that requires sensitive data to be transmitted over the Web. Learn how to >>> best implement a security strategy that keeps consumers' information secure >>> and instills the confidence they need to proceed with transactions. >>> http://p.sf.net/sfu/oracle-sfdevnl >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >>> >>> >> >> > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |
From: Doug B. <dou...@gm...> - 2011-01-11 14:36:54
|
Nick, Looks very nice! Some comments below: On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: > Devs, > > I have just committed a change which adds a new bottombar to Gramps. > > You can enable the bottom bar from the menu: View -> Bottombar. > > Each tab contains one gramplet. You can re-order them by drag-and-drop. This does look nice along the bottom. You thinking of leaving the gramplets on the side as they are currently implemented (eg, drag to arrange, borders, columns, etc)? Or each one in a tab on the side? > There are three buttons on the right hand side of the bottombar. Use > these to add or remove gramplets and also to close the bottombar. (Looks like current add-with-right-click on sidebar adds without borders.) > I have removed the normal gramplet controls. This creates more space > and presents a cleaner interface to the user. The minimise button is > not applicable for the bottom bar, and drag-and-drop functionality has > moved to the tab. I have not implemented detaching of gramplets yet, > but this could be achieved by dragging the tab out of the notebook (this > is standard gtk functionality). > > I have written four example bottombar gramplets for the Person Views: > > 1. Details: This combines the primary picture, with parents, events and > attributes to create a summary view for a person. > > 2. Gallery: This displays the pictures of a person in a scrollable > list. Double-click to view the image with the default viewer application. > > 3. Residence: An example displaying a single event type. Double-click > to edit an event. > > 4. Attributes: Just a GUI version of the existing Attributes gramplet. > Double-click for the quick report. Yes, very nice. I was working on something like this myself, but was trying to turn the Editors into read-only views. > I was trying to make the gramplets look like they are part of core > Gramps. Similar functionality is available in the person editor, but > the bottom bar gramplets are intended to be optimised for viewing the > data rather than editing it. > > I look forward to your feedback. I like this very much. This suggests some further enhancements: an API that allows a gramplet to indicate if there is something to see, so that it can turn the tab name bold. That way you will know when there is something to see, like the tabs in the editors. I guess we could make the gramplets-as-notebook-tabs or gramplets-as-tabular-grid an option, unless it is obvious that bottom should always be notebook, and sidebar should always be grid? -Doug > Regards, > > > Nick. > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2011-01-11 18:37:03
|
Doug Blank wrote: > Nick, > > Looks very nice! Some comments below: > > On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: > >> Devs, >> >> I have just committed a change which adds a new bottombar to Gramps. >> >> You can enable the bottom bar from the menu: View -> Bottombar. >> >> Each tab contains one gramplet. You can re-order them by drag-and-drop. >> > > This does look nice along the bottom. You thinking of leaving the > gramplets on the side as they are currently implemented (eg, drag to > arrange, borders, columns, etc)? Or each one in a tab on the side? > I thought of changing the sidebar to match the bottombar, but I didn't want to do too much without getting some feedback. > >> There are three buttons on the right hand side of the bottombar. Use >> these to add or remove gramplets and also to close the bottombar. >> > > (Looks like current add-with-right-click on sidebar adds without borders.) > This should be easy to fix. > >> I have removed the normal gramplet controls. This creates more space >> and presents a cleaner interface to the user. The minimise button is >> not applicable for the bottom bar, and drag-and-drop functionality has >> moved to the tab. I have not implemented detaching of gramplets yet, >> but this could be achieved by dragging the tab out of the notebook (this >> is standard gtk functionality). >> >> I have written four example bottombar gramplets for the Person Views: >> >> 1. Details: This combines the primary picture, with parents, events and >> attributes to create a summary view for a person. >> >> 2. Gallery: This displays the pictures of a person in a scrollable >> list. Double-click to view the image with the default viewer application. >> >> 3. Residence: An example displaying a single event type. Double-click >> to edit an event. >> >> 4. Attributes: Just a GUI version of the existing Attributes gramplet. >> Double-click for the quick report. >> > > Yes, very nice. I was working on something like this myself, but was > trying to turn the Editors into read-only views. > > Perhaps you could try some of your ideas as bottombar gramplets. >> I was trying to make the gramplets look like they are part of core >> Gramps. Similar functionality is available in the person editor, but >> the bottom bar gramplets are intended to be optimised for viewing the >> data rather than editing it. >> >> I look forward to your feedback. >> > > I like this very much. This suggests some further enhancements: an API > that allows a gramplet to indicate if there is something to see, so > that it can turn the tab name bold. That way you will know when there > is something to see, like the tabs in the editors. Good idea. I'll add that functionality. > I guess we could > make the gramplets-as-notebook-tabs or gramplets-as-tabular-grid an > option, unless it is obvious that bottom should always be notebook, > and sidebar should always be grid? > > I think that the bottombar should always be tabs - the interface looks good and the frame and buttons take up useful screen space. I am tempted to make the sidebar tabs-only as well to make the interface consistent. I don't think that I would ever use more than one column in the sidebar. What type of gramplets do you see us using in the sidebar? Navigation? Data entry? This may influence our decision. Nick. > -Doug > > >> Regards, >> >> >> Nick. >> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any company >> that requires sensitive data to be transmitted over the Web. Learn how to >> best implement a security strategy that keeps consumers' information secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > > > |
From: Benny M. <ben...@gm...> - 2011-01-12 08:36:58
|
Looks nice. I can see people really liking this. Some comments: 1/ Users don't discover functionality easily. So I suggest that we all try this a bit and in a month for 3.3 to query if we should have the bottom bar visible by default on fresh install, and if so what gramplets. 2/ Write a quick blog post of this work. Some users do react to that. 3/ We must make it clear to users that they still need to double click or press edit button on the listview to actually change a person. That is, the editors are not in the gramplets (although gramplets can be written for it, I would not experiment with that for 3.3) 4/ Passing key presses: When I select an attribute in Attributes bottombar, then ctrl+ins does still do insert person. That is good. However, ctrl+enter or enter does not edit the current person. We need a keypress to edit person when things are selected on the gramplet 5/ How to know the name of the gramplet in the bottombar. Eg after remove, you want to add it again, but don't know the name. Perhaps the tooltip on the tab to contain the name of the gramplet? 6/ In Attributes, tooltip on an entry says: Drag Properties Button to move and click it for setup. I don't understand this tooltip. 7/ Double click on attribute gives a quick-view. I suppose this is gramplet functionality? If so, having this action in a context menu too would be nice. Other quickviews can be added then, eg: sources of attribute, ... . Most important though: Users will expect double click to allow edit of the person attribute! How can we offer this? Context menu with 'Edit Attribute', that opens the person editor and the attribute editor of the correct attribute? This is a usability concept we should have a clear answer to. See 3/ and 4/ above. That's it for now. Benny 2011/1/11 Nick Hall <nic...@ho...> > Devs, > > I have just committed a change which adds a new bottombar to Gramps. > > You can enable the bottom bar from the menu: View -> Bottombar. > > Each tab contains one gramplet. You can re-order them by drag-and-drop. > > There are three buttons on the right hand side of the bottombar. Use > these to add or remove gramplets and also to close the bottombar. > > I have removed the normal gramplet controls. This creates more space > and presents a cleaner interface to the user. The minimise button is > not applicable for the bottom bar, and drag-and-drop functionality has > moved to the tab. I have not implemented detaching of gramplets yet, > but this could be achieved by dragging the tab out of the notebook (this > is standard gtk functionality). > > I have written four example bottombar gramplets for the Person Views: > > 1. Details: This combines the primary picture, with parents, events and > attributes to create a summary view for a person. > > 2. Gallery: This displays the pictures of a person in a scrollable > list. Double-click to view the image with the default viewer application. > > 3. Residence: An example displaying a single event type. Double-click > to edit an event. > > 4. Attributes: Just a GUI version of the existing Attributes gramplet. > Double-click for the quick report. > > I was trying to make the gramplets look like they are part of core > Gramps. Similar functionality is available in the person editor, but > the bottom bar gramplets are intended to be optimised for viewing the > data rather than editing it. > > I look forward to your feedback. > > Regards, > > > Nick. > > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any > company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2011-01-12 13:18:43
|
On Wed, Jan 12, 2011 at 3:36 AM, Benny Malengier <ben...@gm...> wrote: > Looks nice. I can see people really liking this. > > Some comments: > > 1/ Users don't discover functionality easily. So I suggest that we all try > this a bit and in a month for 3.3 to query if we should have the bottom bar > visible by default on fresh install, and if so what gramplets. Good idea. I think some (or most) views are better with some specific gramplets. We can get some user input on this too, Eg, what functionality/data do you want to see on each view? > 2/ Write a quick blog post of this work. Some users do react to that. > > 3/ We must make it clear to users that they still need to double click or > press edit button on the listview to actually change a person. That is, the > editors are not in the gramplets (although gramplets can be written for it, > I would not experiment with that for 3.3) > > 4/ Passing key presses: When I select an attribute in Attributes bottombar, > then ctrl+ins does still do insert person. That is good. However, ctrl+enter > or enter does not edit the current person. We need a keypress to edit person > when things are selected on the gramplet > > 5/ How to know the name of the gramplet in the bottombar. Eg after remove, > you want to add it again, but don't know the name. Perhaps the tooltip on > the tab to contain the name of the gramplet? That confused me too at first as there is no way to tell currently which gramplets are showing. The gramplet pane has support too to undelete a deleted gramplet. This is nice as some gramplets have data in them that would be bad if you couldn't get it back. Perhaps we can have an undo button or menu option for this. > 6/ In Attributes, tooltip on an entry says: Drag Properties Button to move > and click it for setup. > I don't understand this tooltip. This is only for the gramplet grid view, where gramplets can be moved. Setup is now in config. > 7/ Double click on attribute gives a quick-view. I suppose this is gramplet > functionality? If so, having this action in a context menu too would be > nice. Other quickviews can be added then, eg: sources of attribute, ... . > Most important though: Users will expect double click to allow edit of the > person attribute! How can we offer this? Context menu with 'Edit Attribute', > that opens the person editor and the attribute editor of the correct > attribute? This is a usability concept we should have a clear answer to. See > 3/ and 4/ above. I'll work on the unified context menu infrastructure, as mentioned a week or two ago. -Doug > That's it for now. > > Benny > > > 2011/1/11 Nick Hall <nic...@ho...> >> >> Devs, >> >> I have just committed a change which adds a new bottombar to Gramps. >> >> You can enable the bottom bar from the menu: View -> Bottombar. >> >> Each tab contains one gramplet. You can re-order them by drag-and-drop. >> >> There are three buttons on the right hand side of the bottombar. Use >> these to add or remove gramplets and also to close the bottombar. >> >> I have removed the normal gramplet controls. This creates more space >> and presents a cleaner interface to the user. The minimise button is >> not applicable for the bottom bar, and drag-and-drop functionality has >> moved to the tab. I have not implemented detaching of gramplets yet, >> but this could be achieved by dragging the tab out of the notebook (this >> is standard gtk functionality). >> >> I have written four example bottombar gramplets for the Person Views: >> >> 1. Details: This combines the primary picture, with parents, events and >> attributes to create a summary view for a person. >> >> 2. Gallery: This displays the pictures of a person in a scrollable >> list. Double-click to view the image with the default viewer application. >> >> 3. Residence: An example displaying a single event type. Double-click >> to edit an event. >> >> 4. Attributes: Just a GUI version of the existing Attributes gramplet. >> Double-click for the quick report. >> >> I was trying to make the gramplets look like they are part of core >> Gramps. Similar functionality is available in the person editor, but >> the bottom bar gramplets are intended to be optimised for viewing the >> data rather than editing it. >> >> I look forward to your feedback. >> >> Regards, >> >> >> Nick. >> >> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any >> company >> that requires sensitive data to be transmitted over the Web. Learn how >> to >> best implement a security strategy that keeps consumers' information >> secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Nick H. <nic...@ho...> - 2011-01-12 22:13:46
|
Doug Blank wrote: > On Wed, Jan 12, 2011 at 3:36 AM, Benny Malengier > <ben...@gm...> wrote: > >> Looks nice. I can see people really liking this. >> >> Some comments: >> >> 1/ Users don't discover functionality easily. So I suggest that we all try >> this a bit and in a month for 3.3 to query if we should have the bottom bar >> visible by default on fresh install, and if so what gramplets. >> > > Good idea. I think some (or most) views are better with some specific > gramplets. We can get some user input on this too, Eg, what > functionality/data do you want to see on each view? > > Yes, I think that each view should have its own set of gramplets. For the bottom bar, I think that a default set of gramplets should be suitable for most users. We just have to carefully think about which gramplets are the right ones for the defaults. :) User input would be useful here. I can see that the choice of sidebar gramplets may be much more dependent on user preferences. >> 2/ Write a quick blog post of this work. Some users do react to that. >> >> 3/ We must make it clear to users that they still need to double click or >> press edit button on the listview to actually change a person. That is, the >> editors are not in the gramplets (although gramplets can be written for it, >> I would not experiment with that for 3.3) >> >> 4/ Passing key presses: When I select an attribute in Attributes bottombar, >> then ctrl+ins does still do insert person. That is good. However, ctrl+enter >> or enter does not edit the current person. We need a keypress to edit person >> when things are selected on the gramplet >> >> 5/ How to know the name of the gramplet in the bottombar. Eg after remove, >> you want to add it again, but don't know the name. Perhaps the tooltip on >> the tab to contain the name of the gramplet? >> > > That confused me too at first as there is no way to tell currently > which gramplets are showing. > > The gramplet pane has support too to undelete a deleted gramplet. This > is nice as some gramplets have data in them that would be bad if you > couldn't get it back. Perhaps we can have an undo button or menu > option for this. > > I'll add a restore button to the interface. This is something I just didn't get around to doing yet. I also need to enable configuration for the bottombar gramplets. >> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to move >> and click it for setup. >> I don't understand this tooltip. >> > > This is only for the gramplet grid view, where gramplets can be moved. > Setup is now in config. > > >> 7/ Double click on attribute gives a quick-view. I suppose this is gramplet >> functionality? If so, having this action in a context menu too would be >> nice. Other quickviews can be added then, eg: sources of attribute, ... . >> Most important though: Users will expect double click to allow edit of the >> person attribute! How can we offer this? Context menu with 'Edit Attribute', >> that opens the person editor and the attribute editor of the correct >> attribute? This is a usability concept we should have a clear answer to. See >> 3/ and 4/ above. >> > > I'll work on the unified context menu infrastructure, as mentioned a > week or two ago. > > This will be very helpful to ensure that we get consistent context menus. Nick. > -Doug > > >> That's it for now. >> >> Benny >> >> >> 2011/1/11 Nick Hall <nic...@ho...> >> >>> Devs, >>> >>> I have just committed a change which adds a new bottombar to Gramps. >>> >>> You can enable the bottom bar from the menu: View -> Bottombar. >>> >>> Each tab contains one gramplet. You can re-order them by drag-and-drop. >>> >>> There are three buttons on the right hand side of the bottombar. Use >>> these to add or remove gramplets and also to close the bottombar. >>> >>> I have removed the normal gramplet controls. This creates more space >>> and presents a cleaner interface to the user. The minimise button is >>> not applicable for the bottom bar, and drag-and-drop functionality has >>> moved to the tab. I have not implemented detaching of gramplets yet, >>> but this could be achieved by dragging the tab out of the notebook (this >>> is standard gtk functionality). >>> >>> I have written four example bottombar gramplets for the Person Views: >>> >>> 1. Details: This combines the primary picture, with parents, events and >>> attributes to create a summary view for a person. >>> >>> 2. Gallery: This displays the pictures of a person in a scrollable >>> list. Double-click to view the image with the default viewer application. >>> >>> 3. Residence: An example displaying a single event type. Double-click >>> to edit an event. >>> >>> 4. Attributes: Just a GUI version of the existing Attributes gramplet. >>> Double-click for the quick report. >>> >>> I was trying to make the gramplets look like they are part of core >>> Gramps. Similar functionality is available in the person editor, but >>> the bottom bar gramplets are intended to be optimised for viewing the >>> data rather than editing it. >>> >>> I look forward to your feedback. >>> >>> Regards, >>> >>> >>> Nick. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Gaining the trust of online customers is vital for the success of any >>> company >>> that requires sensitive data to be transmitted over the Web. Learn how >>> to >>> best implement a security strategy that keeps consumers' information >>> secure >>> and instills the confidence they need to proceed with transactions. >>> http://p.sf.net/sfu/oracle-sfdevnl >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >> ------------------------------------------------------------------------------ >> Protect Your Site and Customers from Malware Attacks >> Learn about various malware tactics and how to avoid them. Understand >> malware threats, the impact they can have on your business, and how you >> can protect your company and customers by using code signing. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> >> > > > |
From: jerome <rom...@ya...> - 2011-01-13 11:45:21
|
Note, there is a bug in gramplet pane configuration (also stable release) ... 3.2.6-SVN: 26671: ERROR: gramps.py: line 138: Unhandled exception Traceback (most recent call last): File "/usr/share/gramps/gui/widgets/grampletpane.py", line 1192, in add_gramplet self.columns[pos].pack_start(gramplet.mainframe, expand=gramplet.expand) IndexError: list index out of range trunk: 170189: ERROR: gramps.py: line 142: Unhandled exception Traceback (most recent call last): File "/home/nono/gramps/trunk/src/gui/widgets/grampletpane.py", line 1289, in add_gramplet self.columns[pos].pack_start(gramplet.mainframe, expand=gramplet.expand) IndexError: list index out of range How to reproduce it ? Just set number of column (gramplet layout) to "0" ! Agreed, stupid but it returns Index error. :( Jérôme --- En date de : Mer 12.1.11, Doug Blank <dou...@gm...> a écrit : > De: Doug Blank <dou...@gm...> > Objet: Re: [Gramps-devel] New Gramps bottombar > À: "Benny Malengier" <ben...@gm...> > Cc: "Gramps developers" <gra...@li...> > Date: Mercredi 12 janvier 2011, 14h18 > On Wed, Jan 12, 2011 at 3:36 AM, > Benny Malengier > <ben...@gm...> > wrote: > > Looks nice. I can see people really liking this. > > > > Some comments: > > > > 1/ Users don't discover functionality easily. So I > suggest that we all try > > this a bit and in a month for 3.3 to query if we > should have the bottom bar > > visible by default on fresh install, and if so what > gramplets. > > Good idea. I think some (or most) views are better with > some specific > gramplets. We can get some user input on this too, Eg, > what > functionality/data do you want to see on each view? > > > 2/ Write a quick blog post of this work. Some users do > react to that. > > > > 3/ We must make it clear to users that they still need > to double click or > > press edit button on the listview to actually change a > person. That is, the > > editors are not in the gramplets (although gramplets > can be written for it, > > I would not experiment with that for 3.3) > > > > 4/ Passing key presses: When I select an attribute in > Attributes bottombar, > > then ctrl+ins does still do insert person. That is > good. However, ctrl+enter > > or enter does not edit the current person. We need a > keypress to edit person > > when things are selected on the gramplet > > > > 5/ How to know the name of the gramplet in the > bottombar. Eg after remove, > > you want to add it again, but don't know the name. > Perhaps the tooltip on > > the tab to contain the name of the gramplet? > > That confused me too at first as there is no way to tell > currently > which gramplets are showing. > > The gramplet pane has support too to undelete a deleted > gramplet. This > is nice as some gramplets have data in them that would be > bad if you > couldn't get it back. Perhaps we can have an undo button or > menu > option for this. > > > 6/ In Attributes, tooltip on an entry says: Drag > Properties Button to move > > and click it for setup. > > I don't understand this tooltip. > > This is only for the gramplet grid view, where gramplets > can be moved. > Setup is now in config. > > > 7/ Double click on attribute gives a quick-view. I > suppose this is gramplet > > functionality? If so, having this action in a context > menu too would be > > nice. Other quickviews can be added then, eg: sources > of attribute, ... . > > Most important though: Users will expect double click > to allow edit of the > > person attribute! How can we offer this? Context menu > with 'Edit Attribute', > > that opens the person editor and the attribute editor > of the correct > > attribute? This is a usability concept we should have > a clear answer to. See > > 3/ and 4/ above. > > I'll work on the unified context menu infrastructure, as > mentioned a > week or two ago. > > -Doug > > > That's it for now. > > > > Benny > > > > > > 2011/1/11 Nick Hall <nic...@ho...> > >> > >> Devs, > >> > >> I have just committed a change which adds a new > bottombar to Gramps. > >> > >> You can enable the bottom bar from the menu: > View -> Bottombar. > >> > >> Each tab contains one gramplet. You can > re-order them by drag-and-drop. > >> > >> There are three buttons on the right hand side of > the bottombar. Use > >> these to add or remove gramplets and also to close > the bottombar. > >> > >> I have removed the normal gramplet controls. > This creates more space > >> and presents a cleaner interface to the user. > The minimise button is > >> not applicable for the bottom bar, and > drag-and-drop functionality has > >> moved to the tab. I have not implemented > detaching of gramplets yet, > >> but this could be achieved by dragging the tab out > of the notebook (this > >> is standard gtk functionality). > >> > >> I have written four example bottombar gramplets > for the Person Views: > >> > >> 1. Details: This combines the primary picture, > with parents, events and > >> attributes to create a summary view for a person. > >> > >> 2. Gallery: This displays the pictures of a > person in a scrollable > >> list. Double-click to view the image with the > default viewer application. > >> > >> 3. Residence: An example displaying a single > event type. Double-click > >> to edit an event. > >> > >> 4. Attributes: Just a GUI version of the > existing Attributes gramplet. > >> Double-click for the quick report. > >> > >> I was trying to make the gramplets look like they > are part of core > >> Gramps. Similar functionality is available in > the person editor, but > >> the bottom bar gramplets are intended to be > optimised for viewing the > >> data rather than editing it. > >> > >> I look forward to your feedback. > >> > >> Regards, > >> > >> > >> Nick. > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> Gaining the trust of online customers is vital for > the success of any > >> company > >> that requires sensitive data to be transmitted > over the Web. Learn how > >> to > >> best implement a security strategy that keeps > consumers' information > >> secure > >> and instills the confidence they need to proceed > with transactions. > >> http://p.sf.net/sfu/oracle-sfdevnl > >> _______________________________________________ > >> Gramps-devel mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > ------------------------------------------------------------------------------ > > Protect Your Site and Customers from Malware Attacks > > Learn about various malware tactics and how to avoid > them. Understand > > malware threats, the impact they can have on your > business, and how you > > can protect your company and customers by using code > signing. > > http://p.sf.net/sfu/oracle-sfdevnl > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. > Understand > malware threats, the impact they can have on your business, > and how you > can protect your company and customers by using code > signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2011-01-13 11:53:26
|
On Thu, Jan 13, 2011 at 6:45 AM, jerome <rom...@ya...> wrote: > Note, there is a bug in gramplet pane configuration (also stable release) ... > > 3.2.6-SVN: > 26671: ERROR: gramps.py: line 138: Unhandled exception > Traceback (most recent call last): > File "/usr/share/gramps/gui/widgets/grampletpane.py", line 1192, in add_gramplet > self.columns[pos].pack_start(gramplet.mainframe, expand=gramplet.expand) > IndexError: list index out of range > > trunk: > 170189: ERROR: gramps.py: line 142: Unhandled exception > Traceback (most recent call last): > File "/home/nono/gramps/trunk/src/gui/widgets/grampletpane.py", line 1289, in add_gramplet > self.columns[pos].pack_start(gramplet.mainframe, expand=gramplet.expand) > IndexError: list index out of range > > How to reproduce it ? > > Just set number of column (gramplet layout) to "0" ! Reminds me of an old joke: Patient: "Doctor! It hurts when I move my arm this way!" Doctor: "Well, then, don't move it that way." Seriously though, I'll fix that :) -Doug > Agreed, stupid but it returns Index error. :( > > > Jérôme > > > --- En date de : Mer 12.1.11, Doug Blank <dou...@gm...> a écrit : > >> De: Doug Blank <dou...@gm...> >> Objet: Re: [Gramps-devel] New Gramps bottombar >> À: "Benny Malengier" <ben...@gm...> >> Cc: "Gramps developers" <gra...@li...> >> Date: Mercredi 12 janvier 2011, 14h18 >> On Wed, Jan 12, 2011 at 3:36 AM, >> Benny Malengier >> <ben...@gm...> >> wrote: >> > Looks nice. I can see people really liking this. >> > >> > Some comments: >> > >> > 1/ Users don't discover functionality easily. So I >> suggest that we all try >> > this a bit and in a month for 3.3 to query if we >> should have the bottom bar >> > visible by default on fresh install, and if so what >> gramplets. >> >> Good idea. I think some (or most) views are better with >> some specific >> gramplets. We can get some user input on this too, Eg, >> what >> functionality/data do you want to see on each view? >> >> > 2/ Write a quick blog post of this work. Some users do >> react to that. >> > >> > 3/ We must make it clear to users that they still need >> to double click or >> > press edit button on the listview to actually change a >> person. That is, the >> > editors are not in the gramplets (although gramplets >> can be written for it, >> > I would not experiment with that for 3.3) >> > >> > 4/ Passing key presses: When I select an attribute in >> Attributes bottombar, >> > then ctrl+ins does still do insert person. That is >> good. However, ctrl+enter >> > or enter does not edit the current person. We need a >> keypress to edit person >> > when things are selected on the gramplet >> > >> > 5/ How to know the name of the gramplet in the >> bottombar. Eg after remove, >> > you want to add it again, but don't know the name. >> Perhaps the tooltip on >> > the tab to contain the name of the gramplet? >> >> That confused me too at first as there is no way to tell >> currently >> which gramplets are showing. >> >> The gramplet pane has support too to undelete a deleted >> gramplet. This >> is nice as some gramplets have data in them that would be >> bad if you >> couldn't get it back. Perhaps we can have an undo button or >> menu >> option for this. >> >> > 6/ In Attributes, tooltip on an entry says: Drag >> Properties Button to move >> > and click it for setup. >> > I don't understand this tooltip. >> >> This is only for the gramplet grid view, where gramplets >> can be moved. >> Setup is now in config. >> >> > 7/ Double click on attribute gives a quick-view. I >> suppose this is gramplet >> > functionality? If so, having this action in a context >> menu too would be >> > nice. Other quickviews can be added then, eg: sources >> of attribute, ... . >> > Most important though: Users will expect double click >> to allow edit of the >> > person attribute! How can we offer this? Context menu >> with 'Edit Attribute', >> > that opens the person editor and the attribute editor >> of the correct >> > attribute? This is a usability concept we should have >> a clear answer to. See >> > 3/ and 4/ above. >> >> I'll work on the unified context menu infrastructure, as >> mentioned a >> week or two ago. >> >> -Doug >> >> > That's it for now. >> > >> > Benny >> > >> > >> > 2011/1/11 Nick Hall <nic...@ho...> >> >> >> >> Devs, >> >> >> >> I have just committed a change which adds a new >> bottombar to Gramps. >> >> >> >> You can enable the bottom bar from the menu: >> View -> Bottombar. >> >> >> >> Each tab contains one gramplet. You can >> re-order them by drag-and-drop. >> >> >> >> There are three buttons on the right hand side of >> the bottombar. Use >> >> these to add or remove gramplets and also to close >> the bottombar. >> >> >> >> I have removed the normal gramplet controls. >> This creates more space >> >> and presents a cleaner interface to the user. >> The minimise button is >> >> not applicable for the bottom bar, and >> drag-and-drop functionality has >> >> moved to the tab. I have not implemented >> detaching of gramplets yet, >> >> but this could be achieved by dragging the tab out >> of the notebook (this >> >> is standard gtk functionality). >> >> >> >> I have written four example bottombar gramplets >> for the Person Views: >> >> >> >> 1. Details: This combines the primary picture, >> with parents, events and >> >> attributes to create a summary view for a person. >> >> >> >> 2. Gallery: This displays the pictures of a >> person in a scrollable >> >> list. Double-click to view the image with the >> default viewer application. >> >> >> >> 3. Residence: An example displaying a single >> event type. Double-click >> >> to edit an event. >> >> >> >> 4. Attributes: Just a GUI version of the >> existing Attributes gramplet. >> >> Double-click for the quick report. >> >> >> >> I was trying to make the gramplets look like they >> are part of core >> >> Gramps. Similar functionality is available in >> the person editor, but >> >> the bottom bar gramplets are intended to be >> optimised for viewing the >> >> data rather than editing it. >> >> >> >> I look forward to your feedback. >> >> >> >> Regards, >> >> >> >> >> >> Nick. >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Gaining the trust of online customers is vital for >> the success of any >> >> company >> >> that requires sensitive data to be transmitted >> over the Web. Learn how >> >> to >> >> best implement a security strategy that keeps >> consumers' information >> >> secure >> >> and instills the confidence they need to proceed >> with transactions. >> >> http://p.sf.net/sfu/oracle-sfdevnl >> >> _______________________________________________ >> >> Gramps-devel mailing list >> >> Gra...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Protect Your Site and Customers from Malware Attacks >> > Learn about various malware tactics and how to avoid >> them. Understand >> > malware threats, the impact they can have on your >> business, and how you >> > can protect your company and customers by using code >> signing. >> > http://p.sf.net/sfu/oracle-sfdevnl >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> > >> >> ------------------------------------------------------------------------------ >> Protect Your Site and Customers from Malware Attacks >> Learn about various malware tactics and how to avoid them. >> Understand >> malware threats, the impact they can have on your business, >> and how you >> can protect your company and customers by using code >> signing. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > > > |
From: jerome <rom...@ya...> - 2011-01-13 13:40:21
|
OK, I did not want to generate a "quick & dirty" patch for this. I suppose to force "1" when "0" has been set could be the way to do that. Why I did this unwanted thing ? Because I thought that column width on gramplet pane might be an alternative to standard use (maybe width set for gramplet pane ?). Note, it is not the first time I get some strange display with custom widget and translations: http://www.gramps-project.org/bugs/view.php?id=3596 http://www.gramps-project.org/bugs/view.php?id=3793 http://www.gramps-project.org/bugs/view.php?id=4410 http://www.gramps-project.org/bugs/view.php?id=3595 ... Sometimes the solution was to translate with less words/characters as possible. But the real solution should be somewhere else. gen.plug.menu / EnumeratedListOption ? Sometimes, it was just to set a greater value on model or to let glade builder use the available space (do not use 'width_request'). Gramplet pane and sidebar are working with viewmanager, list, gui, etc... that's more complexe for me! The display/behavior should be the same with and without translation. I understand that list expand the dialog or window according entries, but in these cases there was some available spaces before expansion of the main dialog/tab/window. There is surely a value, which do not need to be defined somewhere, but as this is not visible without the translation, I guess it will be easier to fix this if I find the cause. To remove Search Bar is also an alternative but maybe the unwanted one. Jérôme --- En date de : Jeu 13.1.11, Doug Blank <dou...@gm...> a écrit : > De: Doug Blank <dou...@gm...> > Objet: Re: [Gramps-devel] New Gramps bottombar > À: "jerome" <rom...@ya...> > Cc: "Benny Malengier" <ben...@gm...>, "Gramps developers" <gra...@li...> > Date: Jeudi 13 janvier 2011, 12h53 > On Thu, Jan 13, 2011 at 6:45 AM, > jerome <rom...@ya...> > wrote: > > Note, there is a bug in gramplet pane configuration > (also stable release) ... > > > > 3.2.6-SVN: > > 26671: ERROR: gramps.py: line 138: Unhandled > exception > > Traceback (most recent call last): > > File > "/usr/share/gramps/gui/widgets/grampletpane.py", line 1192, > in add_gramplet > > self.columns[pos].pack_start(gramplet.mainframe, > expand=gramplet.expand) > > IndexError: list index out of range > > > > trunk: > > 170189: ERROR: gramps.py: line 142: Unhandled > exception > > Traceback (most recent call last): > > File > "/home/nono/gramps/trunk/src/gui/widgets/grampletpane.py", > line 1289, in add_gramplet > > self.columns[pos].pack_start(gramplet.mainframe, > expand=gramplet.expand) > > IndexError: list index out of range > > > > How to reproduce it ? > > > > Just set number of column (gramplet layout) to "0" ! > > Reminds me of an old joke: > > Patient: "Doctor! It hurts when I move my arm this way!" > > Doctor: "Well, then, don't move it that way." > > Seriously though, I'll fix that :) > > -Doug > > > Agreed, stupid but it returns Index error. :( > > > > > > Jérôme > > > > > > --- En date de : Mer 12.1.11, Doug Blank <dou...@gm...> > a écrit : > > > >> De: Doug Blank <dou...@gm...> > >> Objet: Re: [Gramps-devel] New Gramps bottombar > >> À: "Benny Malengier" <ben...@gm...> > >> Cc: "Gramps developers" <gra...@li...> > >> Date: Mercredi 12 janvier 2011, 14h18 > >> On Wed, Jan 12, 2011 at 3:36 AM, > >> Benny Malengier > >> <ben...@gm...> > >> wrote: > >> > Looks nice. I can see people really liking > this. > >> > > >> > Some comments: > >> > > >> > 1/ Users don't discover functionality easily. > So I > >> suggest that we all try > >> > this a bit and in a month for 3.3 to query if > we > >> should have the bottom bar > >> > visible by default on fresh install, and if > so what > >> gramplets. > >> > >> Good idea. I think some (or most) views are better > with > >> some specific > >> gramplets. We can get some user input on this too, > Eg, > >> what > >> functionality/data do you want to see on each > view? > >> > >> > 2/ Write a quick blog post of this work. Some > users do > >> react to that. > >> > > >> > 3/ We must make it clear to users that they > still need > >> to double click or > >> > press edit button on the listview to actually > change a > >> person. That is, the > >> > editors are not in the gramplets (although > gramplets > >> can be written for it, > >> > I would not experiment with that for 3.3) > >> > > >> > 4/ Passing key presses: When I select an > attribute in > >> Attributes bottombar, > >> > then ctrl+ins does still do insert person. > That is > >> good. However, ctrl+enter > >> > or enter does not edit the current person. We > need a > >> keypress to edit person > >> > when things are selected on the gramplet > >> > > >> > 5/ How to know the name of the gramplet in > the > >> bottombar. Eg after remove, > >> > you want to add it again, but don't know the > name. > >> Perhaps the tooltip on > >> > the tab to contain the name of the gramplet? > >> > >> That confused me too at first as there is no way > to tell > >> currently > >> which gramplets are showing. > >> > >> The gramplet pane has support too to undelete a > deleted > >> gramplet. This > >> is nice as some gramplets have data in them that > would be > >> bad if you > >> couldn't get it back. Perhaps we can have an undo > button or > >> menu > >> option for this. > >> > >> > 6/ In Attributes, tooltip on an entry says: > Drag > >> Properties Button to move > >> > and click it for setup. > >> > I don't understand this tooltip. > >> > >> This is only for the gramplet grid view, where > gramplets > >> can be moved. > >> Setup is now in config. > >> > >> > 7/ Double click on attribute gives a > quick-view. I > >> suppose this is gramplet > >> > functionality? If so, having this action in a > context > >> menu too would be > >> > nice. Other quickviews can be added then, eg: > sources > >> of attribute, ... . > >> > Most important though: Users will expect > double click > >> to allow edit of the > >> > person attribute! How can we offer this? > Context menu > >> with 'Edit Attribute', > >> > that opens the person editor and the > attribute editor > >> of the correct > >> > attribute? This is a usability concept we > should have > >> a clear answer to. See > >> > 3/ and 4/ above. > >> > >> I'll work on the unified context menu > infrastructure, as > >> mentioned a > >> week or two ago. > >> > >> -Doug > >> > >> > That's it for now. > >> > > >> > Benny > >> > > >> > > >> > 2011/1/11 Nick Hall <nic...@ho...> > >> >> > >> >> Devs, > >> >> > >> >> I have just committed a change which adds > a new > >> bottombar to Gramps. > >> >> > >> >> You can enable the bottom bar from the > menu: > >> View -> Bottombar. > >> >> > >> >> Each tab contains one gramplet. You > can > >> re-order them by drag-and-drop. > >> >> > >> >> There are three buttons on the right hand > side of > >> the bottombar. Use > >> >> these to add or remove gramplets and also > to close > >> the bottombar. > >> >> > >> >> I have removed the normal gramplet > controls. > >> This creates more space > >> >> and presents a cleaner interface to the > user. > >> The minimise button is > >> >> not applicable for the bottom bar, and > >> drag-and-drop functionality has > >> >> moved to the tab. I have not > implemented > >> detaching of gramplets yet, > >> >> but this could be achieved by dragging > the tab out > >> of the notebook (this > >> >> is standard gtk functionality). > >> >> > >> >> I have written four example bottombar > gramplets > >> for the Person Views: > >> >> > >> >> 1. Details: This combines the primary > picture, > >> with parents, events and > >> >> attributes to create a summary view for a > person. > >> >> > >> >> 2. Gallery: This displays the pictures > of a > >> person in a scrollable > >> >> list. Double-click to view the image > with the > >> default viewer application. > >> >> > >> >> 3. Residence: An example displaying a > single > >> event type. Double-click > >> >> to edit an event. > >> >> > >> >> 4. Attributes: Just a GUI version of > the > >> existing Attributes gramplet. > >> >> Double-click for the quick report. > >> >> > >> >> I was trying to make the gramplets look > like they > >> are part of core > >> >> Gramps. Similar functionality is > available in > >> the person editor, but > >> >> the bottom bar gramplets are intended to > be > >> optimised for viewing the > >> >> data rather than editing it. > >> >> > >> >> I look forward to your feedback. > >> >> > >> >> Regards, > >> >> > >> >> > >> >> Nick. > >> >> > >> >> > >> >> > >> >> > >> > ------------------------------------------------------------------------------ > >> >> Gaining the trust of online customers is > vital for > >> the success of any > >> >> company > >> >> that requires sensitive data to be > transmitted > >> over the Web. Learn how > >> >> to > >> >> best implement a security strategy that > keeps > >> consumers' information > >> >> secure > >> >> and instills the confidence they need to > proceed > >> with transactions. > >> >> http://p.sf.net/sfu/oracle-sfdevnl > >> >> > _______________________________________________ > >> >> Gramps-devel mailing list > >> >> Gra...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > > >> > > >> > > >> > ------------------------------------------------------------------------------ > >> > Protect Your Site and Customers from Malware > Attacks > >> > Learn about various malware tactics and how > to avoid > >> them. Understand > >> > malware threats, the impact they can have on > your > >> business, and how you > >> > can protect your company and customers by > using code > >> signing. > >> > http://p.sf.net/sfu/oracle-sfdevnl > >> > > _______________________________________________ > >> > Gramps-devel mailing list > >> > Gra...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > > >> > > >> > >> > ------------------------------------------------------------------------------ > >> Protect Your Site and Customers from Malware > Attacks > >> Learn about various malware tactics and how to > avoid them. > >> Understand > >> malware threats, the impact they can have on your > business, > >> and how you > >> can protect your company and customers by using > code > >> signing. > >> http://p.sf.net/sfu/oracle-sfdevnl > >> _______________________________________________ > >> Gramps-devel mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > > > > > > > > > |
From: Nick H. <nic...@ho...> - 2011-01-12 19:51:34
|
Benny, Thanks for your comments. I haven't finished writing this functionality yet, but I got to the stage where I thought that I needed some feedback before continuing. Benny Malengier wrote: > Looks nice. I can see people really liking this. I'm glad you like it. > > Some comments: > > 1/ Users don't discover functionality easily. So I suggest that we all > try this a bit and in a month for 3.3 to query if we should have the > bottom bar visible by default on fresh install, and if so what gramplets. I'm happy with that. I will make the default to show the bottombar. > > 2/ Write a quick blog post of this work. Some users do react to that. Good idea. > > 3/ We must make it clear to users that they still need to double click > or press edit button on the listview to actually change a person. That > is, the editors are not in the gramplets (although gramplets can be > written for it, I would not experiment with that for 3.3) Yes, I agree - for 3.3 the bottombar gramplets should be for viewing data only. The users should edit data using the editors. We could allow users to invoke editors from the bottombar gramplets though. > > 4/ Passing key presses: When I select an attribute in Attributes > bottombar, then ctrl+ins does still do insert person. That is good. > However, ctrl+enter or enter does not edit the current person. We need > a keypress to edit person when things are selected on the gramplet > This looks like a bug. I'll look into it. > 5/ How to know the name of the gramplet in the bottombar. Eg after > remove, you want to add it again, but don't know the name. Perhaps the > tooltip on the tab to contain the name of the gramplet? Adding a tooltip to the tab would be easy. We also need to think about which gramplets we allow in the sidebar and bottombar in each view. A bottombar gramplet designed for a person view would probably not be appropriate for the event view. Also, a bottombar gramplet will be designed to be displayed horizontally and may not look good in the sidebar. Perhaps we need to add some extra classification to the gramplet plugin data? > > 6/ In Attributes, tooltip on an entry says: Drag Properties Button to > move and click it for setup. > I don't understand this tooltip. Fixed. I have now added some tooltips. > > 7/ Double click on attribute gives a quick-view. I suppose this is > gramplet functionality? If so, having this action in a context menu > too would be nice. Other quickviews can be added then, eg: sources of > attribute, ... . > Most important though: Users will expect double click to allow edit of > the person attribute! How can we offer this? Context menu with 'Edit > Attribute', that opens the person editor and the attribute editor of > the correct attribute? This is a usability concept we should have a > clear answer to. See 3/ and 4/ above. The four gramplets I created were intended to demonstrate some ideas. We will have to make the interface consistent. I was looking at the bottombar tabs as similar to the editor tabs, but optimised for viewing the data rather than editing it. The Details tab, which I intend to have for every view, doesn't have a double-click action at the moment. It looks like the Relationship View though, so users may expect to click an icon to invoke an editor. The Gallery tab, was inspired by the feature request, 4219: shortcut to view a media file from events or sources. http://www.gramps-project.org/bugs/view.php?id=4219 A double-click to invoke a viewer rather than an editor seems correct here. The Attributes tab, is just a gui version of the existing gramplet. I kept the same double-click action. The Residence tab, was just meant to illustrate a possibility. We probably need to think about this further, but I like the idea f the context menu. Nick. > > That's it for now. > > Benny > > > 2011/1/11 Nick Hall <nic...@ho... > <mailto:nic...@ho...>> > > Devs, > > I have just committed a change which adds a new bottombar to Gramps. > > You can enable the bottom bar from the menu: View -> Bottombar. > > Each tab contains one gramplet. You can re-order them by > drag-and-drop. > > There are three buttons on the right hand side of the bottombar. Use > these to add or remove gramplets and also to close the bottombar. > > I have removed the normal gramplet controls. This creates more space > and presents a cleaner interface to the user. The minimise button is > not applicable for the bottom bar, and drag-and-drop functionality has > moved to the tab. I have not implemented detaching of gramplets yet, > but this could be achieved by dragging the tab out of the notebook > (this > is standard gtk functionality). > > I have written four example bottombar gramplets for the Person Views: > > 1. Details: This combines the primary picture, with parents, > events and > attributes to create a summary view for a person. > > 2. Gallery: This displays the pictures of a person in a scrollable > list. Double-click to view the image with the default viewer > application. > > 3. Residence: An example displaying a single event type. > Double-click > to edit an event. > > 4. Attributes: Just a GUI version of the existing Attributes > gramplet. > Double-click for the quick report. > > I was trying to make the gramplets look like they are part of core > Gramps. Similar functionality is available in the person editor, but > the bottom bar gramplets are intended to be optimised for viewing the > data rather than editing it. > > I look forward to your feedback. > > Regards, > > > Nick. > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of > any company > that requires sensitive data to be transmitted over the Web. > Learn how to > best implement a security strategy that keeps consumers' > information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > <mailto:Gra...@li...> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Peter L. <pet...@te...> - 2011-01-12 08:55:08
|
<snip> > 6/ In Attributes, tooltip on an entry says: Drag Properties Button to move > and click it for setup. > I don't understand this tooltip. This tool tip is used on many/every gramplet. Seems to be some "default". It is defined in src\gui\widgets\grampletpane.py /Peter |
From: Benny M. <ben...@gm...> - 2011-01-12 09:07:14
|
Doug, as Rob also already remarked: Do we remove Split view gramplets now from the addons? I think that would be best. Benny 2011/1/11 Doug Blank <dou...@gm...> > Nick, > > Having troubling running trunk: > > 22061: ERROR: gramps.py: line 142: Unhandled exception > Traceback (most recent call last): > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, > in view_changed > self.__change_page(page_num) > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1214, > in __change_page > self.active_page.set_active() > File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > line 220, in set_active > ListView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/listview.py", line > 240, in set_active > NavigationView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", > line 153, in set_active > PageView.set_active(self) > File "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line > 379, in set_active > self.bottombar.set_active() > File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, in > set_active > title = get_title(self.notebook, page) > File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, in > get_title > return notebook.get_tab_label_text(notebook.get_nth_page(page_num)) > TypeError: Gtk.Notebook.get_tab_label_text() argument 1 must be > gtk.Widget, not None > > 29382: ERROR: gramps.py: line 142: Unhandled exception > Traceback (most recent call last): > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, > in view_changed > self.__change_page(page_num) > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1211, > in __change_page > self.__disconnect_previous_page() > File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1241, > in __disconnect_previous_page > self.active_page.set_inactive() > File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", > line 228, in set_inactive > self.uistate.viewmanager.tags.tag_disable() > File "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, in > tag_disable > self.uistate.uimanager.remove_ui(self.tag_id) > TypeError: Parameter 'merge_id' must be an int or a long > > I deleted my ~/.gramps/gramps33/*.ini files, but no avail. > > -Doug > > On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: > > Devs, > > > > I have just committed a change which adds a new bottombar to Gramps. > > > > You can enable the bottom bar from the menu: View -> Bottombar. > > > > Each tab contains one gramplet. You can re-order them by drag-and-drop. > > > > There are three buttons on the right hand side of the bottombar. Use > > these to add or remove gramplets and also to close the bottombar. > > > > I have removed the normal gramplet controls. This creates more space > > and presents a cleaner interface to the user. The minimise button is > > not applicable for the bottom bar, and drag-and-drop functionality has > > moved to the tab. I have not implemented detaching of gramplets yet, > > but this could be achieved by dragging the tab out of the notebook (this > > is standard gtk functionality). > > > > I have written four example bottombar gramplets for the Person Views: > > > > 1. Details: This combines the primary picture, with parents, events and > > attributes to create a summary view for a person. > > > > 2. Gallery: This displays the pictures of a person in a scrollable > > list. Double-click to view the image with the default viewer > application. > > > > 3. Residence: An example displaying a single event type. Double-click > > to edit an event. > > > > 4. Attributes: Just a GUI version of the existing Attributes gramplet. > > Double-click for the quick report. > > > > I was trying to make the gramplets look like they are part of core > > Gramps. Similar functionality is available in the person editor, but > > the bottom bar gramplets are intended to be optimised for viewing the > > data rather than editing it. > > > > I look forward to your feedback. > > > > Regards, > > > > > > Nick. > > > > > > > ------------------------------------------------------------------------------ > > Gaining the trust of online customers is vital for the success of any > company > > that requires sensitive data to be transmitted over the Web. Learn how > to > > best implement a security strategy that keeps consumers' information > secure > > and instills the confidence they need to proceed with transactions. > > http://p.sf.net/sfu/oracle-sfdevnl > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any > company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2011-01-12 13:09:14
|
On Wed, Jan 12, 2011 at 4:07 AM, Benny Malengier <ben...@gm...> wrote: > Doug, as Rob also already remarked: Do we remove Split view gramplets now > from the addons? > I think that would be best. Yes, there are a few going away. -Doug > Benny > > 2011/1/11 Doug Blank <dou...@gm...> >> >> Nick, >> >> Having troubling running trunk: >> >> 22061: ERROR: gramps.py: line 142: Unhandled exception >> Traceback (most recent call last): >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, >> in view_changed >> self.__change_page(page_num) >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1214, >> in __change_page >> self.active_page.set_active() >> File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> line 220, in set_active >> ListView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/listview.py", line >> 240, in set_active >> NavigationView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/navigationview.py", >> line 153, in set_active >> PageView.set_active(self) >> File "/home/dblank/gramps/trunk/src/gui/views/pageview.py", line >> 379, in set_active >> self.bottombar.set_active() >> File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 235, in >> set_active >> title = get_title(self.notebook, page) >> File "/home/dblank/gramps/trunk/src/gui/bottombar.py", line 347, in >> get_title >> return notebook.get_tab_label_text(notebook.get_nth_page(page_num)) >> TypeError: Gtk.Notebook.get_tab_label_text() argument 1 must be >> gtk.Widget, not None >> >> 29382: ERROR: gramps.py: line 142: Unhandled exception >> Traceback (most recent call last): >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1202, >> in view_changed >> self.__change_page(page_num) >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1211, >> in __change_page >> self.__disconnect_previous_page() >> File "/home/dblank/gramps/trunk/src/gui/viewmanager.py", line 1241, >> in __disconnect_previous_page >> self.active_page.set_inactive() >> File "/home/dblank/gramps/trunk/src/plugins/view/familyview.py", >> line 228, in set_inactive >> self.uistate.viewmanager.tags.tag_disable() >> File "/home/dblank/gramps/trunk/src/gui/views/tags.py", line 128, in >> tag_disable >> self.uistate.uimanager.remove_ui(self.tag_id) >> TypeError: Parameter 'merge_id' must be an int or a long >> >> I deleted my ~/.gramps/gramps33/*.ini files, but no avail. >> >> -Doug >> >> On Mon, Jan 10, 2011 at 8:50 PM, Nick Hall <nic...@ho...> wrote: >> > Devs, >> > >> > I have just committed a change which adds a new bottombar to Gramps. >> > >> > You can enable the bottom bar from the menu: View -> Bottombar. >> > >> > Each tab contains one gramplet. You can re-order them by >> > drag-and-drop. >> > >> > There are three buttons on the right hand side of the bottombar. Use >> > these to add or remove gramplets and also to close the bottombar. >> > >> > I have removed the normal gramplet controls. This creates more space >> > and presents a cleaner interface to the user. The minimise button is >> > not applicable for the bottom bar, and drag-and-drop functionality has >> > moved to the tab. I have not implemented detaching of gramplets yet, >> > but this could be achieved by dragging the tab out of the notebook (this >> > is standard gtk functionality). >> > >> > I have written four example bottombar gramplets for the Person Views: >> > >> > 1. Details: This combines the primary picture, with parents, events and >> > attributes to create a summary view for a person. >> > >> > 2. Gallery: This displays the pictures of a person in a scrollable >> > list. Double-click to view the image with the default viewer >> > application. >> > >> > 3. Residence: An example displaying a single event type. Double-click >> > to edit an event. >> > >> > 4. Attributes: Just a GUI version of the existing Attributes gramplet. >> > Double-click for the quick report. >> > >> > I was trying to make the gramplets look like they are part of core >> > Gramps. Similar functionality is available in the person editor, but >> > the bottom bar gramplets are intended to be optimised for viewing the >> > data rather than editing it. >> > >> > I look forward to your feedback. >> > >> > Regards, >> > >> > >> > Nick. >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Gaining the trust of online customers is vital for the success of any >> > company >> > that requires sensitive data to be transmitted over the Web. Learn how >> > to >> > best implement a security strategy that keeps consumers' information >> > secure >> > and instills the confidence they need to proceed with transactions. >> > http://p.sf.net/sfu/oracle-sfdevnl >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any >> company >> that requires sensitive data to be transmitted over the Web. Learn how >> to >> best implement a security strategy that keeps consumers' information >> secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Peter L. <pet...@te...> - 2011-01-12 15:31:58
|
Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: > <snip> > > > 6/ In Attributes, tooltip on an entry says: Drag Properties Button to > > move and click it for setup. > > I don't understand this tooltip. > > This tool tip is used on many/every gramplet. Seems to be some "default". > > It is defined in src\gui\widgets\grampletpane.py If there is no tool tip defined, wouldn't it be better to let the tool tip be an empty string in stead of this "Drag Properties Button to move and click it for setup", which seems to be completely out of context? /Peter |
From: Nick H. <nic...@ho...> - 2011-01-12 22:15:16
|
Peter, I have now added tooltips. The default tooltip is applicable to the grid layout only. We should always override the default for the tabbed layout. Nick. Peter Landgren wrote: > Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: > >> <snip> >> >> >>> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to >>> move and click it for setup. >>> I don't understand this tooltip. >>> >> This tool tip is used on many/every gramplet. Seems to be some "default". >> >> It is defined in src\gui\widgets\grampletpane.py >> > > If there is no tool tip defined, wouldn't it be better to let the tool tip be an empty string in > stead of this "Drag Properties Button to move and click it for setup", which seems to be completely > out of context? > > /Peter > > > |
From: Peter L. <pet...@te...> - 2011-01-13 09:30:29
|
Nick, OK. But if I, as an example, add the simple Clock Gramplet, I get this tool tip "Drag Properties Button to move and click it for setup." Independet of where I add it; gramplet view, bottombar or sidebar. This is so for both branch and trunk. /Peter > Peter, > > I have now added tooltips. > > The default tooltip is applicable to the grid layout only. We should > always override the default for the tabbed layout. > > Nick. > > Peter Landgren wrote: > > Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: > >> <snip> > >> > >>> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to > >>> move and click it for setup. > >>> I don't understand this tooltip. > >> > >> This tool tip is used on many/every gramplet. Seems to be some > >> "default". > >> > >> It is defined in src\gui\widgets\grampletpane.py > > > > If there is no tool tip defined, wouldn't it be better to let the tool > > tip be an empty string in stead of this "Drag Properties Button to move > > and click it for setup", which seems to be completely out of context? > > > > /Peter -- Peter Landgren Talken Hagen 671 94 BRUNSKOG 0570-530 21 070-345 0964 pet...@te... Skype: pgl4820.2 |
From: Nick H. <nic...@ho...> - 2011-01-13 14:14:38
|
Peter, OK. I'll change the default for the tabbed layout to no tooltip. Nick. Peter Landgren wrote: > Nick, > > OK. > But if I, as an example, add the simple Clock Gramplet, I get this tool tip "Drag Properties Button > to move and click it for setup." Independet of where I add it; gramplet view, bottombar or sidebar. > > This is so for both branch and trunk. > > /Peter > > > >> Peter, >> >> I have now added tooltips. >> >> The default tooltip is applicable to the grid layout only. We should >> always override the default for the tabbed layout. >> >> Nick. >> >> Peter Landgren wrote: >> >>> Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: >>> >>>> <snip> >>>> >>>> >>>>> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to >>>>> move and click it for setup. >>>>> I don't understand this tooltip. >>>>> >>>> This tool tip is used on many/every gramplet. Seems to be some >>>> "default". >>>> >>>> It is defined in src\gui\widgets\grampletpane.py >>>> >>> If there is no tool tip defined, wouldn't it be better to let the tool >>> tip be an empty string in stead of this "Drag Properties Button to move >>> and click it for setup", which seems to be completely out of context? >>> >>> /Peter >>> > > |
From: Nick H. <nic...@ho...> - 2011-01-13 23:51:47
|
Benny, I can't reproduce this problem. The ctrl+enter works for me, even when a row in the attributes gramplet is selected. Could you try this again and let me know the steps to reproduce it. Thanks, Nick. Benny Malengier wrote: > > 4/ Passing key presses: When I select an attribute in Attributes > bottombar, then ctrl+ins does still do insert person. That is good. > However, ctrl+enter or enter does not edit the current person. We need > a keypress to edit person when things are selected on the gramplet > > |
From: Nick H. <nic...@ho...> - 2011-01-13 23:53:21
|
Peter, I have now removed the default tooltip for the tabbed gramplet layout. Nick. Peter Landgren wrote: > Nick, > > OK. > But if I, as an example, add the simple Clock Gramplet, I get this tool tip "Drag Properties Button > to move and click it for setup." Independet of where I add it; gramplet view, bottombar or sidebar. > > This is so for both branch and trunk. > > /Peter > > > >> Peter, >> >> I have now added tooltips. >> >> The default tooltip is applicable to the grid layout only. We should >> always override the default for the tabbed layout. >> >> Nick. >> >> Peter Landgren wrote: >> >>> Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: >>> >>>> <snip> >>>> >>>> >>>>> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to >>>>> move and click it for setup. >>>>> I don't understand this tooltip. >>>>> >>>> This tool tip is used on many/every gramplet. Seems to be some >>>> "default". >>>> >>>> It is defined in src\gui\widgets\grampletpane.py >>>> >>> If there is no tool tip defined, wouldn't it be better to let the tool >>> tip be an empty string in stead of this "Drag Properties Button to move >>> and click it for setup", which seems to be completely out of context? >>> >>> /Peter >>> > > |
From: Peter L. <pet...@te...> - 2011-01-14 10:12:40
|
Nick, After svn up, the tool tip is not visible in bottom bar, but it's still visible in the Gramplet view and in the sidebar for all gramplets which don't have a tool tip defined. I think it should be empty, as it shows this message all over the Data Entry Gramplet. What/where is the "Properties Button"? I can't find any button like that. /Peter > Peter, > > I have now removed the default tooltip for the tabbed gramplet layout. > > Nick. > > Peter Landgren wrote: > > Nick, > > > > OK. > > But if I, as an example, add the simple Clock Gramplet, I get this tool > > tip "Drag Properties Button to move and click it for setup." Independet > > of where I add it; gramplet view, bottombar or sidebar. > > > > This is so for both branch and trunk. > > > > /Peter > > > >> Peter, > >> > >> I have now added tooltips. > >> > >> The default tooltip is applicable to the grid layout only. We should > >> always override the default for the tabbed layout. > >> > >> Nick. > >> > >> Peter Landgren wrote: > >>> Den Wednesday 12 January 2011 09.57.54 skrev Peter Landgren: > >>>> <snip> > >>>> > >>>>> 6/ In Attributes, tooltip on an entry says: Drag Properties Button to > >>>>> move and click it for setup. > >>>>> I don't understand this tooltip. > >>>> > >>>> This tool tip is used on many/every gramplet. Seems to be some > >>>> "default". > >>>> > >>>> It is defined in src\gui\widgets\grampletpane.py > >>> > >>> If there is no tool tip defined, wouldn't it be better to let the tool > >>> tip be an empty string in stead of this "Drag Properties Button to move > >>> and click it for setup", which seems to be completely out of context? > >>> > >>> /Peter -- Peter Landgren Talken Hagen 671 94 BRUNSKOG 0570-530 21 070-345 0964 pet...@te... Skype: pgl4820.2 |