Comments for Nicollet.Net

Comment on Reusable CSS by PHP 5.3 Closures as Block Literals? at Nicollet.Net

PHP 5.3 Closures as Block Literals? at Nicollet.Net — Thu, 04 Mar 2010 21:41:36 +0000

[...] explained earlier a few things about writing reusable CSS code, and how it interacted with PHP. Let’s start with this basic HTML for generating two columns, [...]

Comment on Lorem Ipsum by Brian

Brian — Wed, 03 Mar 2010 23:21:35 +0000

Your unsubtle hint will not go unaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaanswered

Comment on No Wheat Please by Georgette Thee

Georgette Thee — Tue, 02 Mar 2010 19:40:54 +0000

Great blog and post cheers. How long has this site been running now? The only thing is I seem to be having slight technical difficulties getting to your RSS feed though. Georgette Thee

Comment on Reusable CSS by Onecuts Web Solutions

Onecuts Web Solutions — Tue, 23 Feb 2010 19:41:54 +0000

[...] the original here: Reusable CSS at Nicollet.Net Tags: CSS, functions, neither-functions, nor-variables, perverted-beyond This entry [...]

Comment on Best Practices by Niven Denune

Niven Denune — Thu, 28 Jan 2010 09:38:25 +0000

I started following your posts now and really find it interesting. From the many sites i usually rampage through this article definitely stands out. Thanks.

Comment on DOM removal and events by That DOM removal thing, again at Nicollet.Net

That DOM removal thing, again at Nicollet.Net — Fri, 22 Jan 2010 09:12:06 +0000

[...] this month, I pondered what looked like a bug in JavaScript/DOM/jQuery: removing an element from the DOM with jQuery (either manually with remove() or by setting the [...]

Comment on OCaml Web Sites by Guillaume Yziquel

Guillaume Yziquel — Mon, 18 Jan 2010 21:06:10 +0000

I believe that the Ocsigen server and the Eliom framework are simply fantastic. The OCaml/Ocsigen community is somehow too focused (in my opinion) on producing statically typed valid (X)HTML. But you can insert raw HTML if you wish to simplify quick development.

Then, to build a web application that is highly interactive, you can do really cool stuff with Lwt and the React module. In my case, the web app was handling interaction with an Asterisk server, and was used to automate dialing. Agents would use log into a webpage, connect with their softfone with the Asterisk server, and the webapp was administrating everything, automating calls coming in and out, and handling dynamically with (statically typed) ExtJS the status and outcome of phone calls. And there was another similar webpage for the administrator. All this was fully reactive (An agent event or an Asterisk event or an administrator event usually hd an impact on both Asterisk, the agent’s webpage and the administrator’s webpage), and happening mostly in RAM. The DB was just to memorise what was going on, and was not the heart of a state machine, as is too often the case…

Everything was done in a functional and reactive way. Took me two weeks, only evenings, to develop that.

Somehow, even a Ruby on Rails app is a state machine. Perhaps a “better state machine”, but a state machine nonetheless, in the sense that incoming requests interact with each other by modifying the internal data.

With Ocsigen / Eliom, it’s completely different: it’s a “safely” multithreaded, compiled, application. And that makes all the difference.

Besides, there’s O’Browser, which is an OCaml bytecode machine that is interpreted in Javascript. Meaning that you can run OCaml code in the browser. What would be cool is to have cool javascript libraries such as ExtJS binded to O’Browser: you could use really high abstraction for windowing, etc…

Much has been done for browser-side technology. On server-side, somehow, the “state machine” paradigm has been a hindrance. To some extent, Ocsigen and Eliom fixes that when using high level stuff such as React.

I really think you should have a look at Ocsigen / Eliom / Lwt / React and write another post after that. There are some caveats, and a steep learning curve, but overall, it’s really impressive.

Comment on Hacking Magento by Magento/Wordpress injection vulnerability | Manchester Magento web design, development, Magento hosting and aftercare :: sonassi

Wed, 13 Jan 2010 19:20:38 +0000

[...] is a nice article on hacking Magento at nicollet.net. Last 5 posts in Knowledge BaseIMAP/POP3/SMTP DetailsQuick script to batch create [...]

Comment on DOM removal and events by Victor Nicollet

Victor Nicollet — Fri, 08 Jan 2010 10:19:03 +0000

@Adam and Tom: thank you for your answers. I already know why the element itself sticks around and can be inserted into the DOM again: JS is a garbage-collected language, and the DOM elements stay alive as long as they are referenced.

What I don’t know is why the click event I registered on the object disappears.

Comment on DOM removal and events by Tom

Tom — Fri, 08 Jan 2010 02:07:38 +0000

Emptying the body doesn’t destroy the reference to the element you created. Imagine creating a variable with a string. Would you expect that to suddenly disappear if you emptied the body? In the same way, the element you created a reference for (in this case button), still exists, with or without the page.