cryptoquick - Developer IT

OS X contains heapsort in stdlib.h which conflicts with heapsort in sort library

- by CryptoQuick

I'm using Ariel Faigon's sort library, found here: http://www.yendor.com/programming/sort/ I was able to get all my code working on Linux, but unfortunately, when trying to compile with GCC on Mac, its default stdlib.h contains another heapsort, which unfortunately results in a conflicting types error. Here's the man page for Apple heapsort: http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man3/heapsort.3.html Commenting out the heapsort in the sort library header causes a whole heap of problems. (pardon the pun) I also briefly thought of commenting out my use of stdlib.h, but I use malloc and realloc, so that won't work at all. Any ideas?

Read the article

Making an SVG DOM JavaScript class

- by CryptoQuick

I'm unsatisfied with other JavaScript libraries and frameworks like jQuery, MooTools, and Raphael, because of their inability to support SVG grouping. You'd think it'd be a very simple thing for them to implement. Anyway, I'm trying to make a JavaScript class (using John Resig's class.js script) like this: var El = Class.extend({ el: null, svgNS: "http://www.w3.org/2000/svg", init: function (type) { this.el = document.createElementNS(this.svgNS, type); }, set: function (name, attr) { this.el.setAttributeNS(null, name, attr); }, get: function (el, name) { var attr = this.el.getAttributeNS(null, name); return attr; }, add: function (targEl) { targEl.el.appendChild(this.el); }, remove: function (targEl) { targEl.el.removeChild(this.el); }, setEl: function (docId) { this.el = document.getElementById(docId); } }); I can add elements to the DOM using these statements outside of the class, but storing the element inside the class becomes problematic. Anyone have any creative ideas?

Read the article

Fullscreen HTML Element using window.innerHeight/Width different with DOCTYPE

- by CryptoQuick

I'm trying to make an HTML5 canvas element fullscreen with the window.innerHeight and innerWidth properties. Unfortunately, on Chrome 10, when I set use the following doctype: <!DOCTYPE HTML> ...there is some extra scrolling space indicated by scroll bars which shouldn't appear. Without a doctype, everything is fine. The element is an HTML5 canvas, so styling with 100% will only stretch the content. Is it worth using a doctype which breaks my functionality (without which might be bad?), or should I subtract, say, 15px from the values in order to keep scroll bars from appearing? (which is kludgy)

Developer IT