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
The same would go for _boiler_. I would have these two modules configured in main.js in the require config to always load from extend\*. All new modules can now be created in extend allowing overrides of core files, helper files and new core extensions to be added without touching core itself.
Implement a Backbone style 'extend' static on core classes
So I stole the Backbone extend function and placed it into boilerplate. I have then modified all core classes to use the extend method as a static extend.
I 'd like to know your thoughts, this structure works very well for me and I'm sure it'd work well for most that have used Boilerplate.js to bootstrap their projects.
The text was updated successfully, but these errors were encountered:
As with most projects I don't like modifying core files (although this project does present a unique case to do it). My proposal is as follows.
Split core directory into two structures
The Helpers extended module would look like this :
The same would go for
_boiler_
. I would have these two modules configured inmain.js
in the require config to always load fromextend\*
. All new modules can now be created in extend allowing overrides of core files, helper files and new core extensions to be added without touching core itself.Implement a Backbone style 'extend' static on core classes
So I stole the Backbone extend function and placed it into boilerplate. I have then modified all core classes to use the extend method as a static
extend
.This allows
I 'd like to know your thoughts, this structure works very well for me and I'm sure it'd work well for most that have used Boilerplate.js to bootstrap their projects.
The text was updated successfully, but these errors were encountered: