Thanks for the attention,
l.
--
You received this message because you are subscribed to the Google Groups "Firefinder" group.
To post to this group, send email to firef...@googlegroups.com.
To unsubscribe from this group, send email to firefinder+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/firefinder?hl=en.
http://ggsfoundry.altervista.org/patch-to-add-jquery-selecter-to-firefinder.zip
The Sizzle engine based evaluation is triggered by writing the
selector using jquery syntax.
e.g. $('a')
Bye,
Luigi
On Mar 24, 9:14 am, Robert Nyman <robny...@gmail.com> wrote:
> Hi,
>
> Interesting! The first version actually used Sizzle for the selectors, but
> then I went for the native querySelectorAll support, for the best possible
> performance and light-weight code.
> However, if you want to, please post somewhere where it can be downloaded
> for those that are interested.
>
> Best regards,
> Robert
>
> On Wed, Mar 24, 2010 at 9:05 AM, l.gualtieri <luigi.gualti...@gmail.com>wrote:
>
> > Hi group,
> > I worked for a long time with firefinder and I don't have to explain
> > you how it's useful.
> > I spend a lot of time dealing with jquery selector, so last night I
> > mumbled if was possible
> > add this feature to firefinder.
> > So I've modified the original code to add sizzle engine support, at
> > the moment it's
> > just a quick&dirty patch ... but works pretty well without changing
> > the original behavior
> > Anyone interessed ?
>
> > Thanks for the attention,
> > l.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Firefinder" group.
> > To post to this group, send email to firef...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > firefinder+...@googlegroups.com<firefinder%2Bunsu...@googlegroups.com>
To unsubscribe from this group, send email to firefinder+...@googlegroups.com.
--
--
Your extension, so your call of course. I think you are missing out on the huge user jQuery use base though. To be clear, I am suggesting adding it as an option – native CSS and XPath would be the default unless you entered the $ (or you could add a drop-down). Just something to think about.
d