Re: PISI 0.4 released
Sounds great! Welcome to the team ... :) You could start by requesting access to the code - I would create a branch for you, so you could play around. There is a basic class diagram in the docs, which should help with the basic understanding of the architecture ... Feel free to ask about anything ... also about Python if you want. Michael c_c wrote: Hi, I would be willing to help/code (my python is weak though) to get sync support for e-tasks through PISI. Perhaps sync to / from evolution can be looked at in the beginning. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Packaging of Python Programs (was Re: PISI 0.4 released)
Hi all, since I am getting a bit confused about this topic, I thought I start a small discussion on it. Background was our sync app PISI (written in Python), which we now tried to include in distributions (here SHR) using BB files. Martin was kind enough to prepare a first draft of the bb file (and all the other stuff required) in order to get a running package for PISI (thx again) ... Last night, I was then trying to take these avaialbe files and wanted to modify in order to suit our needs appropriately. I started with changing the files ... was looking around on setuptools documents, changed more files - and then came back to the following question: *** Should we really install a Python application as a site-package?? *** Setuptools (and whatever similar stuff is out there for Python packaging) is a very good tool to assemble and distribute Python site-packages (so to say Python libraries) - stuff, that extends Python by some additional functionality. A program, however, does not extend the functionaility of the language - it is just an application itself. So, my question is, whether we should distinguish between libraries and applications when talking about packaging Python programs. libraries would go into site-packages; applications into some corresponding folder (e.g. /opt/$PROGRAMNAME) ... That is just a suggestion - I am really not sure, which is the way to go. How are other Python applications handling this issue? For me it looks somehow artificial to put an application under site-packages for Python. Comments are very welcome ... :D Michael Original-Nachricht Datum: Tue, 18 Aug 2009 12:54:28 +0200 Von: Martin Jansa martin.ja...@gmail.com An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released Hi, on Friday I uploaded patch for OE repository to shr trac: http://trac.shr-project.org/trac/ticket/592 http://trac.shr-project.org/trac/ticket/592Patch contains support for setuptools (http://pypi.python.org/pypi/setuptools), which seems like standard tool for managing python packages, that's files ez_setup.py, setup.py and setup.cfg. It would be nice if you include those 3 files in your source distribution package. I also found few files missing from http://projects.openmoko.org/frs/download.php/888/pisi-src-0.4.4.tar.gz, which were available in subversion repository, so I made only bbfile for live subversion version of pisi, I can found which files were missing if you can include them to pisi-src too. As last modification of your source distribution I created pisi python module and moved all pisi stuff and subdirs there, because this bbfile installs pisi directly in /usr/lib/python*/site-packages/pisi not to /opt/pisi and having lots of files and directories only for pisi directly in site-packages seemed wrong for me. So i rearranged source files like this: mkdir pisi mv pisi*.py pisi touch pisi/__init__.py mv contacts/ modules/ events/ tests/ thirdparty/ pisi As I said before, I'm not python programer so setuptools and python packages are new for me, so it would be nice if someone could confirm, that this structure is sane and you could rearrange files in subversion to simplyfi building process. I'll try to prepare bbfiles for new development version dependencies as you wrote in second thread. JaMa On Fri, Aug 14, 2009 at 7:35 PM, Michael Pilgermann kichka...@gmx.dewrote: JaMa, thx for this offer. I don't really know, what in detail you are talking about ... i was quite happy, that I managed to assemble ipkg - this is all done automatically using a Makefile: https://projects.openmoko.org/plugins/scmsvn/viewcvs.php/*checkout*/trunk/Makefile?rev=135root=pisi But integrating all this in feeds of repositories of course sounds good to me ... just let me know, what exactly I can do for you - I am sure we can sort that out (till now I have always just copied the files into my ipkgs) Michael Martin Jansa wrote: On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa martin.ja...@gmail.com mailto:martin.ja...@gmail.com wrote: I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. I had some spare time.. so before going for vacation, here is something which works for me, at least seems like working for me :). Maybe something could be integrated upstream so simplify bbfile for next version. Regards, JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community
Re: Packaging of Python Programs (was Re: PISI 0.4 released)
*** Should we really install a Python application as a site-package?? *** Setuptools (and whatever similar stuff is out there for Python packaging) is a very good tool to assemble and distribute Python site-packages (so to say Python libraries) - stuff, that extends Python by some additional functionality. A program, however, does not extend the functionaility of the language - it is just an application itself. I agree, installing applications in site-packages just feels *wrong*. That being said, A number of applications still do it. :( Im not sure, but perhaps setuptools, can be told to install to an alternative location? Adolph ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
2009/8/10 Michael Pilgermann kichka...@gmx.de: We just released PISI 0.4. i did a sync a moment ago, from sim to interactive vcf file. it popped up a dialogue ox asking for a file anme, but i couldn't read most of it, because too much of it was off screen. could you modify this, so i can figure out what's happening? cheers ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi, on Friday I uploaded patch for OE repository to shr trac: http://trac.shr-project.org/trac/ticket/592 http://trac.shr-project.org/trac/ticket/592Patch contains support for setuptools (http://pypi.python.org/pypi/setuptools), which seems like standard tool for managing python packages, that's files ez_setup.py, setup.py and setup.cfg. It would be nice if you include those 3 files in your source distribution package. I also found few files missing from http://projects.openmoko.org/frs/download.php/888/pisi-src-0.4.4.tar.gz, which were available in subversion repository, so I made only bbfile for live subversion version of pisi, I can found which files were missing if you can include them to pisi-src too. As last modification of your source distribution I created pisi python module and moved all pisi stuff and subdirs there, because this bbfile installs pisi directly in /usr/lib/python*/site-packages/pisi not to /opt/pisi and having lots of files and directories only for pisi directly in site-packages seemed wrong for me. So i rearranged source files like this: mkdir pisi mv pisi*.py pisi touch pisi/__init__.py mv contacts/ modules/ events/ tests/ thirdparty/ pisi As I said before, I'm not python programer so setuptools and python packages are new for me, so it would be nice if someone could confirm, that this structure is sane and you could rearrange files in subversion to simplyfi building process. I'll try to prepare bbfiles for new development version dependencies as you wrote in second thread. JaMa On Fri, Aug 14, 2009 at 7:35 PM, Michael Pilgermann kichka...@gmx.dewrote: JaMa, thx for this offer. I don't really know, what in detail you are talking about ... i was quite happy, that I managed to assemble ipkg - this is all done automatically using a Makefile: https://projects.openmoko.org/plugins/scmsvn/viewcvs.php/*checkout*/trunk/Makefile?rev=135root=pisi But integrating all this in feeds of repositories of course sounds good to me ... just let me know, what exactly I can do for you - I am sure we can sort that out (till now I have always just copied the files into my ipkgs) Michael Martin Jansa wrote: On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa martin.ja...@gmail.com mailto:martin.ja...@gmail.com wrote: I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. I had some spare time.. so before going for vacation, here is something which works for me, at least seems like working for me :). Maybe something could be integrated upstream so simplify bbfile for next version. Regards, JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Robin, thx for your feedback ... We used standard GTK Filedialog for this ... I am trying to think of any solution (with no need to touch GTK code ;)) ... To be honest - I can't bring up any good ... for the mean time, you could simply hard code the path of the vcf file in your config file (/home/root/.pisi/conf: instead of @interactive@) ... I don't even know, whether there are any efforts for fitting GTK on mobile devices - anybody else here with some input?? Michael Original-Nachricht Datum: Tue, 18 Aug 2009 22:25:52 +1200 Von: Robin Paulson robin.paul...@gmail.com An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released 2009/8/10 Michael Pilgermann kichka...@gmx.de: We just released PISI 0.4. i did a sync a moment ago, from sim to interactive vcf file. it popped up a dialogue ox asking for a file anme, but i couldn't read most of it, because too much of it was off screen. could you modify this, so i can figure out what's happening? cheers ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi JaMa, Great! Really great stuff - thank you so much for all this work. I had a quick look on the ticket and the patch - I can see, that you also included all the dependencies! Lovely! If I understand you correctly, all I need to do is taking the following files from the patch: - setup.py - pisi_svn.bb - ez_setup.py Apply my changes (to the first two entries) and put them into my svn repository. I will as well send them over to you. The missing files are actually by purpose - that's stuff one shouldn't need when playing around with the code (such as Makefile) ... but wouldn't mind to include everything if this is required or common practice. In the end, we shouldn't release from SVN as there might be a non-working version in the trunk. How would I proceed from there whenever I have a new release? Is there a patch / ticket required every time? I also noticed - from the dependencies there is openldap missing (maybe it was in SHR already?) thx and greetings (happy) Michael BTW: What is the OE-rep about? An SHR specific one? PS: We should think about putting all this information / stuff you are doing right now into a wiki - otherwise you might end up assembling bb-files for all new apps ... :) Original-Nachricht Datum: Tue, 18 Aug 2009 12:54:28 +0200 Von: Martin Jansa martin.ja...@gmail.com An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released Hi, on Friday I uploaded patch for OE repository to shr trac: http://trac.shr-project.org/trac/ticket/592 http://trac.shr-project.org/trac/ticket/592Patch contains support for setuptools (http://pypi.python.org/pypi/setuptools), which seems like standard tool for managing python packages, that's files ez_setup.py, setup.py and setup.cfg. It would be nice if you include those 3 files in your source distribution package. I also found few files missing from http://projects.openmoko.org/frs/download.php/888/pisi-src-0.4.4.tar.gz, which were available in subversion repository, so I made only bbfile for live subversion version of pisi, I can found which files were missing if you can include them to pisi-src too. As last modification of your source distribution I created pisi python module and moved all pisi stuff and subdirs there, because this bbfile installs pisi directly in /usr/lib/python*/site-packages/pisi not to /opt/pisi and having lots of files and directories only for pisi directly in site-packages seemed wrong for me. So i rearranged source files like this: mkdir pisi mv pisi*.py pisi touch pisi/__init__.py mv contacts/ modules/ events/ tests/ thirdparty/ pisi As I said before, I'm not python programer so setuptools and python packages are new for me, so it would be nice if someone could confirm, that this structure is sane and you could rearrange files in subversion to simplyfi building process. I'll try to prepare bbfiles for new development version dependencies as you wrote in second thread. JaMa On Fri, Aug 14, 2009 at 7:35 PM, Michael Pilgermann kichka...@gmx.dewrote: JaMa, thx for this offer. I don't really know, what in detail you are talking about ... i was quite happy, that I managed to assemble ipkg - this is all done automatically using a Makefile: https://projects.openmoko.org/plugins/scmsvn/viewcvs.php/*checkout*/trunk/Makefile?rev=135root=pisi But integrating all this in feeds of repositories of course sounds good to me ... just let me know, what exactly I can do for you - I am sure we can sort that out (till now I have always just copied the files into my ipkgs) Michael Martin Jansa wrote: On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa martin.ja...@gmail.com mailto:martin.ja...@gmail.com wrote: I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. I had some spare time.. so before going for vacation, here is something which works for me, at least seems like working for me :). Maybe something could be integrated upstream so simplify bbfile for next version. Regards, JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
2009/8/19 Michael Pilgermann kichka...@gmx.de: We used standard GTK Filedialog for this ... I am trying to think of any solution (with no need to touch GTK code ;)) ... To be honest - I can't bring up any good ... for the mean time, you could simply hard code the path of the vcf file in your config file (/home/root/.pisi/conf: instead of @interactive@) ... right, i can do that no problem. i wasn't actually sure what an interactive vcf file was...now i realise interactive refers to the method of using it, not the file itself. ah, the joys of the english language and it's many ambiguities I don't even know, whether there are any efforts for fitting GTK on mobile devices - anybody else here with some input?? i could only suggest re-writing it in e, but that's a huge amount of work that probably justifiably, you're not keen to do oh, excellent software by the way. cheers for the effort ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
JaMa, thx for this offer. I don't really know, what in detail you are talking about ... i was quite happy, that I managed to assemble ipkg - this is all done automatically using a Makefile: https://projects.openmoko.org/plugins/scmsvn/viewcvs.php/*checkout*/trunk/Makefile?rev=135root=pisi But integrating all this in feeds of repositories of course sounds good to me ... just let me know, what exactly I can do for you - I am sure we can sort that out (till now I have always just copied the files into my ipkgs) Michael Martin Jansa wrote: On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa martin.ja...@gmail.com mailto:martin.ja...@gmail.com wrote: I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. I had some spare time.. so before going for vacation, here is something which works for me, at least seems like working for me :). Maybe something could be integrated upstream so simplify bbfile for next version. Regards, JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi, I got around this problem with manual restart of SHR dates backend process after every sync. A pre- / post-routine option was added - so in your configuration file you can configure shell instructions now, which will be executed by PISI before / after sync (working well for me). Don't forget to modify your configuration file after upgrading to get it working: ## ## 1.3) ## Local ICS file (iCalendar) for dates software from pimlico (dates in some distros) ## [pimlicodates] description= Pimlico Dates module=calendar_ics path=/home/root/.evolution/calendar/local/system/calendar.ics postprocess=killall e-calendar-factory I noticed, that you can do quite some funny stuff using this option - e.g. I can sync my Desktop Calendar (Sunbird / Lightning) now using SSH commands: ## ## 1.5) ## Remote ICS file (on a SSH-Server (scp)) ## ## - make sure, you don't need a password for this account (e.g. key file without password) ## - I notied, you should create your key file on Openmoko - otherwise will bring an error: ## dropbearkey -t rsa -f ~/.ssh/id_rsa ## This example is an ICalendar on your desktop machine, which you have configured in ## Sunbird / Lightning as 'file:///home/username/test.ics' (on the desktop) ## [sshIcs] description=ICalendar on SSH Server module=calendar_ics path=/tmp/pisi-tmpcal.ics preprocess=scp -i /home/root/.ssh/id_rsa \ usern...@192.168.0.200:/home/username/test.ics /tmp/pisi-tmpcal.ics postprocess=scp /tmp/pisi-tmpcal.ics \ usern...@192.168.0.200:/home/username/test.ics rm \ /tmp/pisi-tmpcal.ics I have not yet uploaded a new version to opkg.org - find a priliminary version (I used for testing) attached to this email; a new version will follow end of this weekend ... Michael What do you think about this: Fow short term solution, I could add a flag in the configuration file, where the user can configure whether to restart the backend process automatically after sync. That wouldn't be too much efforts - and it would do the job (not nice, but it would do the job) ... Sounds like an acceptable work around to me. I guess that will be in PISI before the next week starts ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
I did change my mind and uploaded a new version (0.4.5) to opkg.org. Michael Michael Pilgermann wrote: Hi, I got around this problem with manual restart of SHR dates backend process after every sync. A pre- / post-routine option was added - so in your configuration file you can configure shell instructions now, which will be executed by PISI before / after sync (working well for me). Don't forget to modify your configuration file after upgrading to get it working: ## ## 1.3) ## Local ICS file (iCalendar) for dates software from pimlico (dates in some distros) ## [pimlicodates] description= Pimlico Dates module=calendar_ics path=/home/root/.evolution/calendar/local/system/calendar.ics postprocess=killall e-calendar-factory I noticed, that you can do quite some funny stuff using this option - e.g. I can sync my Desktop Calendar (Sunbird / Lightning) now using SSH commands: ## ## 1.5) ## Remote ICS file (on a SSH-Server (scp)) ## ## - make sure, you don't need a password for this account (e.g. key file without password) ## - I notied, you should create your key file on Openmoko - otherwise will bring an error: ## dropbearkey -t rsa -f ~/.ssh/id_rsa ## This example is an ICalendar on your desktop machine, which you have configured in ## Sunbird / Lightning as 'file:///home/username/test.ics' (on the desktop) ## [sshIcs] description=ICalendar on SSH Server module=calendar_ics path=/tmp/pisi-tmpcal.ics preprocess=scp -i /home/root/.ssh/id_rsa \ usern...@192.168.0.200:/home/username/test.ics /tmp/pisi-tmpcal.ics postprocess=scp /tmp/pisi-tmpcal.ics \ usern...@192.168.0.200:/home/username/test.ics rm \ /tmp/pisi-tmpcal.ics I have not yet uploaded a new version to opkg.org - find a priliminary version (I used for testing) attached to this email; a new version will follow end of this weekend ... Michael What do you think about this: Fow short term solution, I could add a flag in the configuration file, where the user can configure whether to restart the backend process automatically after sync. That wouldn't be too much efforts - and it would do the job (not nice, but it would do the job) ... Sounds like an acceptable work around to me. I guess that will be in PISI before the next week starts ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Edder, thx for your feedback regarding new features for PISI. I think, they are all really interesing suggestions ... please see my comments below. Original-Nachricht Datum: Wed, 12 Aug 2009 13:52:49 +0200 Von: Edder ed...@tkwsping.nl An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released Hi, I installed the latest version (0.4.4) and have a couple of questions: 1) Are there any plans to support google tasks? It is a widget within gmail and would be nice if that one could be synced to for example tasks or e-tasks. I have not yet planned to integrate tasks support in PISI - however, the modular approach would easily allow for that. For myself, this is not really a high priority thing - but, if more people are requesting that feature, I would be fine with supporting it (for the beginning, I filed a feature request on the projects page). 2) Long contact names. I have quite a few contacts with long names and at the moment syncing (with google contacts) causes problems, because it doesn't recognise that my phone contact Bla der BladiBla* == googlecontact Bla der BladiBladder. Ofcourse this shouldn't be a problem anymore when opimd is the default, so I'd understand if this is low priority. I know ... I am having the same problems. I thought about a fix of having some temporary mapping file somewhere in the file system, which can do the translation between full names and shortened names. But then I had in mind this opimd thing as well - which will overcome all these problems. It is again a think of proirities - pretty much depends on the timeline of opimd - as I count the time we have to wait for opimd dialer in days and weeks (rather than in months) I am not too motivated to spend too much time on that issue. 3) Are you planning to solve the problem with e-calendar-factory needing a restart? The existence of this background process suggests (to me) that proper updates to the calendar should go through that process. Do you know if that is true? And would that solve the restart issue? I have never looked deeply into this backend process - but sure, you are right about 'doing it the proper way'. The nice thing about the current solution is, that I could simply use our existing ICalendar support - by applying one additional configuration section we had DATES support. What do you think about this: Fow short term solution, I could add a flag in the configuration file, where the user can configure whether to restart the backend process automatically after sync. That wouldn't be too much efforts - and it would do the job (not nice, but it would do the job) ... One last thing - when talking about so many things, which are not of high priority for me - let me at least mention, what are the next steps in my eyes - I would really appreciate a discussion on that. * There is a couple of bugs I really have to address soon. * The next feature I am aiming for is SyncML supporrt - this is the 'standard' used in propriety mobiles - and (with some plugins) allows for synchronization with desktop applicatins (e.g. http://www.topologilinux.com/syncml/index.php?menu=1 or funambol) Michael Cheers, Edwin On Sun, Aug 9, 2009 at 6:58 PM, Michael Pilgermannkichka...@gmx.de wrote: We just released PISI 0.4. The major enhancement this time is opimd support for contacts. Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On Thu, Aug 13, 2009 at 09:39:20AM +0200, Michael Pilgermann wrote: Hi Edder, thx for your feedback regarding new features for PISI. I think, they are all really interesing suggestions ... please see my comments below. Hi Michael, thx for working on PISI. I would like to finish OE bbfiles for pisi and deps to help shr devs integrate it in feeds soon. Bbfiles for deps python-webdav, python-ldap, python-vobject, python-gdata were easy, as they're using distutils/setuptools already. Are you planing to use some build/install support too? I can finish pisi bbfile with list of installed files, but just inheriting distutils/setuptools would be easier and nicer :). I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. Regards, JaMa pgpCoAe7NcITV.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Michael, On Thu, Aug 13, 2009 at 9:39 AM, Michael Pilgermannkichka...@gmx.de wrote: Hi Edder, 1) Are there any plans to support google tasks? It is a widget within gmail and would be nice if that one could be synced to for example tasks or e-tasks. I have not yet planned to integrate tasks support in PISI - however, the modular approach would easily allow for that. For myself, this is not really a high priority thing - but, if more people are requesting that feature, I would be fine with supporting it (for the beginning, I filed a feature request on the projects page). I had a quick look into this (thinking I might implement it myself) and it seems that at the moment there is no google api for the tasks available yet, so I guess this feature would have to wait anyway But then I had in mind this opimd thing as well - which will overcome all these problems. It is again a think of proirities - pretty much depends on the timeline of opimd - as I count the time we have to wait for opimd dialer in days and weeks (rather than in months) I am not too motivated to spend too much time on that issue. Let's hope that you are right and that this support will happen in the coming weeks, but it seems to my impatient eye that support has been around the corner for some time already :) What do you think about this: Fow short term solution, I could add a flag in the configuration file, where the user can configure whether to restart the backend process automatically after sync. That wouldn't be too much efforts - and it would do the job (not nice, but it would do the job) ... Sounds like an acceptable work around to me. * There is a couple of bugs I really have to address soon. Always important! :) * The next feature I am aiming for is SyncML supporrt - this is the 'standard' used in propriety mobiles - and (with some plugins) allows for synchronization with desktop applicatins (e.g. http://www.topologilinux.com/syncml/index.php?menu=1 or funambol) This would be a great feature to have! Are you planning on using already existing libraries, or will you need to implement your own? Cheers, Edwin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Edwin, But then I had in mind this opimd thing as well - which will overcome all these problems. It is again a think of proirities - pretty much depends on the timeline of opimd - as I count the time we have to wait for opimd dialer in days and weeks (rather than in months) I am not too motivated to spend too much time on that issue. Let's hope that you are right and that this support will happen in the coming weeks, but it seems to my impatient eye that support has been around the corner for some time already :) Who is actually developing this thing? Maybe could be nice, to get some forcast here in order to make a decision. What do you think about this: Fow short term solution, I could add a flag in the configuration file, where the user can configure whether to restart the backend process automatically after sync. That wouldn't be too much efforts - and it would do the job (not nice, but it would do the job) ... Sounds like an acceptable work around to me. I guess that will be in PISI before the next week starts ;) * The next feature I am aiming for is SyncML supporrt - this is the 'standard' used in propriety mobiles - and (with some plugins) allows for synchronization with desktop applicatins (e.g. http://www.topologilinux.com/syncml/index.php?menu=1 or funambol) This would be a great feature to have! Are you planning on using already existing libraries, or will you need to implement your own? It has been really hard to find Python libs for SyncML. Lately, I was in touch with John Carr, a / the developer of Conduit (Gnome Sync written in Python), who recently integrated SyncML in a Conduit branch. He gave me some information about his implementation and I will have a look this weekend, how much I can apply this to PISI. Fingers crossed ... Michael Cheers, Edwin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi, I would be willing to help/code (my python is weak though) to get sync support for e-tasks through PISI. Perhaps sync to / from evolution can be looked at in the beginning. -- View this message in context: http://n2.nabble.com/PISI-0.1-released-tp2597801p3437532.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa martin.ja...@gmail.comwrote: I have no experience with python, but I can try to prepare setup.py for setuptools next week, if you have no time or interest in it and then send you patch. I had some spare time.. so before going for vacation, here is something which works for me, at least seems like working for me :). Maybe something could be integrated upstream so simplify bbfile for next version. Regards, JaMa 0020-New-bbfiles-for-PISI-and-dependencies.patch Description: Binary data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi, I installed the latest version (0.4.4) and have a couple of questions: 1) Are there any plans to support google tasks? It is a widget within gmail and would be nice if that one could be synced to for example tasks or e-tasks. 2) Long contact names. I have quite a few contacts with long names and at the moment syncing (with google contacts) causes problems, because it doesn't recognise that my phone contact Bla der BladiBla* == googlecontact Bla der BladiBladder. Ofcourse this shouldn't be a problem anymore when opimd is the default, so I'd understand if this is low priority. 3) Are you planning to solve the problem with e-calendar-factory needing a restart? The existence of this background process suggests (to me) that proper updates to the calendar should go through that process. Do you know if that is true? And would that solve the restart issue? Cheers, Edwin On Sun, Aug 9, 2009 at 6:58 PM, Michael Pilgermannkichka...@gmx.de wrote: We just released PISI 0.4. The major enhancement this time is opimd support for contacts. Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Problem was https. I changed to http - should be fine now. sorry for that. Michael Original-Nachricht Datum: Sun, 9 Aug 2009 17:29:17 -0700 Von: jeremy jozwik jerjoz.for...@gmail.com An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released On Sun, Aug 9, 2009 at 12:18 PM, Michael Pilgermannkichka...@gmx.de wrote: thx for your input. There was a small problem with hard-coding the sim entry max number at one point ... I fixed this and have put up PISI 0.4.3 now ... Please go and update (and let us know, whether it's fine now) ... Michael thanks for making this app! copied the commands of the opkg.org page: Collected errors: * Cannot find package https://projects.openmoko.org/frs/download.php/884/pisi_0.4.3_armv4t.ipk. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Original-Nachricht
Datum: Sun, 9 Aug 2009 22:43:44 +0200
Von: Michele Brocco ssj2mi...@gmail.com
An: List for Openmoko community discussion community@lists.openmoko.org
Betreff: Re: PISI 0.4 released
Hi and thanks for the very fast fix! :)
Maybe I should have taken a little bit more time (at least for testing ;) ) ...
Getting the same error here now ... I am going to fix this tonight ...
Michael
Now I get the following error in pisi cli with the same setup as
before (om_sqlite - opimd):
ERROR:dbus.connection:Unable to set arguments ({'Departement': None,
'HomeState': None, 'Surname': None, 'Name': u'Kundenbetreuun',
'BusinessState': None, 'Title': None, 'Middlename': None,
'Organisation': None, 'Work phone': None, 'BusinessStreet': None,
'HomeCity': None, 'E-mail': None, 'HomeStreet': None, 'BusinessCity':
None, 'HomeCountry': None, 'HomePostalCode': None, 'Fax phone': None,
'Cell phone': None, 'BusinessCountry': None, 'BusinessPostalCode':
None, 'Home phone': u'+4917955222'},) according to signature u'a{sv}':
type 'exceptions.TypeError': Don't know how which D-Bus type to use
to encode type NoneType
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 206, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 173, in
_saveOperationAdd
contacts.Add(fields)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in
__call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in
__call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
612, in call_blocking
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type
NoneType
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
silly mistake of mine in the module - forgot to check whether all
attributes are really set
Well 0.4.2 is out ... please go and update; should be fine then ...
For the menu-item thing - an updated version of the config file is
placed in /home/root/.pisi/conf-default (in order not to overwrite your
settings from last version) ... you can find a section in there and copy
it to your old conf file.
Michael
Michele Brocco wrote:
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
We just released PISI 0.4.
The major enhancement this time is opimd support for contacts.
Supported Contacts data sources:
- SIM via DBUS (e.g. SHR)
- QTopia address book (e.g. OM 2008.12)
- LDAP (read only)
- VCF files (local / webdav)
- Google contacts
- OPIMD
Supported Calendar data sources:
- Google calendars
- ICalendar files (local / webdav)
Get your copy here:
http://www.opkg.org/package_191.html
Thanks for the release first of all! I tried to sync sqlitedb with
opimd and get the following error:
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 200, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 145, in
_saveOperationAdd
fields['E-mail'] = contact.attributes['email']
KeyError: 'email'
Besides that in the GUI there is no OPIMD menuitem. Dont know if that
is correct.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi and thanks for the very fast fix! :) Maybe I should have taken a little bit more time (at least for testing ;) ) ... Getting the same error here now ... I am going to fix this tonight ... Michael release early, release often, we will help you to collect all the bugs, no worries :) Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
2009/8/10 Michael Pilgermann kichka...@gmx.de: Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html excellent, been waiting for some updates. i get this on installing from opkg.org: * Package python-vobject md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-gdata md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-ldap md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-dateutil md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-dateutil md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. this is on shr-unstable, all updates applied, as of 2009/08/10 cheers ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Robin, I remember that I have heart somebody reporting similar problems. I am not absolutely sure, but I think, he got around this by removing opkg.org from the repository list and installing PISI manually (using the link on opkg.org). Long-term I have to establish a proper numbering for all the dependency packages ... Michael Original-Nachricht Datum: Mon, 10 Aug 2009 21:44:28 +1200 Von: Robin Paulson robin.paul...@gmail.com An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: PISI 0.4 released 2009/8/10 Michael Pilgermann kichka...@gmx.de: Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html excellent, been waiting for some updates. i get this on installing from opkg.org: * Package python-vobject md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-gdata md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-ldap md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-dateutil md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. * Package python-dateutil md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'. this is on shr-unstable, all updates applied, as of 2009/08/10 cheers ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Michele,
this got fixed. Should be fine with version 0.4.4.
Greetings
Mike
Michele Brocco wrote:
Hi and thanks for the very fast fix! :)
Now I get the following error in pisi cli with the same setup as
before (om_sqlite - opimd):
ERROR:dbus.connection:Unable to set arguments ({'Departement': None,
'HomeState': None, 'Surname': None, 'Name': u'Kundenbetreuun',
'BusinessState': None, 'Title': None, 'Middlename': None,
'Organisation': None, 'Work phone': None, 'BusinessStreet': None,
'HomeCity': None, 'E-mail': None, 'HomeStreet': None, 'BusinessCity':
None, 'HomeCountry': None, 'HomePostalCode': None, 'Fax phone': None,
'Cell phone': None, 'BusinessCountry': None, 'BusinessPostalCode':
None, 'Home phone': u'+4917955222'},) according to signature u'a{sv}':
type 'exceptions.TypeError': Don't know how which D-Bus type to use
to encode type NoneType
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 206, in saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 173, in _saveOperationAdd
contacts.Add(fields)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in
__call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in
__call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
612, in call_blocking
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type NoneType
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
silly mistake of mine in the module - forgot to check whether all
attributes are really set
Well 0.4.2 is out ... please go and update; should be fine then ...
For the menu-item thing - an updated version of the config file is
placed in /home/root/.pisi/conf-default (in order not to overwrite your
settings from last version) ... you can find a section in there and copy
it to your old conf file.
Michael
Michele Brocco wrote:
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
We just released PISI 0.4.
The major enhancement this time is opimd support for contacts.
Supported Contacts data sources:
- SIM via DBUS (e.g. SHR)
- QTopia address book (e.g. OM 2008.12)
- LDAP (read only)
- VCF files (local / webdav)
- Google contacts
- OPIMD
Supported Calendar data sources:
- Google calendars
- ICalendar files (local / webdav)
Get your copy here:
http://www.opkg.org/package_191.html
Thanks for the release first of all! I tried to sync sqlitedb with
opimd and get the following error:
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 200, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 145, in
_saveOperationAdd
fields['E-mail'] = contact.attributes['email']
KeyError: 'email'
Besides that in the GUI there is no OPIMD menuitem. Dont know if that
is correct.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On Sun, Aug 9, 2009 at 11:21 PM, Michael Pilgermannkichka...@gmx.de wrote: Problem was https. I changed to http - should be fine now. sorry for that. Michael works great now, thanks! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Thanks Michael!
The sync seems to work fine now, no errors so far. Will test it in
more detail the next days.
On 8/10/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
this got fixed. Should be fine with version 0.4.4.
Greetings
Mike
Michele Brocco wrote:
Hi and thanks for the very fast fix! :)
Now I get the following error in pisi cli with the same setup as
before (om_sqlite - opimd):
ERROR:dbus.connection:Unable to set arguments ({'Departement': None,
'HomeState': None, 'Surname': None, 'Name': u'Kundenbetreuun',
'BusinessState': None, 'Title': None, 'Middlename': None,
'Organisation': None, 'Work phone': None, 'BusinessStreet': None,
'HomeCity': None, 'E-mail': None, 'HomeStreet': None, 'BusinessCity':
None, 'HomeCountry': None, 'HomePostalCode': None, 'Fax phone': None,
'Cell phone': None, 'BusinessCountry': None, 'BusinessPostalCode':
None, 'Home phone': u'+4917955222'},) according to signature u'a{sv}':
type 'exceptions.TypeError': Don't know how which D-Bus type to use
to encode type NoneType
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 206, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 173, in
_saveOperationAdd
contacts.Add(fields)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in
__call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in
__call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
612, in call_blocking
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type
NoneType
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
silly mistake of mine in the module - forgot to check whether all
attributes are really set
Well 0.4.2 is out ... please go and update; should be fine then ...
For the menu-item thing - an updated version of the config file is
placed in /home/root/.pisi/conf-default (in order not to overwrite your
settings from last version) ... you can find a section in there and copy
it to your old conf file.
Michael
Michele Brocco wrote:
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
We just released PISI 0.4.
The major enhancement this time is opimd support for contacts.
Supported Contacts data sources:
- SIM via DBUS (e.g. SHR)
- QTopia address book (e.g. OM 2008.12)
- LDAP (read only)
- VCF files (local / webdav)
- Google contacts
- OPIMD
Supported Calendar data sources:
- Google calendars
- ICalendar files (local / webdav)
Get your copy here:
http://www.opkg.org/package_191.html
Thanks for the release first of all! I tried to sync sqlitedb with
opimd and get the following error:
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 200, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 145, in
_saveOperationAdd
fields['E-mail'] = contact.attributes['email']
KeyError: 'email'
Besides that in the GUI there is no OPIMD menuitem. Dont know if that
is correct.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Thanks Michael!
The sync seems to work fine now, no errors so far. Will test it in
more detail the next days.
On 8/10/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
this got fixed. Should be fine with version 0.4.4.
Greetings
Mike
Michele Brocco wrote:
Hi and thanks for the very fast fix! :)
Now I get the following error in pisi cli with the same setup as
before (om_sqlite - opimd):
ERROR:dbus.connection:Unable to set arguments ({'Departement': None,
'HomeState': None, 'Surname': None, 'Name': u'Kundenbetreuun',
'BusinessState': None, 'Title': None, 'Middlename': None,
'Organisation': None, 'Work phone': None, 'BusinessStreet': None,
'HomeCity': None, 'E-mail': None, 'HomeStreet': None, 'BusinessCity':
None, 'HomeCountry': None, 'HomePostalCode': None, 'Fax phone': None,
'Cell phone': None, 'BusinessCountry': None, 'BusinessPostalCode':
None, 'Home phone': u'+4917955222'},) according to signature u'a{sv}':
type 'exceptions.TypeError': Don't know how which D-Bus type to use
to encode type NoneType
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 206, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 173, in
_saveOperationAdd
contacts.Add(fields)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in
__call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in
__call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
612, in call_blocking
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type
NoneType
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
silly mistake of mine in the module - forgot to check whether all
attributes are really set
Well 0.4.2 is out ... please go and update; should be fine then ...
For the menu-item thing - an updated version of the config file is
placed in /home/root/.pisi/conf-default (in order not to overwrite your
settings from last version) ... you can find a section in there and copy
it to your old conf file.
Michael
Michele Brocco wrote:
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
We just released PISI 0.4.
The major enhancement this time is opimd support for contacts.
Supported Contacts data sources:
- SIM via DBUS (e.g. SHR)
- QTopia address book (e.g. OM 2008.12)
- LDAP (read only)
- VCF files (local / webdav)
- Google contacts
- OPIMD
Supported Calendar data sources:
- Google calendars
- ICalendar files (local / webdav)
Get your copy here:
http://www.opkg.org/package_191.html
Thanks for the release first of all! I tried to sync sqlitedb with
opimd and get the following error:
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 200, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 145, in
_saveOperationAdd
fields['E-mail'] = contact.attributes['email']
KeyError: 'email'
Besides that in the GUI there is no OPIMD menuitem. Dont know if that
is correct.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
PISI 0.4 released
We just released PISI 0.4. The major enhancement this time is opimd support for contacts. Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote: We just released PISI 0.4. The major enhancement this time is opimd support for contacts. Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html Thanks for the release first of all! I tried to sync sqlitedb with opimd and get the following error: Traceback (most recent call last): File /bin/pisi, line 156, in module pisicli.startCLI() File /opt/pisi/pisicli.py, line 246, in startCLI pisi.applyChanges(source) File /opt/pisi/pisi.py, line 125, in applyChanges source[1].saveModifications() File /opt/pisi/modules/contacts_opimd.py, line 200, in saveModifications self._saveOperationAdd(id) File /opt/pisi/modules/contacts_opimd.py, line 145, in _saveOperationAdd fields['E-mail'] = contact.attributes['email'] KeyError: 'email' Besides that in the GUI there is no OPIMD menuitem. Dont know if that is correct. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote: Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Please keep in mind opimd by default already incorporates data from SIM (thanks to SIM-Contacts-FSO backend), so synchronizing beetwen SIM and opimd doesn't make sense :) -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
pisi0.4 new to pisi, so please bear with me. im getting the fallowing errors: DBUS_SIM: Loading SIM Card Limitations: 250 entries maximum; no more than 16 characters per name Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Traceback (most recent call last): File /bin/pisi, line 156, in module pisicli.startCLI() File /opt/pisi/pisicli.py, line 223, in startCLI source[0].load() File /opt/pisi/modules/contacts_dbussim.py, line 107, in load del self._availableIds[dbus_id] KeyError: dbus.Int32(247) though the contacts.vcf does contain contact information. not sure if it contains all the contacts but there is information in it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi Michele, silly mistake of mine in the module - forgot to check whether all attributes are really set Well 0.4.2 is out ... please go and update; should be fine then ... For the menu-item thing - an updated version of the config file is placed in /home/root/.pisi/conf-default (in order not to overwrite your settings from last version) ... you can find a section in there and copy it to your old conf file. Michael Michele Brocco wrote: On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote: We just released PISI 0.4. The major enhancement this time is opimd support for contacts. Supported Contacts data sources: - SIM via DBUS (e.g. SHR) - QTopia address book (e.g. OM 2008.12) - LDAP (read only) - VCF files (local / webdav) - Google contacts - OPIMD Supported Calendar data sources: - Google calendars - ICalendar files (local / webdav) Get your copy here: http://www.opkg.org/package_191.html Thanks for the release first of all! I tried to sync sqlitedb with opimd and get the following error: Traceback (most recent call last): File /bin/pisi, line 156, in module pisicli.startCLI() File /opt/pisi/pisicli.py, line 246, in startCLI pisi.applyChanges(source) File /opt/pisi/pisi.py, line 125, in applyChanges source[1].saveModifications() File /opt/pisi/modules/contacts_opimd.py, line 200, in saveModifications self._saveOperationAdd(id) File /opt/pisi/modules/contacts_opimd.py, line 145, in _saveOperationAdd fields['E-mail'] = contact.attributes['email'] KeyError: 'email' Besides that in the GUI there is no OPIMD menuitem. Dont know if that is correct. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Jeremy, thx for your input. There was a small problem with hard-coding the sim entry max number at one point ... I fixed this and have put up PISI 0.4.3 now ... Please go and update (and let us know, whether it's fine now) ... Michael jeremy jozwik wrote: pisi0.4 new to pisi, so please bear with me. im getting the fallowing errors: DBUS_SIM: Loading SIM Card Limitations: 250 entries maximum; no more than 16 characters per name Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Traceback (most recent call last): File /bin/pisi, line 156, in module pisicli.startCLI() File /opt/pisi/pisicli.py, line 223, in startCLI source[0].load() File /opt/pisi/modules/contacts_dbussim.py, line 107, in load del self._availableIds[dbus_id] KeyError: dbus.Int32(247) though the contacts.vcf does contain contact information. not sure if it contains all the contacts but there is information in it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
Hi and thanks for the very fast fix! :)
Now I get the following error in pisi cli with the same setup as
before (om_sqlite - opimd):
ERROR:dbus.connection:Unable to set arguments ({'Departement': None,
'HomeState': None, 'Surname': None, 'Name': u'Kundenbetreuun',
'BusinessState': None, 'Title': None, 'Middlename': None,
'Organisation': None, 'Work phone': None, 'BusinessStreet': None,
'HomeCity': None, 'E-mail': None, 'HomeStreet': None, 'BusinessCity':
None, 'HomeCountry': None, 'HomePostalCode': None, 'Fax phone': None,
'Cell phone': None, 'BusinessCountry': None, 'BusinessPostalCode':
None, 'Home phone': u'+4917955222'},) according to signature u'a{sv}':
type 'exceptions.TypeError': Don't know how which D-Bus type to use
to encode type NoneType
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 206, in saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 173, in _saveOperationAdd
contacts.Add(fields)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in __call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
612, in call_blocking
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type NoneType
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
Hi Michele,
silly mistake of mine in the module - forgot to check whether all
attributes are really set
Well 0.4.2 is out ... please go and update; should be fine then ...
For the menu-item thing - an updated version of the config file is
placed in /home/root/.pisi/conf-default (in order not to overwrite your
settings from last version) ... you can find a section in there and copy
it to your old conf file.
Michael
Michele Brocco wrote:
On 8/9/09, Michael Pilgermann kichka...@gmx.de wrote:
We just released PISI 0.4.
The major enhancement this time is opimd support for contacts.
Supported Contacts data sources:
- SIM via DBUS (e.g. SHR)
- QTopia address book (e.g. OM 2008.12)
- LDAP (read only)
- VCF files (local / webdav)
- Google contacts
- OPIMD
Supported Calendar data sources:
- Google calendars
- ICalendar files (local / webdav)
Get your copy here:
http://www.opkg.org/package_191.html
Thanks for the release first of all! I tried to sync sqlitedb with
opimd and get the following error:
Traceback (most recent call last):
File /bin/pisi, line 156, in module
pisicli.startCLI()
File /opt/pisi/pisicli.py, line 246, in startCLI
pisi.applyChanges(source)
File /opt/pisi/pisi.py, line 125, in applyChanges
source[1].saveModifications()
File /opt/pisi/modules/contacts_opimd.py, line 200, in
saveModifications
self._saveOperationAdd(id)
File /opt/pisi/modules/contacts_opimd.py, line 145, in
_saveOperationAdd
fields['E-mail'] = contact.attributes['email']
KeyError: 'email'
Besides that in the GUI there is no OPIMD menuitem. Dont know if that
is correct.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
We just released PISI 0.4. - OPIMD this is great, thank you! will try tomorrow :) Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: PISI 0.4 released
On Sun, Aug 9, 2009 at 12:18 PM, Michael Pilgermannkichka...@gmx.de wrote: thx for your input. There was a small problem with hard-coding the sim entry max number at one point ... I fixed this and have put up PISI 0.4.3 now ... Please go and update (and let us know, whether it's fine now) ... Michael thanks for making this app! copied the commands of the opkg.org page: Collected errors: * Cannot find package https://projects.openmoko.org/frs/download.php/884/pisi_0.4.3_armv4t.ipk. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
