Hi,
thanks for your answer.
Well, if I run the index.html manually in the browser I get this messages in
firebug:
source version:
Transport error 0: Unknown status code
var error = new Error(ex.toString());
AND:
003028 qx.io.remote.transport.XmlHttp[jm]: Failed to send data:
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIXMLHttpRequest.send]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///E|//stefan/studium/5.%20semester/studienarbeit/programme/qooxdoo/qooxdoo-0.8.3-sdk/framework/source/class/qx/io/remote/transport/XmlHttp.js
:: anonymous :: line 323" data: no]
build version:
Transport error 0: Unknown status code
if(u==0){if(F!=null){var G=new Error(F.toString());\n
If I run the versions from webserver I have the same effect I described in
the past.
But I don't know why I get this messages now.
Can you see the problem?
Thanks,
chakoteystme
2009/12/5 thron7 <[email protected]>
> Hi,
>
> > Yes, I try to run my source and my build version from a web server.
>
> You shouldn't do that for the source version. Running the source version
> from a web server requires additional efforts, potentially including
> tweaking your web server config.
>
> > If I open the file (build or source version index.html) manually from
> disk
> > directly the browser shows me the title of the website but no
> > qooxdoo-elements. this means it is the same if I try to load the
> > source-version from the webserver.
> > this means only the buildversion with the webserver runs.
>
> This is indeed very weird, as a build version running from the server
> should equally run from disk, unless you do some magic with web requests
> in your app. Do you?
>
> > in firebug I can see the javascript source from the file custom.js (in
> the
> > source version this file is very short and in the build version it is
> > really
> > big).
>
> That's normal.
>
> > I opened the files via the webserver.
>
> Why would you do that, when you load the index.html from disk?!
>
> > I don't know how I can see
> > more
> > files (you said around 300).
>
> Well, if Firebug's script tag doesn't show you more files, it means they
> are not loaded, which is the whole cause your app is not showing in the
> browser. The difficulty is to find out why the other files are not loaded.
>
> Let's focus on the source version loaded from disk. If you cannot get this
> to work, it's no use struggling with the build version, let alone running
> a version from the web server.
>
> Could you alongside to your 'htdocs' application create a new skeleton
> application using 'create-application.py -n sample'. Then cd sample and do
> a 'generate.py source'. Load source/index.html in your browser from disk.
> Do you see the sample application with the "Hello world" button?!
>
> T.
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
