<?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>RichNetApps &#187; CSS/Ajax</title> <atom:link href="http://www.richnetapps.com/category/web/feed/" rel="self" type="application/rss+xml" /><link>http://www.richnetapps.com</link> <description>Internet Applications - Flash, Flex, Silverlight, JavaFX</description> <lastBuildDate>Fri, 09 Jul 2010 07:34:47 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0</generator> <item><title>The (sad) state of web fonts embedding</title><link>http://www.richnetapps.com/web-fonts-embedding/</link> <comments>http://www.richnetapps.com/web-fonts-embedding/#comments</comments> <pubDate>Mon, 04 Jan 2010 17:13:42 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[News]]></category> <category><![CDATA[css]]></category> <category><![CDATA[cufon]]></category> <category><![CDATA[embedding]]></category> <category><![CDATA[flash]]></category> <category><![CDATA[fonts]]></category> <category><![CDATA[typography]]></category><guid isPermaLink="false">http://www.richnetapps.com/?p=521</guid> <description><![CDATA[In case you think embedding fonts in web pages is something new, I made the first font embedding experiments in browsers in 1998. It was working - cross-browser too: Internet Explorer 4 and Netscape Navigator 4. See, EOT from Microsoft is quite old (introduced in 1996) and Netscape had their own format, called .pfr, based on the TrueDoc technology developed by Bitstream. So how comes that more than a decade later we still don't have a fully working way of using custom fonts on the web?]]></description> <wfw:commentRss>http://www.richnetapps.com/web-fonts-embedding/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Javascript animated collapsible panels without any frameworks</title><link>http://www.richnetapps.com/javascript-animated-collapsible-panels-without-frameworks/</link> <comments>http://www.richnetapps.com/javascript-animated-collapsible-panels-without-frameworks/#comments</comments> <pubDate>Mon, 13 Apr 2009 08:13:22 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[ajax]]></category> <category><![CDATA[animation]]></category> <category><![CDATA[code]]></category> <category><![CDATA[css]]></category> <category><![CDATA[download]]></category> <category><![CDATA[javascript]]></category> <category><![CDATA[tutorial]]></category><guid isPermaLink="false">http://www.richnetapps.com/?p=389</guid> <description><![CDATA[If you need to make collapsible panels that remember their state, but don't want to use any javascript framework, this tutorial will help you do this with no headaches - and you'll learn some neat javascript tricks too!]]></description> <wfw:commentRss>http://www.richnetapps.com/javascript-animated-collapsible-panels-without-frameworks/feed/</wfw:commentRss> <slash:comments>29</slash:comments> </item> <item><title>Google, Deep Web and GET vs. POST</title><link>http://www.richnetapps.com/google-deep-web-get-vs-post/</link> <comments>http://www.richnetapps.com/google-deep-web-get-vs-post/#comments</comments> <pubDate>Thu, 17 Apr 2008 16:39:35 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[google]]></category><guid isPermaLink="false"></guid> <description><![CDATA[I just read on Google&#8217;s official Webmaster blog that they&#8217;ve started experimenting with more advanced crawling to help them index pages inaccessible via links. Their crawler is actually filling and submitting forms from the site and check the results. From the blog: Specifically, when we encounter a &#60;FORM&#62; element on a high-quality site, we might [...]]]></description> <wfw:commentRss>http://www.richnetapps.com/google-deep-web-get-vs-post/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Using javascript expressions in CSS</title><link>http://www.richnetapps.com/using_javascript_expressions_in_css/</link> <comments>http://www.richnetapps.com/using_javascript_expressions_in_css/#comments</comments> <pubDate>Mon, 30 Oct 2006 18:11:11 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[css]]></category> <category><![CDATA[internet explorer]]></category> <category><![CDATA[javascript]]></category><guid isPermaLink="false"></guid> <description><![CDATA[I usually prefer a fixed layout for pages, because this allows for more control over typography, readability and so on. Still, one of biggest clients specifically required two years ago their site to be built with a liquid layout that expands full-width; the whole site (about 2000 html and aspx pages) was eventually done this [...]]]></description> <wfw:commentRss>http://www.richnetapps.com/using_javascript_expressions_in_css/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Viewing XSL transformation result in IE</title><link>http://www.richnetapps.com/viewing_xsl_transformation_result_in_ie/</link> <comments>http://www.richnetapps.com/viewing_xsl_transformation_result_in_ie/#comments</comments> <pubDate>Fri, 13 Oct 2006 18:13:56 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[xml]]></category> <category><![CDATA[xslt]]></category><guid isPermaLink="false"></guid> <description><![CDATA[If you've ever used XML+XSLT in your browser, you know that using View Source presents you with the original XML file, not the HTML that you might have expected; this makes debugging XSL transformations somewhat difficult.]]></description> <wfw:commentRss>http://www.richnetapps.com/viewing_xsl_transformation_result_in_ie/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Automatically highlight current page in menu via Javascript</title><link>http://www.richnetapps.com/automatically_highlight_current_page_in/</link> <comments>http://www.richnetapps.com/automatically_highlight_current_page_in/#comments</comments> <pubDate>Wed, 14 Dec 2005 18:35:11 +0000</pubDate> <dc:creator>Armand Niculescu</dc:creator> <category><![CDATA[CSS/Ajax]]></category> <category><![CDATA[ajax]]></category> <category><![CDATA[css]]></category> <category><![CDATA[html]]></category> <category><![CDATA[javascript]]></category><guid isPermaLink="false"></guid> <description><![CDATA[Whenever one builds a website, one issue is always guaranteed time consuming: highlighting the current page or section in the website with a different style. In theory, this is relatively simple, just add a .current class to the link in question. So, if you have a menu styled from a list, you&#8217;d have: &#60;ul&#62; &#60;li&#62;&#60;a [...]]]></description> <wfw:commentRss>http://www.richnetapps.com/automatically_highlight_current_page_in/feed/</wfw:commentRss> <slash:comments>55</slash:comments> </item> </channel> </rss>
<!-- Served from: www.richnetapps.com @ 2010-07-30 09:54:56 by W3 Total Cache -->