Hi Karlos, Glad to see you again as you are, obviously, the best person for the job.
GTG has a DBus interface now, so here's the current plan for the web interface: - Build the webinterface using DBus on top of a "normal desktop PC" - Later, we will separate GTG into GTG-server and GTG-gtk, making the UI speak through DBus too. But it could happen later, it is not a problem to start the work right now. The DBus interface might not be complete. Also, I believe that liblarch itself should be exposed through DBus, it would make things a lot more easier. So, what you should do now is : 1) identify the DBus API you need to start working 2) start working 3) As soon as you need a new API, get in touch with me or Izidor The biggest challenge I foresee is multi-user storage. Currently, GTG has no concept of user. But, obviously, the web interface will require a valid logged user (assume that the user login is an email address). My take is that currently we have a 123123123.xml file for the task list and that it could be relatively easy to give "[email protected]" parameter to DBus so it opens only "[email protected]/12123123.xml". The good thing about re-using GTG is that backends will still be available in the web interface. Lionel Le 14/02/12 00:19, Karlo Jež a écrit : > Hello, GTGers. > > Congratulations to Izidor and Lionel for releasing 0.2.9. :) > > I see there is interest in continuing the web interface. I would > really like to continue my work on GTG web, because I do miss it. > My lack of activity since then was due to my focus on getting a > masters degree. I have just finished my final exams last week (yaay!) > and I basically have a free semester only to work on my thesis, so I > have lots of free time. :) > Also, there was the issue of Paul Kishimoto's project from 2010. which > wasn't finished, and the web interface depends on it. (well, it > doesn't now because it uses a dummy backend, but it needs a proper > dbus server) > > I think there are three options for a functional web interface: > > 1. Separating GTG to a client-server system with dbus interface > between them. I believe that was the original project. > 2. Keeping a monolithic GTG with a dbus interface and running the web > on top of that - like the web view in Transmission. That means that > server needs to run on a desktop computer or that GTG should be > modified so it can run in the background without displaying anything. > 3. Making the GTG web interface a regular django application with > tasks in models. There would be a lot of duplication of work, as the > web interface would be a completely separate project. > > My preferred option would be 2. as it requires the least amount of > work - only expanding the dbus interface for the desktop mode. Bit > more work for it to work in the background. > > What do you think? > > > _______________________________________________ > Mailing list: https://launchpad.net/~gtg-contributors > Post to : [email protected] > Unsubscribe : https://launchpad.net/~gtg-contributors > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~gtg-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg-contributors More help : https://help.launchpad.net/ListHelp
