#9352: Improved search results
----------------------------+-----------------------------------------------
Reporter: laurenskling | Owner: spliter
Type: PLIP | Status: assigned
Priority: major | Milestone: 4.2
Component: Infrastructure | Keywords: search
----------------------------+-----------------------------------------------
Comment(by spliter):
Replying to [comment:141 ldr]:
> Is the Search object really in the global scope? The code executes in an
anonymous block, so I can't see how it ends up in the global scope. The
normal way to do this is to set it explicitly on the ``window`` object. If
it is meant to be in the global scope then it should be called something
like ``plone_search`` instead of ``Search`` to avoid clashes.
That's a good point, Laurence. The search object is really not in the
global scope indeed. I am currently working on moving the object to the
global scope and some other improvements to the javascript. Those are not
really blockers for the merge I suppose, but will be good to have before
final release. The plan is to move the object to the global scope and
switch to JSON in the ajax call to make search results available
everywhere with a simple javascript call. Next step will be to implement
such a JS call in the livesearch in order to provide an example. Then the
same approach might be used in the new collections or listings in order to
fetch the results.
So… I am on it :)
--
Ticket URL: <http://dev.plone.org/plone/ticket/9352#comment:142>
Plone <http://plone.org>
Plone Enterprise Content Management System
_______________________________________________
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-plip-advisories
