Christian,
You need to take a step back from your code for a minute and re-think your
application. My application is about 10x the size of yours, and is 100% data
driven and everything you see when it runs is generated on the the fly,
there are no pre-written screens. And my entire application is developed
using mock data and the server is tested separately from the client. There
is no need to see 'real' data while you are developing something, all you
need to know is what the data is going to 'look' like. Then create a sample
set of data, or even a few sample sets and randomly return then if you don't
want to always see the same thing. There is, IMHO, never a need to have a
connected back end as a requirement during development. You should always be
able to use mocks on the client side, or at the least, have the mocks served
up from the server until you get all your server code properly written. In
my job, mocks are essential to day-to-day development.
Jim
On Sun, Oct 11, 2009 at 6:29 AM, panyasan <i...@bibliograph.org> wrote:
>
> Hello Thomas,
>
>
> thron7-2 wrote:
> >
> > 2) Backend Integration
> > It saddens to see how often backend integration is mentioned in the
> > context of development difficulties, both within and outside this thread.
> > After 20+ years of client-server development (and this what you all do)
> > and modular design it is still not apparent to many people that you do
> > backend integration *as rarely as possible* during development (namely,
> > when you do integration testing). All other times you make your best
> > effort to *decouple* the client part of your application from the
> backend.
> > In my view, this is the only sane way to develop client-server
> > applications. If you think, doing so is too much effort, you haven't
> > thought about the cost of not doing so. Rather than struggling with
> server
> > integration every time you make a change to your frontend
> >
> > - test the server independent from the frontend (e.g. with a simple
> test
> > client)
> > - provide the client with mock objects and -data, so it can run
> > completely independent of the server.
> >
>
> That sounds good in theory, and I fully agree about the client-server
> independence. Using JSON-RPC goes along way towards that goal. However, if
> you look, for example, at the application I am developing:
>
> http://n2.nabble.com/file/n3803350/Bild%2B1.png
>
> There are SO many server data request necessary that all depend on each
> other (because one request's result determines the subsequent requests).
> There is simply no way this could be done in a mock setup.
>
>
> thron7-2 wrote:
> >
> >
> > To that end, I had expected to see for quite a while
> >
> > - an RPCTestClient contribution that lets you enter a service URL and
> > request parameter, send the request to the server, and inspect the
> > returned data, in a simple, form-style application
> >
> >
>
> If have something like this in qcl (PHP backend):
>
> http://n2.nabble.com/file/n3803350/Bild%2B2.png
>
>
> https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/qcl/trunk/backend/php/class/qcl/server/debug_console.php
>
> But it is VERY primitive. I for a long time have wanted to replace it with
> a
> qooxdoo frontend. But there is only so much one can do at a time ;-). So if
> anyone would throw some time into this, it'd be very welcomed. Derrell's
> RpcExample contribution is a good basis on which to build on.
>
> Cheers,
>
> Christian
>
>
> --
> View this message in context:
> http://n2.nabble.com/qooxdoo-IDE-Request-for-Comments-tp3782909p3803350.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
