-
24 Aug 2012 10:44 AM #1
citybars completed project files have errors in Sencha 2.1.0 build 588
citybars completed project files have errors in Sencha 2.1.0 build 588
I completed the citybars example and got an error so I downloaded the completed project files, updated the yelp key, and I see the same error in my Chrome console...
404 not found GET http://localhost/senchaArchitect/cit...=1345832867285 4
The path is incorrect it seems to be adding an extra "citybars" to the path. The path should be...
GET http://localhost/senchaArchitect/cit...=1345832867285 4
This error occurs after all the yelp locations load successfully and I click on one of them and it attempts to load the detailPanel view.
Any idea what is causing this? And what can be done to resolve it? I hope I don't have to wait for an update to secha itself!
Thanks in advance for the help.
-
24 Aug 2012 2:03 PM #2
You won't have to update sencha.
Seems the loader is getting crazy with you!
I would check what your settings are on your Application (select application and view code vs what's in github). Also what different about your detailPanel vs that one.Phil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
-
26 Aug 2012 11:15 AM #3
git version works, unable to figure out why tutorial version does not
git version works, unable to figure out why tutorial version does not
I ran the git version successfully. The version downloaded the tutorial page found here I could not figure out how to get it to run successfully. Below is what I did to troubleshoot it by comparing the git version to the tutorial version. None of the changes I tried got rid of the error I described in the initial post.

1.
When comparing the application settings the tutorial version had this...
Ext.Loader.setConfig({
enabled: true
});
The git version did not have this. I couldn't figure out how to remove it but I was able to add a "loader config" and unchecked "enabled" which changed the code to this...
Ext.Loader.setConfig({
});
2. When comparing this file, /controller/business.js I found the following differences
a. Tutorial version had an "init function", git had a "launch function", I removed the init and added the launch function, no change.
b. The "onListItemTap" functions were different. I replaced this function with the git version, no change.
c. config mainNav reference from tutorial is "#mainNav" and is "mainNav" from git. Changing this did not help.
3. When comparing this file, /view/detailPanel.js, I found the button container from tutorial has id, "MyContainer2", button container from git has no id. Removing the id did not help.
I am guessing if you download the xda file from the tutorial you should be able to reproduce the issue I am having. Even though I have the citybars tutorial working now from the git version I would really like to figure out how to fix the tutorial version to further my knowledge of Sencha and the process of how to troubleshoot issues like this.
-
27 Aug 2012 9:29 AM #4
1. are you looking at app.js or in Architect 'application node'?
I see the loader setConfig for both ...
2. Thank you! I suspect this was a merge conflict that wasn't handled correctly. I'm updating the tutorial now.
3. shouldn't matter.
I've updated the tutorial and the github projectPhil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
-
2 Sep 2012 7:03 PM #5
Found the issue, problem solved
Found the issue, problem solved
I finally discovered that if I changed the application name (ext.app.application: name) to "CityBars" the app would successfully load the detailView. Any other name would cause the 404 error mentioned in the first post. I assumed the app name would change everywhere but it was not changed inside of the "onListItemTap" function. As soon as I changed this to the proper app name it worked, here is the offending code...
details = Ext.create('CityBars.view.DetailPanel', {
title: 'Details'
});
Thanks for all your help!
-
5 Sep 2012 7:27 AM #6
Yes this would not change in code written by the user. It's smart but doesn't try to make leaps that could screw up the user.
A refactor ability would be a nice addition.Phil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team


Reply With Quote