|
an skeleton posted:AngularJS question ahead: What are you using to determine if it's valid or not? I'm assuming adding ng validations to the template? I don't see anything in the API that could be doing it otherwise. Can you post the HTML and JS that are creating and populating this grid?
|
# ¿ Feb 3, 2014 23:08 |
|
|
# ¿ May 4, 2024 08:07 |
|
an skeleton posted:How do you detect the cell change? http://angular-ui.github.io/ng-grid/ afterSelectionChange function (rowItem, event) {} Callback for when you want to validate something after selection. It's a grid option, so you just give it the callback. Edit is a selection event, so you're probably doing this anyway.
|
# ¿ Feb 6, 2014 15:11 |
|
Dangerllama posted:^^ For the next two hours, Manning has all their JS books at 50% off, including AngularJS in Action. AngularJS in Action will probably be really good in about 6 months. Right now, it's so empty.
|
# ¿ Feb 27, 2014 12:48 |
|
more like dICK posted:I "installed" angular by downloading the files and putting them in a 'static/js' directory in my project. Bower is just a package manager for website libraries. It handles things like dependencies and keeping your libraries up to date for you, like any package manager. So if you have AngularJS + Bootstrap + Bootstrap-Angular + UI-Router all together, it can get a bit frustrating to manage all of that. That's where Bower is great. Just using AngularJS? Drop that SOB in your JS folder. Or, even better, use one of the open CDNs for it (GoogleCDN is the official one @ https://developers.google.com/speed/libraries/devguide#angularjs ) -- no need to even download it in that case, and you might speed up your user's experience some too.
|
# ¿ Jun 21, 2014 04:59 |
|
NovemberMike posted:IIRC it's literally a git wrapper. It just goes to the git repository for the project, finds the right tag, excludes a bunch of files that somebody specified and downloads the rest. Yeah, this. It's basically all up to the package author how it's laid out. Half of them are just dist files, half are a full distribution including src and tests. It really is crap, but it's the kind of crap that comes about when working backwards with no central authority.
|
# ¿ Jun 22, 2014 19:30 |
|
Bower is a step in the right direction. It's even a good first step. It could really use a central authority dictating some guidelines (release in the package, source in package-devel for instance) and enforcing them.
|
# ¿ Jun 22, 2014 22:57 |
|
Huragok posted:The drawback of using Polymer is it doesn't play nicely with older browsers. In before "don't you mean bonus?" Though, to be honest, I think we are at a point where legacy browsers can be ignored for modern web apps. The auto update processes in every browser are a lot better, I don't see much old school usage.
|
# ¿ Jul 6, 2014 23:22 |
|
|
# ¿ May 4, 2024 08:07 |
|
CSS performance question: Is it better to have one block of rules with a lot of selectors up top, or a lot of duplicate blocks with simple selectors up top? Basically, a coworker is using extend-only selectors in SASS for things like our buttons. Our code is clean when we write it, but we end up with generated CSS that makes me want to die: CSS code:
|
# ¿ Oct 20, 2014 15:40 |