Closed Bug 1057835 Opened 10 years ago Closed 6 years ago

Modifying Building Blocks to support a front-end framework

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aleksanderkoko, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140715214327

Steps to reproduce:

I have developed 2 applications for Firefox OS. Building Blocks it's quite nice. After developing with Building Blocks I noticed that is easier for everyone if you have every element predefined. It looked fine when I started using it.


Actual results:

That pushed me to start the hybrid mobile application development. I found a nice tool called Ionic which is one of the top most used frameworks for hybrid mobile applications. Ionic doesn't differ to much from Building Blocks but is backed with AngularJs. It has a proper architecture and the navigation between different views is hapens using configuration. I think Building Blocks lacks of this feature. I searched on Yeoman, Bower but I found nothing like this. My idea is to make a separate repo (fork) and construct Building Blocks with a proper front-end framework. We can do proper architecture, a grunt or gulp configuration and these kind of things. What I understood from using BB and Ionic is that BB requires you to do the things manually and in the end you waste time to do things that you will do every time you use it.


Expected results:

If we do this I think that the community will develop applications faster, more scalable (EmberJs, AngularJs are scalable) with more quality.
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.