Re: [SMW-devel] Dynamic filtered output

2012-10-30 Thread Andru Vallance
Hi Stephan,
I understand your preference for the speed of client-side filtering. Sadly 
that's only the case for very small data-sets. Practical Plants has over 7,000 
results to filter, so clientside filtering would require an unacceptably large 
query upfront.

I'm not at all surprised the attention the filtered format is getting, it's 
hugely useful functionality. I'll gladly give you some time to consolidate. For 
the time being I'll continue to develop my filter functionality as a separate 
extension (named Semantic Discovery), and I hope we can find a way to bring 
them together in the future. 

Yours
Andru




El 15/10/2012, a las 13:40, Stephan Gambke escribió:

 Hi,
 
 On 15 October 2012 12:10, Jeroen De Dauw jeroended...@gmail.com wrote:
 Would there be any demand for this?
 
 Yes, having dynamic filtering and continuation for result formats is pretty
 high on the wish list for result formats in general. Which is why people are
 so excited about the filtered format. I however have two concerns about this
 format:
 
 * It seems to need specific code for each result format it supports, which
 leads to less versatility and a lot more maintenance effort then some
 generic system
 * It loads all data and then does filter operations on it, which does not
 work for big datasets and for others is not always desired
 
 When I started working on this I consciously decided to do the
 filtering on the client side to reduce round trips. My reasoning was
 that you could achieve server side filtering by using the RunQuery
 special page from Semantic Formats. But I agree that in a lot of cases
 doing the round trip would be preferrable to client side filtering and
 I have some ideas on how this could be done. This might also solve the
 first problem and leverage existing formats. For simple filters it
 should be as easy as sending the query amended by the filter condition
 to the server and displaying the result. For something like e.g. the
 distance filter it might be less easy.
 
 Andrew, I very much like your stuff. I am excited (and a bit
 overwhelmed) at the attention this format gets. Right now it is still
 very much a construction area and will see a lot of changes before it
 becomes reasonably stable. There are still a lot of mechanisms in how
 stuff is handled that I want to improve. Normally I would be very
 happy to ask you to provide a patch. In this case however, to prevent
 us from having to somehow manually merge large amounts of code I would
 ask you to give me some more time to consolidate the format.
 
 Cheers,
 Stephan


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Dynamic filtered output

2012-10-30 Thread Andru Vallance
Hi Yury,
1) You can specify a default query to run when it first loads. For practical 
plants it queries all pages with [[Show on main page search::Yes]], so we can 
define a few key plants to show upfront
2) I don't understand this question! Could you clarify?

Thanks for the kind words about the skin. It's a very complex custom skin which 
has a dependency on a companion extension, and also a number of custom 
extensions. I don't currently have any plans to release the skin itsself, but 
I'm working on releasing some of the custom extensions (I'll shortly release 
the filtered search as an extension named Semantic Discovery). So far I've made 
the following available:

Bootstrap - https://github.com/andru/mediawiki-bootstrap
This integrates Twitter Bootstrap into MediaWiki in a way compatible with the 
ResourceLoader, giving a base to build custom themes.

MoveToSkin - https://github.com/andru/mediawiki-movetoskin
This enables a {{#movetoskin}} function which moves content from the wikitext 
to predefined areas in the skin. For example, this allows me to move the TOC 
from within the content to a sidebar without relying on Javascript after the 
DOM has loaded. 

WikiSEO - https://github.com/andru/wiki-seo
A simple extension which enables a {{#seo}} function to change the page title, 
meta description, and meta keywords.


Yours
Andru


El 15/10/2012, a las 13:48, Yury Katkov escribió:

 Hi Andru! 
 
 It looks terrific and we really need similar AJAX-feature for fitered format.
 1)  Do I understand correctly that by default (with no filters turned on) you 
 show some amount of results (say 20 results)? 
 2) a question to developers: how fast are the count queries? Maybe it's good 
 to use them when the user
 And your skin is also lovely, if you have any plans to release it as open 
 source, I'll gladly help with that. 
 
 -
 Yury Katkov, WIkiVote
 
 
 
 
 On Mon, Oct 15, 2012 at 12:48 PM, Andru Vallance an...@tinymighty.com wrote:
 For the wiki I develop, I was interested in using the filtered output format, 
 but needed the results to be loaded dynamically when filters were changed, as 
 I have 7000+ results to filter.
 
 I began making changes to this effect, but under time pressure and with no 
 documentation on the filtered output plugin, I realised it would be quicker 
 to roll my own plugin which interfaces with the SMW API to create dynamic 
 filters.
 
 My plugin operates quite differently, functioning as a parser function which 
 takes a JSON object of settings to initiate rather than operating as an 
 output format for an ask query, however if there is demand I could try and 
 merge the dynamic functionality into the filtered output.
 
 You can see my plugin in action here: http://practicalplants.org/wiki/Search
 
 Would there be any demand for this? Or is it distinct enough in operation 
 that it would be preferred that I polish up my own plugin and release it as a 
 separate entity? If the former, is there any documentation on the operation 
 of output formats to assist me in integration?
 
 Ta
 Andru Vallance
 --
 Don't let slow site performance ruin your business. Deploy New Relic APM
 Deploy New Relic app performance management and know exactly
 what is happening inside your Ruby, Python, PHP, Java, and .NET app
 Try New Relic at no cost today and get our sweet Data Nerd shirt too!
 http://p.sf.net/sfu/newrelic-dev2dev
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
 

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Dynamic filtered output

2012-10-15 Thread Krabina Bernhard
very cool!

And I also like your mediawiki-skin. Is that available somewhere?

regards,
Bernhard

- Ursprüngliche Mail -
 For the wiki I develop, I was interested in using the filtered output
 format, but needed the results to be loaded dynamically when filters
 were changed, as I have 7000+ results to filter.
 
 I began making changes to this effect, but under time pressure and
 with no documentation on the filtered output plugin, I realised it
 would be quicker to roll my own plugin which interfaces with the SMW
 API to create dynamic filters.
 
 My plugin operates quite differently, functioning as a parser
 function which takes a JSON object of settings to initiate rather
 than operating as an output format for an ask query, however if
 there is demand I could try and merge the dynamic functionality into
 the filtered output.
 
 You can see my plugin in action here:
 http://practicalplants.org/wiki/Search
 
 Would there be any demand for this? Or is it distinct enough in
 operation that it would be preferred that I polish up my own plugin
 and release it as a separate entity? If the former, is there any
 documentation on the operation of output formats to assist me in
 integration?
 
 Ta
 Andru Vallance
 --
 Don't let slow site performance ruin your business. Deploy New Relic
 APM
 Deploy New Relic app performance management and know exactly
 what is happening inside your Ruby, Python, PHP, Java, and .NET app
 Try New Relic at no cost today and get our sweet Data Nerd shirt too!
 http://p.sf.net/sfu/newrelic-dev2dev
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
 

--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Dynamic filtered output

2012-10-15 Thread Jeroen De Dauw
Hey,

 Would there be any demand for this?

Yes, having dynamic filtering and continuation for result formats is pretty
high on the wish list for result formats in general. Which is why people
are so excited about the filtered format. I however have two concerns about
this format:

* It seems to need specific code for each result format it supports, which
leads to less versatility and a lot more maintenance effort then some
generic system
* It loads all data and then does filter operations on it, which does not
work for big datasets and for others is not always desired

(Don't get me wrong I think filtered is pretty awesome)

Your approach seems to tackle the second point. Since both approaches do
not tackle the first one, it'd be best to at least share code in some way,
else the already to big maintenance costs doubles. As to how to do this I
cannot really advise, as I'm not familiar with the filtered code or the
stuff you wrote.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Dynamic filtered output

2012-10-15 Thread Stephan Gambke
Hi,

On 15 October 2012 12:10, Jeroen De Dauw jeroended...@gmail.com wrote:
 Would there be any demand for this?

 Yes, having dynamic filtering and continuation for result formats is pretty
 high on the wish list for result formats in general. Which is why people are
 so excited about the filtered format. I however have two concerns about this
 format:

 * It seems to need specific code for each result format it supports, which
 leads to less versatility and a lot more maintenance effort then some
 generic system
 * It loads all data and then does filter operations on it, which does not
 work for big datasets and for others is not always desired

When I started working on this I consciously decided to do the
filtering on the client side to reduce round trips. My reasoning was
that you could achieve server side filtering by using the RunQuery
special page from Semantic Formats. But I agree that in a lot of cases
doing the round trip would be preferrable to client side filtering and
I have some ideas on how this could be done. This might also solve the
first problem and leverage existing formats. For simple filters it
should be as easy as sending the query amended by the filter condition
to the server and displaying the result. For something like e.g. the
distance filter it might be less easy.

Andrew, I very much like your stuff. I am excited (and a bit
overwhelmed) at the attention this format gets. Right now it is still
very much a construction area and will see a lot of changes before it
becomes reasonably stable. There are still a lot of mechanisms in how
stuff is handled that I want to improve. Normally I would be very
happy to ask you to provide a patch. In this case however, to prevent
us from having to somehow manually merge large amounts of code I would
ask you to give me some more time to consolidate the format.

Cheers,
Stephan

--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Dynamic filtered output

2012-10-15 Thread Yury Katkov
Hi Andru!

It looks terrific and we really need similar AJAX-feature for fitered
format.
1)  Do I understand correctly that by default (with no filters turned on)
you show some amount of results (say 20 results)?
2) a question to developers: how fast are the count queries? Maybe it's
good to use them when the user
And your skin is also lovely, if you have any plans to release it as open
source, I'll gladly help with that.

-
Yury Katkov, WIkiVote




On Mon, Oct 15, 2012 at 12:48 PM, Andru Vallance an...@tinymighty.comwrote:

 For the wiki I develop, I was interested in using the filtered output
 format, but needed the results to be loaded dynamically when filters were
 changed, as I have 7000+ results to filter.

 I began making changes to this effect, but under time pressure and with no
 documentation on the filtered output plugin, I realised it would be quicker
 to roll my own plugin which interfaces with the SMW API to create dynamic
 filters.

 My plugin operates quite differently, functioning as a parser function
 which takes a JSON object of settings to initiate rather than operating as
 an output format for an ask query, however if there is demand I could try
 and merge the dynamic functionality into the filtered output.

 You can see my plugin in action here:
 http://practicalplants.org/wiki/Search

 Would there be any demand for this? Or is it distinct enough in operation
 that it would be preferred that I polish up my own plugin and release it as
 a separate entity? If the former, is there any documentation on the
 operation of output formats to assist me in integration?

 Ta
 Andru Vallance

 --
 Don't let slow site performance ruin your business. Deploy New Relic APM
 Deploy New Relic app performance management and know exactly
 what is happening inside your Ruby, Python, PHP, Java, and .NET app
 Try New Relic at no cost today and get our sweet Data Nerd shirt too!
 http://p.sf.net/sfu/newrelic-dev2dev
 ___
 Semediawiki-devel mailing list
 Semediawiki-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel