Oh, OK - yes, this was partly an idea behind POM, right ;)

On Tue, Dec 15, 2009 at 12:58 PM, Yaron Koren <yaron57@gmail.com> wrote:
Hi,

Actually, Semantic Forms already has querying functionality - the "Run query" feature:

[1] http://www.mediawiki.org/wiki/Extension:Semantic_Forms#Querying_data

Hauke - Were you aware of this? If so, how would what you're proposing be different?

Sergey - He was talking about using the addition of querying as an excuse to refactor SF to use POM - which is not a bad instinct in principle. :)

-Yaron


On Tue, Dec 15, 2009 at 11:55 AM, Sergey Chernyshev <sergey.chernyshev@gmail.com> wrote:
I'm not sure if you can reuse SF form language as it seems to be targeted specifically at data entry.
Also, did you check out Semantic DrillDown? It does some filtered navigation and allows for drop-downs and stuff.

Not sure how POM is related to this... did you include wrong link?

        Sergey



On Mon, Dec 14, 2009 at 6:37 PM, Hauke Pribnow <hauke.pribnow@gmx.net> wrote:
Hello everybody!

While working on my Semantic Multi Edit Page I got the idea of also
creating another extension for Semantic MediaWiki which would allow
more-skilled users to create something like "search forms" for
less-skilled users who might not directly understand the semantic query
syntax.

It would be great if the form design syntax for such an extension was
similar to the one of the already existing Semantic Forms extension; IMO
it would make even more sense to pretty much re-design the FormPrinter
from scratch and - during this process - turn it into a more general
code base for creating all sorts of forms, i.e. make the whole thing
more extendable.

As already mentioned here
<http://www.mediawiki.org/wiki/Extension:Semantic_Forms/POM>, the
current FormPrinter implementation acutally doesn't just print the form
(as the name suggests), but also does up to five other tasks like
parsing the page that should be edited, handling form input and actually
committing the change to a page that was modified through a form. To me,
this is way too much work for a class that - going by its name - should
only print out a neat form. Redesigning that class is/will be necessary
anyway.

What do you think about these ideas?


Hauke Pribnow

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel