Comments for Martin Geisler Online http://mgeisler.net Adventures with Computers Sat, 20 Mar 2010 02:40:34 +0000 http://wordpress.org/?v=2.6-bleeding Comment on My Dell 3007WFP is here! by Jack http://mgeisler.net/2006/11/my-dell-3007wfp-is-here/#comment-384119 Jack Wed, 10 Mar 2010 17:16:27 +0000 http://mgeisler.net/2006/11/24/my-dell-3007wfp-is-here/#comment-384119 <p>Congrats on the new computer. Looks awesome. I am in bad need of an upgrade myself!</p> Congrats on the new computer. Looks awesome. I am in bad need of an upgrade myself!

]]> Comment on E17 has been committed to CVS by Canonical Taps Enlightenment for Ubuntu ARM Devices | google android os blog http://mgeisler.net/2000/12/e17-has-been-committed-to-cvs/#comment-383602 Canonical Taps Enlightenment for Ubuntu ARM Devices | google android os blog Tue, 02 Mar 2010 09:21:42 +0000 http://mgeisler.net/2000/12/09/e17-has-been-committed-to-cvs/#comment-383602 <p>[...] (E17) release seems to be in a perpetual "just about ready to release" state. Started in December of 2000, the Enlightenment re-write is still only available from SVN and as unofficial packages from [...]</p> [...] (E17) release seems to be in a perpetual "just about ready to release" state. Started in December of 2000, the Enlightenment re-write is still only available from SVN and as unofficial packages from [...]

]]> Comment on My Dell 3007WFP is here! by Martin Geisler http://mgeisler.net/2006/11/my-dell-3007wfp-is-here/#comment-383432 Martin Geisler Sat, 27 Feb 2010 10:08:28 +0000 http://mgeisler.net/2006/11/24/my-dell-3007wfp-is-here/#comment-383432 <p>Jay: heh, I love the comment about the keyboard :-) You're spot on -- I think I payed $10 for it... I got it as a temporary keyboard after I broke my normal keyboard by pouring cola into it :-)</p> Jay: heh, I love the comment about the keyboard :-) You’re spot on — I think I payed $10 for it… I got it as a temporary keyboard after I broke my normal keyboard by pouring cola into it :-)

]]> Comment on My Dell 3007WFP is here! by Jay http://mgeisler.net/2006/11/my-dell-3007wfp-is-here/#comment-383386 Jay Fri, 26 Feb 2010 17:27:09 +0000 http://mgeisler.net/2006/11/24/my-dell-3007wfp-is-here/#comment-383386 <p>I love the pic. You've got one of THE BEST, most Luxurious monitors on the market, the real "no expenses spared" deal. Then you've got it paired with a little crappy standard white keyboard that you probably got free somewhere, ROFL. That's like wearing a tuxedo while picking up your supermodel girlfriend, then getting on a rusty bicycle to go to dinner.</p> <p>And don't worry, I'm not laughing at you, but with you. Thanks for the article BTW, I'm about to get this monitor here and I'm very excited.</p> I love the pic. You’ve got one of THE BEST, most Luxurious monitors on the market, the real “no expenses spared” deal. Then you’ve got it paired with a little crappy standard white keyboard that you probably got free somewhere, ROFL. That’s like wearing a tuxedo while picking up your supermodel girlfriend, then getting on a rusty bicycle to go to dinner.

And don’t worry, I’m not laughing at you, but with you. Thanks for the article BTW, I’m about to get this monitor here and I’m very excited.

]]> Comment on Switching to the Z shell by John http://mgeisler.net/2001/08/switching-to-the-z-shell/#comment-383045 John Fri, 19 Feb 2010 18:08:10 +0000 http://mgeisler.net/2001/08/19/switching-to-the-z-shell/#comment-383045 <p>How is the Z shell working? Still using it?</p> How is the Z shell working? Still using it?

]]> Comment on Martin Geisler by Yanbo http://mgeisler.net/martin-geisler/#comment-383011 Yanbo Fri, 19 Feb 2010 00:44:13 +0000 http://mgeisler.net/martin-geisler/#comment-383011 <p>Hello Martin, fortunately I have found your blog. I've tested your PEL project and tried to use it in my project.</p> <p>But when I create a new PelJpeg object, I get a PHP warning: Warning: unixtojd() expects parameter 1 to be long, string given in PelEntryAscii.php on line 313, and an other one, Deprecated: Function split() is deprecated in PelEntryAscii.php on line 320.</p> <p>I don't know how to solve this problem, could you help me please. Thanks alot.</p> Hello Martin, fortunately I have found your blog. I’ve tested your PEL project and tried to use it in my project.

But when I create a new PelJpeg object, I get a PHP warning: Warning: unixtojd() expects parameter 1 to be long, string given in PelEntryAscii.php on line 313, and an other one, Deprecated: Function split() is deprecated in PelEntryAscii.php on line 320.

I don’t know how to solve this problem, could you help me please. Thanks alot.

]]> Comment on The Gladiator by intissar http://mgeisler.net/2000/06/the-gladiator/#comment-382970 intissar Wed, 17 Feb 2010 18:06:13 +0000 http://mgeisler.net/2000/06/28/the-gladiator/#comment-382970 <p>the photos it's very good adn i crazy about it</p> the photos it’s very good adn i crazy about it

]]> Comment on The Gladiator by swatkhaoula http://mgeisler.net/2000/06/the-gladiator/#comment-382659 swatkhaoula Sat, 06 Feb 2010 13:23:46 +0000 http://mgeisler.net/2000/06/28/the-gladiator/#comment-382659 <p>hi gladiator is the best</p> hi gladiator is the best

]]> Comment on Global variables in WordPress by John Wells http://mgeisler.net/2005/05/global-variables-in-wordpress/#comment-382484 John Wells Mon, 01 Feb 2010 02:30:04 +0000 http://mgeisler.net/2005/05/24/global-variables-in-wordpress/#comment-382484 <p>This has been the biggest problem I have faced in writing the WP-United integration. When embedding multiple pieces of software, I naturally want to write OO, or at least, compartmentalised code, but WordPress relies too much on variables being in the global scope.</p> <p>As it is now, I end up having to use a painful combination of globalising long lists of variables, and preparing all code paths in functions and class members, but eval()ing it in the global scope.</p> <p>There are still some instances where I really do have to run the code in a function scope -- it is just too swkward to bend the code into the global scope, but despite tracking WordPress' globals with each iteration, it turns out that the majority of plugins are written assuming that they themselves are in the global scope.</p> <p>Then you have to clean up the mess they make afterwards.</p> <p>The problem is that none of this can be undone -- with tens of thousands of plugins and themes all working on the assumption that they are in the global scope, nothing will ever be able to wrap WordPress 100% cleanly and reliably.</p> <p>WordPress in general has excellent, clean and easy to follow code, but this was a decision that has sent them down the wrong path. Forcing all plugins and themes into a function scope, while more painful initially, would have completely removed all of these issues.</p> <p>Right now I have even resorted to "compiling" plugins -- parsing the files before they are executed, grepping all the "global xxx" definitions, and proactively making them global before they are defined. Huge pain, but necessary if I want wordpress to run at specific points in a third-party application -- e.g. during user authentication.</p> This has been the biggest problem I have faced in writing the WP-United integration. When embedding multiple pieces of software, I naturally want to write OO, or at least, compartmentalised code, but WordPress relies too much on variables being in the global scope.

As it is now, I end up having to use a painful combination of globalising long lists of variables, and preparing all code paths in functions and class members, but eval()ing it in the global scope.

There are still some instances where I really do have to run the code in a function scope — it is just too swkward to bend the code into the global scope, but despite tracking WordPress’ globals with each iteration, it turns out that the majority of plugins are written assuming that they themselves are in the global scope.

Then you have to clean up the mess they make afterwards.

The problem is that none of this can be undone — with tens of thousands of plugins and themes all working on the assumption that they are in the global scope, nothing will ever be able to wrap WordPress 100% cleanly and reliably.

WordPress in general has excellent, clean and easy to follow code, but this was a decision that has sent them down the wrong path. Forcing all plugins and themes into a function scope, while more painful initially, would have completely removed all of these issues.

Right now I have even resorted to “compiling” plugins — parsing the files before they are executed, grepping all the “global xxx” definitions, and proactively making them global before they are defined. Huge pain, but necessary if I want wordpress to run at specific points in a third-party application — e.g. during user authentication.

]]> Comment on The LaTeX Font Catalogue by Dave http://mgeisler.net/2006/01/the-latex-font-catalogue/#comment-382328 Dave Wed, 27 Jan 2010 16:50:41 +0000 http://mgeisler.net/the-latex-font-catalogue/#comment-382328 <p>Wow thats facinating stuff!</p> Wow thats facinating stuff!

]]>