Hi,
On Mon, Sep 22, 2008 at 4:55 PM, Rob Challen [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I can get autocomplete on category to work but having no joy with
autocomplete on property. I have been searching but can't find out
whether this is a known issue or not?
It has indeed been fixed already. Sorry for the noise.
Patrick.
--
Key ID: 0x86E346D4http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4
--~--~-~--~~~---~--~~
You received this message because you are
Hi,
I don't know since when, but I'm sure it didn't happen before:
When I now use a form definition like
{{{for template|Organisation functions|label=Functions / States}}}
{| class=formtable
! Is potential cooperation partner
| {{{field|IsPotentialCooperationPartner|input type=checkbox}}}
|}
Hi Yaron,
Yaron Koren wrote:
Could you explain this in more detail - this happens only for newer
forms, not older forms, on the same wiki? If so, is there any difference
between the two sets of forms?
It somehow only happens on forms that I created after upgrading to SMW 1.4.0 (I
think). I
Hi Yaron,
Yaron Koren wrote:
Well, what do you know, that really is a bug in Semantic Forms... thanks
for creating the test wiki, that helped a lot. Apparently, through some
combination of the Semantic MediaWiki version and the specific contents
of the form and template page, SMW's language
Hi Yaron,
Thanks a lot, the Boolean/Checkbox bug is fixed now. I fear there has been
another regression though...
The one-step process doesn't work in version 1.3.8 anymore - the unique
number isn't added to the page title, even when it should.
Test scenario:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaron Koren wrote:
Maybe this thread should be kept to people who actually use the extension.
:)
Ok, I apologise... I guess my post was a bit out of place.
I just wanted to point out to Bobby, who seems to really want to support
progress in our
Hi Yaron,
thanks for the new version!
[...]
- Two new parameters, values from category= and values from concept=
have been added to field declarations within form definitions. These
fulfill a request that's been around since nearly the beginning of the
extension: the ability to have a
Hi Yaron
On 2009-01-06 02:38, Yaron Koren wrote:
- setting any of the parameters values=, values from category= or
values from concept= for a field that represents a property of type
'Page' now produces a dropdown, instead of a text entry as it was
(incorrectly) before.
One more little
Hi,
On 2009-02-13 01:59, robertuva wrote:
I'm trying to use the following:
[[{{fullurl:{{PAGENAME}}|action=formedit#Name}}|Add]]
Basically what I am trying to do is create a link that will go to the
current article's formedit page anchoring down to Name, but I want
to post the link as
Hi,
I don't know which update exactly caused this (MediaWiki 1.13.3-1.14.0,
Semantic Forms 1.4.2-1.5.2 - since I updated them in a batch), but
autocompletion doesn't seem to work any longer for me:
Try to autocomplete here (either on a property or on a category):
Hi,
after seeing Davide's way of using the HeaderTabs extension together with the
SemanticForms extension [1], I thought I'd also give it a try on a Wiki I'm
working on.
I found a usability problem:
The error message that SemanticForms shows when a mandatory form field hasn't
been filled
Hi,
it would be good to have a button next to a date/datetime field that inserts
the current date into the field (via JavaScript). Example: in our Wiki we have
a Task end date, which should only be filled in after the task ended (so
default value that's set from the beginning is not a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Answering my own post...
On 2009-04-15 13:49, Patrick Nagel wrote:
Can anyone think of another way I could get a button into that form?
I figured out that the HTML/JavaScript would have to look like this:
input type=button value=Fill
Hi Dan,
On 2009-05-07 16:16, Dan Bolser wrote:
Have you looked at the Call Extension?
http://www.mediawiki.org/wiki/Extension:Call
Not sure if you can hack this to do what you want, or if it can be
made to play nicely with SF, but it may be worth having a look at this
if you didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yaron,
On 2009-05-08 23:25, Yaron Koren wrote:
Hm, that's not a bad idea... maybe a new tag type like variable is the
right way to go, so that you could add DisableLanguageBlock=... to the
query string, and then have
Hi Yaron,
On 2009-05-13 10:23, Yaron Koren wrote:
As Semantic Forms matures, it almost by necessity gets bigger - more
features, workarounds, etc. This is as it should be, but every
additional feature means more code to maintain, more to document and
more for users to understand. For
Hi,
On 2009-05-13 00:40, Yaron Koren wrote:
That's true in theory; though, given that it's already possible using
another extension, and given how (seemingly) rare the need is, maybe
it's not worth it to add this feature to SF for now.
Ok, I created a new tip for now:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 2009-06-16 21:40, Yaron Koren wrote:
Dropdowns also work - you implement them the same way you would in forms to
add and edit data - either with a values parameter or using a property
that has allowed values. Basically, the query forms
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yaron,
I think it would be a good idea to merge the lists, if the SMW lists' admins
concur. The advantages of a unified list clearly prevail.
The only concern I have, is, what appears to be a general shoddiness of the
SourceForge mailing list
Hi Joon,
On 2009-07-22 15:15, Joonyeengyo wrote:
In the semantic forms example, we have the Has genre property which
has several allowed values.
How would you go about it to make it possible for the users to add
more genres to it rather than manually editing the property page?
I would
21 matches
Mail list logo
