Hi,
I've created a PRJQuerySearchWidget as a plug in replacement for the existing PRAjaxSearchWidget. It uses the new Seaside JQuery autocomplete widget, which Lukas has recently added. I implemented it as I'm using other JQuery widgets on my page and didn't want to be without autocomplete search AND I haven't found a satisfactory way to mix scriptaculous and jquery widgets on the same page.
I'll check it in as soon as a couple of fixes go into Seaside:
Currently if you create an default pier instance with:
PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named: 'pier') ..Scriptaculous libraries (if present) are added in PRPierFrame class>>configureApplication:
Perhaps we should allow either JQuery or Scripaculous to be specified for this default implementation, or at least add the JQuery libraries (if present), if the Scriptaculous libraries are absent. Thoughts? Nick _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
> I've created a PRJQuerySearchWidget as a plug in replacement for the
> existing PRAjaxSearchWidget. It uses the new Seaside JQuery autocomplete > widget, which Lukas has recently added. I implemented it as I'm using other > JQuery widgets on my page and didn't want to be without autocomplete search > AND I haven't found a satisfactory way to mix scriptaculous and jquery > widgets on the same page. Pay attention, the JQueryUI Autocompleter and the JQueryUI Buttons are not fully integrated into Seaside yet. Also they base on unstable Javascript code. > I'll check it in as soon as a couple of fixes go into Seaside: > http://lists.squeakfoundation.org/pipermail/seaside/2010-January/022458.html > http://lists.squeakfoundation.org/pipermail/seaside/2010-February/022485.html I will have a look at that today. > Perhaps we should allow either JQuery or Scripaculous to be specified for > this default implementation, or at least add the JQuery libraries (if > present), if the Scriptaculous libraries are absent. > Thoughts? I think the default installation should not depend any of these large Javascript libraries. Pier-Seaside should remain agnostic from the library used. That's also why we rewrote the editor plugin using bare Javascript, and not build on top of Scriptaculous. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Hi Lukas,
Pay attention, the JQueryUI Autocompleter and the JQueryUI Buttons are So do you think my PRJQuerySearchWidget should be added to Pier to provide the JQuery counterpoint to the scriptaculous version - PRAjaxSearchWidget - that's already the repository? Would you like to review the code first? It's working OK for me, though I'm happy to wait for the JQuery implementation to stabilise, if you'd prefer.
Nick _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
> So do you think my PRJQuerySearchWidget should be added to Pier to provide
> the JQuery counterpoint to the scriptaculous version - PRAjaxSearchWidget - > that's already the repository? Would you like to review the code first? It's > working OK for me, though I'm happy to wait for the JQuery implementation > to stabilise, if you'd prefer. I would prefer to remove PRAjaxSerachWidget from Pier-Seaside. It is sort of alien, because it is the only component that depends on some Javascript library. I guess both components could go into a plugin as soon as JQueryUI stabilizes ... hopefully soon. Lukas > Nick > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Free forum by Nabble | Edit this page |