What's weird Thomas is that if I reply to your messages on this thread it
brings up your personal email but [email protected] for
everyone else.  The reason I didn't repost is because you can see my
arguments in your response :P.  I'm currently waiting for a response about
getting contrib abilities.  Would put this in contrib as
RPCServerPythonCherrypy and of course document it on the wiki so it would
actually get used. :P

On Wed, Jun 24, 2009 at 8:17 AM, Thomas Herchenröder <
[email protected]> wrote:

> In case you choose not to re-post this message (which I think would be a
> shame since your reasoning is interesting), I want to at least comment on
> it.
>
>
>  Honestly I only created cause I didn't see an up to date project being
>> maintained.  I like the syntax that the QXRPCController class <
>> http://en.letras.ru/media/blogs/enletras/qxrpc.py.txt> used, however I
>> don't see any handling of the errors laid down by the protocol as explained
>> on the rpc server wiki page.  I could wrap up my "Cooks do cherry pie" into
>> a standalone app with no dependencies or just leave as an easy to customize
>> module for cherrypy.  I don't care what the direction chosen by the qooxdoo
>> developer, just that there is an officially supported option for python.
>>
>
> If you make your project a qooxdoo-contrib I'd love to see this kind of
> reasoning in the accompanying documentation (Readme or wiki or else).
> Personally, I pretty much doubt that e.g. Victor is still actively
> interested in maintaining his Python RPC implementation. We'll see...
>
>  While I have the qooxdoo developers "on the line", will/could there ever
>> be a port of the QWT to a python web toolkit?  I'm a 3d artist that codes a
>> bit and if there was a python version of QWT I could make interfaces to my
>> tools in a single language for multiple 3d applications which is a huge
>> maintainance boost.
>>
>
> I'm not sure, and if you asked that on the mailing list, Andreas, our
> project lead, might have an opinion on that. I would rather not bet on it.
> QWT is a mighty tool, and re-implementing that in Python seems no light task
> to me, which I don't see any resources being available for any time soon.
>
> If you feel comfortable with XML there is another project, qxtransformer,
> which follows a declarative, XML-based approach to getting qooxdoo-based
> GUIs. Their tools are in Python.
> http://qooxdoo.org/contrib/project#qxtransformer_xml_ui-building
>
> T.
>
>
>>
>> On Wed, Jun 24, 2009 at 2:43 AM, Thomas Herchenröder <
>> [email protected] <mailto:[email protected]>>
>> wrote:
>>
>>    I got the cc: alright.
>>
>>    T.
>>
>>    Andreas Ecker wrote:
>>
>>        Hi Delaney, Viktor, Thomas,
>>
>>        I CC'd you in my recent post to the qooxdoo mailing list, but
>>        it looks
>>        like it was stripped off. :-(
>>        Anyway, I'll forwarding this now, so you get to know about
>>        this asap.
>>
>>        Bye,
>>
>>        Andreas
>>
>>
>>  ------------------------------------------------------------------------
>>
>>        Subject:
>>        Re: [qooxdoo-devel] RPC server implemented using Python (Cherrypy)
>>        From:
>>        Andreas Ecker <[email protected]
>>        <mailto:[email protected]>>
>>        Date:
>>        Wed, 24 Jun 2009 09:47:15 +0200
>>        To:
>>        qooxdoo Development <[email protected]
>>        <mailto:[email protected]>>
>>
>>        To:
>>        qooxdoo Development <[email protected]
>>        <mailto:[email protected]>>
>>        CC:
>>        Jacques Bousseau <[email protected]
>>        <mailto:[email protected]>>
>>
>>
>>
>>        Howdy!
>>
>>        On Wed, 2009-06-24 at 07:53 +0200, Jacques Bousseau wrote:
>>
>>            See this project :
>>            http://en.letras.ru/2009/01/qooxdoo-controller-for-cherrypy
>>
>>            Jacques
>>
>>            Delaney Gillilan a écrit :
>>                I noticed there is no is no official Python server so
>>                I made an
>>                initial stab at creating one using the awesome and
>>                fast http
>>                cherrypy server (www.cherrypy.org
>>                <http://www.cherrypy.org>).  Created with svn trunk of
>>
>>                cherrypy but 3.1 should work as well.  Obviously my
>>                tests need work
>>                but I implemented everything on
>>
>> http://qooxdoo.org/documentation/0.8/rpc_server_writer_guide.
>>                 Made
>>                a bitbucket project for it at
>>                http://bitbucket.org/delaney/cooks_do_cherry_pie/.
>>                 Any comments or
>>                thoughts for this are welcomed.
>>
>>
>>        Seems there is quite some effort to implement Python RPC
>>        solutions for
>>        qooxdoo. Besides the two approaches mentioned here there is the
>>        original, "official" implementation by Viktor Ferenczi, see
>>        http://qooxdoo.org/documentation/0.8/rpc_python
>>
>>        I'd like to have Viktor on board as the creator of the original
>>        qooxdoo/Python RPC solution, as he's always had many ideas to
>>        improve
>>        the current solution but lacking time/resources. Also Thomas
>>        (at least
>>        as an observer/supporter) as he's maintaining and advancing the
>>        Python-based qooxdoo tool chain.
>>        It would be great the qooxdoo/Python devs would enjoy to
>>        collaborate in
>>        providing an up-to-date RPC solution. This could also ensure
>>        the project
>>        kept being actively maintained and not going stale. Is there
>>        more than
>>        one environment to target (e.g. built around Cherry.py or
>>        not), which
>>        would mean more than on project?
>>        Let's see what the technical discussion leads to (for now I'd
>>        suggest to
>>        use the mailinglist for discussion, not a dedicated
>>        enhancement request
>>        in bugzilla). Whatever the proposals might be, I can well
>>        envision to
>>        start to host and incubate at least one such project as a
>>        contribution
>>        in qooxdoo-contrib.
>>
>>        qooxdoo/Python people speak up!   ;-)
>>
>>        Andreas
>>
>>
>>
>>    --    Thomas Herchenröder
>>    Development Technology & Architecture - Web Technologies
>>
>>    1&1 Internet AG       phone: +49 (0)721 91374-4482
>>    Ernst-Frey-Str.9      web  : www.1und1.de <http://www.1und1.de>
>> 76135 Karlsruhe              qooxdoo.org <http://qooxdoo.org>
>>
>>    Amtsgericht Montabaur HRB 6484
>>
>>    Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich,
>>    Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning
>>    Kettler,
>>    Dr. Oliver Mauss, Jan Oetjen
>>    Aufsichtsratsvorsitzender: Michael Scheeren
>>
>>
>>
>>
> --
> Thomas Herchenröder
> Development Technology & Architecture - Web Technologies
>
> 1&1 Internet AG       phone: +49 (0)721 91374-4482
> Ernst-Frey-Str.9      web  : www.1und1.de    76135 Karlsruhe
> qooxdoo.org
>
> Amtsgericht Montabaur HRB 6484
>
> Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich,
> Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler,
> Dr. Oliver Mauss, Jan Oetjen
> Aufsichtsratsvorsitzender: Michael Scheeren
>
>
>
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to