Stand alone AngularJS date picker that does not require huge framework - angularjs

Would like to know what others are using as of 2015 for an Angular date picker that is an independent plugin.
Note: I saw this answer, which references UI Bootstrap, but the requirement is for a stand alone library. So that rules out Angular Strap as well :(
What I found so far:
http://720kb.github.io/angular-datepicker/
The 720k angular-datepicker looks promising, says it is responsive, and is recently maintained. IE compatibility is a question mark on its github page though, which would be nice.
https://github.com/alongubkin/angular-datepicker Port of pickdate.js to Angular, with jQuery stripped out. Interesting that it is 'responsive', but I wonder how well the bugs are worked out.
https://github.com/g00fy-/angular-datepicker Pretty full featured, but lacks docs.

After having a few issues with angular-strap I implemented the following:
https://github.com/dbushell/Pikaday
Worked well!

http://myplanet.github.io/angular-date-picker/
Localizable
Pure CSS – does not use any images
Pure Angular – does not rely on any other libraries
Compatible with IE8+

Related

Is zurb-foundation compatible with Angular JS?

I need to migrate an site from one framework to another because I need to use Angular JS.
I found zurb-foundation very interesting. It happens that it seems to use jQuery.
According to this website https://scotch.io/tutorials/how-to-correctly-use-bootstrapjs-and-angularjs-together
When building out Angular projects, you should not add on the full jQuery library. jQlite is already included in Angular and this should be all the jQuery that is necessary.
I had a bad experience running Bootstrap and Angular together and I don't want to repeat the same mistake.
It happens that I found the following line at zurb-foundation index.html
<script src="js/vendor/jquery.js"></script>
A quick search has shown that it seems to be a "simplified" version of jQuery (am I wrong?).
I've seem many people questioning things related to Angular in Foundation apps.
My question is: Is Angular compatible with Foundation?
While you'll read in many places that you should stay away from jQuery when using Angular, you'll also notice a subtle "at first" here and there. Angular is quite opinionated, and employs a declarative way of doing things, whereas jQuery is imperative. Check this out for more on the topic.
To answer your question:
Scotch.io's tutorial about Angular and Bootstrap involves UI Bootstrap, a library of directives written in Angular to be able to integrate common Bootstrap functionalities easier.
The equivalent of UI Bootstrap for Foundation is Angular Foundation. I recommend giving this thread a look-over as well, as it contains information that may be relevant to your use case.
So yes, Angular is compatible with Foundation. Happy hacking :)
a quick answer is of course they are compitable with each other. check this out from Zurb. However if you do not want to use JQuery, then the easiest way is to use pineconellc for foundation 5. foundation 6 does not have a port yet as far as I know.

How to extend angular-material components?

I want to apply angular-material in my recent project, but I am afraid that it will be very difficult to find other components which are not available currently. Like treeview, date/time picker, carousel and so on...
How can I deal with these things? any opinions?
I've just tried to use Angular-Material in a site with an existing style, and found a number of issues that I wasn't able to resolve:
- Site UI was feeling very sluggish
- There was a paralax script that became extremely slow and lagged when there was a quick scroll.
- Odd behavior with fonts when it loaded (when I re-sized the screen and back again it was working again) in chrome.
This became a real issue - for the most part it doesn't feel complete. I was really hoping for something like Material-UI, which appears to rely on React.
However, I have come across this https://fezvrasta.github.io/bootstrap-material-design/bootstrap-elements.html which appears to be suitable and works with bootstrap.
There's a really good answer : Using Bootstrap for Angular and Material design for Angular together for some of the issues you will face when using Material with bootstrap.
Also, I tested on a mobile phone and the site was terrible (in performance), you'd never want to get site up with that type of performance.
Also, there's lumx if you want angularjs support (e.g directives etc...). My other issue with lumx and angularjs material is that swapping over libraries is not an easy task. I'm not sure whether this is the norm, and heading this way in the future - but I'm from the Jquery days where my markup remained consistent and I can activate features. However, both lumx and angularjs material require specific tags which means that swapping over libraries requires me to edit my mark-up.
Maybe here is another view of using Angular Material.
I have been using Angular Material as the only web component for my work projects. Angular Material is still in beta version, and like you said, many components such as table, color picker, and sidenav are still missing. If you have to use those components in your projects and not able to implement yours, Angular Material may not be a right choice. Something like Angular-UI or Polymer is probably what you are looking for.
The reason we choose Angular Material at work rather than other nearly complete web component library/collection is because it is being very actively maintained. Currently there are 900+ open issues and lots of pull requests are still going on. For me, a complete version will be more guaranteed. Treeview, date/time/color picker, table these kinds of components are already in the open issues. Here you can search for it.
https://github.com/angular/material/issues
Currently we will find workaround or overwrite the material to solve problems. Or we will open issues if there is no solution. And again, it is still in beta version, you should decide whether you want to use it in your project. But you can definitely look at their available components to determine if Angular Material is a right choice for you.
https://material.angularjs.org/latest/#/

Does it make sense to implement md-data-table for angular material design?

I just created the md-data-table repository based on google material.
It will be an extension for angular-material design:
https://github.com/iamisti/md-data-table
demo: http://iamisti.github.io/md-data-table/
Does it make sense to implement?
I mean, I didnt see any md-data-table in the milestone of angular material (which I dont see why). So that I just want to make sure, I don't waste my time.
Update: This answer is from 2015. What was said below about the feature did not arrive.
As ThomasBurleson wrote about a month ago in this github comment on an issue similar to your question or poll here.
This is a very important component for Angular Material and any UI
Component library.
With the current schedule and goals for v1.0, however, the mdDataTable
will be implemented after the v1.0 release of Angular Material.
At the time of writing ng-material is on version 0.10/0.10.1-rc1, and it has been stated they are working for a v1 release this summer.
ThomasBurleson again: (source)
Angular Material 1.0 has a planned release for summer of 2015.
I'm sure I've seen some implementations of datatables so far by the ng/ng-material community, so I guess we'll have to make do with user-contributed solutions for now. (user-created datatable here or here)

AngularJS-based UI Components, quantumui vs. angular-strap vs. angular-bootstrap-ui

I have been looking for a component set for a start-up project which would be based on AngularJS.
After some research, I have found three common component sets which can be applicable.
The first is AngularJS Bootstrap UI. It seems clear, but there are no enough examples and documentation.
The second is angular-strap. I have seen that it is a simple implementation of bootstrap.js with some additional features, but it seem very simple.
And the last one is QuantumUI. I have seen that it is amazing, but it seems very new.
What is the experience with these frameworks? Can you list pros cons for them?
I am owner of QuantumUI and is is not truth to say anything about other's projects.
However I can say that in short;
ui-bootstrap: is pure angular based, but it is old and not compatiable with new angular versions. Also it's plugins are very simple.
Also angular-strap is a implementation of bootstrap.js. Namely, it isn't a project of angular thinking.
However QuantumUI is a compact angular solution. It's components are powerful, server and developer friendly and also there is no Jquery dependency. All components are results of angular thinking.

AngularJS 1.3 and IE8

So I know that AngularJS dropped support for IE8. I'd like to learn, whether this means that they won't simply test in IE8, or did they introduce some features that simply break in IE8.
Did anyone actually succeeded in setting up Angular 1.3+ application on IE8? What kind of approaches/shims are needed (modernir, es5-shims, respond.js, others?)
I have Angular 1.3 working with IE8.
It requires jQuery, a couple of shims and one source code change to Angular. I'm maintaining builds of Angular with a lot of the shims baked in and instructions on what else to include here:
https://github.com/fergaldoyle/angular.js-ie8-builds
I can't get the unit tests running properly with IE8 so can't confirm 100% compatibility, but using a broad smoke test I can confirm every feature I've ever used with Angular works fine in IE8 + 1.3
It simply means that they've stopped testing for anything beyond 1.2.x, which enables them to "add more exciting features to Angular faster, decrease Angular's support burden, and cut [their] build time in half, while affecting only a very small proportion of users."
They're not necessarily removing the hacks from Angular that made IE8 work but there's no guarantee that changes in anything after 1.2.x won't break an application running on IE8 since they've stopped supporting it and addressing any issues that are solely related to it.
The above was what they said in a post about a year ago, so it might very well be the case that there are certain features that break today. With that said, your safest bet would be to work with 1.2.x, unless you want to use 1.3.x and test it yourself.
References:
https://blog.angularjs.org/2013/12/angularjs-13-new-release-approaches.html#!http://angularjs.blogspot.com/2013/12/angularjs-13-new-release-approaches.html
https://docs.angularjs.org/guide/ie
After trying it on my own - no, Angular 1.3 simply won't run on IE8. It's not a matter of shims, or other libraries, or some hacks. It just won't work at all.

Resources