Yeah - I can see how that might be a pain for existing users. I am about to embark on a fairly significant project and we will certainly want to start with jquery-bootstrap as, I expect, most new users will. I'd support keeping the branches separate and asking people like me to help with making sure that improvements are made to both branches.
Kevin On Friday, December 7, 2012 10:20:58 AM UTC-8, Bruno wrote: > > > As for your question; it's hard to say. The jquery branch is pretty > stable, except for those few bugfixes you mentioned. The problem with > merging it in is that any existing apps (like, say, Curbly.com) will have a > pretty rough upgrade path since the jquery branch changes so much of the > underlying html. In particular, apps with modifications or overrides to the > view templates will have a tricky upgrade in store for them. > > I'd love to hear suggestions for how to eases this pain for people. My > tendency right now is to just leage jquery-bootstrap where it is (if > someone wants to pull in bugfixes from master, that'd be cool), and let > people choose it as a starting point for new apps, or upgrade existing apps > over time. > -- You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To view this discussion on the web visit https://groups.google.com/d/msg/communityengine/-/YSLcrtn8zNQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/communityengine?hl=en.
