Open GoogleCodeExporter opened 9 years ago
I'd be willing to collaborate on this, just let me know what your plans are and
how they differ from the old issue.
Original comment by conormac...@gmail.com
on 15 Jun 2012 at 8:08
thanks Conor - the plans are not really all that different. I just think it
makes sense to keep it in the core and have fewer redundant systems.
my plan is to have a simple core functionality which can do basic searches
through pages, but for each page type, it will check first to see if that page
has its own dedicated search method, in which case that will be used instead
and the results segregated (possibly - may also have a "merged results" view
similar to Google)
also, I want results to be viewed using an Ajax-like viewer that can scroll
forward/back within its section of results (sections would be "normal pages",
"blogs", "products", etc).
I have another idea which is to have an RSS for search results, so people that
are interested in new search results for "mountain bikes" will know when they
are added to the system. this is probably a bad idea.
for the search widget, i think a clone of what you were doing with your Dynamic
Search plugin is a good idea, using a "merged results" view so it doesn't take
too much space
Original comment by kae.verens@gmail.com
on 15 Jun 2012 at 9:31
ok, well i'm happy enough to start coding over the weekend.
so each plugin will register a search function for their page type. the new
search functionality will go through all pages, check their page type, if not
"Normal" it will check to see if a plugin has a search function for that type,
if so it will use that rather than the default. sound right?
I think i'll add that functionality first, then add ajax page viewing to the
search page, then do the search widget and possibly the RSS after.
Original comment by conormac...@gmail.com
on 15 Jun 2012 at 11:27
will have to check out your new API code, wasn't finished last time i was
working with webme
Original comment by conormac...@gmail.com
on 15 Jun 2012 at 11:28
the API is very stable now. have fun with that!
Original comment by kae.verens@gmail.com
on 15 Jun 2012 at 11:59
Original issue reported on code.google.com by
kae.verens@gmail.com
on 14 Jun 2012 at 8:07