* Alexis wrote:
>
> Hi all,
Hi!
> What would be useful would be an 'official', fleshed-out spec for
> org-contacts data, which handles a greater range of contact-related
> info. At the moment, for example, my org-contacts file makes use of the
> properties:
>
> #+PROPERTY: LANDLINE
> #+PROPERTY:
Michael Strey writes:
> Hi Daimrod,
>
> On 2014-05-29, Daimrod wrote:
>
>> Hmm, I kinda like this. It seems a bit verbose but it's better than
>> having multiple values per properties (IMHO).
>>
>> Though, if we adopt this scheme, we would need to add some helper
>> bindings/functions so that we
Hi Daimrod,
On 2014-05-29, Daimrod wrote:
> Hmm, I kinda like this. It seems a bit verbose but it's better than
> having multiple values per properties (IMHO).
>
> Though, if we adopt this scheme, we would need to add some helper
> bindings/functions so that we don't have to fill this by hands.
Michael Strey writes:
Hi Michael,
> Reading http://orgmode.org/worg/dev/org-syntax.html#Node_Properties
> I just realised that my clumsy property keys are against the rules since
> they are containing whitespace characters.
>
> Nevertheless I still like the idea of having a Type, a number and a
>
Reading http://orgmode.org/worg/dev/org-syntax.html#Node_Properties
I just realised that my clumsy property keys are against the rules since
they are containing whitespace characters.
Nevertheless I still like the idea of having a Type, a number and a
Value for every property that can occur multip
On 2014-05-23, Alexis wrote:
> What would be useful would be an 'official', fleshed-out spec for
> org-contacts data, which handles a greater range of contact-related
> info. At the moment, for example, my org-contacts file makes use of the
> properties:
>
> #+PROPERTY: LANDLINE
> #+PROPERTY: MOBI
Daimrod writes:
> Sure, but then how would we define the map? with a fixed set of rules?
> with a user customizable map (e.g. '(("MOBILE" -> "TELL;CELL")
> ("EMAIL_WORK" -> "EMAIL;TYPE=work")))?
More the latter. My initial (again, brainstorming!) thinking has an
user-modifiable data structure a
Alexis writes:
> Daimrod writes:
>
>> So, as you said, we would need to define and document a specification
>> for org-contacts. And we need to be clear from the beginning about
>> what it can do and what it can not do. For example, it is unlikely
>> that org-contacts will be a 1:1 mapping with
Daimrod writes:
> So, as you said, we would need to define and document a specification
> for org-contacts. And we need to be clear from the beginning about
> what it can do and what it can not do. For example, it is unlikely
> that org-contacts will be a 1:1 mapping with the vCard format in its
Alexis writes:
> Hi all,
Hi,
> [snip...]
>
> Fleshing out an extended spec for org-contacts data could be part of the
> process of making org-contacts a first-class citizen of org-mode, and
> provide a more solid foundation on which people can build (and share)
> the org-contacts functionality t
Rasmus writes:
> Check here:
>
> https://f-droid.org/repository/browse/?fdfilter=carddav&fdpage=1&page_id=0
>
> DAVdroid works very well.
Oh okay, i didn't realise DAVdroid was FOSS.
DAVdroid makes use of the ez-vcard library, which is BSD-licensed, and
certainly seems like it might be useful.
Alexis writes:
> There might already be
> a FOSS CardDAV library for Android out there that could be used for
> syncing, but i've not researched that yet.
Check here:
https://f-droid.org/repository/browse/?fdfilter=carddav&fdpage=1&page_id=0
DAVdroid works very well.
--
Sådan en god dansk la
Alexander Baier writes:
> For what it's worth, I would love to help out in any way I can. I use
> org-contacts myself and know elisp well enough to also do some
> implementing. But I wouldn't mind writing some documentation, either.
Thank you! At this point i'm studying RFC 6350 (vCard 4) and
Hi Alexander,
Alexander Baier writes:
> For what it's worth, I would love to help out in any way I can. I use
> org-contacts myself and know elisp well enough to also do some
> implementing. But I wouldn't mind writing some documentation, either.
> I, however, don't know much about Android pro
On 2014-05-24 12:15 Alexis wrote:
> Alexander Baier writes:
>
>> About the spec, might it make sense to use a standard already in
>> existence as a starting point or even a major inspiration? Something
>> like vCard for example?
>
> Yeah, i like the idea of building on top of vCard, given how wid
Bastien writes:
> Alexis writes:
>
>> *nod* Good point i'd be happy to assign copyright to the FSF,
>> myself, but i know that doing so is an issue for many people.
>
> Here you go!
>
> http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt
>
> :)
Heh, thank you! i'll de
Alexis writes:
> *nod* Good point i'd be happy to assign copyright to the FSF,
> myself, but i know that doing so is an issue for many people.
Here you go!
http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt
:)
--
Bastien
Xebar Saram writes:
> This sounds awesome, i would love syncing org contacts with my android
> phone
:-) It's good to know i'm not the only one wanting this functionality -
gives me more incentive to actually implement it!
Alexis.
Alexander Baier writes:
> About the spec, might it make sense to use a standard already in
> existence as a starting point or even a major inspiration? Something
> like vCard for example?
Yeah, i like the idea of building on top of vCard, given how widely it's
used and supported, and that it d
Bastien writes:
> Improving org-contacts.el and making it part of Org core are two
> separate issues -- not everything that is part of Org core gets a
> lot of attention, and some contributed packages do.
Oh okay, fair enough!
> I'd say: go ahead with whatever conventions you want to enforce
>
Rasmus writes:
> You could also put yourself a slightly different challenge: map
> between the org-contacts-format and an carddav server that you
> establish as a backend on your phone. E.g. google contacts is a
> carddav server, I think.
>
> I use DAVdroid for syncing my calendar and my contac
Hi Alexis
This sounds awesome, i would love syncing org contacts with my android phone
thx alot!
z
On Fri, May 23, 2014 at 1:30 PM, Alexander Baier <
alexander.ba...@mailbox.org> wrote:
> Hello Alexis,
>
> On 2014-05-23 06:07 Alexis wrote:
>
> [...]
>
> > What would be useful would be an 'off
Hello Alexis,
On 2014-05-23 06:07 Alexis wrote:
[...]
> What would be useful would be an 'official', fleshed-out spec for
> org-contacts data, which handles a greater range of contact-related
> info. At the moment, for example, my org-contacts file makes use of the
> properties:
>
> #+PROPERTY:
Bastien writes:
> PS: Actually, being part of Org core sometimes slow down things,
> because substantial contributions then need to come from people
> who assign their copyright to the Free Software Foundation.
PPS: This is a feature.
--
ツ
Hi Alexis,
Alexis writes:
> What do people think?
Improving org-contacts.el and making it part of Org core are two
separate issues -- not everything that is part of Org core gets a
lot of attention, and some contributed packages do.
I'd say: go ahead with whatever conventions you want to enfor
Alexis writes:
> What i'd now like to do is to add support for transferring data back and
> forth between my org-contacts file and the Contacts store on my
> phone. The challenge is the mapping between these two systems.
You could also put yourself a slightly different challenge: map
between the
Hi all,
i use org-contacts as my primary system for contact
management. Consequently, i'd love to be able to make use of my
org-contacts data on my Android phone.
To that end, i recently wrote some code for MobileOrg-Android which adds
basic PROPERTIES drawer support:
https://github.com/matburt
27 matches
Mail list logo
