Author Topic: ajax, the easy way. (Read 4312 times)

xavier · November 13, 2008, 10:31:19 am

Hi,

While modifying the tags so they can be grouped by parents, I'm toying with the rest interface.

I have now a working Raw js function,

CiviREST (entity, function,params), that returns a json. Eg CiviREST ('contact','search', array(...) ) or CiviREST ('tagEntity', 'add',array(...))

That's nice and it works. I'm wondering if/when go a bit higher in the abstraction, and have a server.contact.search() server.tagEntity.add ()...

Basically, have a OO interface on the js that more or less matches the one on the server, at least for some basic functions (CRUD), or something like the api.

Anyway, the code is a bit of a mess, and I had to add things here and there. Any input greatly appreciated, and Lobo, do you think I can still provide you the hierarchical tags before the code freeze (it's using jquery, shall I include it or is it now always on) ?

X+

Donald Lobo · November 13, 2008, 11:09:35 am

hey xavier:

we are still tweaking the jquery interface. ideally we will avoid loading in all pages, but do it selectively on pages that use it. Still a work in progress

Do u wanna post your code, so we can kinda see what it is / does. messy code is fine to begin with (we specialize in it

submitting your code a week or so before code freeze will help make it into the release

lobo

xavier · November 13, 2008, 11:40:39 am

Hi,

Not that I don't like doing patch and adding them on the issue tracker, and then realising that I didn't give you the right version, but based on your experience, what's the best way of sharing code in progress like that ?

Do you use git or do you have a "experimental" branch you could give me write access to ?

X+

Donald Lobo · November 13, 2008, 11:59:31 am

we can give u access to a branch / trunk. But before that, can you file an issue and a detailed description of what you are doing/planning to do, so we can agree on the functionality and what the deliverables are

. If the descriptio is too long etc, you might be better off doing it on the wiki

thanx

lobo

Matt2000 · November 18, 2008, 12:41:06 pm

This topic is largely outside my expertise, but since I was asked to comment, this is all that comes to mind:

Is there a way to leverage code from Drupal's Services module?
http://drupal.org/handbook/modules/services
http://drupal.org/project/services

From what I've seen, Services looks like a great framework, and might provide a nice abstraction layer for remote API's of all kinds, including those not yet invented.

Or does the wheel really need to be re-invented to maintain cross-CMS support?

Or maybe it really is more efficient to add on top of what we already have, rather than trying to star over on a different foundation? I wouldn't know. Just my 2c.

acrosman · November 18, 2008, 02:15:34 pm

Matt, While I like the idea of using the work of others as a platform to stand on, that seems like it's asking for trouble to make it cross-CMS/stand-alone compatible. It might be the case that for future versions we can use ideas/code from that module to help make Civi's interface stronger.

That's my initial response anyway.
Aaron

xavier · December 10, 2008, 12:25:38 am

In svn trunk

http://civicrm.org/node/483

CiviCRM Community Forums (archive)

News:

Author Topic: ajax, the easy way. (Read 4312 times)

xavier

ajax, the easy way.

Donald Lobo

Re: ajax, the easy way.

xavier

Re: ajax, the easy way.

Donald Lobo

Re: ajax, the easy way.

Matt2000

Re: ajax, the easy way.

acrosman

Re: ajax, the easy way.

xavier

Re: ajax, the easy way.