Re: [limesurvey-developers] Like to help you improve the "RemoteControl 2 API"

[Vincent B. <v.b...@mi...>]

Hi Marcel,

Thanks for pointing to the documentation concerning process to add 
features.
Concerning the API I will get back to you (and all mailing list :) ) 
soon with some proposal.

Vincent

On 18/10/2013 09:37, Marcel Minke wrote:
> Hi Vincent,
>
> thanks for saying "Hello" to us. We are always looking for skilled 
> developers helping to improve Limesurvey. There are many important 
> features missing at the current API, so feel free to add what you need.
>
> In order to be able to add your feature to the core, please follow the 
> process described here: 
> http://manual.limesurvey.org/wiki/How_to_contribute_new_features.
>
> Best regards,
> Marcel
> --
> Dr. Marcel Minke
>
> Head Consultant at Limesurvey-Consulting.com 
> <http://www.limesurvey-consulting.com>
> Owner of the Limesurvey Template Shop 
> <http://www.limesurvey-templates.com>
> Head of Support at Limesurvey <http://www.limesurvey.org>
>
> Feel free to add me at LinkedIn 
> <http://de.linkedin.com/in/marcelminke> | Xing 
> <https://www.xing.com/profile/DrMarcel_Minke> | Google+ 
> <https://plus.google.com/u/0/102812116525985282322/about>
>
> Am 18.10.2013 00:53, schrieb Vincent Biragnet:
>> Hi all,
>>
>> Actually, I'm a freelance IT guy, mainly working with XML related 
>> technologies (e.g. my stackoverflow profile here: 
>> http://stackoverflow.com/users/780733/vincent-biragnet) and java.
>>
>> I'm currently using limesurvey in a professional environment. I 
>> wanted to add features in the Remote control API and offer to share 
>> my dev with limesurvey community.
>>
>> I'm working with the Json api, as recommanded in documentation.
>>
>> I noticed that:
>> 1) objects order in the "params" array has to fit params order in the 
>> function.
>> 2) optional params may be mandatory. e.g.: if i need to pass the 
>> optional param number n, then optional param number (n-1) has to be 
>> defined in the json.
>>
>> I made a pull request to fix those two problems (see here: 
>> https://github.com/LimeSurvey/LimeSurvey/pull/147)
>>
>> Then I have some ideas to add features to export survey responses and 
>> statistics. For example: the export_responses_by_token may be 
>> extended to accept a list of tokens.
>>
>> If you are interested in such work, let me know and don't hesitate to 
>> tell me if there are special rules or guidelines concerning the api.
>>
>> Best Regards,
>> Vincent
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>>
>>
>> _______________________________________________
>> limesurvey-developers mailing list
>> lim...@li...
>> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers
>>    
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> limesurvey-developers mailing list
> lim...@li...
> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers