Sam Stephenson
|
6bb309afb7
|
Selector API change: replace Prototype.Selector.filter with Prototype.Selector.find, which works like the old Selector.findElement.
|
2009-12-02 15:57:58 -06:00 |
Tobie Langel
|
83826829a7
|
Add Prototype.Selector.engine which simply holds a reference to the actual selector engine used.
|
2009-10-24 16:12:38 +02:00 |
|
Tobie Langel
|
5f85799c3f
|
Refactor NWMatcher adapter.
|
2009-10-23 19:29:03 +02:00 |
|
Tobie Langel
|
75aab03eba
|
Repo and Rakefile refactoring.
|
2009-10-23 18:32:07 +02:00 |
|
Tobie Langel
|
7f5ce1e6c2
|
Clean-up NWMatcher proxy.
|
2009-10-23 13:17:53 +02:00 |
|
Tobie Langel
|
ed27b225a5
|
Fix Element extension when using the NWMatcher selector engine. (jddalton)
|
2009-10-23 07:31:37 +02:00 |
|
Tobie Langel
|
15c323b9ac
|
Include NWMatcher as a submodule.
|
2009-10-23 07:18:52 +02:00 |
|
Tobie Langel
|
7762e002cb
|
Reorder repository to allow for custom selector engines to be included instead of Sizzle (the current default). Selector engines belong in the vendor directory and must have a selector_engine.js file. To build a Prototype with your engine of choice just spepcify it at build time using the SELECTOR_ENGINE option. For example, to build a version with NSMatcher: rake dist SELECTOR_ENGINE=nwmatcher.
|
2009-10-23 05:49:40 +02:00 |