I have just started evaluating qooxdoo + phonegap for a mobile application and have completed the getting started manual and created a test application which works as expected. The default app created has page1 with a button to navigate to page2 and back.
I have edited application.js to show a list by copying the list sample script into it but the list creation fails with error TypeError: Cannot read property 'List' of undefined
I have tried looking into the documentation to see if i have to make any changes to the app to load the list package but have not able to find anything. Can someone point me in the right direction?
Did you call
./generate.py source
after adding the qx.Mobile list to your application?
Calling ./generate.py source did not help ./generate.py source-all did the trick
Related
Hi Thanks in advance for your help.
The project I am developing is an adaptation of
https://codesandbox.io/s/r3f-wouter-routes-7kohn
I have split the project above into a larger project structure making use of web pack and other dependencies. My project with the bug can be viewed here:-
https://codesandbox.io/s/cranky-wood-hmub1
If that codesandbox does not work for you, you can clone from here:-
git clone https://github.com/SILVA-DIGITAL/SILVADIGITAL.git
yarn
yarn start
Steps to re-produce the bug:
Click on knot or bomb ( Top right hand navigation Menu ).
The knot or bomb model loads then disappears. Console mentions a shader error.
Known research:
I believe the bug is found within /components/shapes/index.tsx.
For some reason when switching the route to load a different model, the material class for the model to switch to fails its as if its not cached or does not have time to execute? I have tried wrapping the models in a suspense but that does not make a difference.
Here is the console error:
All objects should be stored in useState() if they are within the render function.
I am trying to use View Engine to return an HTML page in my window application. URL gets called but when i try to return a View, i get ViewNotFoundException error.
In an error message, I cant see the extensions available and locations inspected but i still get an error as Below:
Nancy.RequestExecutionException: Oh noes! ---> Nancy.ViewEngines.ViewNotFoundException: Unable to locate view 'test' Currently available view engine extensions: sshtml,html,htm,cshtml,vbhtml
I have checked the Demo project on git and it works fine but that's a web project whereas mine is window service (i might be missing something). Has anyone tried to implement View Engine in windows service and got it working.
Error is quite self-explanatory but i cant seems to get my head around where the test file should go for it to work.
Edit:
Nancy version: 1.4.2
I tried var foo = typeof(RazorViewEngine); and it does return all the View Engine values with locations inspected and all that.
My Project structure is:
Modules
---- myModule.cs
Views
---- Test.cshtml
views/test is in locations inspected but it looks like, its looking somewhere instead of my structure.
Thanks in advance
What is the best way to reference another app in the visual query designer?
I am using the blog app and I created a second app to list the tags that are used in the main blog app. This way when the app goes to a detail page of a post, I can still have the tags listed on the website without the view changing automatically. I set up my blog tags app with a visual query that list all of the tags used in the main app. Everything was working fine in development.
The problem that I have run into is that when I move the app to a production site the AppId was different than the one I was currently using and development. Now, the tags app is showing an error and I am not able to get into the settings to change the app ID of the visual query to the proper one in order to get the information needed. Is there a better way that I should be handling this?
This sounds like the right way to do it - your main issues is getting into the admin-ui when the template you have shows an error.
I suggest that you quickly rename your current template (so it's not used till you fix the bug) and create an empty template with the original name. This way you can go to the normal settings.
Another option is to switch into dnn-edit-mode, and use the black-dnn buttons to get to app-admin.
I'm having an odd issue after having migrated my drupal project to a client's server.
After configuring the apache http.conf to accept clean urls, I'm now finding that the administrative overlay does not always respond.
-The Find content shortcut doesn't respond, but the Content link on the overlay does.
-The Edit link when on a node's detail page makes the site darken like it does when the overlay is being loaded, but the Edit window for the node never appears.
-The X (close) on an overlay page (like when using Content to see the list of all nodes, but then want to quit out of it and go back to the site) fails to close the overlay and a strange, second vertical scrollbar appears on the right of the browser screen.
I have had a similar problem before, but chalked it up to javascript on the page interfering with the overlay's own javascript. Now I'm not so sure.
If anyone else has had this problem, or can surmise what the issue might be, then I would appreciate any and all help given.
My thanks,
~M#
It looks as if you are using a jQuery version that is incompatible with the overlay module. It's probably because $.browser is deprecated in jQuery 1.9, see the following issue:
Uncaught TypeError: Cannot read property 'msie' of undefined - jQuery tools
To fix this issue, you'll need to install the latest jQuery Update module and select something below jQuery 1.9 for the admin interface. This should clear up your problems in IE.
I am working through this extJS tutorial where you type in code into Firebug, press CTRL-Enter and it renders it for you, it worked for the simple example but then I got this error:
Instructions:
What happens:
What else do I need to do to get this example to work as it states it will in the demo?
You need to have ext-all.js (and maybe ext-base.js?) loaded in the page you're testing for this to work. The example isn't working properly for you because the Panel file cannot be located. It doesn't exist because you haven't added it.
Test the Ext.Panel code in firebug at the API site: http://dev.sencha.com/deploy/dev/docs/
You'll see that the desired behavior occurs because the page has all of the proper JS files loaded. Any time you see the message "... is not a constructor" should be an indication that the JS file containing the object has not been loaded into the page.