gtg-contributors team mailing list archive

[Bertrand Rousseau <bertrand.rousseau@xxxxxxxxx>]

2012/3/25 meg ford <meg387@xxxxxxxxx>:
>
>
> 2012/3/25 meg ford <meg387@xxxxxxxxx>
>>
>> Hi,
>>
>> 2012/3/25 Bertrand Rousseau <bertrand.rousseau@xxxxxxxxx>
>>>
>>> 2012/3/25 Radina Matic <radina.matic@xxxxxxxxx>:
>>> > After working some more with the daily GTG build, I have more
>>> > questions,
>>> > comments and suggestions:
>>> >
>>> > -----
>>> >
>>> > Is there any special reason that the item "Backends" stands alone
>>> > inside the
>>> > menu Edit? It seems to me that, since Backends are optional features of
>>> > GTG,
>>> > they should be visible as another tab in the Preferences window just
>>> > like
>>> > Plugins...
>>>
>>> I can't remember any specific reason (maybe someone else does).
>>>
>>> IMHO, it's there because it's more visible. Conceptually, its place is
>>> next to the plugins, indeed. Another solution would be to put the
>>> plugins in the menu too. I guess this should be decided by favoring
>>> consistency among GNOME app. Is there some kind of GNOME policy for
>>> this?
>>
>>
>> The guidance I'm seeing in GNOME 3 HIG so far for this is here.
>> The editable lists template would most likely apply to the submenu,
>> though, rather than the tab in the main UI.
>
>
> Sorry, I mean popup window rather than submenu :)

I have a hard time finding objective reason to back a solution here.
However, the following elements seem relevant to me:

 - the backend configuration UI is large, I think it would feel out of
place in the preference pane (it subjective, I know).
 - the closest concept I know is the "Account" configuration pane of
app with online services (e.g. empathy), which are available directly
in the "Edit" menu.
 - I like the idea of putting this forward in a more visible place

So the best place to me seems to keep this element in the Edit menu
(but under another name, like "Synchronization services..."

Those are not good reasons (they're not linked to any kind of
usability considerations), I admit. However, on the other hand, I'm
also under the impression that the way GTG proposes the sync service
feature should be rethought a bit (right now it is very
feature-oriented rather than service-oriented). So maybe we shouldn't
be too picky until the feature is thoroughly thought, and then design
a better UI.

>>
>>
>> For handling the edit menu, there is some guidance here.
>> IMO, I think we need to ask about this, however, since the page is not yet
>> complete and is marked as experimental.
>>
>> Meg
>>
>>>
>>> If both functionalities are put in the preference dialog, than we
>>> should make sure to advertise them right so that users don't miss it
>>> (those are significant GTG features).
>>>
>>> >
>>> > -----
>>> >
>>> > Preferences window:
>>> >
>>> > I propose to rename the tab "Behaviour" into "General", and rename the
>>> > label
>>> > "General" into "Startup".
>>>
>>> Works for me.
>>>
>>> > -----
>>> >
>>> > Suggestions for the items in the Main Menu > Help
>>> >
>>> > - Contents F1 (should open the Mallard Help in the making ;)
>>> > - Get Help Online... (should link to GTG Wiki page)
>>> > - Translate GTG into your Language (should link to Launchpad
>>> > Translations)
>>> > - Report a Problem (not sure it should open Apport or link to Launchpad
>>> > Bugs)
>>>
>>> It should link to launchpad.
>>>
>>> > - About (same as now but copyright info should be updated)
>>>
>>> Good point. Could you file a bug about this?
>>>
>>>
>>> Thanks again for your work!
>>>
>>> Regards,
>>>
>>> Bertrand
>>>
>>> >
>>> > ------
>>> >
>>> > Cheers,
>>> > Radina
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > 2012/3/23 Izidor Matušov <izidor.matusov@xxxxxxxxx>
>>> >>
>>> >> Hi,
>>> >>
>>> >> I started working on a branch to apply you string modifications. It's
>>> >> late
>>> >> here, I would finish it tomorrow or after weekend. I am sharing my few
>>> >> suggestions bellow.
>>> >>
>>> >> Am 23.03.2012 03:24, schrieb Radina Matic:
>>> >>
>>> >>> Bertrand, I am glad that my comments will make GTG more usable :)
>>> >>>
>>> >>> These details are easier to catch for somebody with less programming
>>> >>> knowledge like me, as I am closer to the point of view of the
>>> >>> ordinary
>>> >>> user...
>>> >>>
>>> >>> To make the my replies clearer (replying on mailing lists often gets
>>> >>> so
>>> >>> messy) I'll strip the text to just the important bits:
>>> >>>
>>> >>> ---------------------------------
>>> >>>  > 39.
>>> >>>
>>> >>> Actually the subject of this phrase is automatically added with
>>> >>> "self.software.title()" in the code. It should thus read something
>>> >>> like: "Tomboy was found on the system, but it (...)". So I guess this
>>> >>> string is ok.
>>> >>>
>>> >>>  > was found on the system, but it does not provide a DBUS interface
>>> >>> which is
>>> >>>  > required by the Tomboy/Gnote plugin.
>>> >>>
>>> >>> This is perfect!
>>> >>
>>> >>
>>> >> It seems that according official pages [0], it is written as D-Bus. I
>>> >> would use D-Bus or DBus, but not DBUS because it feels like shouting.
>>> >>
>>> >>
>>> >> 0: http://www.freedesktop.org/wiki/Software/dbus
>>> >>
>>> >>
>>> >>
>>> >>> ------------------------
>>> >>>
>>> >>> Ok, now that I know that "self.software.title()" in the code will
>>> >>> result
>>> >>> in app name (Tomboy in this case) then I would rephrase the string
>>> >>> again:
>>> >>>
>>> >>> program seems to be installed on your system, but it does not provide
>>> >>> a
>>> >>> DBUS interface which is required by the Tomboy/Gnote plugin in GTG.
>>> >>
>>> >>
>>> >> I updated the string to be:
>>> >>
>>> >> message_format = _("%s seems to be installed on your "
>>> >>
>>> >>   "system, but it does not provide a DBUS interface "
>>> >>   "which is required by the Tomboy/Gnote plugin "
>>> >>   "in GTG.") % self.software.title()
>>> >>
>>> >> It should produce strings:
>>> >>  "Tomboy seems to be ..."
>>> >>  "Gnote seems to be ..."
>>> >>
>>> >> Is that what you asked for?
>>> >>
>>> >>> It's actually more of a synchronization service. It's a specific
>>> >>> category of optional features that are kind of distinct of plugins.
>>> >>> But I agree that this might be confusing. That would certainly
>>> >>> require
>>> >>> some discussion. This could be done during the ongoing redesign
>>> >>> effort.
>>> >>>
>>> >>> Right now, for the sake of consistency, I'd leave it that way. If we
>>> >>> were to adopt "plugins" for instance, then we would also have to
>>> >>> change the UI a bit (right now those features have separate UI
>>> >>> spaces).
>>> >>> --------------------
>>> >>>
>>> >>> I understand, and I am not proposing to necessarily get rid of it
>>> >>> altogether, just to explain it better. So, if it is kind of a
>>> >>> synchronization service (which is fairly understandable), why not
>>> >>> call
>>> >>> it "*backend **synchronization service*". It may be long, but it is
>>> >>>
>>> >>> clearer. I know that KISS is mantra, but sometimes longer is
>>> >>> better... ;)
>>> >>
>>> >>
>>> >> I don't want to be nitpicking but there are also just import or
>>> >> read-only
>>> >> backends: fetch the list of bugs assigned to me, import unread
>>> >> e-mails,
>>> >> import articles from RSS and so on => just one way.
>>> >>
>>> >> Synchronization means both ways: I get some tasks, modify them and
>>> >> send
>>> >> them away. Although it wouldn't be correct, probably everybody would
>>> >> use
>>> >> just synchronization backends... ehm.. services.
>>> >>
>>> >>
>>> >>> Anyway, I do not think there is any significant difference in
>>> >>> meaning,
>>> >>> and the point is to choose one way of calling a certain feature and
>>> >>> stick with it everywhere: main menu, contextual menus and the app
>>> >>> window.
>>> >>
>>> >>
>>> >> Software is evolving over the time. Maybe somebody added a new menu
>>> >> item
>>> >> and didn't check the capitalization, used a synonym, etc. If you find
>>> >> any
>>> >> other glitch, just report it - I am willing to correct it.
>>> >>
>>> >>
>>> >>
>>> >>>  > 267. "Make a Task" - is this different from "New Task"?
>>> >>>
>>> >>> I can't seem to find where this string is used...
>>> >>> ---------------------------------------------------------------
>>> >>>
>>> >>> I couldn't either, maybe it is an obsolete part of the code?
>>> >>
>>> >>
>>> >> Yes, it is unused code. Thanks for pointing it out.
>>> >>
>>> >> Izidor
>>> >>
>>> >> _______________________________________________
>>> >> Mailing list: https://launchpad.net/~gtg-contributors
>>> >> Post to     : gtg-contributors@xxxxxxxxxxxxxxxxxxx
>>> >> Unsubscribe : https://launchpad.net/~gtg-contributors
>>> >> More help   : https://help.launchpad.net/ListHelp
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Mailing list: https://launchpad.net/~gtg-contributors
>>> > Post to     : gtg-contributors@xxxxxxxxxxxxxxxxxxx
>>> > Unsubscribe : https://launchpad.net/~gtg-contributors
>>> > More help   : https://help.launchpad.net/ListHelp
>>> >
>>>
>>>
>>>
>>> --
>>> Bertrand Rousseau
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~gtg-contributors
>>> Post to     : gtg-contributors@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~gtg-contributors
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>



-- 
Bertrand Rousseau