<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Neyric.com &#187; yui</title>
	<atom:link href="http://neyric.com/tag/yui/feed/" rel="self" type="application/rss+xml" />
	<link>http://neyric.com</link>
	<description>projects, programming, blogging...</description>
	<lastBuildDate>Sat, 29 Jan 2011 19:51:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>inputEx 0.7.0 release and Roadmap</title>
		<link>http://neyric.com/2011/01/07/inputex-0-7-0-release-and-roadmap/</link>
		<comments>http://neyric.com/2011/01/07/inputex-0-7-0-release-and-roadmap/#comments</comments>
		<pubDate>Fri, 07 Jan 2011 11:00:55 +0000</pubDate>
		<dc:creator>neyric</dc:creator>
				<category><![CDATA[inputEx]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[YUI Library]]></category>
		<category><![CDATA[yui]]></category>
		<category><![CDATA[yui3]]></category>

		<guid isPermaLink="false">http://neyric.com/?p=206</guid>
		<description><![CDATA[inputEx 0.7.0 was released today ! Most importantly, we upgraded YUI dependency to version 2.8.2r1 to fix security issues, and fixed a major bug for Internet Explorer 9. We also worked on setting correct names for all sub-fields in order &#8230; <a href="http://neyric.com/2011/01/07/inputex-0-7-0-release-and-roadmap/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p><img class="alignnone" title="inputEx" src="http://neyric.github.com/inputex.jpg" alt="" width="120" height="90" /></p>
<p>inputEx 0.7.0 was released today !</p>
<p>Most importantly, we upgraded YUI dependency to version <a href="http://www.yuiblog.com/blog/2010/10/25/yui-2-8-2-security-update/">2.8.2r1 to fix security issues</a>, and fixed a major bug for Internet Explorer 9.</p>
<p>We also worked on setting correct names for all sub-fields in order to use classical browser form posting. You can now safely use <em>Group</em> and <em>List</em> fields using standard forms.</p>
<p>Finally, I merged all the various Wiki pages we had into the <a href="http://neyric.github.com/inputex/guide.html">new inputEx Guide</a>. Obviously far from being complete, this first version will help us replying to questions from the forum, and hopefully help newcomers.</p>
<p>You can take a look at the complete <a href="http://neyric.github.com/inputex/version.txt">changeset here</a>, and d<a href="http://cloud.github.com/downloads/neyric/inputex/inputex-0.7.0.zip">ownload the 0.7.0 version here</a>.</p>
<p><strong>inputEx Roadmap</strong></p>
<p>Now, where are we going ?</p>
<p>With the upcoming YUI 3.3.0 release, it is now time to seriously work on upgrading inputEx to YUI3.</p>
<p>Of course, this is not a new idea, and we&#8217;ve already tried to <a href="http://xkcd.com/844/">start the project over</a>, leveraging the YUI 3 widget infrastructure. However, this appeared to be a huge amount of work, while throwing away most of the current code.</p>
<p>Facing our failure, we&#8217;ve decided to take a smaller step to get there, so we&#8217;ll start by forking the current version to make it work with YUI3, using <a href="http://developer.yahoo.com/yui/3/examples/yui/yui-compat.html">yui2in3</a> for widgets dependencies, while keeping code changes to the strict minimum.</p>
<p>Once this version is out, we&#8217;ll be able to continue with the following goals in mind :</p>
<ul>
<li>remove unrelated code from the library (yql-related stuff, JsonTreeInspector, &#8230;)</li>
<li>removing YUI2 dependencies while widgets get integrated into YUI3</li>
<li>make inputEx available on the YUI gallery (and leverage Yahoo! CDN )</li>
<li>finally use the YUI Widget framework</li>
</ul>
<p>You will be able to follow the progress of the inputEx-yui3 branch on <a href="https://github.com/neyric/inputex/network">https://github.com/neyric/inputex/network</a>.</p>
<p>Happy new year !</p>
<div class="shr-publisher-206"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://neyric.com/2011/01/07/inputex-0-7-0-release-and-roadmap/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>inputEx version 0.1.0 released</title>
		<link>http://neyric.com/2008/05/07/inputex-010-released/</link>
		<comments>http://neyric.com/2008/05/07/inputex-010-released/#comments</comments>
		<pubDate>Wed, 07 May 2008 13:12:48 +0000</pubDate>
		<dc:creator>neyric</dc:creator>
				<category><![CDATA[inputEx]]></category>
		<category><![CDATA[YUI Library]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[yui]]></category>

		<guid isPermaLink="false">http://javascript.neyric.com/blog/?p=70</guid>
		<description><![CDATA[It&#8217;s finally time ! I just finished the first public version of inputEx. I had this project in my bag since summer 2007. Visit the website at http://javascript.neyric.com/inputex . Here is a short introduction from the documentation : Introduction inputEx &#8230; <a href="http://neyric.com/2008/05/07/inputex-010-released/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p><strong>It&#8217;s finally time !</strong></p>
<p>I just finished the first public version of inputEx. I had this project in my bag since summer 2007.</p>
<p>Visit the website at <a title="inputEx javascript library" href="http://javascript.neyric.com/inputex">http://javascript.neyric.com/inputex</a> . Here is a short introduction from the documentation :</p>
<blockquote>
<h2>Introduction</h2>
<p><a href="../..">inputEx</a> is a javascript library to <strong>build fields and forms</strong>.<br />
It can also be considered as an interface framework, since it provides a good structure to <a href="create_field.html">create you own fields</a>.</p>
<p>It is built on top of the <a href="http://developer.yahoo.com/yui/">YUI library</a>, and we tried to be as close as possible to the YUI philosophy.</p>
<p>It is of course fully skinable using CSS and currently supports Firefox 1.5+, Safari 2.0+, IE 7.0 and Opera 9+.</p>
<h2>A unique field library</h2>
<p>With so many form libraries out there, why would we create another one ?</p>
<ul>
<li>HTML fields/forms are <strong>very</strong> limited</li>
<li>no existing good input library for YUI (let me know if I&#8217;m wrong !), except YUI widgets</li>
<li>it&#8217;s not all about validation !</li>
</ul>
<p>Here are the features we implemented that makes inputEx unique :</p>
<ul>
<li><strong>json configuration</strong> for each field</li>
<li><strong>complex data structures</strong> (list/objects/tree/list of urls/objects of objects etc&#8230;)</li>
<li><strong>composition</strong> between the fields (for &#8220;meta&#8221;-fields such as InPlaceEdit,List,Tree,Pair,&#8230;)</li>
<li><strong>javascript object mapping</strong> for greater interactivity</li>
<li>a <strong>common &#8220;updated&#8221; event</strong> to handle different browsers and different field interactions</li>
</ul>
<h2>No HTML ?</h2>
<p>InputEx uses <strong>no html</strong> (it is the opposite of unobtrusive librairies): all the fields and forms are configured <strong>using <a href="http://json.org/">json</a></strong>, then rendered by <a href="dom_helpers.html">manipulating the DOM</a>.<br />
It is therefore a library to create <strong>javascript web applications, not webpages</strong>.</p>
<p>This approach has a great advantage: adding/modifying a field is made in <strong>one place only</strong>. Combined with<br />
the json configuration that can be stored server-side, it makes customization of your web application very easy.</p>
<h2>Help Us</h2>
<p>It is very easy to help us improving the library :</p>
<ul>
<li><strong>Extend the library</strong>: send your custom fields to the <a href="http://code.google.com/p/inputex/w/list" target="_new">wiki</a>, it might help others !</li>
<li><strong>Give your feedback</strong> on the <a href="http://groups.google.com/group/inputex/" target="_new">forum</a></li>
<li><a href="http://code.google.com/p/inputex/issues/list">Report</a> any bug</li>
</ul>
<h2>Other resources</h2>
<p>If you didn&#8217;t find what you were looking for, please visit these websites :</p>
<ul>
<li><a href="http://javascript.neyric.com/inputex/doc/js_docs_out/examples.html">Examples</a> &#8211; many examples for each field</li>
<li><a href="http://groups.google.com/group/inputex/">Forum</a> &#8211; discussions about inputEx</li>
<li><a href="http://javascript.neyric.com/blog/category/inputex/">Blog</a> &#8211; inputEx news</li>
<li><a href="http://code.google.com/p/inputex/w/list">Wiki</a> &#8211; community ressources</li>
<li>Contact the author: <a href="mailto:inputex@neyric.com">inputex@neyric.com</a></li>
</ul>
</blockquote>
<div class="shr-publisher-70"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://neyric.com/2008/05/07/inputex-010-released/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>inputEx coming real soon</title>
		<link>http://neyric.com/2008/02/07/inputex-coming-real-soon/</link>
		<comments>http://neyric.com/2008/02/07/inputex-coming-real-soon/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 09:26:27 +0000</pubDate>
		<dc:creator>neyric</dc:creator>
				<category><![CDATA[inputEx]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[input]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[yui]]></category>

		<guid isPermaLink="false">http://javascript.neyric.com/blog/2008/02/07/inputex-coming-real-soon/</guid>
		<description><![CDATA[inputEx is an open-source javascript form library, built on top of the Yahoo! User Interface (YUI) Library. It is still under development and will be released real soon, under the MIT License. Another Form Library ? Why would I create &#8230; <a href="http://neyric.com/2008/02/07/inputex-coming-real-soon/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p>inputEx is an open-source javascript form library, built on top of the <a href="http://developer.yahoo.com/yui/">Yahoo! User Interface (YUI) Library</a>. It is still under development and will be released real soon, under the <a href="http://en.wikipedia.org/wiki/MIT_license">MIT License</a>.</p>
<p><strong>Another Form Library ? </strong></p>
<p>Why would I create another form library, when we already have so many of them ?</p>
<p>I really like the way the YUI Library is built and I wanted a form library to be very close to the YUI philosophy. I believe the YUI library is really missing something: it has a lot of useful widgets, but you have to integrate them yourself within your forms, over and over again&#8230;</p>
<p>Have you ever created a web application or website without any input field ?</p>
<p><strong>Unobtrusive ?</strong></p>
<p>No !  I want the opposite. I hate HTML (although I&#8217;m still writing HTML every day for 10 years&#8230;). With inputEx, you describe your forms using <a href="http://json.org/" target="_blank">json</a> !</p>
<p><strong>It&#8217;s not all about validation </strong></p>
<p>Validation has been the main milestone for many form libraries. inputEx aims to tackle other issues, such as:</p>
<ul>
<li>Form creation: each field will include its own configuration form. Thanks to a &#8220;type&#8221; field, we can then provide a form to create forms !</li>
</ul>
<ul>
<li>Extendability: form libraries always miss the field you need. A good form library should make it easy to create new fields easily. This pitfall has a unique solution: a good documentation !</li>
</ul>
<p>Please be patient ! <img src='http://neyric.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<div class="shr-publisher-69"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://neyric.com/2008/02/07/inputex-coming-real-soon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reporting javascript errors to the server</title>
		<link>http://neyric.com/2007/04/26/reporting-javascript-errors-to-the-server/</link>
		<comments>http://neyric.com/2007/04/26/reporting-javascript-errors-to-the-server/#comments</comments>
		<pubDate>Thu, 26 Apr 2007 13:12:13 +0000</pubDate>
		<dc:creator>neyric</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[yui]]></category>

		<guid isPermaLink="false">http://javascript.neyric.com/blog/?p=21</guid>
		<description><![CDATA[In every web application that intensivly uses javascript: errors may occur ! Since I&#8217;m not able to fully-test my web-application each time a modification is made, I decided to report javascript errors to the server. It proved to be very &#8230; <a href="http://neyric.com/2007/04/26/reporting-javascript-errors-to-the-server/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p>In every web application that intensivly uses javascript: errors may occur !<br />
Since I&#8217;m not able to fully-test my web-application each time a modification is made, I decided to report javascript<br />
errors to the server. It proved to be very useful to detect bugs very quickly.</p>
<p>Here&#8217;s an example on how to do so with <a href="http://developer.yahoo.com/yui/" target="_blank">YUI</a> :</p>
<pre>
window.onerror = function(msg, href, lineNo) {
  var postData = 'msg='+msg+'&amp;file='+href+'&amp;line='+
		lineNo+'&amp;infos='+navigator.userAgent;
 YAHOO.util.Connect.asyncRequest('POST', 'report_error.php',
              { success: function(o){}, failure: function(o){} }, postData);
}</pre>
<p>I just added &#8220;navigator.userAgent&#8221; to the parameters of window.onerror, so you know<br />
which browser generated the error.</p>
<div class="shr-publisher-128"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://neyric.com/2007/04/26/reporting-javascript-errors-to-the-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>YUI improved Ajax</title>
		<link>http://neyric.com/2006/10/14/yui-improved-ajax/</link>
		<comments>http://neyric.com/2006/10/14/yui-improved-ajax/#comments</comments>
		<pubDate>Sat, 14 Oct 2006 18:28:01 +0000</pubDate>
		<dc:creator>neyric</dc:creator>
				<category><![CDATA[YUI Library]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[yui]]></category>

		<guid isPermaLink="false">http://javascript.neyric.com/blog/?p=45</guid>
		<description><![CDATA[&#8220;The Yahoo! User Interface (YUI) Library is a set of utilities and controls, written in JavaScript, for building richly interactive web applications using techniques such as DOM scripting, DHTML and AJAX.&#8221; I found YUI very helpful for my applications. It&#8217;s &#8230; <a href="http://neyric.com/2006/10/14/yui-improved-ajax/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p><em>&#8220;The Yahoo! User Interface (YUI) Library is a set of utilities and controls, 		  written in JavaScript, for building richly interactive web applications 		  using techniques such as DOM scripting, DHTML and AJAX.&#8221;</em></p>
<p>I found <a href="http://developer.yahoo.com/yui/" target="_blank">YUI </a>very helpful for my applications. It&#8217;s not the most complete framework that exists (look at <a href="http://www.backbase.com/" target="_blank">BackBase</a> for example) but it is very promising. You can make new Components easily ( with YAHOO.util.Dom, YAHOO.util.Event ), ajaxified behaviour (with YAHOO.util.Connect.asyncRequest ) etc&#8230;<br />
I recommand two web sites :</p>
<ul>
<li><a href="http://developer.yahoo.com/yui/" target="_blank">YUI Home Page (examples, good documentation and downloads)<br />
</a></li>
<li><a href="http://www.jackslocum.com/yui/index.php" target="_blank">Jack Slocum&#8217;s Blog (<span class="blog-desc">Using the YUI library &#8211; Beyond the Examples)</span></a></li>
</ul>
<p>For WordPress users, you can even use YUI to for the <a href="http://www.jackslocum.com/yui/2006/10/09/my-wordpress-comments-system-built-with-yahoo-ui-and-yahooext/" target="_blank">comments system</a>.</p>
<div class="shr-publisher-119"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://neyric.com/2006/10/14/yui-improved-ajax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

