brite.js 1.1.6 released -
- Put #britejs on NPM npmjs.com/search?q=brite.
- Refactor code to be npm friendly and better componentized with nodejs require/module model.

Next: Refactor the lifecycle code to prepare for the new hook APIs, which will allow to decouple the DAO from the view lifecycle code and make brite.js hookable.

See changelog and roadmap britejs.org/download #DOMCentricMVC

Post has attachment
Hi,

I got interested in brite.js based on a recent Quora.com thread. However, after looking at the age of the posts in this group, as well as the update activity on GitHub, I'm wondering about the health of brite.js. Is brite.js still being actively developed and supported? If not, is there another js MVC framework that could be recommended?

Thanks

Post has attachment

Hello,what is the major difference between angularjs and britejs
or other javascript mvc framework.

Is there video tutorial that we can view  to better understand britejs framework

Post has attachment

Post has shared content
Here are some questions I got from someone and I wanted to share the answers with everybody. 

Q: What is the differences between snow.jar vs brite.js

snow.jar and brite.js are two independent technologies that happen to share the same philosophy of being lightweight and close to their respective environments. 

brite.js is a HTML/JavaScript library that brings a lightweight DOM centric MVC to HTML. Contrary to Sencha, Angulars.js and many other high abstraction MVC JavaScript frameworks, brite.js just add the strict minimum to the DOM to make it a robust and scalable MVC environment to build highly interactive application in a scalable manner. Meaning, it does not try to bring a meta-binding language or make everything a widget with over killed inheritance, but rather, give a fully asynchronous lifecycle for bigger component (composite views) while encouraging to use native HTML/CSS and event delegation for smaller elements (e.g., buttons and list items). The key API of brite.js is brite.registerView and brite.displayView. 

Snow.java has the same philosophy than brite.js but on the server side with Java. Snow is a Web Binding frameworks based on Guice with a efficiently, lightweight, and extremely flexible way to bind HTTP request to Java methods for WebREST api or SEO based HTML pages use Freemarker as a templating engine. Contrary to Spring, snow.java does not intend to solve all common problems neither think that a single framework should do so, and promote targeted libraries or micro framework rather than big mega frameworks a la Spring or JEE.

Q: My app uploads and display images, integrates with aws s3 and aws rds. I'm using mysql-stored procedure for all my dao

Snow and its approach are perfect for this use case. I would create my own DAO scheme that rather to use the Snow embedded Hibernate facilities, I would create by own DAO hierarchy with a DAOHelper that would have the lower level DB APIs that your Dao would use. 

I would have a @Provide DAOHelper in the AppConfig.java (the Guice Module) which will create the pooled DataSource and initialize the DAOHelper (this will be a @Singleton), and then @Inject DAOHelper in my Entity daos that would also be @Singleton. 

For your image upload, just do a @WebPost that and have a @WebParam(…) FileItem fileItem, and you should get the file uploaded. A while back I also added the ability to add multiple files with FileItem[] fileItems from a user’s request (let me know if it does not work). 

Also, one cool thing about the way Snow properties file, is that you can have your default properties in the /WEB-INF/snow.properties, which will point to your development mysql and all, but then, when you deploy you can override any properties by putting a files name [appfoldername].properties in the /webapps/ folder. So, let’s say your application is name “coolpix”, then you would have: 

/webapps/coolpix/ (war folder)
/webapps/coolpix.properties (any properties in this file would override the default /WEB-INF/snow.properties)

This is very simple but very flexible. 

Post has attachment
brite.js 1.1.2 released
https://github.com/BriteSnow/brite#112-march-22nd-2014

+ added brite.config.jsPath and brite.config.cssPath for configuring the location of the brite view components when using on demand loading
. updated examples to jquery 1.11
. minor reformating to be more jshint compliant. Updated to bootstrap 3.1.1
. update to handlebars 1.3.0 and fix taskmanager with latest bootstrap
+ Makes brite.js compatible with AMD and CommonJS (Thanks to Sankar Gorthi)
. updated sample/taskmanager to point correctly to the bootstrap 3.0 and use handlebars-1.0.0
! remove the brite.gtx (canvas utilities) from brite (moved gtx.js to /extra)
- btap issue when binding only on parent, btap on child does not propagate
- Fix btap event to fire only once (without the use of preventDefault which would be too destructive for other event handlers)

How come you hard-coded into brite.js the expected file paths (eg js, css files). I suggest you offer users the option of setting their own paths/folder structure for their apps. I have 124 js files (modules,views,models etc) and I do not want to put them all into a single js/ folder. I want to like britejs but the lack of this most basic feature is a show stopper for me.

Post has attachment
#JSBuildSystem  Gulp to take over Grunt? 

My take is that some of those stuff (contatination and minimization) are better handled in runtime when possible, since then you can just turn a flag in production or testing to have each file individually making JS and especially css debugging infinitely easier. 

However, those built systems have other interesting advantages, and should definintely be used when there is not server support for on-demand concatination & minimization. 
Wait while more posts are being loaded