<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Designs Advice Tag: javascript</title>
<link>http://designsadvice.com/forums/</link>
<description>Designs Advice Tag: javascript</description>
<language>en</language>
<pubDate>Mon, 06 Sep 2010 16:13:53 +0000</pubDate>

<item>
<title>annebach on "mootools jquery spry or script.aculo.us"</title>
<link>http://designsadvice.com/forums/topic/mootools-jquery-spry-or-scriptaculous#post-206</link>
<pubDate>Wed, 09 Apr 2008 09:43:30 +0000</pubDate>
<dc:creator>annebach</dc:creator>
<guid isPermaLink="false">206@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;With both libraries functioning well, my own decision came down&#60;br /&#62;
to the fact that the jQuery team tends to take into consideration the thoughts and concerns of design/development communities who would like the major js libraries to function well TOGETHER if ever the need arise, while the developers of Mootools have a very pronounced leaning in favor of an exclusive/proprietary library.&#60;/p&#62;
&#60;p&#62;Since both function well, I feel it's clearly best to adopt the library that at least TRIES to play nice with others.&#60;/p&#62;
&#60;p&#62;I find that jQuery is a very community focused project while Mootools is a strictly Mootools focused project.
&#60;/p&#62;</description>
</item>
<item>
<title>2dcandy on "Modalbox user friendly popups and wizards"</title>
<link>http://designsadvice.com/forums/topic/modalbox-user-friendly-popups-and-wizards#post-130</link>
<pubDate>Sat, 16 Jun 2007 14:12:05 +0000</pubDate>
<dc:creator>2dcandy</dc:creator>
<guid isPermaLink="false">130@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;nice1 thanks
&#60;/p&#62;</description>
</item>
<item>
<title>idesign on "Modalbox user friendly popups and wizards"</title>
<link>http://designsadvice.com/forums/topic/modalbox-user-friendly-popups-and-wizards#post-129</link>
<pubDate>Fri, 15 Jun 2007 00:44:58 +0000</pubDate>
<dc:creator>idesign</dc:creator>
<guid isPermaLink="false">129@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;This might be a useful resource for some people.&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;ModalBox is a JavaScript technique for creating modern (Web 2.0-style) modal dialogs or even wizards (sequences of dialogs) without using conventional popups and page reloads. It's inspired by Mac OS X modal dialogs. And yes, it may also be useful for showing bigger versions of images. :)&#60;/p&#62;
&#60;p&#62;ModalBox is built with pure JavaScript and is based on Sam Stephenson's excellent Prototype JavaScript Framework, script.aculo.us and valid XHTML/CSS. ModalBox uses AJAX to load content.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;&#60;a href=&#34;http://wildbit.com/demos/modalbox/&#34; rel=&#34;nofollow&#34;&#62;http://wildbit.com/demos/modalbox/&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>drew on "mootools jquery spry or script.aculo.us"</title>
<link>http://designsadvice.com/forums/topic/mootools-jquery-spry-or-scriptaculous#post-94</link>
<pubDate>Tue, 29 May 2007 07:54:40 +0000</pubDate>
<dc:creator>drew</dc:creator>
<guid isPermaLink="false">94@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;Best thing you can do is experiment with both and even throw in some of the others (YUI, Dojo, Mochi) and see which style fits you best. The benefits of using one over the other are going to vary differently for different people and different projects.&#60;/p&#62;
&#60;p&#62;Once you play around with the different libraries out there. I believe you will find jQuery to be more oriented at making your life much easier when having to muck about with the DOM and your typical daily tasks as a web developer. Once you start to really dig into jQuery you will find that the code you write on top of jQuery is extremely small and packs a large punch.
&#60;/p&#62;</description>
</item>
<item>
<title>twofivethreetwo on "mootools jquery spry or script.aculo.us"</title>
<link>http://designsadvice.com/forums/topic/mootools-jquery-spry-or-scriptaculous#post-92</link>
<pubDate>Tue, 29 May 2007 01:16:32 +0000</pubDate>
<dc:creator>twofivethreetwo</dc:creator>
<guid isPermaLink="false">92@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;Just like most everything else it depends on you. You can search Google and find tons of people debating which is the best and each claim the one they use is the best. So, browse around all of them. Here is a discussion at 9rules about it as well; &#60;a href=&#34;http://9rules.com/programming/notes/2156/&#34; rel=&#34;nofollow&#34;&#62;http://9rules.com/programming/notes/2156/&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>idesign on "mootools jquery spry or script.aculo.us"</title>
<link>http://designsadvice.com/forums/topic/mootools-jquery-spry-or-scriptaculous#post-89</link>
<pubDate>Mon, 28 May 2007 17:47:53 +0000</pubDate>
<dc:creator>idesign</dc:creator>
<guid isPermaLink="false">89@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;What do you all think would be the best library to adopt? I guess the main use initially would be for effects and form verification.
&#60;/p&#62;</description>
</item>
<item>
<title>idesign on "Script.aculo.us Dom Builder className"</title>
<link>http://designsadvice.com/forums/topic/scriptaculous-dom-builder-classname#post-24</link>
<pubDate>Wed, 16 May 2007 19:57:31 +0000</pubDate>
<dc:creator>idesign</dc:creator>
<guid isPermaLink="false">24@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;heres a snippet of code&#60;br /&#62;
&#60;code&#62;&#60;br /&#62;
element = Builder.node('div',{id:'newProjPanel'+String(projNum),className:'projectPanelcss',style:'display:none;width:85%;margin:4px 0 4px 0;padding:5px;background-color:#EEE;position:relative;'},[&#60;br /&#62;
		Builder.node('a',{onclick:&#34;Effect.SlideUp('newProjPanel&#34;+String(projNum)+&#34;',{duration:0.5,afterFinish: deleteElements});&#34;,style:'z-index:'+String(projNum+1)+';position:absolute;top:0;right:0;'},[&#60;br /&#62;
			Builder.node('img',{src:'images/delete.gif'})&#60;br /&#62;
		])]);&#60;br /&#62;
&#60;/code&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>idesign on "Script.aculo.us Dom Builder className"</title>
<link>http://designsadvice.com/forums/topic/scriptaculous-dom-builder-classname#post-23</link>
<pubDate>Wed, 16 May 2007 19:56:51 +0000</pubDate>
<dc:creator>idesign</dc:creator>
<guid isPermaLink="false">23@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;Yeah, it's not getting applied. I don't know why. Rackn' my brain. I'll try looking into it tomorrow I guess.
&#60;/p&#62;</description>
</item>
<item>
<title>blackstudio on "Script.aculo.us Dom Builder className"</title>
<link>http://designsadvice.com/forums/topic/scriptaculous-dom-builder-classname#post-22</link>
<pubDate>Wed, 16 May 2007 19:56:30 +0000</pubDate>
<dc:creator>blackstudio</dc:creator>
<guid isPermaLink="false">22@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;Yes the css styles should be getting applied to those elements. I haven't used the Dom builder before, but I have dynamicaly created html elements using javascript and the styles are always applied.
&#60;/p&#62;</description>
</item>
<item>
<title>idesign on "Script.aculo.us Dom Builder className"</title>
<link>http://designsadvice.com/forums/topic/scriptaculous-dom-builder-classname#post-21</link>
<pubDate>Wed, 16 May 2007 19:55:39 +0000</pubDate>
<dc:creator>idesign</dc:creator>
<guid isPermaLink="false">21@http://designsadvice.com/forums/</guid>
<description>&#60;p&#62;Anyone use Script.aculo.us Dom Builder before. I'm having problems with the className attribute. It's supposed to assign a class to the element you are creating with the Dom builder, which it does (FireFox's dom inspector proves it). But the css style with that class name does not get applied. Do css styles get applied to dynamically created elements?
&#60;/p&#62;</description>
</item>

</channel>
</rss>
