@NicolasIglesias wrote:
Hello , I need help with my application. I'm trying to load a view within < ion - nav -view > but the same is not in the "index.html ". Look at this example:
My index.html:
<!DOCTYPE html> <html> <head> include ... bla bla bla </head> <body ng-app="myApp"> <ion-nav-view></ion-nav-view> </body> </html>and this is my other view (where I have the menu and toolbar)
my app.html
<!DOCTYPE html> <html>(delete the code of the menu and toolbar for more clarity)
<ion-nav-view></ion-nav-view> </body> </html>in my app.js config routing:
....
.config(....){$stateProvider
.state('onboarding', {
url: '/onboarding',
templateUrl: 'app/onboarding/onboarding.html',
controller: 'OnbCtrl'
}).state("preLogin",{
url: '/preLogin',
templateUrl: 'app/login/pre-login.html',
controller: 'PloginCtrl'
}).state('app', {
url: '/app',
abstract: true,
templateUrl: 'app/body/app.html'
}).state("app.login", {
url: '/login',
templateUrl: 'app/login/login.html',
controller: 'LoginCtrl',
})My problem is that the first 2 screens " onboarding " and " prelogin " would be charged in the ion - nav -view of the index , while the " login" it would be loaded in the app.html that has the menu and the toolbar . But when browsing from my app ( on an Android device) to the login screen takes too long to load (a few seconds ) and makes the effect of delay before loading properly .. however if login I define it as the other two screens ( without inheriting the toolbar and menu ) a much more pleasant transition is..
I think my problem is the misuse of the second ion - nav -view but I can not understand how to solve this problem of performance
Thanks for your time!
Posts: 1
Participants: 1