I nominate Christian for the "CONTRIBUTOR OF THE MONTH" award! Christian has
been consistently providing both full releases and snippets of very useful
code, and has even done a great job with wiki documentation! Not only has
Christian supported the code that he wrote, but has also taken it upon
himself to become the new maintainer of the Python backend.
Three cheers to Christian!
Derrell
On Sun, Nov 29, 2009 at 16:19, panyasan <[email protected]> wrote:
>
> Hi,
>
> As you might have noticed, I have been busy on the backend front and am
> happy to be able to finish this weekend with a couple of releases:
>
> RpcConsole 0.1
>
> http://qooxdoo.org/contrib/project#rpcconsole
> http://qooxdoo.org/contrib/project/rpcconsole
>
> This debugging tool should be pretty stable by now and could very well be
> 1.0 soon. I am still waiting because I am still interested in feedback on
> the mockup data generation feature
> (http://qooxdoo.org/contrib/project/rpcconsole#creating_mockup_data)
> through
> the rpcconsole.MRpcMockup mixin. Let your voices be heard whether this
> makes
> any sense or how else you would implement mockup data integration. I think
> we need something like rpcconsole.MRpcMockup inside the framework rather
> than as a contribution.
>
> RpcPhp 1.1.0
>
> http://qooxdoo.org/contrib/project#rpcphp
> http://qooxdoo.org/documentation/0.8/rpc_php
>
> This is the first release of the OO-rewrite of Derrell's JSON-RPC server in
> PHP. Should be pretty stable, too, and works with PHP 4.3 (!!). The trunk
> will now drop PHP 4 support.
>
> RpcPython 0.1
>
> http://qooxdoo.org/contrib/project#rpcpython
> http://qooxdoo.org/documentation/RPC_Python
>
> The first release of the re-integrated python json-rpc server. In contrast
> to the first trunk version, I have introduced the requirement that service
> classes MUST subclass qxjsonrpc.server.JsonRpcService in order to be
> executed. Since Python allows multiple inheritance, this shouldn't be a
> problem.
>
> Both RpcPython and RpcPhp support the system.getCapabilities() method and
> service introspection (with some limitations):
>
> http://qooxdoo.org/documentation/jsonrpc_extensions
>
> Where should rpc documentation go?
>
> As you can see from the disparate URLs, it is not quite clear to me where
> to
> place the documentation concerning the backends. To put them into the
> qooxdoo-versioned documentation (documentation/0.8/...) doesn't make too
> much sense, since the JSON-RPC standard is version-independent, and the
> servers move in their own versioning system. So the documentation could be
> moved into its own namespace (documentation/backends/jsonrpc/...). Or
> placed
> with the individual contributions (contrib/project/RpcXXX). Any thoughts?
>
> Cheers,
>
> Christian
> --
> View this message in context:
> http://n2.nabble.com/New-contrib-releases-RpcConsole-RpcPhp-RpcPython-tp4084412p4084412.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
