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
Eric Bollens edited this page Sep 23, 2013
·
2 revisions
The Core Subgroup focuses on maintaining and extending the WebBlocks compiler and constituent parts. Some of the things this group will look at include compiler performance, unit tests, package availability, configurability and additional adapters.
Please add your name and email to the list if you are interested in engaging with this subgroup
Topics
Packages
Updates
WebBlocks 1.0 includes distributions of a handful of packages currently; each needs to be assessed and determined if the version should be bumped (must be backwards compatible or else a new mechanism is needed to specify default, with the default staying as the current version of the package).
External Packages
Currently, packages must be included from within the WebBlocks file structure; this creates an issue where one cannot add their own packages without having to fork and modify the WebBlocks structure itself. Ideally, it should be possible to specify a package with an location and handler that lie outside of the WebBlocks structure.
Adapters
Bootstrap 3
Bootstrap is currently linked to v2. It cannot be updated to v3 without a decent chunk of work because it changes semantics and is not backwards compatible. Ideally, we should seek to still implement a single adapter but rather allow the user to configure the version of Bootstrap they wish to use and then push that information into a SASS variable so that the adapter can intelligently choose its binding points. A detailed plan should be developed regarding this approach, or if it is not possible, then it will instead require the development of a new adapter.