You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, congrats with this framework. I huge help for the community to try and get away from being forced into using Angular when using AppGyver.
We are planning to use Aurelia.io instead of BackBone. I'm very interested in some general guidelines for how to port your approach to using something else.
What is the starting point of the app and do you hook up the essential infrastructure to be compatible with AppGyver steroids?
I see that your App object in Index.js is a Backbone Controller.
var App = Backbone.Controller.extend({`
initialize: ...
}
in Aurelia you would usually have the Router instead
But I guess for AppGyver you don't use routing as every page is its own miniapp?
Then in the initializer you call various other initializers such as self._initPages(); which creates all pages, by creating instance of page then calling initializePage().
So here a supersonic ui view is created stored in self.m_page.
Is this a specific to supersonic or just your own convention?
var PageView = Backbone.View.extend({
/**
Create the Steroids page / view identity
@method initializePage
**/
initializePage: function () {
var self = this;
self.m_page = new supersonic.ui.View({
location: self.location,
id: self.pageID
});
self.m_page.start();
if (self.options && self.options.init == false)
return self;
self._initialize();
return self;
I could ask so many more questions about this whole architecture... Would be awesome if you could write up a blog post explaining the main design considerations. Thanks! Cheers :)
The text was updated successfully, but these errors were encountered:
Yes, I have seen that video a few weeks ago. Is that enough to go by? What about my questions above?
I don't really need all your extra infrastructure at this point (maybe some of it for later), right now I'm just curious about minimal framework integration with supersonic, ie. Aurelia views in my case.
First, congrats with this framework. I huge help for the community to try and get away from being forced into using Angular when using AppGyver.
We are planning to use Aurelia.io instead of BackBone. I'm very interested in some general guidelines for how to port your approach to using something else.
What is the starting point of the app and do you hook up the essential infrastructure to be compatible with AppGyver steroids?
I see that your App object in
Index.js
is a Backbone Controller.in Aurelia you would usually have the Router instead
But I guess for AppGyver you don't use routing as every page is its own miniapp?
Then in the initializer you call various other initializers such as
self._initPages();
which creates all pages, by creating instance of page then callinginitializePage()
.So here a supersonic ui view is created stored in
self.m_page
.Is this a specific to supersonic or just your own convention?
I could ask so many more questions about this whole architecture... Would be awesome if you could write up a blog post explaining the main design considerations. Thanks! Cheers :)
The text was updated successfully, but these errors were encountered: