crescentfresh

29 ms·

241.
by crescentfresh 15y ago
"...we need to be able to rederive the plaintext" The use of the word rederive sounds like it may be encrypted to me.
242.
by crescentfresh 15y ago
Your comment reads like that is a Bootstap version/"upgrade" of the Ajax Control Toolkit's picker. However it looks to be a completely separate project.
243.
by crescentfresh 15y ago
> You file with your labor board. Excuse my ignorance, but there was no union involved far as I can tell. What does this comment mean?
244.
by crescentfresh 15y ago
Which device/browser are you referring to? I cannot duplicate the toolbars moving up and down slightly as the page scrolls in safari on a 3GS (iOS 5), with the latest RC demo.
245.
by crescentfresh 15y ago
Does it just go without saying these days that jQuery is required? Trello uses it, as well as jQuery UI, date.js, and highcharts.js far as I can tell. I mention it because they mention other parts of the client stack (Backbone.js for ex), b
246.
by crescentfresh 15y ago
Does backbone use .data()?
247.
by crescentfresh 15y ago
Something about the marketing of this makes me feel uneasy. The graphs that depict size are misleading. The initial release (today) is already at v0.9 and the site (opened 1 week ago?) says it's "fully ready to use in production" The video
248.
by crescentfresh 15y ago
http://www.youtube.com/watch?v=MwNdWZsRXgk
249.
by crescentfresh 15y ago
Have you considered filtering of "all tickets" in the client, for different subsets? Eg http://stackoverflow.com/q/6865316/172188
250.
by crescentfresh 15y ago
> One way to avoid the problem is to remember to pass the ticket object from the collection to the model and not instantiate a new one. My initial thought exactly. > However, as your app grows complex, you will not be able to keep a
251.
by crescentfresh 15y ago
The melodrama comes out of a fear of losing them. Would you "throw yourself under a bus" to save them? When I think about why the answer is always yes, it does my head in. Puts my priorities in check.
252.
by crescentfresh 15y ago
I've tweaked the proposal at http://stackoverflow.com/questions/6865174/backbone-js-corre... to do just what you describe.
253.
by crescentfresh 15y ago
They've ported their controls to work under the .NET MVC umbrella: http://demos.telerik.com/aspnet-mvc
254.
by crescentfresh 15y ago
D'oh!
255.
by crescentfresh 15y ago
The payload is not JSONP and strikes me as a bit impractical: Geo = { /* object literal */ } I assume this service is meant to be consumed via <script> tag injection. Without a JSONP-style callback parameter, what are consu
256.
by crescentfresh 15y ago
No leak in IE6. No leak in FF 3.6.8.
257.
by crescentfresh 15y ago
I meant, explicit checks on the return value will break (not that this is a bad thing). Specifically, neither `'disabled' == true` nor `undefined == false` will ever be true[thy] and are thus breaking changes. Perhaps you meant implicit con
258.
by crescentfresh 15y ago
> code written against 1.5.2 will work 100% against 1.6.1 Nope. attr() returns a different value than it did before 1.6. Anything that relied on that value (eg $elem.attr('disabled') == true/false) is still going to break.
259.
by crescentfresh 15y ago
Trying to get some clarity around this commit. As I understand it this addresses usecases where an element's boolean property is set to true, and .attr() is called as a getter for said property, correct? Eg $(optionElement) .prop('s
260.
by crescentfresh 15y ago
Simple reproduce case: <html> <head> <script src="http://code.jquery.com/jquery-1.6.min.js"></script> </head> <body> <script> $('body').append( '<span><
261.
by crescentfresh 15y ago
Relying on the following attributes as returned from .attr() will break, and should get ported to use .prop() instead: 'checked', 'disabled', 'readonly', 'selected' (for <option>s), 'multiple' (for <select>s), 'ismap' (for &
262.
by crescentfresh 15y ago
> Continuing to use .attr()/.removeAttr() will probably be just fine Your blog post calls them "breaking changes" for a reason though. Code that does `if ($elem.attr('checked'))` needs to be rewritten to use .prop when upgrading. Saying
263.
by crescentfresh 19y ago
It's funny how the article uses parenthesis and brackets as examples of unneccessary 'cruft' that muddles your program's readability, yet to explain a common 'Rails-ism' the author re-introduces both of them into the sample code to make it