I hate to be nitpicky, but I have to mention JSON as an option for serializing data across http (http://www.crockford.com/JSON/), esp. since it's really easy for _javascript_ environments to use, which includes both mac dashboard and ajax.  xml-rpc and other things like mac plists define an xml language to make associative arrays, lists, strings, and numbers... so why not cut to the chase and just send those around?  and json parsers exist for every language.  Though json doesn't have a remote method calling standard the way xml-rpc does, though one could be made with a little bit of effort (ok, i was going to do such a little bit of effort for js and python, but never got around to it..)

brendan


On 1/11/06, Alec Flett <[EMAIL PROTECTED]> wrote:
Morgen Sagen wrote:
> For next week's sprint I thought I might work on a simple XML-RPC
> server parcel to make it easy for other clients to get data in/out of
> Chandler.  Then along with that parcel write an OSX dashboard widget
> which uses XML-RPC to display (and possibly edit) Chandler items.
>
Morgen - I'd like to experiment with an AJAX frontend to the repository
- basically write Attribute Editors in HTML and embed them in the
web-based repository viewer. I was thinking that I'd need XML-RPC access
to the repository so this would be perfect!

Alec

> ~morgen
>
> On Jan 11, 2006, at 4:04 PM, Katie Capps Parlante wrote:
>
>> We're going to be doing parcel writing sprints, both here at OSAF
>> next week, as well as at PyCon in Dallas in late February. We'd love
>> to have people join us at PyCon.
>>
>> What does it mean to do a "parcel writing sprint"? Two people pick a
>> small project, either to create a new extension parcel or extend an
>> existing one. They sit down and pair program for a few hours (or
>> days) to work on the project. Alternatively, a developer could work
>> on a solo project. By having several of these small projects going at
>> the same time, we have a group of people focusing on similar
>> problems, raising issues and learning from each other.
>>
>> Even if you can't join the sprinting at PyCon, now would be a great
>> time to take 0.6 out for a spin and try writing some extension
>> parcels. It would be great to get feedback, both on what we've done
>> so far (including documentation), as well as what would be helpful
>> next steps to make Chandler more capable in supporting extensions.
>>
>> If you are looking for inspiration, check out the list of parcels
>> Morgen put together (parcels that Morgen and others have started):
>> http://wiki.osafoundation.org/bin/view/Projects/ChandlerParcels
>>
>> Also, a quick brainstorm the other day about parcels people would
>> like to write or see written yielded this list:
>>    - query and get events from eventful/evdb
>>    - calendar data sync with Apple iSync
>>    - jabber client
>>    - bugzilla interface
>>    - exchange sync (talk directly to outlook exchange)
>>    - backup and restore tool (back up data on collection by
>> collection basis)
>>    - ups/fedex package tracker (a "parcel" parcel!)
>>    - structural tension charting
>>    - address book
>>    - im presence manager
>>    - irc client
>>    - parcel manager (keep track of what extension parcels are installed)
>>
>> We may not yet have good infrastructure to support each of these, but
>> it might be fun and productive to push and see where we fall down.
>>
>> Cheers,
>> Katie
>>
>>
>>
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/dev
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to