[Tomdroid-dev] Snowy synchronization branch
Hi list, I'm currently trying to have Tomdroid synchronize with Snowy. I've set up a branch at https://code.launchpad.net/~benoit.garret/tomdroid/web-sync which contains the work so far. I've reached a stage where things are testable, meaning a bit useful but still not ready for the everyman. It is not doing any synchronization per se, but it fetches all remote notes and inserts them in the tomdroid database. As notes currently aren't editable, I don't think we would benefit from much more than that at the moment. If anyone is interested and is willing to download, compile and test, I'm open to feedback and suggestions about code, bugs, UI design, features or whatever you think could be useful. I would also be happy to help if someone has a problem setting up a local instance of the snowy server to test the code. Cheers, Benoît Garret ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Snowy synchronization branch
On Mon, Aug 24, 2009 at 6:32 PM, Olivier Bilodeau wrote: > That's awesome! > As far as the switch from note directory to the database goes, do you feel > that your code has any regression? If not, i'll review that portion quickly > then merge it and start looking at the editing problem. Everything should be working as before, except the load note from web feature. I cannot think of a case where it would be useful and I'm really tempted to remove it. Would you accept a branch or a patch for this? I'd like to work a bit more on this before it gets merged. If I'm not mistaken, Tomboy and Snowy use the guid as an unique identifier for a note. I'd like to add this field in the database and make sure we use it everywhere we need to uniquely identify a note. This would be useful to implement remote note deletion as Sandy suggested. ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Snowy synchronization branch
On Mon, Aug 24, 2009 at 3:59 PM, Sandy Armstrong wrote: > Out of curiosity, does your web-sync branch handle server-side > deletes? I'm guessing not, since a quick grep in the source code > indicates that you're not tracking the last sync revision. This also > means that every time you sync, you are getting every single note on > the server. You could save bandwidth by tracking the last sync > revision, and only getting note updates since that revision (this > would also allow you to process deletes if you wanted to). You're right, it doesn't support that at the moment. I will handle that as soon as I get the note guid stored in the database. There's still one thing I didn't quite get about the remote note deletion. The examples of GET requests on http://domain/api/1.0/user/notes don't mention note deletion. Is that an omission or should I be able to infer the deleted notes from the response (in that case, I don't see how I could do that)? Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Snowy-capable branch
Hi Stuart, The only branch that I know to be able to synchronize with Snowy is the one I made: https://code.launchpad.net/~benoit.garret/tomdroid/web-sync . This should be your best bet unless someone is hacking on a top-secret branch that isn't in Launchpad. It was working fine when I last worked on it (which was approx. 1 month ago), but I did not test it with Ubuntu One. Things it doesn't do at the moment: * OAuth 1.0a (Snowy doesn't either, as far as I know). * Check if notes have been deleted on the server. Thanks very much for having a look at this, Benoît On Tue, Oct 13, 2009 at 5:11 PM, Stuart Langridge wrote: > Hey, all. I'd like to have a play with Tomdroid synchronising with Snowy > (well, synchronising with Ubuntu One's implementation of the Snowy API), > but I'm having difficulty finding where exactly the most up-to-date > Tomdroid implementation is. What's the best place for me to look? > > sil > > ___ > Mailing list: https://launchpad.net/~tomdroid-dev > Post to : tomdroid-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~tomdroid-dev > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Web sync branch hurdles
Thanks a lot for your feedback! Motivation is much more easy to find when you know people are actually using and testing the code. On Sun, Nov 8, 2009 at 10:58 PM, Sandy Armstrong wrote: > Hi Folks, > > I finally got an Android environment set up (sadly, Eclipse just > failed totally in openSUSE, so I'm using my Mac for Android stuff). I also gave up on installing the Ubuntu Eclipse packages, installing plugins fails in every conceivable way. I usually download the tarball from eclipse.org and run it from my home dir. > I pulled Benoit's web sync branch and decided to play around and see if > I could get it to work with Ubuntu One. The first thing I did was to > change the default sync backend pref from "sdcard" to "snowy", because > without a tomdroid directory on the SD card I was getting exceptions > on startup. I'll have to catch the exception anyway. My reasoning here was that the sd card sync should be the default because it doesn't have to be configured but if someone has an argument against it I'll gladly change this. > Then I replaced the signpost jar files with the latest > 1.1 jar files I could find, since supposedly they contain OAuth 1.0a > support. I'm not really satisfied with the solution of having a jar file versioned in bzr. If someone knows if there is an equivalent to svn exports or if it would be okay to put a whole svn checkout under bzr, I'd really like to know. > The last thing I did was to change the oauth consumer pair > constants from "tomdroid"/"tomdroid" to "anyone"/"anyone". > > With these changes I was able to get pretty far in the authentication > process, but not far enough. Then you got further than I did when I tried, I kept hitting internal server errors during the first part of the authentication. I gave up quickly for I didn't have any mean of knowing what really happened on U1. > When the callback URL (tomdroid://sync) > was called by the browser, it seemed like a new Tomdroid instance came > up (or at least, the welcome message was shown again), and then > nothing happened. At this point I'm kind of out of time to keep > digging in today, but really I'm just not sure what the expected > behavior is when running Tomdroid from the web sync branch, in the > emulator, starting with an empty SD card. The menu should contain a sync item as soon as the authentication process is finished, but we really should inform the user about the progress. I tested U1 with the patch you provided below (which should be the only changes required to support oauth 1.0a). You're absolutely correct in your assumption that Tomdroid is handling the tomdroid:// url, that's why another instance seems to be started (we should only show the popup on the first run). I get the following exception when trying to do the last part of the auth process: OAuthExpectationFailedException: Request token or token secret not set in server reply. The service provider you use is probably buggy. I'm sorry I don't have any tips to share as we're roughly at the same point and I unfortunately won't have time to dig deeper into this until this weekend. Thanks for your time! Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Web sync branch hurdles
On Mon, Nov 9, 2009 at 11:01 PM, Sandy Armstrong wrote: > On Mon, Nov 9, 2009 at 1:36 PM, Benoit Garret > wrote: >> The menu should contain a sync item as soon as the authentication >> process is finished, but we really should inform the user about the >> progress. > > Yeah, I would suggest that the welcome message not be shown...instead, > a screen (don't know the right android UI terminology here) stating > that auth was successful and sync is in progress (along with a > progress indicator) would really be best. When the sync is done, it > should go straight to your notes. I agree, the lack of information about what's going on is something I'm not pleased with in the current code. > copying Signpost source directly in to Tomdroid bzr would > allow debugging deeper into Signpost, right? Absolutely. I can't remember why I put the jar instead of the full source (something about the maven build system but I'm not even sure the reasoning was valid) but the latter should be the way to go. ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Web sync branch hurdles
Hey, On Mon, Nov 9, 2009 at 11:01 PM, Sandy Armstrong wrote: > On Mon, Nov 9, 2009 at 1:36 PM, Benoit Garret > wrote: >> I tested U1 with the patch you provided below (which should be the >> only changes required to support oauth 1.0a). You're absolutely >> correct in your assumption that Tomdroid is handling the tomdroid:// >> url, that's why another instance seems to be started (we should only >> show the popup on the first run). I get the following exception when >> trying to do the last part of the auth process: >> >> OAuthExpectationFailedException: Request token or token secret not set >> in server reply. The service provider you use is probably buggy. > > That is the same exception I got, and tried ignoring, with > unsatisfactory results. :-) I'd really like to see the response sent > by U1 here...copying Signpost source directly in to Tomdroid bzr would > allow debugging deeper into Signpost, right? I made a few commits today: * the expectation failed exception is a known problem in signpost: http://code.google.com/p/oauth-signpost/issues/detail?id=20#c8. I committed a hack which should fix the issue while we wait for a proper fix from upstream. * the notes api url was hardcoded, I'm now GETting the proper resource from the server. Syncing with U1 now works (for me) but more feedback is welcome ;-) . ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Web sync branch hurdles
On Sun, Nov 15, 2009 at 5:08 PM, Sandy Armstrong wrote: > Awesome! I just pulled your changes and they are working fine on > Android 1.6. Some things I noticed: > > * I have to manually change the 1.0a pref to true. But I'm pretty > sure that there's no harm in treating Snowy or other OAuth 1.0 servers > identically to an OAuth 1.0a server, as long as you don't freak out > when oauth_verifier isn't returned (does signpost freak out in that > situation?). It would suck to have users have to pick OAuth > versions...maybe we should just bite the bullet and add 1.0a support > to django-piston for snowy so that Tomdroid can safely assume 1.0a > (this is assuming signpost really can't handle 1.0a mode on a 1.0 > server). Strange, the signpost documentation states that it is possible to know which protocol version is used by the server after the request token handshake. The pref should be automagically populated after the said handshake, I'm not sure what goes wrong here as it works fine for me. > * Should probably rename "Snowy" in the UI to "Tomboy Web" (that's the > string we use in Tomboy, and in general it's how we refer to > "something that implements the Tomboy Web REST API"). After all, > U1/Midgard/etc != Snowy. Agreed. > * Syncing notes was super slow and I had no idea it was working. I > assumed it had failed because I was still able to press the "Sync" > button. This can be broken down into a few problems: > 1. No indication that sync is in progress > 2. Long delay before I even see first note sync'd in the log > 3. Each note takes almost a second to sync > 4. Can still press Sync button (no idea if this means multiple sync > operations are running) > These are all totally fixable, though. Yes, yes, yes and yes. The fastest way to fix these would be to have some sort of modal progress dialog. While this may not be the best solution (usability-wise), it is the easiest to implement and is far better than the current interface. > * The Tomdroid UI seems slow in general, but I haven't deployed it to > my G1 yet so I can't really quantify that. Also, for all I know there > is another sync job going on in the background from pressing the > button too many times. :-P > > Anyway, great progress...it was really exciting to see my notes. What > issues are blocking a new release with these features? A lack of time from Olivier and myself? Though it's true we could cut some corners as the audience for such a release is mostly technical, Tomdroid won't be on the Market tomorrow... Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] tomdroid's storage-redesign && what do we want to keep in the database as a note?
On Tue, Nov 17, 2009 at 6:17 AM, Olivier Bilodeau
wrote:
> I _really_ find it disgusting, it looks like:
>
> String tag = "<";
>
> if (uri != null) {
> if (uri.equals(NS_LINK)) {
> tag += PREFIX_LINK+":";
> } else if (uri.equals(NS_SIZE)) {
> tag += PREFIX_SIZE+":";
> }
> }
>
> tag += localName+">";
> xmlContent.append(tag);
So do I, even though I wrote this (and I'm quite ashamed to admit it).
I'm pretty confident this will break as soon as it encounters
something not formatted like the Tomboy notes I have on my computer.
I'm saying this because I'm far from understanding the intricacies of
xml.
> 1- store the whole note instead of just note-content in the database
> This way we won't lose addins metatags, full note encryption support will be
> possible, etc. Also, parsing the few lines of metadata on each load won't be
> that big of a penalty since its the note's content that is always the
> biggest.
I'd be in favor of this solution, provided we do not find any blocker.
Xml is a complex beast and I'd sleep better at night knowing someone
knowledgeable about the format handles the decoding for us.
> 2- Forget about xml parsing just regexp out the note-content portion then
> parse the rest of the note. Or just use an xml lib that allows to extract
> part of the raw xml structure (or find the way to do it in Sax).
I initially tried to extract the raw content between the note-content
tags with SAX and couldn't find any way to do it. But this could be
handy if we manage to do it, we get the best of both worlds: a tested
library to decode xml and parsing only what we need to show the note
content.
If I remember correctly, the regexp solution is the one used by Tomboy
in the web sync addin.
Cheers,
Benoit
___
Mailing list: https://launchpad.net/~tomdroid-dev
Post to : tomdroid-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~tomdroid-dev
More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] FOSDEM
I was just thinking it would be cool to attend, but I then realized I will be in Chile for the first two weeks of February, not exactly the nearest place from Brussels :-/ Benoît Garret On Tue, Nov 17, 2009 at 5:12 PM, pjv wrote: > Hi, > > Have any of you considered attending the next FOSDEM conference > (http://www.fosdem.org)? Gnome has a large presence each year so I'm > sure Tomboy has been discussed there before. But for the Android side of > things, we at OpenIntents are seriously considering of applying for a > Lightning Talk. Just interested to know if there are other Android > projects that might want to get involved. > > Regards, > -- > pjv > > > ___ > Mailing list: https://launchpad.net/~tomdroid-dev > Post to : tomdroid-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~tomdroid-dev > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] tomdroid's storage-redesign && what do we want to keep in the database as a note?
On Tue, Nov 17, 2009 at 8:19 PM, Olivier Bilodeau wrote: >> >> > 1- store the whole note instead of just note-content in the database >> > This way we won't lose addins metatags, full note encryption support >> > will be >> > possible, etc. Also, parsing the few lines of metadata on each load >> > won't be >> > that big of a penalty since its the note's content that is always the >> > biggest. >> >> I'd be in favor of this solution, provided we do not find any blocker. >> Xml is a complex beast and I'd sleep better at night knowing someone >> knowledgeable about the format handles the decoding for us. > > > I was thinking about it this morning. I have a new question: what do you get > when you ask for a note using Tomboy's REST API? Do you ask for metadata and > note-content separately or is it all together? It's one request to get a JSON object containing the metadata in various fields and the note content as xml in another field, like the example at http://live.gnome.org/Tomboy/Synchronization/REST#line-78 The note-content field is exactly what's between the note-content tags in a xml note, this was why I decided to put it as-is in the database. ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Introducing myself
Hi everybody, On Fri, Mar 5, 2010 at 5:25 AM, Olivier Bilodeau wrote: > On Thu, Mar 4, 2010 at 6:01 AM, bacatta wrote: > >> >> I am interested in tomdroid and I want to help, especially the web-sync >> branch, because I think tomdroid is useless without it ! > > Nice to have you on board, the web-sync branch is a start but it is far from being finished. I could use your help. However, it would be good if you could wait until the end of this weekend before starting any work on top of the web-sync branch, for the reasons outlined below. If you are interested in working on the web-sync branch, I would suggest > that you branch of it and try to integrate it with the trunk series. Here's > the story: > > Benoit did the database redesign, then he went on and created the web-sync > on top of it (in a separate branch). I merged his database work for 0.3 but > made *a lot* of changes to it. This means that web-sync specific changes > would need to be re-based on top of 0.3.1. > This really makes me regret we aren't using git, I'm using it at work and rebase is more awesome than you can imagine. This is definitely not a call to switch to git, I found bazaar much more easy to grasp at the beginning. > It could be just a matter of doing a bzr merge with trunk, fixing the > conflicts and making sure nothing broke. > I really like how you make it sound simple ;-) . I tried that and it was a mess, mostly because I moved files in the web-sync branch and bazaar refused to cope with the additional changes you stacked on these. I ended up with starting from the main branch, copying the files of the web-sync one and selectively committing the results. This was much easier to do, but I'm afraid that every soul who got the code off my web-sync branch will have to download it again. This being said, I did not see any related branches on Launchpad so I assumed that nobody had worked on top of it. I didn't push it for now because I didn't really test the result of the merge and waited for Ubuntu One not to return an empty note content for every single note I uploaded :-/ . I'll get a Snowy instance working on my machine this weekend to test everything and will hopefully push the resulting code to Launchpad. Thanks for your interest! > As a side note, this project is attracting a lot of people from France, I > wonder why is that? Maybe my french-styled english? :) > Nay, it's because us French people are attracted by shiny things (why else would we call Paris the city of lights?) and Tomdroid IS shiny. As a related note, I wanted to submit a proposal to change the default background from black (which is boring) to a bright and shiny yellow, with the note titles in red. In case it would be rejected, I'm ready to play my trump card: put the French flag in the background. Tomdroid has a bright future, I tell you that! Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Introducing myself
Hi, Just to let everyone know, I have rebased the web-sync branch on top of the latest main. The branch url is the same as before (lp:~benoit.garret/tomdroid/web-sync). Cheers, Benoît ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
[Tomdroid-dev] Call for help
Hi everyone, A few people have expressed a desire to contribute to the web-sync part of Tomdroid. I'm currently the only one, as far as I know, who did any work on that part. To speed up the whole process, I'm listing the areas that can be improved with the hope that someone will be interested and help. I'm not saying that I will stop working on this, but it will be far more enjoyable and faster with some help. The current tasks are up for grabs: * Interface: the current code doesn't provide many cues about what's happening behind the scenes and may confuse the user. It could use some work in order to be able to tell the user about the state of the authentication/sync. It could be divided in two subtasks. The first one is the design of the interface with its flow. I don't think it is a good idea to rush blindly without a bit of prior planning, it requires some thought. The second one is some code refactoring to be able to extract useful information about the running sync process (http download progress, etc). * Background sync: Tomboy recently added the support for this, and I'm jealous. Background syncing in itself is not very difficult to implement but good integration with the global Android ecosystem requires some attention to detail (eg. detecting if the network is up or if the user has disabled the data synchronization settings). * The core synchronization code: the work I've done only works in the case of a one-way synchronization. Olivier is working on note editing, which will break the current synchronization code. I'd rather plan this ahead than have to remove the sync feature. The current Tomboy code can be used as an example, it shouldn't be difficult to implement but some changes to the database schema will be needed. These descriptions are very rough, I don't expect anyone to know exactly what needs to be done and instantly jump in. If any brave soul wants to help and stake their claim to fame, they're welcome to reply on or off-list where I can explain more precisely what needs to be done and give a few pointers to get them started. I can also help with the setup of a development environment if you've never done any Android development or never used Launchpad and bazaar. Hope to talk to you all soon ;-) Cheers, Benoît ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Call for help
I've just filed the corresponding bugs in Launchpad: * Auto background synchronization: https://bugs.launchpad.net/tomdroid/+bug/549646 * Two-way synchronization: https://bugs.launchpad.net/tomdroid/+bug/549647 * Interface: https://bugs.launchpad.net/tomdroid/+bug/549643 Cheers, Benoît On Wed, Mar 24, 2010 at 10:37 PM, Sandy Armstrong wrote: > On Wed, Mar 24, 2010 at 1:36 PM, Benoit Garret > wrote: >> Hi everyone, >> >> A few people have expressed a desire to contribute to the web-sync >> part of Tomdroid. I'm currently the only one, as far as I know, who >> did any work on that part. > > And many thanks for getting this work off the ground! :-) > >> To speed up the whole process, I'm listing the areas that can be >> improved with the hope that someone will be interested and help. I'm >> not saying that I will stop working on this, but it will be far more >> enjoyable and faster with some help. > > Great idea, I've tweeted a link to this mail to spread the word a bit. > >> * Background sync: Tomboy recently added the support for this, and >> I'm jealous. Background syncing in itself is not very difficult to >> implement but good integration with the global Android ecosystem >> requires some attention to detail (eg. detecting if the network is up >> or if the user has disabled the data synchronization settings). > > Somewhere in the Android Settings UI you can toggle per-provider > background sync preferences. I hope third-party apps can tie into > this, and also that in Tomdroid's preferences you could toggle > autosync on or off. My G1 has awful battery life so all of my apps > besides Gmail and Google Calendar are set for manual sync. > >> * The core synchronization code: the work I've done only works in the >> case of a one-way synchronization. Olivier is working on note editing, >> which will break the current synchronization code. I'd rather plan >> this ahead than have to remove the sync feature. The current Tomboy >> code can be used as an example, it shouldn't be difficult to implement >> but some changes to the database schema will be needed. > > The overall two-way sync algorithm is in this giant method: > > http://git.gnome.org/browse/tomboy/tree/Tomboy/Synchronization/SyncManager.cs#n362 > > The code that is specific to syncing with the Tomboy Web REST API is > in the WebSyncService add-in, and perhaps the best place to start > looking is here: > > http://git.gnome.org/browse/tomboy/tree/Tomboy/Addins/WebSyncService/WebSyncServer.cs > >> These descriptions are very rough, I don't expect anyone to know >> exactly what needs to be done and instantly jump in. If any brave soul >> wants to help and stake their claim to fame, they're welcome to reply >> on or off-list where I can explain more precisely what needs to be >> done and give a few pointers to get them started. I can also help with >> the setup of a development environment if you've never done any >> Android development or never used Launchpad and bazaar. > > Maybe you should make sure that Launchpad bugs are filed for each of > these issues, to make it easier for others to participate and track > the work. > > Sandy > > ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] A voice recorder
On Thu, Apr 8, 2010 at 3:18 PM, Edouard Richard wrote: > Hello, > I finally committed the voice note feature for Tomdroid! > https://code.launchpad.net/~vied12/tomdroid/voiceNote This looks awesome. One remark though, I haven't looked at the code nor used it but the UI in the fourth screenshot looks a bit weird because of the element spacing. Feel free to ask if you want a code review on a particular point. You should also ask explicitly for a merge when you feel your code is sufficiently polished to be reintegrated in the main branch, else we won't know if you're planning to do further work. Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] A voice recorder
On Sun, Apr 11, 2010 at 6:26 PM, Edouard Richard wrote: > Here is the new recorder's interface : > http://picasaweb.google.fr/lh/photo/K7uIyaQMMwQRJCuv8INI59sDpIRxcbNLkPLZlDQ9fCs?feat=directlink > Is it more suitable ? Yep, I feel that your new interface is both cleaner and clearer about the use of each element. Your work as a whole looks totally cool, I tested it a little bit and really liked the thought you put in the integration with the existing interface. Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Renaming SyncService
Hi Rodja, I originally named them that way by copying the sync architecture of Tomboy. Your arguments seem sensible, +1 for me. Benoît On Sun, Jun 13, 2010 at 10:52 AM, Rodja Trappe wrote: > Hi, > > I like to rename the SyncService class and all similar names to > SyncStrategy or SyncMethod. 'Service' is not very descriptive and > misleading. Also in Android a Service is a background process. In > Tomdroid we should have a SyncService inherited from android.app.Service > which would either use the SdCardSyncMethod or the SnowySyncMethod -- as > choosen in the prefs. We are using the strategy pattern, let's do the > naming accordingly. > > Any thoughts? > > Rodja > > ___ > Mailing list: https://launchpad.net/~tomdroid-dev > Post to : tomdroid-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~tomdroid-dev > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] [UNSURE]Re: Looking for a driver for the next few releases / months
On Tue, Oct 19, 2010 at 3:13 PM, Sandy Armstrong wrote: > On Tue, Oct 19, 2010 at 1:43 AM, Rodja Trappe wrote: >> >> As a driver, I would want to drastically change some things: >> >> * switching from Launchpad to GitHub > > Is this really necessary? Switching code/bug/wiki hosting is a giant > pain for maintainers, developers, and users. What if the next person > says "hey I prefer hg and bitbucket, let's move there"? Hey, I prefer hg and bitbucket, let's move there! Kidding aside, I strongly agree with Sandy's points. Moreover, as much as I love git (I use it daily at work and it's awesome once you get used to its quirks), its learning curve is steep as hell and I swore at it more than I would have liked to as a beginner. Tomdroid is an awesome app to get your teeth cut on, let's not deter beginners from contributing with a bad choice of tools. Something that's been on my mind for some time is the fact that we're not really welcoming to beginners. Maybe I'm using a straw-man here, but the problem I see is that they have to figure out everything by themselves. When you don't know anything about either bazaar, launchpad, android, java or even the way open source works, this can be quite an ordeal. In order to ease this pain, we could put up a "Tomdroid bootstrapping" guide, ie how to get the android sdk and eclipse installed, how to clone and publish changes with bazaar, etc. This information is already available somewhere on the net, but it would be much easier if this info was centralized on a page in the wiki, even if it's just a collection of links. >> * publishing Tomdroid on the Android Market (each release, and a >> separate dev-preview build for testing) >> * much more frequent releases (with very small change logs) >> * automatic code formatting These are very good points, my personal favorite is the last one. The code base is looking like Frankenstein atm, with tabs, spaces and inconsistent formatting everywhere. On the original question: I also don't have much time currently (no wonder the project hasn't advanced as much as we all would have liked to) and I would be dishonest if I pretended to be able to handle the maintainer's work. I can try a little harder to step up and handle part of the boring work but certainly not all of it. This being said, do we really have to have only one person doing most of the work? Can't we give the keys of the project to a team of two or three people? I'm speaking from inexperience here and there are many reasons this wouldn't work, I guess input from someone more experienced in open source than us would be very welcome (wink wink Sandy ;-) ). Have a nice evening, afternoon, morning or whatever, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] Tomdroid now on the Android Market!
> For some reason, I wasn't able to install from Market on my phone yet. No > sure if the issue is my phone or if it's a publish lag on Google's side.. If > some of you can try, the feedback would be appreciated. I had no problem installing it from the french market on an HTC Magic. I guess new apps take a little while to appear on the listings. Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
Re: [Tomdroid-dev] [UNSURE]Re: Tomdroid now on the Android Market!
On Thu, Oct 28, 2010 at 1:47 AM, mark strawser wrote: > I believe I saw something on this list mentioning that some > documentation needs written - is that right? I no longer have the > original message, so could someone reiterate? I am getting pummelled by > school work but if I can find some time I'd like to help. The only documentation task I can name from the top of my head is the beginners guide. It should walk through zero to a complete development environment with the following rough steps: * Getting and setting up the android sdk * (optional) Getting and setting up Eclipse along with the android plugin * Installing bazaar, cloning the repo and pushing changes to a personal development branch Olivier mentioned that the doc/user/README and doc/dev/README contain an attempt at this, and I believe they should be merged and put somewhere more visible on the web site. Launchpad doesn't seem to offer project pages, so the location of such a guide will have to be determined. I know the above isn't much of a help, but anything you can come up with will at least be integrated in the READMEs. Cheers, Benoit ___ Mailing list: https://launchpad.net/~tomdroid-dev Post to : tomdroid-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tomdroid-dev More help : https://help.launchpad.net/ListHelp
