Open mcasimir opened 10 years ago
Does the switch to Gulp mean that anyone using MobileAngularUI in their projects will also need to switch to Gulp? We use Grunt and really do not want to switch.
Also, if you had a guess, when do you think this will be ready to use?
Many thanks, -Lyle
Hi @lylepratt, the switch to Gulp will be demanded to a future release, so I think no problem for now.
Cool., but just because Mobile Angular UI uses gulp, that doesn't mean projects built with it have to use it as well right? As long as we are both using Bower it should be fine regardless.
Also, if Gulp is not going to be a part of 1.2, then we should remove it from this Roadmap.
Gulp seems to be more popular now. Even core ng team use it (I believe).
On 29 October 2014 16:13, Lyle Pratt notifications@github.com wrote:
Cool., but just because Mobile Angular UI uses gulp, that doesn't mean projects built with it have to use it as well right? As long as we are both using Bower it should be fine regardless.
Also, if Gulp is not going to be a part of 1.2, then we should remove it from this Roadmap.
— Reply to this email directly or view it on GitHub https://github.com/mcasimir/mobile-angular-ui/issues/109#issuecomment-60953322 .
also see: Why Gulp over Grunt? in Google Web Starter Kit (Beta) http://developers.google.com/web/starter-kit https://github.com/google/web-starter-kit/wiki/FAQ
Yeah, I agree that Gulp is better for new projects. However, we (and others) do not have new projects... we have complex build processes already built on Grunt. It doesn't really matter though, just because MAUI switches, does not mean projects using it have to switch as well.
1.2 development goes on: https://github.com/mcasimir/mobile-angular-ui/tree/1.2
Goals
Tasks
[ ] Test Transform support for any browser [ ] Test yieldTo should work despite is added before or after contentFor [ ] Test ui-switch directive [ ] Ui switch should work with swipe if present [ ] Transform should support 3d transforms too [ ] Generalize exporting SharedState states to query params [ ]
swipe
module should provide directives too [ ] ui-* should not take into account$scope
for efficiency but should work withng-repeat
if possible [ ] Support for drag gestures, eg. to create snap.js like sidebars and swipeable/draggable carousels, drag to refresh... (Needs a robust way to retrieve coordinates mixing translate3d and static/relative positioning) should be something as capable as http://pep.briangonzalez.org/. [ ] Move.scrollable
to core? (needs moving css style to js).overlay
class to a modal makes it an overlay.scrollable-header
/.scrollable-footer
Generator
Collaborate