-
15 Feb 2013 3:06 AM #1
Profiled Views not showing up after building production/testing
Profiled Views not showing up after building production/testing
Hello Everyone,
i've written a sencha 2.1.1 app with an extra profile for tablet&desktop and everything is working correctly while im developing. But after i'm building production and testing with SenchaCMD3.0.2 the "normal" views are showing up.
If added an extra console.log in the profile-launch function and it appears in the console, so the profile must been loaded correctly, but neverthelesss the correct views not appear.
Thanks in advance,
Urbanism
-
17 Feb 2013 8:00 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,582
- Vote Rating
- 433
Ext.app.Application should Ext.require the profile dependencies however doesn't look like it is. For now you can manually require the dependencies.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
17 Feb 2013 11:04 PM #3
You mean add 'Ext.app.Profile' to the requires in the app.js?
-
18 Feb 2013 9:11 AM #4Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,582
- Vote Rating
- 433
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
19 Feb 2013 1:35 AM #5
Sorry but i don't get it work
This is my app.js code
and this my Tablet.jsCode://<debug> Ext.Loader.setPath({ 'Ext' : 'touch/src', 'TestApp' : 'app' }); // </debug> Ext.application({ models : [ "ConfigModel", "UserModel", "ChatModel", "TaskModel", "TourModel", "VehicleModel" ], stores : [ "ConfigStore", "UserStore", "ChatStore", "TaskStore", "TourStore", "VehicleStore" ], controllers : [ "LoginController", "ProfileController", "TourController", "TaskController", "MapController", "ChatController" ], profiles : [ "Tablet" ], name : 'TestApp', //requires of the profiled views requires : [ 'Ext.MessageBox', 'Ext.dataview.List', 'Ext.field.Select', 'Ext.field.DatePicker', 'Ext.field.Password', 'Ext.field.Checkbox', 'Ext.Map', 'Ext.form.FieldSet', 'Ext.Img', 'Ext.SegmentedButton', 'Ext.field.DatePicker' ], //also added profiled views here views : [ 'Main', 'Login', 'Tab', 'Chat', 'Home', 'Tour', 'Task', 'Map', 'Profile', 'tablet.Main', 'tablet.Login', 'tablet.Tab', 'tablet.Chat', 'tablet.Home', 'tablet.Tour', 'tablet.Task', 'tablet.Map', 'tablet.Profile' ], launch : function() { // Destroy the #appLoadingIndicator element Ext.fly('appLoadingIndicator').destroy(); // Initialize the main view Ext.Viewport.add(Ext.create('TestApp.view.Main')); } });
Build executes with no erros.Code:Ext.define('TestApp.profile.Tablet', { extend : 'Ext.app.Profile', config : { views : [ 'Main', 'Login', 'Tab', 'Chat', 'Home', 'Tour', 'Task', 'Map', 'Profile' ], models : [], stores : [], controllers : [] }, isActive : function(app) { return Ext.os.is.Tablet || Ext.os.is.Desktop; }, launch : function() { console.log("profile.Tablet launch") Ext.Viewport.add(Ext.create('TestApp.view.tablet.Main')); } });
But the Profiled Views still not showing up.
Can you post an example?
You found a bug! We've classified it as
TOUCH-4004
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote