<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>gimme Work Item Rss Feed</title><link>http://www.codeplex.com/gimme/WorkItem/List.aspx</link><description>gimme Work Item Rss Description</description><item><title>CLOSED ISSUE: Gimme.query is broken</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=9012</link><description>Most recent checkin to fix an issue with Safari2 broken the CSS Querying Engine for other browsers&lt;br /&gt;Comments: Fixed with changset #14359</description><author>sstchur</author><pubDate>Wed, 05 Dec 2007 21:15:19 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Gimme.query is broken 20071205091519P</guid></item><item><title>CREATED ISSUE: Gimme.query is broken</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=9012</link><description>Most recent checkin to fix an issue with Safari2 broken the CSS Querying Engine for other browsers&lt;br /&gt;</description><author>sstchur</author><pubDate>Wed, 05 Dec 2007 21:03:24 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Gimme.query is broken 20071205090324P</guid></item><item><title>CLOSED ISSUE: Gimme.query is slow and should be optimized</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=6153</link><description>Gimme.query is often slow when retrieving elements on a page with a large and complicated DOM structure.  This is because Gimme blindly queries backwards and doesn&amp;#39;t bother to trim the tree at all.&lt;br /&gt;&lt;br /&gt;Ex&amp;#58;  &amp;#35;a &amp;#35;b .dog&lt;br /&gt;&lt;br /&gt;If there is only one .dog element, Gimme will still check all elements on the page, because it works backwards&amp;#58; first, retrieving all elements and weeding out those that do not have the class .dog&amp;#59; then walking the ancestry chain to ensure that those that do have the class .dog have ancestors &amp;#35;b and &amp;#35;a.&lt;br /&gt;&lt;br /&gt;This could be made much more efficient by first ensuring that &amp;#35;b and &amp;#35;a exist in the DOM.  If not, no need to progress further.  If so, we can trim the tree by only retrieving the descendants of &amp;#35;b and making sure than they have the class .dog &amp;#40;as opposed to checking all elements&amp;#41;.&lt;br /&gt;Comments: Resolved</description><author>sstchur</author><pubDate>Tue, 16 Oct 2007 20:54:30 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Gimme.query is slow and should be optimized 20071016085430P</guid></item><item><title>COMMENTED ISSUE: Gimme.query is slow and should be optimized</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=6153</link><description>Gimme.query is often slow when retrieving elements on a page with a large and complicated DOM structure.  This is because Gimme blindly queries backwards and doesn&amp;#39;t bother to trim the tree at all.&lt;br /&gt;&lt;br /&gt;Ex&amp;#58;  &amp;#35;a &amp;#35;b .dog&lt;br /&gt;&lt;br /&gt;If there is only one .dog element, Gimme will still check all elements on the page, because it works backwards&amp;#58; first, retrieving all elements and weeding out those that do not have the class .dog&amp;#59; then walking the ancestry chain to ensure that those that do have the class .dog have ancestors &amp;#35;b and &amp;#35;a.&lt;br /&gt;&lt;br /&gt;This could be made much more efficient by first ensuring that &amp;#35;b and &amp;#35;a exist in the DOM.  If not, no need to progress further.  If so, we can trim the tree by only retrieving the descendants of &amp;#35;b and making sure than they have the class .dog &amp;#40;as opposed to checking all elements&amp;#41;.&lt;br /&gt;Comments: ** Comment from web user: sstchur ** &lt;p&gt;Resolved in Caspian &amp;#40;v1.5&amp;#41;&lt;/p&gt;</description><author>sstchur</author><pubDate>Tue, 16 Oct 2007 20:54:22 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: Gimme.query is slow and should be optimized 20071016085422P</guid></item><item><title>CREATED ISSUE: Gimme.query is slow and should be optimized</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=6153</link><description>Gimme.query is often slow when retrieving elements on a page with a large and complicated DOM structure.  This is because Gimme blindly queries backwards and doesn&amp;#39;t bother to trim the tree at all.&lt;br /&gt;&lt;br /&gt;Ex&amp;#58;  &amp;#35;a &amp;#35;b .dog&lt;br /&gt;&lt;br /&gt;If there is only one .dog element, Gimme will still check all elements on the page, because it works backwards&amp;#58; first, retrieving all elements and weeding out those that do not have the class .dog&amp;#59; then walking the ancestry chain to ensure that those that do have the class .dog have ancestors &amp;#35;b and &amp;#35;a.&lt;br /&gt;&lt;br /&gt;This could be made much more efficient by first ensuring that &amp;#35;b and &amp;#35;a exist in the DOM.  If not, no need to progress further.  If so, we can trim the tree by only retrieving the descendants of &amp;#35;b and making sure than they have the class .dog &amp;#40;as opposed to checking all elements&amp;#41;.&lt;br/&gt;</description><author>sstchur</author><pubDate>Thu, 06 Sep 2007 18:03:30 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Gimme.query is slow and should be optimized 20070906060330P</guid></item><item><title>CREATED ISSUE: .getScreenPosition and .getPagePosition could be better</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=6152</link><description>The two functions&amp;#58; .getScreenPosition and .getPagePosition might be able to be improved by using some proprietary methods from IE and Mozilla.&lt;br /&gt;&lt;br /&gt;Currently both implementations rely on the rather buggy properties of .offsetLeft and .offsetTop &amp;#40;browsers have sharp disagreements over what these properties should return and often have bugs regarding padding, borders, and overflow&amp;#41;.&lt;br /&gt;&lt;br /&gt;IE offers .getBoundingClientRect, which appears to be very accurate, though it seems to return the screen position, not the page position, so extra will be needed to ensure the proper x&amp;#47;y values are returned when the page is scrolled.&lt;br /&gt;&lt;br /&gt;Mozilla offsets document.getBoxObjectFor, which also appears to be more accurate than .offsetTop&amp;#47;Left.  However, it is not a publicly documented method.  It is apparently meant for Add-on developers of Firefox, and the Mozilla devs discourage that use of this in public web sites -- special care will be needed to determine if this is a safe method to use.&lt;br/&gt;</description><author>sstchur</author><pubDate>Thu, 06 Sep 2007 17:58:42 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: .getScreenPosition and .getPagePosition could be better 20070906055842P</guid></item><item><title>CLOSED TASK: Separate "glitz" from core Gimme</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=51</link><description>Gimme has an extension model, now that Gimme has been updated to use .prototype.

This should be leveraged and all "glitzy", fx-related functions should be moved to gimmefx.js, while the core functionality of gimme will remain in gimme.js </description><author>sstchur</author><pubDate>Wed, 20 Jun 2007 04:46:04 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: Separate "glitz" from core Gimme 20070620044604A</guid></item><item><title>COMMENTED TASK: Separate "glitz" from core Gimme</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=51</link><description>Gimme has an extension model, now that Gimme has been updated to use .prototype.

This should be leveraged and all "glitzy", fx-related functions should be moved to gimmefx.js, while the core functionality of gimme will remain in gimme.js Comments: ** Comment from web user: sstchur ** &lt;p&gt;This is now complete.  Two files&amp;#58; gimme.animation.js and gimme.effects.js work together to offer &amp;#34;glitzy&amp;#34; effects to the library&lt;/p&gt;</description><author>sstchur</author><pubDate>Wed, 20 Jun 2007 04:45:59 GMT</pubDate><guid isPermaLink="false">COMMENTED TASK: Separate "glitz" from core Gimme 20070620044559A</guid></item><item><title>CREATED TASK: Separate "glitz" from core Gimme</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=51</link><description>Gimme has an extension model, now that Gimme has been updated to use .prototype.

This should be leveraged and all "glitzy", fx-related functions should be moved to gimmefx.js, while the core functionality of gimme will remain in gimme.js </description><author>sstchur</author><pubDate>Thu, 26 Apr 2007 00:29:04 GMT</pubDate><guid isPermaLink="false">CREATED TASK: Separate "glitz" from core Gimme 20070426122904A</guid></item><item><title>COMMENTED TASK: Implement ParseComplexSelector(..)</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=41</link><description>The regular expression used to split up complex selectors is not robust enough.  Looks like this is going to need to be parsed manually. Comments: ** Comment from web user: sstchur ** &lt;p&gt;Implemented basic ParseComplexSelector.  It seems to work for my simple samples, but I suspect as the tests get more rigorous, this function may need additional tweaking.  Marking as fixed, but not closed -- further testing is needed.&lt;br/&gt;&lt;/p&gt;</description><author>sstchur</author><pubDate>Thu, 26 Apr 2007 00:26:26 GMT</pubDate><guid isPermaLink="false">COMMENTED TASK: Implement ParseComplexSelector(..) 20070426122626A</guid></item><item><title>CREATED TASK: Implement ParseComplexSelector(..)</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=41</link><description>The regular expression used to split up complex selectors is not robust enough.  Looks like this is going to need to be parsed manually. </description><author>sstchur</author><pubDate>Mon, 23 Apr 2007 21:47:04 GMT</pubDate><guid isPermaLink="false">CREATED TASK: Implement ParseComplexSelector(..) 20070423094704P</guid></item><item><title>CREATED ISSUE: g('E[attr=val') broken</title><link>http://www.codeplex.com/gimme/WorkItem/View.aspx?WorkItemId=17</link><description>Desc:
Gimme by attribute selector broke during the implementation of ComplexGimme(..)

Reason:
ComplexGimme(..) splits the selector by \s, ~, + and |.  But when spaces exist in an attribute value, ComplexGimme(..) thinks the space is a descendant combinator -- not good.

Fix:
Not sure yet, what the best fix for this is. </description><author>sstchur</author><pubDate>Sat, 21 Apr 2007 00:29:39 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: g('E[attr=val') broken 20070421122939A</guid></item></channel></rss>