[jQuery] Re: XHTML Selector Nightmare

*This message was transferred with a trial version of CommuniGate(r) Pro*
Thanks Erik. That worked perfectly. It was one of those "duhhhhh..."
moments as I read your email. I tried taking the "not" filter out of
the initial expression and chaining it onto the end but still only used
an expression rather than using a Jquery array. I did notice the index
method is actually faster than pulling 900 rows and filtering out 870 of
them for a selection but at least I know how to accomplish this in the
future.

Thanks again.

Chris

Erik Beeson wrote:
> Try this:
>
> $('.sMarker ~ row', myTable).not($('.eMarker ~ row', myTable))
>
> That will get what you want, but I think it won't include the .sMarker
> row. To get .sMarker also, maybe try:
>
> $('.sMarker,.sMarker ~ row', myTable).not($('.eMarker ~ row', myTable))
>
> You can also do it by index without each() like this:
>
> var $rows = $('row', myTable);
> var $range = $rows.slice($rows.index($rows.filter('.sMarker')),
> $rows.index($rows.filter('.eMarker'))+1);
>
> Hope it helps.
>
> --Erik
>
>
> On Wed, Oct 1, 2008 at 11:31 AM, greenteam003 <c@eac.bz
> <mailto:c@eac.bz>> wrote:
>
>
>
> I really don't know why I'm having such a hard time with this
> (maybe its the
> two monsters and three cups of coffee) but I'm trying to select a
> range of
> rows in a 1000 row xhtml table, between starting row with class
> "sMarker"
> and ending row with class "eMarker". I'm trying to use the following
> selector...
>
> $('.sMarker ~ row:not(".eMarker ~ row")',myTable)
>
> In my mind this should take my ".sMarker" row, grab all sibling
> rows after,
> and then filter out any rows that come after my ".eMarker" row.
> Or am I
> just overthinking this?
>
> Currently that selector will select ALL rows after my ".sMarker"
> excluding
> the single row marked with ".eMarker".
>
> Note: To filter out any responses that are blindingly obvious,
> the table
> row tags in my xhtml are really "row" not tr.
>
> I don't know how else to get this "between" functionality without
> using
> indexes and the each iteration is a huge performance loss when
> dealing with
> larger tables.
>
> Please help because I can not wrap my head around this one this
> morning.
>
> Thanks,
> greenteam
>
>
>
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/XHTML-Selector-Nightmare-tp19766491s27240p19766491.html
> Sent from the jQuery General Discussion mailing list archive at
> Nabble.com.
>
>