gtg-contributors team mailing list archive

[Paul Natsuo Kishimoto <mail@xxxxxxxxxxxxxxxxxxx>]

On Tue, 2010-06-01 at 23:13 +0200, Karlo Jež wrote:
> On Tue, Jun 1, 2010 at 11:06 PM, Bryce Harrington
> <bryce@xxxxxxxxxxxxx> wrote:
>         On Tue, Jun 01, 2010 at 12:59:55PM -0400, Paul Natsuo
>         Kishimoto wrote:
>         > Currently we have:
>         > data/
>         > doc/
>         > GTG/
>         >         backends/
>         >         core/
>         >         plugins/
>         >         taskbrowser/
>         >         taskeditor/
>         >         tests/
>         >         tools/
>         >         viewmanager/
>         >         ...
>         > po/
>         > scripts/
>         > test/
>         > gtcli
>         > gtg
>         > gtg_new_task
>         > ...
>         >
>         
>         > Please let me know what you think.
>         
>         
>         Note the dbus interface stuff is currently in viewmanager but
>         assuming
>         dbus is the communication layer between client and server,
>         it'd need to
>         be present on the serverside.  Whereas most other stuff in the
>         viewmanager directory would move to the client side in such a
>         split.
>         
>         
>         
> Yes, but there are some parts of the dbus interface that should stay
> on the client side. There are functions that open windows and such and
> those should stay in the viewmanager, while other functions should go
> to the server.
> 
Right, I'd noted that. I'm thinking:

org.GTG → org.gnome.GTG
/org/GTG
→ /org/gnome/GTG/Store, /org/gnome/GTG/Store/Task/7f6fe274-42a6-4ee8-833f-f664e2c4faa2, /org/gnome/GTG/UI, etc.

That is, the server and client will eventually each have their own,
non-overlapping DBus APIs.

-- 
Paul Kishimoto
MASc candidate (2010), Flight Systems & Control Group
University of Toronto Institute for Aerospace Studies (UTIAS)

http://paul.kishimoto.name — +19053029315

Attachment: signature.asc
Description: This is a digitally signed message part