1 May 2013 6:09 AM #1
BUG: Renaming view retains old name in the Application views 
Using SA 2.2.1, Build 951
Tried to rename a view from 'Passphrase' to 'PassphrasePopup'.
SA added the new view to the app.js view: config, but failed to removed the reference to the old view. Once sync'ed with webserver (and old the view Passphrase.js file is removed), the application generates a loader error trying to load the old named, ie: Passphrase.js file.
Resolution: manually go to the Application in the Project inspector, scroll down to the views property in the Config panel and delete the reference to the old named view.
1 May 2013 6:28 AM #2
1 May 2013 6:38 AM #3
Only one rap on the nose w/ rolled newspaper, then pet afterwards for forgiveness.
1 May 2013 8:04 AM #4
Thanks for the report... Can you tell us how to reproduce this?
When entering the view if its picked up by Architect it will put a small icon next to it. These views should be tracked. If you enter some other random name like say "Bla". It will not have an icon next to it and the views name changes will not be tracked.Aaron Conran
1 May 2013 8:36 AM #5
Sorry -- no. I've tried several times to reproduce the problem, but it defies demonstration.
To the best of my knowledge, the sequence of what I did when I saw this earlier today was:
1) drop Ext.window.Window under view (as top level view)
2) did some work on configuring layout of window
3) later on, decided to refine the name (changed by userAlias and userClassName).
4) published to webserver
5) received loader error
Two interesting points to mention.
1st -- I'm pretty certain that I published the app and it seemed to work ok. Then returned to editing within SA (made minor changes to fields displayed within form contained within window). Published a second time, and then saw the error.
2nd -- I know this has happened in the past -- but I too did not report it previously.
I'll keep on the lookout for reproducible.
1 May 2013 8:43 AM #6
I'm in the same boat as far as recreating this... it usually happens when I least expect it and have forgotten exact steps to reproduce.
Something you guys might consider adding to SA is a debug activity log. a timestamp log of every action a user takes within SA (name changes, adds, removes etc..). For something like this, we would flip the flag on then go about our business... when something happens we or your team could see the exact steps taken w/out having to rely on our short-term memory. With this in hand you could implement a replay log to watch the problem live... could even tie this into a learning architect feature. download a sencha replay file to watch how the experts do it.
1 May 2013 7:22 PM #7Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...
When in doubt, check the d4mn source code!
And here are my terms...
- I don't care if you use my source code. (Known as "Code.")
- I don't care if I get any monetary compensation.
- I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
- Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
- By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
- You are welcome to change and improve the Code to best meet your needs.
- I don't care if you use the Code in a commercial or open-source project.
- You are not required to contact me prior to using the Code.