Amit Rana wrote:
> I tried with a simple version too but got the same error.
>
> The issue which Firebug states (when I click on say qx.Class) is :
> GET qx.Class.js - Error 404
>
> It tries to look for /api/script/qx.Class.js but actually the file
> name on server (under api/script) is qx.class.js (Note that
> qx.class.js is with "c" and not "C")
But that means it is looking for an *absolute* server path
(/api/script/qx.Class.js), not for a relative one, which is a big
difference. Again, what is the *exact* URL that is requested by the
browser (don't guess, look), what is at least the server path? If your
initial request for the index.html was myJSfolder/custom/api/index.html,
this is translated to some full URL with a server path like
/a/b/myJSfolder/custom/api/index.html. When now qx.Class.js is requested
it has to translate into an URL with a server path of
/a/b/myJSfolder/custom/api/script/qx.Class.js. - Is this the case?
(I don't think it relates to capitalisation; why would it then work when
you open api/index.html directly. Have you checked capitalisation in
URLs when you open apiviewer directly?).
T.
>
> qx.class.js code snippet:
>
> {type:"class",attributes:{"isStatic":"true","name":"Class","packageName":"qx","fullName":"qx.Class","type":"bootstrap"}...
>
>
>
>
> So, api/index.html#qx.Class should be calling qx.class.js but tries to
> look for qx.Class.js.
>
> This thing works properly if api/index.html is called independently in
> the browser.
>
> Amit
>
> thron7 wrote:
>> Amit Rana wrote:
>>
>>> Hi,
>>>
>>> I saw the source and its pretty straightforward. I don't get why my
>>> code doesn't work. :-(
>>> My index.html is similar but the api/index.html is nested deep
>>> inside (which should not be a problem):
>>>
>>> <li>
>>> <h2>API Viewer</h2>
>>> <p>qooxdoo-based API viewer featuring the API reference.</p>
>>> <span class="local"><a
>>> href="myJSfolder/custom/api/index.html"><b>Open API viewer</b></a>
>>> <span class="publish"><a
>>> href="myJSfolder/custom/api/index.html"><b>Open API
>>> viewer</b></a></span>
>>> </li>
>>>
>>>
>>
>> Why are you using two links with different 'class' attributes around
>> them? Is there some magic in the CSS for those classes going on? Are
>> the resulting URLs correctly requested by the browser once you click
>> them (check Firebug Net tab)? What happens to the URLs on the server
>> (aliases, rewriting, ..)?
>>
>> Can you reproduce the issue in a stripped-down scenario (simple HTML
>> page, no CSS, one link to Apiviewer, no server-side rewriting, ...)?
>>
>> Thomas
>>
>>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
