Hi all,

Version 1.7 of Semantic Forms has been released. Before I get to the
details, I want to thank Ontoprise, who sponsored the development of this
version; it's a great relief to me to be able to have this core development
work paid for, so hats off to them.

So - this is the first time the SF version number has skipped right from one
"sub-decimal" to the next. There are a number of important new developments
that justified that change. This version has the following changes and
additions:

- the special page 'RunQuery' was added. This page lets you run a query
that's contained within a template. Technically, there's nothing
query-specific about the page: it's just a page that lets you enter data
into a form and view the resulting page without saving anything; though in
practice, I assume this would only be used for queries. People have asked
for a while now about adding querying to Semantic Forms; I always turned
down the idea because SF edits templates, and I assumed a query system would
have to be a different mechanism. I didn't realize that querying could just
be done using the same form-template system; thanks to Philip Kinlen for
that important insight. You can see an example of this querying in action
here:

http://discoursedb.org/wiki/Special:RunQuery/Item_query

(Note that the query is case-sensitive, due to SMW's "::~" operator being
case-sensitive: that's annoying, and maybe the solution is to change SMW's
handling.)

- the FCKeditor can now work on a free text input that's placed among the
fields of a template; thanks to Eugene Mednikov for the fix.

- also, FCKeditor, when it's installed, works now with all versions (I
think) of Internet Explorer.

- for pages created by forms, you can now have only the page's free text,
and not any of its template calls, show up when the page is viewed, and have
the template calls hidden within a "<noinclude>" tag. This is done using a
new parameter to the '{{{info}}}' tag, 'includeonly free text'. This is
important for pages that get transcluded in other pages, whether they're
templates or anything else; so that the semantic properties of the original
page won't get carried over to the new page. People tried achieving this
before in various hack-like ways; now there's a way to do it without a hack.
Thanks to Daniel Hansch of Ontoprise for the excellent patch for this
feature.

- the default size for text inputs for fields that are lists was increased
to 100; which should have been done a long time ago. Especially since 100
was what the documentation said. :)

- the "edit with form" tab is now named "create with form" when the page
doesn't exist yet; to match the "edit" tab now being similarly called
"create" in recent versions of MediaWiki.

- newlines can now be added to the "new delimiter" argument for #arraymap
and #arraymaptemplate, using "\n". This was possible for a long time before
for the "delimiter" argument, but not for "new delimiter", for no good
reason. Now you can have newlines in both (or all four, that is).

- Semantic Forms now adds some of its special pages (such as
'CreateProperty', 'CreateTemplate' etc.) to the 'AdminLinks' special page,
defined by the Admin Links extension. For those who don't know this
extension, it can serve as a "control panel" for many of the various
SMW-related extensions; you can read about it here:
http://www.mediawiki.org/wiki/Extension:Admin_Links

- the feature added in version 1.6, of a form, when it adds a page that was
previously deleted, showing a warning message at the top, crashed on older
versions of MediaWiki which didn't define the required classes: this has
been fixed.

-Yaron

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Semantic Forms" group.
To post to this group, send email to semantic-forms@googlegroups.com
To unsubscribe from this group, send email to 
semantic-forms+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to