Hey,
> While you are looking at that part of the code, did you see anything that
would
> enable ( or prohibit ) implementing some kind of dynamic scroll or paging
of results ?
> I know the AJAX piece of this would have to reside browser side but there
has to
> be some code allowing it internally at least.
Right now there are some formats that obtain HTML via the result printers
for continuation functionality, but I think this is a bad idea and cannot
work nicely in general. Just imagine having a list and you want to fetch
additional items - you do not want to get a second list back, but want the
newly fetched items to be inserted into the existing one. So the way I
think we should go is just fetching the query result object in some wrapper
via a dedicated interface (similar to the ask API, or maybe the ask API
actually suffices) and then build the HTML client side. This will require
work per format, and is simply not something we can get for free
considering the current code was not written with the additional loading
via AJAX in mind.
In any case, my current work does not directly impact this, although it
might make implementing it slightly easier at some point.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
