<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title>New RIFERS blogs entries from Maarten Stolte in category programming</title>
		<link>http://rifers.org/blogs</link>
		<description>The feeds of the Rifers community blogs</description>
		<language>en</language>
		<copyright>Copyright of the content contained is attributed to the original authors</copyright>
		<pubDate>Sun, 20 Jul 2008 04:32:48 +0200</pubDate>
		<managingEditor>Rifers Blogs: https://rifers.org/blogs</managingEditor>
		
			<item>
				<title>YUI 2.4 released</title>
				<link>http://rifers.org/blogs/datadevil/2007/12/6/yui_2_4_released</link>
				<description>The YUI library from Yahoo sees another big release in its 2.4 release. &lt;br /&gt;
I&apos;m looking forward to implementing this one on our sites. We have been using the calendar widget quite alot on our backend systems (building confference administration system requires quite alot of date entry stuff), but we have also implemented other parts.&lt;br /&gt;
I&apos;m happy that the calendar widget now has a year selector, which was something that was making entering a date like 20/5/1976  hard; you&apos;d have to click through 12*31something months...&lt;br /&gt;
For those who don&apos;t know YUI, or haven&apos;t looked at it, do it. The documentation of the YUI libraries is great; good api docs, nice cheatsheet pdfs and great videos with experts from Yahoo but also from outside Yahoo, like Peter Paul Koch (PPK).&lt;br /&gt;
</description>
				<pubDate>Thu, 06 Dec 2007 21:13:32 +0100</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2007/12/6/yui_2_4_released</guid>
			</item>
		
			<item>
				<title>Lol</title>
				<link>http://rifers.org/blogs/datadevil/2006/10/28/lol</link>
				<description>&amp;quot;Love JavaScript? Now you can write desktop apps, widgets, and web pages all using the same platform.&amp;quot; ..that made me giggle &lt;img src=&quot;http://rifers.org/images/blog/emoticon-nose.gif&quot; width=&quot;16&quot; height=&quot;16&quot; alt=&quot;:-)&quot; /&gt;&lt;br /&gt;
On the serious side, &lt;a href=&quot;http://ajaxian.com/archives/adobe-apollo-at-max&quot; target=&quot;_blank&quot;&gt;http://ajaxian.com/archives/adobe-apollo-at-max&lt;/a&gt; sounds like fun, wonder if I can write nice apps with RIFE and OpenLaszlo..</description>
				<pubDate>Sat, 28 Oct 2006 20:14:14 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2006/10/28/lol</guid>
			</item>
		
			<item>
				<title>Free AJAX course online</title>
				<link>http://rifers.org/blogs/datadevil/2006/8/16/ajax_course_online</link>
				<description>I don&apos;t want to bury Geerts&apos; facebook news (&lt;a href=&quot;http://rifers.org/blogs/gbevin/2006/8/16/facebook_uses_rife&quot; target=&quot;_blank&quot;&gt;http://rifers.org/blogs/gbevin/2006/8/16/facebook_uses_rife&lt;/a&gt;), but I found this nice AJAX course on &lt;a href=&quot;http://www.javapassion.com/ajaxcodecamp/.&quot; target=&quot;_blank&quot;&gt;http://www.javapassion.com/ajaxcodecamp/.&lt;/a&gt; I still have to start with the first lesson, but a quick glance shows that its quite well done, and I&apos;d take it if only for learning more about Firebug&apos;s Javascript debugging capabilities.</description>
				<pubDate>Wed, 16 Aug 2006 16:15:59 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2006/8/16/ajax_course_online</guid>
			</item>
		
			<item>
				<title>Simple small things to improve</title>
				<link>http://rifers.org/blogs/datadevil/2006/6/4/simple_small_things_to_improve</link>
				<description>When a website is a big as e.g. blogspot.com, you&apos;d expect them to at least have nailed the nitty gritty interface details. When I commented on the blog I linked to in the last post, I found these small things which made me wonder why people can&apos;t &apos;put the dot on the i&apos; (pay attention to the last little details) as we say in dutch.&lt;br /&gt;
The small details I&apos;m talking about are:
&lt;ol&gt;
&lt;li&gt;When there is 1 (one) comment, they say &apos;1 comments&apos;. This might be faster to execute (no code needed), but if that&apos;s really the reason I would be very much surprised :-)&lt;/li&gt;
&lt;li&gt;If you comment on a story and choose &apos;anonymous&apos;, the submit button is still called &apos;Login and Publish&apos;, which was a bit confusing to me. A little Javascript is not too much to ask here is it, and otherwise a different title for the button maybe..&lt;/li&gt;
&lt;/ol&gt;
I told you these were little details, but thats where the devil is ;-)</description>
				<pubDate>Sun, 04 Jun 2006 17:50:06 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2006/6/4/simple_small_things_to_improve</guid>
			</item>
		
			<item>
				<title>Setting the docroot in PHP Eclipse</title>
				<link>http://rifers.org/blogs/datadevil/2006/5/29/setting_the_docroot_in_php_ecli</link>
				<description>&lt;p&gt;
This is not a RIFE post perse, but since my dayjob is working with PHP, and since I could not easily find this information elsewhere, I figured I&apos;d write a bit about it.&lt;/p&gt;
&lt;p&gt;
I had looked at using Eclipse as my php IDE before, but the problem seemed to be that Eclipse wanted everything to be in its workspace/project directory structure, whereas I like to have my php documents in my DocumentRoot directory.&lt;br /&gt;
The workaround I found before was to symlink from the Eclipse project directory to the docroot, but that seems like an ugly hack, and working on Windows one would have to work with the not so well documented &apos;junction&apos; feature of window nt..&lt;/p&gt;
&lt;p&gt;
When I was browsing the EasyEclipse.org site I happened to find &lt;a href=&quot;http://sourceforge.net/forum/message.php?msg_id=3727086&quot;&gt;this post &lt;/a&gt;that explains how to set up the structure. Because it is a bit lacking in its explanation, I give you a more complete explanation, where I assume you have installed &lt;a href=&quot;http://www.easyeclipse.org/site/home/&quot;&gt;EasyEclipse&lt;/a&gt; &apos; LAMP distribution. Any other Eclipse + phpEclipse ought to work as well.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Start Eclipse, and create a new PHP project, with a name of your choosing&lt;/li&gt;
&lt;li&gt;uncheck the &apos;project contents&apos; box, and then fill in the path to your php files (not the docroot perse,e.g. /www/htdocs might not be it, cause you also need files from /www/settings, in this case you&apos;d fill in /www)&lt;/li&gt;
&lt;li&gt;click &apos;finish&apos;&lt;/li&gt;

&lt;li&gt;now rightclick on the project folder in the navigation pane on the left, and choose properties.&lt;/li&gt;
&lt;li&gt;Choose PHP Project settings on the left, and click &apos;use project settings&apos;. Fill in the URL to your local site and  the docroot (/www/htdocs in my example) . Add the Include path(s) &lt;/li&gt;
&lt;li&gt;Now click on the PHP Parser link on the left in this same window, and choose &apos;use project settings&apos;, so that the PHP Parser will know to use your projects&apos; specific settings.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
Now click OK and you&apos;re done with this part.
&lt;/p&gt;
&lt;p&gt;
EasyEclipse also comes with CVS/SVN and DB tools, which a typical LAMP setup probably also uses, but setting those up are something I leave up to you.&lt;/p&gt;
</description>
				<pubDate>Mon, 29 May 2006 15:06:42 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2006/5/29/setting_the_docroot_in_php_ecli</guid>
			</item>
		
			<item>
				<title>Java licensing issues part 937</title>
				<link>http://rifers.org/blogs/datadevil/2006/3/31/java_licensing_issues_part_937</link>
				<description>I have to agree with &lt;a href=&quot;http://www.0xdeadbeef.com/weblog/?p=190&quot;&gt;this post&lt;/a&gt; on nearly all accounts, apart from the LAMP stack one. With frameworks as RIFE and other ones that are attempting to simplify Java, it might have happened if they were around back when PHP was moving in for the P in LAMP, but Java back then was just too inaccesible for the public that PHP attracted. 
The other arguments are pretty good imho, especially the one about people choosing Java over Javascript if that had been possible, and the one about Mono... If Java had been opener, I&apos;m pretty sure folks would have chosen Java over Mono to do developement, maybe extending Java with some of the features that mono/.net folks say make that a better choice.</description>
				<pubDate>Fri, 31 Mar 2006 08:42:49 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2006/3/31/java_licensing_issues_part_937</guid>
			</item>
		
			<item>
				<title>Daily WTF</title>
				<link>http://rifers.org/blogs/datadevil/2005/7/22/daily_wtf</link>
				<description>I found this site with awful programming examples, some really make you feel ashamed of your fellow technology workers, and the thought of them probably being high paid &apos;professionals&apos; quite often makes it only more depressing; &lt;a href=&quot;http://www.thedailywtf.com/&quot; target=&quot;_blank&quot;&gt;http://www.thedailywtf.com/&lt;/a&gt; .&lt;br /&gt;
</description>
				<pubDate>Fri, 22 Jul 2005 14:11:11 +0200</pubDate>
				<author>Maarten Stolte</author>
				<guid>http://rifers.org/blogs/datadevil/2005/7/22/daily_wtf</guid>
			</item>
		
		
	</channel>
</rss>