from:"Michael Pilgermann"

This got fixed.
Will be in the next release.

Vadim, Efimov wrote:
 On Thu, 03 Sep 2009 07:43:50 +0400, Nicola Mfb nicola@gmail.com  
 wrote:
 
 Hi!
 I just tried to transfer the addressbook from my Nokia N70 to opimd.
 As PISI does not support obex/syncml via bt I used msynctool to sync
 with Evolution.
 Finally I transfered the evolution vcf exported file on the freerunner
 and used PISI to sync it with opimd.
 The result was that only sim contacts have the phone field. I tested
 that with opimd gui, cli utils and litephone.
 However it's not an opimd problem as using PISI to sync the same vcf
 with google contacts results in the same problem.

 PISI is 0.4.5, shr is unstable lite 08/08 updated and upgraded before
 trying pisi.

 Here some lines from the vcf file:

 BEGIN:VCARD
 VERSION:3.0
 UID:pas-id-4A9F1EF50120
 X-EVOLUTION-FILE-AS:\, 
 FN: 
 N:;;;;
 REV:20090627T221844Z
 TEL;TYPE=CELL:XX
 END:VCARD

 Regards

 Nicola

 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community
 
 Recently i tried to migrate my contacts too (via KDE Adressbook) and
 found that PISI export only FAX fields. I created few contacts in FR
 directly, and export it to vcf. PISI prefixed all numbers with
 VOICE flag:
 
 BEGIN:VCARD
 VERSION:3.0
 FN:Vadim
 N:Efimov;Vadim;;;
 TEL;TYPE=CELL,VOICE:+71234567890
 END:VCARD
 
 so, i add VOICE prefix to all fields and try again, it imported ok,
 except field what don't have TYPE flag (other number in my SE 810i)
 TYPE=VOICE also don't help...
 
 ___
 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: Contacts from Nokia N70 to opimd with PISI: no phone field

I think, I will release a bug fix version today; however, PISI is still
not in the repos as I am heavily struggeling to set up a build
environment here (for creating and testing bb file).

So, I will have to release on opkg.org again.
I hope, I get this build thing fixed soon (currently struggeling with
some freetype Makefile issue :( )

Michael

Nicola Mfb wrote:
 On Fri, Sep 11, 2009 at 11:55 AM, Michael Pilgermann kichka...@gmx.de wrote:
 This got fixed.
 Will be in the next release.
 
 Thanks! is it scheduled soon or should we try to build a dev version?
 
 ___
 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: Contacts from Nokia N70 to opimd with PISI: no phone field

Fixed. In configuration file user can choose whether to auto-prefix
tel: ...
Will be in upcoming release.


Michael Pilgermann wrote:
 Hi,
 
 although, this is not the standard way of storing phone numbers; I filed a 
 bug to address this issue (as I do not want to start this discussion again).
 
 There will be another option in the config file for opimd PIM sources with 
 the next release, which shall indicate whether to prefix phone numbers 
 automatically in opimd when syncing.
 
 Michael
 
  Original-Nachricht 
 Datum: Mon, 7 Sep 2009 16:15:45 +0200
 Von: Sebastian Krzyszkowiak seba.d...@gmail.com
 An: List for Openmoko community discussion community@lists.openmoko.org
 Betreff: Re: Contacts from Nokia N70 to opimd with PISI: no phone field
 
 On 9/7/09, Vadim, Efimov eva...@evadim.ru wrote:
 On Sun, 06 Sep 2009 00:05:42 +0400, Sebastian Krzyszkowiak
 seba.d...@gmail.com wrote:

 In opimd.

 I can't query it via opimd-cli (console not properly localized), in
 opimd-contacts i see:

 Work phone
 Fax phone
 Cell phone
 Home phone

 After i click edit  save via GUI - small mobile phone
 icon appear:
 So it means PISI isn't adding tel: prefix to field values, which is wrong
 :P

 http://gallery.evadim.ru/d/435-1/opimd-contcts-screen.png

 Also, i can't search in opimd-contacts contacts with russian
 names, even by phone number, but this another story...
 opimd-contacts isn't supposed to be phone suite. Patches are welcome,
 but I won't work on such things by myself, sorry (unless they are
 opimd problems, not opimd-utils).

 -- 
 Sebastian Krzyszkowiak
 dos

 ___
 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.6 released

I just released another minor release (0.4.6) of PISI.

Mainly the bugs discussed here on the list were addressed.

New on top is the integration with SHR repository. The recipe was just
sent to the maintainers; hence, if you wait till tomorrow or so you
should be able to install / upgrade just by

opkg {upgrade|install} pisi

I like that :)

Syncml-Support is very much on the way. Just struggeling with some minor
problems - so 0.5 should be out very soon.

Michael


Michael Pilgermann 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: Contacts from Nokia N70 to opimd with PISI: no phone field

In fact, it even is default already.

However, it is not the standard way of storing phone number information
(if you look around at other backends) - so I decided to leave it up to
the user.

Michael

Sebastian Krzyszkowiak wrote:
 On 9/11/09, Michael Pilgermann kichka...@gmx.de wrote:
 Fixed. In configuration file user can choose whether to auto-prefix
 tel: ...
 
 And every user should choose that (it even should be by default), as
 not doing that with GSM backends is just plain wrong :P
 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Contacts from Nokia N70 to opimd with PISI: no phone field

I was not talking about OPIMD in particular but storing phone
information in general ...

I understand that you are opimd developer and that you have decided
about the implementation (in contrast to standard) ... I totally accept
that and that's why I applied this change to the application.

So long
Michael

Sebastian Krzyszkowiak wrote:
 On 9/11/09, Michael Pilgermann kichka...@gmx.de wrote:
 In fact, it even is default already.
 
 Nice :)
 
 However, it is not the standard way of storing phone number information
 (if you look around at other backends) - so I decided to leave it up to
 the user.
 
 Other backends? I'm opimd developer, and in opimd that's standard
 which apps should follow. You can do what you want in other databases
 and datasources, but in opimd you have to use that, as opimd is
 designed to bring apps support of the same data. When you won't follow
 standards, then you take risk for having stored incompatible data,
 unusable in some apps.
 
 BTW, someone somewhere on ml pointed to some RFC document about URIs,
 and tel: was the correct, standard one for phone numbers.
 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Contacts from Nokia N70 to opimd with PISI: no phone field

As you want to end the topic - just a very last comment on it:
I never asked for any changes on opimd storing - all I said was that it
is not using the widely used way of handling phone information (and same
time, I was implementing a way to still cope with it).

But I totally agree that we can use our time for more productive things
than discussing here ;) ... so have a nice weekend ...

PS: The RFC describes format of phone URIs rather than phone numbers.


Sebastian Krzyszkowiak wrote:
 On 9/11/09, Michael Pilgermann kichka...@gmx.de wrote:
 I was not talking about OPIMD in particular but storing phone
 information in general ...

 I understand that you are opimd developer and that you have decided
 about the implementation (in contrast to standard) ... I totally accept
 that and that's why I applied this change to the application.

 So long
 Michael
 
 I just can't understand how other datasources can influence on way of
 storing data in opimd. But i think we should end topic, as it's fixed
 now ;) And thanks again for your work at opimd support :)
 
 PS. http://www.rfc-archive.org/getrfc.php?rfc=3966
 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: PISI 0.4.6 released

Adam,

I am afraid; this issue has not yet been addressed. (but it is filed as
a bug - so I am going to address this in near future).

Michael


Adam Jimerson wrote:
 On Friday 11 September 2009 12:34:51 pm Michael Pilgermann wrote:
 I just released another minor release (0.4.6) of PISI.

 Mainly the bugs discussed here on the list were addressed.

 New on top is the integration with SHR repository. The recipe was just
 sent to the maintainers; hence, if you wait till tomorrow or so you
 should be able to install / upgrade just by

  opkg {upgrade|install} pisi

 I like that :)

 Syncml-Support is very much on the way. Just struggeling with some minor
 problems - so 0.5 should be out very soon.

 Michael

 
 Is the problem with syncing calendars with recurring events on Google 
 Calendar 
 addressed with this release? 
 --
 We must plan for freedom, and not only for security, if for no other reason 
 than only freedom can make security more secure.  Karl Popper
 
 
 
 
 ___
 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: Contacts from Nokia N70 to opimd with PISI: no phone field

2009-09-07 Thread Michael Pilgermann

Hi,

I think, this is not about opimd at all - it should rather be a problem with 
the VCF implementation in PISI.

I filed a bug already ... I hope, I will find the time to get this fixed till 
end of this week.

Michael

 Original-Nachricht 
 Datum: Mon, 07 Sep 2009 08:51:19 +0400
 Von: Vadim, Efimov eva...@evadim.ru
 An: List for Openmoko community discussion community@lists.openmoko.org
 Betreff: Re: Contacts from Nokia N70 to opimd with PISI: no phone field

 On Sun, 06 Sep 2009 00:05:42 +0400, Sebastian Krzyszkowiak  
 seba.d...@gmail.com wrote:
 
 
  In opimd.
 
 
 I can't query it via opimd-cli (console not properly localized), in
 opimd-contacts i see:
 
 Work phone
 Fax phone
 Cell phone
 Home phone
 
 After i click edit  save via GUI - small mobile phone
 icon appear:
 
 http://gallery.evadim.ru/d/435-1/opimd-contcts-screen.png
 
 Also, i can't search in opimd-contacts contacts with russian
 names, even by phone number, but this another story...
 
 ___
 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: Contacts from Nokia N70 to opimd with PISI: no phone field

2009-09-07 Thread Michael Pilgermann

Hi,

although, this is not the standard way of storing phone numbers; I filed a bug 
to address this issue (as I do not want to start this discussion again).

There will be another option in the config file for opimd PIM sources with the 
next release, which shall indicate whether to prefix phone numbers 
automatically in opimd when syncing.

Michael

 Original-Nachricht 
 Datum: Mon, 7 Sep 2009 16:15:45 +0200
 Von: Sebastian Krzyszkowiak seba.d...@gmail.com
 An: List for Openmoko community discussion community@lists.openmoko.org
 Betreff: Re: Contacts from Nokia N70 to opimd with PISI: no phone field

 On 9/7/09, Vadim, Efimov eva...@evadim.ru wrote:
  On Sun, 06 Sep 2009 00:05:42 +0400, Sebastian Krzyszkowiak
  seba.d...@gmail.com wrote:
 
 
  In opimd.
 
 
  I can't query it via opimd-cli (console not properly localized), in
  opimd-contacts i see:
 
  Work phone
  Fax phone
  Cell phone
  Home phone
 
  After i click edit  save via GUI - small mobile phone
  icon appear:
 
 So it means PISI isn't adding tel: prefix to field values, which is wrong
 :P
 
  http://gallery.evadim.ru/d/435-1/opimd-contcts-screen.png
 
  Also, i can't search in opimd-contacts contacts with russian
  names, even by phone number, but this another story...
 
 opimd-contacts isn't supposed to be phone suite. Patches are welcome,
 but I won't work on such things by myself, sorry (unless they are
 opimd problems, not opimd-utils).
 
 -- 
 Sebastian Krzyszkowiak
 dos
 
 ___
 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: Contacts from Nokia N70 to opimd with PISI: no phone field

2009-09-07 Thread Michael Pilgermann

In this context:
What is the set of prefixes you are using / supporting in opimd?? (any
link to documentation??)
thx in advance
Michael


Sebastian Krzyszkowiak wrote:
 On 9/7/09, Michael Pilgermann kichka...@gmx.de wrote:
 Hi,

 although, this is not the standard way of storing phone numbers; I filed a
 bug to address this issue (as I do not want to start this discussion again).

 There will be another option in the config file for opimd PIM sources with
 the next release, which shall indicate whether to prefix phone numbers
 automatically in opimd when syncing.

 Michael
 
 I seem to remember that discussion and someone pointed to tel: being
 valid and standard way of storing phone numbers (with some nice link
 proving that). Anyway, that's standard which opimd follows with many
 features (like normalizing phone numbers when comparing) and if PISI
 (or any other opimd client) isn't doing that, then it isn't really
 supporting opimd :x
 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Contacts from Nokia N70 to opimd with PISI: no phone field

2009-09-04 Thread Michael Pilgermann

Hi Nicola,

I am currently not at home - I guess it is a problem of selection of fields 
(for PISI) in opimd - actually we were discussing this before on this list here.

As soon as I have come back home (beginning of next week) I will check on this 
...

Greetings
Michael

 Original-Nachricht 
 Datum: Thu, 3 Sep 2009 05:43:50 +0200
 Von: Nicola Mfb nicola@gmail.com
 An: community@lists.openmoko.org
 Betreff: Contacts from Nokia N70 to opimd with PISI: no phone field

 Hi!
 I just tried to transfer the addressbook from my Nokia N70 to opimd.
 As PISI does not support obex/syncml via bt I used msynctool to sync
 with Evolution.
 Finally I transfered the evolution vcf exported file on the freerunner
 and used PISI to sync it with opimd.
 The result was that only sim contacts have the phone field. I tested
 that with opimd gui, cli utils and litephone.
 However it's not an opimd problem as using PISI to sync the same vcf
 with google contacts results in the same problem.
 
 PISI is 0.4.5, shr is unstable lite 08/08 updated and upgraded before
 trying pisi.
 
 Here some lines from the vcf file:
 
 BEGIN:VCARD
 VERSION:3.0
 UID:pas-id-4A9F1EF50120
 X-EVOLUTION-FILE-AS:\, 
 FN: 
 N:;;;;
 REV:20090627T221844Z
 TEL;TYPE=CELL:XX
 END:VCARD
 
 Regards
 
 Nicola
 
 ___
 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: Paroli : migrating SIM contacts

2009-08-26 Thread Michael Pilgermann

Hi Xavier,

may I ask you for the problems you had with PISI? Maybe we are able to solve 
this for future use  thx
Michael

 Original-Nachricht 
 Datum: Wed, 26 Aug 2009 09:55:21 +0200
 Von: Xavier Cremaschi omega.xav...@gmail.com
 An: community@lists.openmoko.org
 Betreff: Re: Paroli : migrating SIM contacts

 I have used a python script to load my VCF file into Paroli, now I have 
 my contacts even if SIM is still empty.
 
 PISI failed to load the VCF file into SIM, but I still want to do that 
 as soon as possible, because SIM is far more reliable than a file on FR.
 
 Xavier.
 
 
 ___
 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: First contact with the community

2009-08-24 Thread Michael Pilgermann

Hi adamou,

welcome! Hope, you will have loads of fun with the device and the community ... 
nice, seeing more people joining the community - especially (from my point of 
view) - when they do Python programming ...

First of all; I really agree with Risto - there is loads of work to do in core 
components of the OM distributions - and Paroli is probably a good example ...

However, if you rather want to start programming on application level, there 
are for sure some projects seeking for support - I can for instance suggest (I 
know, me being quite selfish here) contributing to a synchronization tool for 
the Openmoko called PISI (http://projects.openmoko.org/projects/pisi/).

Depending on your interest, there is tasks
- on GUI (PyGTK extensions or even migration (and re-design) to Elementary)
- on the core (e.g. extend by new domain tasks)
- on module level (integrate with more data sources)

If you are interested, feel free to contact me - ask about anything - get an 
account on gforge (http://projects.openmoko.org/) and request access to the 
project ...

Best regards
Michael


 Original-Nachricht 
 Datum: Sat, 22 Aug 2009 12:15:01 +0300
 Von: Risto H. Kurppa ri...@kurppa.fi
 An: List for Openmoko community discussion community@lists.openmoko.org
 Betreff: Re: First contact with the community

 Hi there!
 
 Nice to hear and see new people entering the community!
 
 And it's great that you'll get your unit soon - it just makes more
 sense to devel with the unit, not with qemu as you can use the
 touchscreen, you feel the speed, accelerometers, everything.
 
 But it all depends on what do you want to do and in what kind of
 projects to participate.
 
 First of all, there are many different distributions you can install
 on the phone. I myself use OM2009 unstable (see
 http://wiki.openmoko.org/wiki/Om2009 ), some other use SHR, some use
 Debian. Also Gentoo, Android, QTextended (or whatever it's called
 nowadays), Hackable1, openwrt are around and some more I forgot.
 
 Then there are many applications written primarly for Openmoko phones,
 like omgps (see http://code.google.com/p/omgps/ ).
 
 If you want to start contributing and you know python, I suggest you
 to have a look at Paroli, the phone application of OM2009. Paroli has
 now been written for maybe some 6 months and is quite usable, but
 still needs some love before it'll be launched as stable. If you're
 interested, have a look at
 http://wiki.openmoko.org/wiki/Om_2009_get_active#Paroli_phone_software
 - the work on Paroli will benefit many users and it's a smooth start
 for you, for example rewriting the wlan workflow (see
 http://www.paroli-project.org/trac/ticket/171 ) or include a bluetooth
 support.
 
 You're welcome to join #paroli irc-channel for more questions.
 
 Enjoy your freedom!
 
 
 r
 
 
 -- 
 | risto h. kurppa
 | risto at kurppa dot fi
 | http://risto.kurppa.fi
 
 ___
 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-08-23 Thread Michael Pilgermann

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

Re: [Shr-User] Request for assistence on assembling library packages

2009-08-23 Thread Michael Pilgermann

Hi Thomas,

Martin did quite some work on packaging PISI and its deps. (see attached
email) ...

I think, all the deps are in there now; haven't yet had the time to test
everything ...

From my point of view, there is still a need to create proper BB-File
for PISI - see discussion in second attached email.

If you have dealt with these things before - what is your opinion about it??

Greetings
Michael

Thomas Zimmermann wrote:
Am Sonntag 16 August 2009 22:17:43 schrieb Michael Pilgermann:
Dear all,

For an Openmoko PIM Synchronization tool (called PISI) I developed a
module to integrate with SyncML-servers this weekend. It is all running
fine on my Linux box (desktop) already.

I had some libs to install in order to get prepared. Now, for putting
the package together for the Openmoko I need to port them. However, I am
not very familar with this stuff (Python programmer) and have no
toolchain installed (I think, I heart that's the way to go for that kind
of stuff) ...

So my question is, whether somebody (who has maybe already a fully
functional toolchain installed) could assemble Openmoko packages (best
ipk I would say) for the following three modules:

- wbxml
(http://sourceforge.net/projects/libwbxml/files/libwbxml/0.10.7/libwbxml-0.
10.7.tar.gz/download) - libsoup (http://live.gnome.org/LibSoup)
- libsyncml
(http://sourceforge.net/projects/libsyncml/files/libsyncml/0.5.4/libsyncml-
0.5.4.tar.gz/download)

Uploading them to opkg.org would be grant - but if you just send them
over, I would do the rest, too ...

Please, please help - if I need to do it myself, it will probably take
me ages (and will look like the openldap module ;))

Michael

Did you find someone who would help you? If not i will do it.

Thomas
___
Shr-User mailing list
shr-u...@lists.shr-project.org
http://lists.shr-project.org/mailman/listinfo/shr-user

---BeginMessage---
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

Re: Paroli : migrating SIM contacts

2009-08-23 Thread Michael Pilgermann

Hi Xavier,

I don't think, you can configure this somewhere. I will have to apply
some minor changes to the code - could you please send me a sample VCF
file (some sanitized version of your file), which triggers the error
message.

I will try to fix this then soon ...
Michael

Xavier Cremaschi wrote:
 Michael Pilgermann a écrit :
 Hi Xavier,

 generally speaking, you could use PISI 
 (http://www.opkg.org/package_191.html) for this problem.

 Although, we developed and tested PISI on SHR. So, I do not know, whether it 
 is running on Om 2009 as well? (Any experiences from anybody??)

 If it is running:
 You could take a copy of your VCF file - synchronize this one with you 
 existing SIM card entries (access via dbus, should be in OM 2009 I think) 
 ... afterwards, you could edit the vcf file and sync again with the new SIM 
 card in the OM.

 The Paroli numbers are not yet visible to PISI; unless Paroli makes use of 
 OPIMD??? But that would be new to me ...

 Michael
 
 Hi,
 I am currently trying to sync my old SIM card with my VCF file, in order 
 to dump the VCF file into my new SIM card later.
 
 PISI can be installed and launched from my Om2009, but I have an 
 encoding problem :
 
 ** Error: Changes to source 2 (VCF) could not be applied due to the 
 following reason: 'ascii' codec can't encode character u'\xe9' in 
 position 36: ordinal not in range(128)
 
 Could you tell me how to run PISI in full UTF-8 ? I think this software 
 could be a good solution for my problem, but my VCF file is an UTF-8 one 
 (I am french)
 
 Best regards,
 Xavier.
 
 
 ___
 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: [ALL] New showroom for Openmoko apps

2009-08-21 Thread Michael Pilgermann

Dear all,

maybe, another perspective here from an apps developer's point of view:

I do believe, that we need a proper / nice directory of applications, which
users may browse through. I am aware of the following repositories right now:

- openmoko wiki - applications (I think, it is a good starting point if you
look for something; but could be somehow more fashined - and up to date)
- opkg.org - good for uploading (or linking) releases - though, I never used it
as a repository (somehow I didn't feel it's a proper rep)
- openmoko projects - from my view a good development plattform, which is doing
the job (it is just not too fancy - but, come on, we are developers)
- community updates
- new: SHR manual (also telling me some bits and pieces about software)
- *** did I forget something? probably I did ***

So, when doing a release right now - I have to update 4 pages already (openmoko
projects, opkg.org, community updates and SHR manual), because each of them
comes with its own installation instructions (the wiki is rather static).

What I want to point out first of all:

* We do not need another plattform ON TOP of all this *

We should rather go and integrate stuff. For me, openmoko projects server
(gforge) is a very good starting point for that:
* source code management (svn)
* file releases
* bug tracking, feature requests
* news support
* and WIKI functionality

I think, we should really keep this as a basis.

But I think, it is not a good plattform for people to browse projects. There is
a point of establishing something inviting* here. However, I would suggest the
following points:

* Make it a really simple, good-looking overview of applications to browse
through
* Keep Openmoko projects as development repository - do not duplicate stuff, we
have in there already (put links instead)
* Make it possible to easily install applications (simple instructions as given
in opkg.org - so we wouldn't need this plattform anymore)
* Do not maintain another list on openmoko wiki - instead put a link there to
this new directory
* Whenever you present information about a project (e.g. community newsletter
or user manuals) provide a link to the app inside this plattform instead of
detailling installation instructions (they might change from one version to the
next)
* Support community input (comments, maybe voting)
* Again: Make it beautiful and simple.

For the packaging issue - I really like the idea of boosting the process to
integrate into reps / distributions. (this would btw. ease the process of
installation).
However, documentation on how to do this is really rare. One could probably
find a way to create a bb file (and also further required files) - but the way
on

* how to get this into a rep. / distribtution? *

is really not transparent. Whom do I need to contact? Do I have to file an
issue somewhere? The Openmoko wiki is not really helpful about this topic.

Lasts words:
I wouldn't spend too much time when bringing up a SHOWROOM on tricky, technical
stuff. Just a plain, simple, beautiful web site (supporting categories and
distributions is nice I think) and - at least for now - manual installation
instructions.
I think, every OM user is able to run 'opkg install APPNAME'. It would be a
great step forward, if deps are resolved and so on ...

Very last words:
Please do not put anything up, when there is no time / resources to maintain
it. It would be a shame to waste so much efforts

Michael

Original-Nachricht
Datum: Thu, 20 Aug 2009 16:04:49 +0200
Von: Sebastian Krzyszkowiak seba.d...@gmail.com
An: List for Openmoko community discussion community@lists.openmoko.org
Betreff: Re: [ALL] New showroom for Openmoko apps

On 8/20/09, Risto H. Kurppa ri...@kurppa.fi wrote:
Hi there!

ABSTRACT
I think a new showroom for community created application is needed to
boost the development and help users to get to know new apps easily.
Now we have opkg.org to show distribute the apps created by the
community for Freerunner.

SETUP
opkg.org has allowed us to easily see what apps are new in the
community, the comment system has alowed us to get in touch with the
developer/packager and we've seen nice screeshots there to encourage
us to try apps. Also the release of opkg.org repository was great!

But:
opkg.org is has many outdated and broken packages with missing
dependencies
opkg.org doesn't separate packages for different distributions
opkg.org doesn't share the source codes as per GPL
opkg.org code can be changed only by the main developer
opkg.org developer doesn't seem to be working on it any more (since
April)
opkg.org developer is not an easy fish to catch

Now have a look at these:
http://www.apple.com/iphone/iphone-3gs/app-store.html
http://www.android.com/market/

https://store.ovi.com/?lid=storeherotxtcid=ovistore-fw-ilc-body-acq-na-ovicom-g0-na-2lang=fi-FI
http://getdeb.net/

Re: [ALL] New showroom for Openmoko apps

2009-08-21 Thread Michael Pilgermann


 Original-Nachricht 
 Datum: Fri, 21 Aug 2009 15:25:25 +0300
 Von: Risto H. Kurppa ri...@kurppa.fi
 An: List for Openmoko community discussion community@lists.openmoko.org
 Betreff: Re: [ALL] New showroom for Openmoko apps

 Opkg.org seems to be owned by the author so if the author is not
 co-operative (cannot be reached, doesn't answer e-mails or jabber)
 there's not much we or OM can do about it.
 
 Summa summarum:
 
 * Looks like there are people around who support the idea of showroom.
+
 * Showroom, not a repository
+
 * Read the data from packages in the repositories of the distributions
+
 * Allow filtering of packages based on existing desktop files and
 categories
+
 * Allow social features like comments  voting on the web site
+
 * Also create a client for FR to search  install apps
(+) low prio
 
 Did I miss something?
 
 Anyone with the skills around willing to work on this? I'd say the one
 who has the skills can decide the technology, be it git+django or
 svn+php or whatever, 
- ... we don't need source file management here I think; let's use stuff 
available on gforge instead. Let's concentrate on presentation and information 
(not the development) ... 

 as long as it's possible for more than one people
 to contribute.
 
 r
 
 
 On Fri, Aug 21, 2009 at 2:17 PM, David Reyes Samblas
 Martinezda...@tuxbrain.com wrote:
  2009/8/21 Risto H. Kurppa ri...@kurppa.fi:
  On Fri, Aug 21, 2009 at 1:12 PM, Sebastian
  Krzyszkowiakseba.d...@gmail.com wrote:
  On 8/21/09, David Reyes Samblas Martinez da...@tuxbrain.com wrote:
  Just an idea, why not use the bb file and source files as README,
  INSTALL, Changelog, and .desktop files if exist as source for this
  showroom?
 
  ++ from me! Some way for browse repository (doesn't matter if from WWW
  or from app on Neo, or even both at once) could be IMO the best
  showroom. It won't be outdated, app authors won't have to package
  their apps (as now they do, which is strange ;x).
 
  I agree, the point is to make it easy and appealing to find cool apps.
  But I wouldn't like to be able to see descriptions of all libraries
  but apps that one can use to do cool stuff.
  the existance or not of desktop file can be used as filter to not
  include libs/console apps if you don't want them, (maybe others are
  searching for a lib and can be useful to include them)
 
  If it can be automated this far, it'd be great! Both WWW and app for
  Openmoko would be nice to have. And somehow - this again should be
  distro-undependant so that it can be easily adapted to work on
  openwrt, shr, om2009 - maybe even on Debian and Gentoo?!
  I'm not familiar with the openwrt and Debian(There is a text file with
  descriptions of the repo, isn't) it the Package system but if they
  have a description field I don't know why it shoudn't be included, the
  work will be to match all those sources of infomation and find a good
  balance to show attractive/useful information ,
 
  A other idea regarding this is use a filter to show all, or just
  one/few distros, and when entering the app description show on what
  distribution  is included an in what version.
 
  Yes its no easy and maybe we must start easy with just one package
  system (read SHR ;) ) and then move one adding more distros and
  finding good ways to merge all this information to this showing room
  system.
 
 
  r
 
  --
  | risto h. kurppa
  | risto at kurppa dot fi
  | http://risto.kurppa.fi
 
  ___
  Openmoko community mailing list
  community@lists.openmoko.org
  http://lists.openmoko.org/mailman/listinfo/community
 
 
 
 
  --
  David Reyes Samblas Martinez
  http://www.tuxbrain.com
  Open ultraportable  embedded solutions
  Openmoko, Openpandora,  Arduino
  Hey, watch out!!! There's a linux in your pocket!!!
 
  ___
  Openmoko community mailing list
  community@lists.openmoko.org
  http://lists.openmoko.org/mailman/listinfo/community
 
 
 
 
 
 -- 
 | risto h. kurppa
 | risto at kurppa dot fi
 | http://risto.kurppa.fi
 
 ___
 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

Packaging of Python Programs (was Re: PISI 0.4 released)

2009-08-19 Thread Michael Pilgermann

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.

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: Paroli : migrating SIM contacts

2009-08-19 Thread Michael Pilgermann

Hi Xavier,

generally speaking, you could use PISI (http://www.opkg.org/package_191.html) 
for this problem.

Although, we developed and tested PISI on SHR. So, I do not know, whether it is 
running on Om 2009 as well? (Any experiences from anybody??)

If it is running:
You could take a copy of your VCF file - synchronize this one with you existing 
SIM card entries (access via dbus, should be in OM 2009 I think) ... 
afterwards, you could edit the vcf file and sync again with the new SIM card in 
the OM.

The Paroli numbers are not yet visible to PISI; unless Paroli makes use of 
OPIMD??? But that would be new to me ...

Michael

 Original-Nachricht 
 Datum: Wed, 19 Aug 2009 10:15:15 +0200
 Von: Xavier Cremaschi omega.xav...@gmail.com
 An: community@lists.openmoko.org
 Betreff: Paroli : migrating SIM contacts

 Hi folks,
 
 I use Om2009/fso/paroli as my daily phone, and today I need to migrate 
 from my old SIM card to a new one.
 And of course I want to keep my contacts.
 
 What I have :
 - old SIM card with contacts (currently in my FR), but some are shorten 
 (like a too long filename in MsDOS) probably because the card is a 9 
 year old one
 - new SIM card with nothing but pre-registered provider numbers
 - a vcf file exported from an old Nokia 9210 in 2008/07 (FR release 
 date), full information (long names...) but of course contacts added 
 between 2008/08 and now are missing
 - 2 contacts added in Paroli... must be on FR flash memory because I can 
 see them even with the new SIM
 - geek abilities and a great FR community (you)
 
 What I want to do (ideally) : set up a centralized thing where I could 
 import contacts from these different sources, then sort a bit the mess, 
 then export everything in the new SIM.
 Do you have any idea ? Is there any SIM-to-vcf or paroli-to-vcf piece of 
 software ?
 
 If not possible : what could be the best way to transfer my old SIM card 
 contact into the new one ? I presume I can fill the holes/rename things 
 manually after the big part of the job is done.
 
 
 Best regards,
 Xavier Cremaschi.
 
 
 ___
 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-08-18 Thread Michael Pilgermann

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

2009-08-18 Thread Michael Pilgermann

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 ... :)

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

[no subject]

2009-08-17 Thread Michael Pilgermann

(cross post from SHR list)

Dear all,

For an Openmoko PIM Synchronization tool (called PISI) I developed a
module to integrate with SyncML-servers this weekend. It is all running
fine on my Linux box (desktop) already.

I had some libs to install in order to get prepared. Now, for putting
the package together for the Openmoko I need to port them. However, I am
not very familar with this stuff (Python programmer) and have no
toolchain installed (I think, I heart that's the way to go for that kind
of stuff) ...


So my question is, whether somebody (who has maybe already a fully
functional toolchain installed) could assemble Openmoko packages (best
ipk I would say) for the following three modules:

- wbxml
(http://sourceforge.net/projects/libwbxml/files/libwbxml/0.10.7/libwbxml-0.10.7.tar.gz/download)
- libsoup (http://live.gnome.org/LibSoup)
- libsyncml
(http://sourceforge.net/projects/libsyncml/files/libsyncml/0.5.4/libsyncml-0.5.4.tar.gz/download)


Uploading them to opkg.org would be grant - but if you just send them
over, I would do the rest, too ...

Please, please help - if I need to do it myself, it will probably take
me ages (and will look like the openldap module ;))

Michael


PS: There were comments already, that BB-files should be the way to go - 
however, about that I know even less ...

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: PISI 0.4 released

2009-08-14 Thread Michael Pilgermann

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

2009-08-14 Thread Michael Pilgermann

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

2009-08-14 Thread Michael Pilgermann

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

2009-08-13 Thread Michael Pilgermann

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

2009-08-13 Thread Michael Pilgermann

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

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 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: OPIMD: List of available attributes documented?

Well, for now I simly used the ones that were documented already and
added fields I use for PISI - the outcome:

Name
Middlename
Surname
Email
Phone / CellPhone
HomePhone
WorkPhone
HomeStreet
HomePostalCode
HomeCity
HomeCountry
HomeState
Organisation
BusinessPostalCode
BusinessStreet
BusinessCity
BusinessCountry
BusinessState
FaxPhone
Title
Departement

However, this is subject to change as soon as somehow a decision
regarding the fields has been achieved.

Enjoy your weekends
Michael


Michael Pilgermann wrote:
 I would vote for syncML structure, even opimd can hold a more flexible 
 structure. But syncML is used in a lot of phones and this way i can be
 easier 
 to integradte opimd in exisiting sync programms, perhaps on windows too.

 So syncML: +1

 Thomas

 which would mean, that we are looking into VCard - here table of contents for 
 the fields taken from the RFC2426 (VCard 3.0, 
 http://www.ietf.org/rfc/rfc2426.txt):
 
 3. VCARD PROFILE FEATURES8
 3.1 IDENTIFICATION TYPES ...8
  3.1.1 FN Type Definition ..8
  3.1.2 N Type Definition ...9
  3.1.3 NICKNAME Type Definition 9
  3.1.4 PHOTO Type Definition ..10
  3.1.5 BDAY Type Definition ...11
 3.2 DELIVERY ADDRESSING TYPES .11
  3.2.1 ADR Type Definition 11
  3.2.2 LABEL Type Definition ..13
 3.3 TELECOMMUNICATIONS ADDRESSING TYPES ...13
  3.3.1 TEL Type Definition 14
  3.3.2 EMAIL Type Definition ..15
  3.3.3 MAILER Type Definition .15
 3.4 GEOGRAPHICAL TYPES 16
  3.4.1 TZ Type Definition .16
  3.4.2 GEO Type Definition 16
 3.5 ORGANIZATIONAL TYPES ..17
  3.5.1 TITLE Type Definition ..17
  3.5.2 ROLE Type Definition ...18
  3.5.3 LOGO Type Definition ...18
  3.5.4 AGENT Type Definition ..19
  3.5.5 ORG Type Definition 20
 3.6 EXPLANATORY TYPES .20
  3.6.1 CATEGORIES Type Definition .20
  3.6.2 NOTE Type Definition ...21
  3.6.3 PRODID Type Definition .21
  3.6.4 REV Type Definition 22
  3.6.5 SORT-STRING Type Definition 22
 
 There would be another advantage - in field parsing (e.g. for addresses) 
 couuld be done by already available libraries for VCard processing.
 However, it would not solve the problem with the phone communication medium:
 
 The RFC says:
 
 3.3.1 TEL Type Definition
 
To: ietf-mime-direct...@imc.org
 
Subject: Registration of text/directory MIME type TEL
 
Type name: TEL
 
Type purpose: To specify the telephone number for telephony
communication with the object the vCard represents.
 
Type encoding: 8bit
 
Type value: A single phone-number value.
 
Type special notes: The value of this type is specified in a
canonical form in order to specify an unambiguous representation of
the globally unique telephone endpoint. This type is based on the
X.500 Telephone Number attribute.
 
The type can include the type parameter TYPE to specify intended
use for the telephone number. The TYPE parameter values can include:
home to indicate a telephone number associated with a residence,
msg to indicate the telephone number has voice messaging support,
work to indicate a telephone number associated with a place of
work, pref to indicate a preferred-use telephone number, voice to
indicate a voice telephone number, fax to indicate a facsimile
telephone number, cell to indicate a cellular telephone number,
video to indicate a video conferencing telephone number, pager to
indicate a paging device telephone number, bbs to indicate a
bulletin board system telephone number, modem to indicate a MODEM
connected telephone number, car to indicate a car-phone telephone
number, isdn to indicate an ISDN service telephone number, pcs to
indicate a personal communication services telephone number. The
default type is voice. These type parameter values can be specified
as a parameter list (i.e., TYPE=work;TYPE=voice) or as a value list
(i.e., TYPE=work,voice). The default can

Re: PISI 0.3 released

That was indeed a missing dependency (SSL) - you need to install
'python-misc' and all will be fine ...
Michael

BitKeeper wrote:
 Hi,
 
 I get this error on shr-u
 
 pisi googleCalendar pimlicodates
 Traceback (most recent call
 last):] Starting
 Configuration
   File /bin/pisi, line 156, in module
 pisicli.startCLI()
   File /opt/pisi/pisicli.py, line 215, in startCLI
 source = pisi.importModules(configfolder,  config,  modulesToLoad, 
 modulesNamesCombined, soft)
   File /opt/pisi/pisi.py, line 82, in importModules
 exec source.append(
 module+i.__str__()+.SynchronizationModule(modulesNamesCombined,
 config, modulesToLoad[i], modulesFolder+modulesToLoad[i]+'/', True, soft) )
   File string, line 1, in module
   File /opt/pisi/modules/calendar_google.py, line 51, in __init__
 self._login( user, password )
   File /opt/pisi/modules/calendar_google.py, line 239, in _login
 self.cal_client.ProgrammaticLogin()
   File /usr/lib/python2.6/site-packages/gdata/service.py, line 753, in
 ProgrammaticLogin
 headers={'Content-Type':'application/x-www-form-urlencoded'})
   File /usr/lib/python2.6/site-packages/atom/http.py, line 93, in request
 connection = self._prepare_connection(url, all_headers)
   File /usr/lib/python2.6/site-packages/atom/http.py, line 234, in
 _prepare_connection
 return HttpClient._prepare_connection(self, url, headers)
   File /usr/lib/python2.6/site-packages/atom/http.py, line 157, in
 _prepare_connection
 return httplib.HTTPSConnection(url.host)
 AttributeError: 'module' object has no attribute 'HTTPSConnection'
 
 
 Something to do with python ssl support?
 
 # python --version
 Python 2.6.2
 
 Thanks,
 Bannon
 
 2009/7/20 Petr Vanek van...@penguin.cz mailto:van...@penguin.cz
 
 could someone help me with setting this up? i've got a new conf file,
 with the necessary items in, so now pimlico dates appears in the
 calendar list
 
 my conf file contains this:
 [googleCalendar]
 description=My Google Calendar
 module=calendar_google
 user=robin.paul...@gmail.com mailto:robin.paul...@gmail.com
 password=my password
 calendarid=robin.paul...@gmail.com mailto:robin.paul...@gmail.com
 
 [pimlicodates]
 description= Pimlico Dates
 module=calendar_ics
 path=/home/root/.evolution/calendar/local/system/calendar.ics
 
 when i select the corresponding items in the pisi gui, and hit start,
 it reports 'Configuring (0%)', but does nothing
 
 i'm guessing i've stuffed up the config for gcalendar, but can't see
 where
 
 on shr-u, make sure you have pisi and dates installed. you have to run
 dates at least once for the storage file to exist.
 
 relevant section of my ./pisi/conf:
 
 [googleCalendar]
 description=My Google Calendar
 module=calendar_google
 user=petr...@gmail.com mailto:petr...@gmail.com
 password=**
 calendarid=petr...@gmail.com mailto:petr...@gmail.com
 
 [pimlicodates]
 description= Pimlico Dates
 module=calendar_ics
 path=/home/root/.evolution/calendar/local/system/calendar.ics
 
 
 This is it. Btw the calendar sync in pisi doesn't have conflict mode
 settings so if you reinstall your distro (like i did now) and your
 appointments are in google only, they will get erased...fortunately
 there is a backup in the .pisi dir :)
 
 good luck
 Petr
 
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org mailto: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.3 released

For the sync from Google to Pimlico:

Took me some time, but I installed all the stuff now and noticed the
following:

You have to restart dates AND the backend process before updates are
visible in the application:

killall e-calendar-factory

(for the backend process - will be automatically restarted with next
dates invocation) ..

Michael


Petr Vanek wrote:
 We just released PISI 0.3.

 Contacts synchronization was extended by SIM (via DBUS) support -
 making it available to SHR users. Python 2.6 is supported as well
 (including all dependency packages).

 Contacts Synchronization currently supports
 - SIM Card via DBUS (e.g. SHR)
 - QTopia SQLite (e.g. OM 2008.12)
 - LDAP (read only)
 - VCF files (local and webdav), and
 - Google Contacts

 Calendar synchronization supports
 - Google Calendar, and
 - ICalendar files (local and webdav)

 Get your copy here:
 http://www.opkg.org/package_191.html
 
 
 
 hey, great! thank you for all the work. sync is what is really needed
 and some people will need even more to upgrade to Paroli (when paroli
 support is added to pisi).
 
 
 I tried:
 
 - contact sync shr_sim-google: (seem to be quite slow due to the
   dbus-sim slow access?) but worked. seemed to complain about 100
   contacts/sim limit but i have to test it more. Also, seems to sync
   only one way to google.
 
 - calendar sync: Pimlico-Google: seems to sync nicely one way -
   pimlico to google but not the other way.
 
 
 Petr
 
 
 ___
 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: OPIMD: List of available attributes documented?

Hi,
thx for the feedback.
Keep it your way - I am going to change PISI ...

Michael


Sebastian Krzyszkowiak wrote:
 
 All of that field names are compatible with opimd client apps I
 already wrote, except two little things: I have E-mail, and Home
 phone, Work phone etc. (with space and with p instead of P).
 Are you fine with it or I should change it in opimd-utils?
 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: PISI 0.3 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

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

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