Hi Alexey,
Yes, that's a good point - I actually thought about an approach like that,
but forgot to include it in the email. A property called "Sort" (a name
like "Has index" might be a little clearer) would solve this problem - and
it would be a more "semantic" solution. On the other hand, it wou
Hi,
The other thread about #subobject and #set_internal reminded me that I've
been meaning to ask about this:
Currently #subobject names all the subobjects it creates in the form "Page
name#hash" (I referred to the hash previously, incorrectly, as a "random
string"). There's a problem with this a
Hi Oliver,
Fantastic! Thank you for looking into this. Assuming this fix works (and I
assume it does), this will solve one of the big remaining issues in
Javascript handling in SF 2.5.2.
-Yaron
On Tue, Jun 11, 2013 at 6:03 PM, Oliver Lutzi wrote:
> Hey,
>
> I encountered the same problem (usin
Hi,
Since you don't want to have a long bikeshed, I'll keep it short. :) I
don't like the idea of having a different namespace for each page type; it
seems unnecessarily complicated.
If you like that specific naming structure, you could always just start
page names with "Hooks:", without the need
Hi,
It would be great to have an interface like that in SF - that kind of thing
shows up in web forms a lot, including in the new Gmail interface, when
adding email addresses. (I would like to see that kind of interface in SF
for regular autocompletion too, but that's another story.) I think this
from "input type=text" and will
> have all autocompletion functons.
>
> Yury Katkov, WikiVote
>
>
>
> On Wed, May 8, 2013 at 6:34 PM, Yaron Koren wrote:
>
>> Hi,
>>
>> I'm turning this into another thread, since I think it's unrelated to th
like "this must be a PDF" with "require
>>filetype=pdf" or something.
>>
>>
>> Just an idea. It "feels" like a good direction to me. And backwards
>> compatibility could be maintained for some period of time.
>> Jamie Thingels
ow. What
> about: "Prepend the field value with the following text" ? This way we will
> broad the usecase further.
> -
> Yury Katkov, WikiVote
>
>
>
> On Wed, May 8, 2013 at 5:26 PM, Yaron Koren wrote:
>
>> Hi Yury,
>>
>> Yes, that's w
duce equal confusion the other way.
>>
>> My $0.02.
>> Jamie Thingelstad <http://www.thingelstad.com/>
>> ja...@thingelstad.com
>> mobile: 612-810-3699
>> find me on AIM Twitter <http://twitter.com/thingles>
>> Facebook<http://www.facebook
tter <http://twitter.com/thingles>
> Facebook<http://www.facebook.com/thingles>
> LinkedIn <http://www.linkedin.com/in/jthingelstad>
>
> On May 7, 2013, at 3:46 PM, Yaron Koren wrote:
>
> Hi,
>
> What about my suggestion?
>
> I'm also curious if an
t; Page Schemas can be great visual tool to edit forms and templates very
> quicky. Now the editing of the schema slows because I have to look up tag
> parameters. More buttons, dropdowns and checkboxes could speed up the
> editing process.
> -
> Yury Katkov, WikiVote
>
>
Hi Yury,
Hm, that's true... I hadn't thought of that. Some checkbox could be added
to the Page Schemas form, but maybe the better solution is just to have
uploadable fields in SF start adding a "File:" to the beginning of file
names they've uploaded. It's something that various people have asked
a
gt; Yury Katkov, WikiVote
>
>
>
> On Mon, May 6, 2013 at 4:51 PM, Yaron Koren wrote:
>
>> Hi Yury,
>>
>> I would definitely like to see SF support VisualEditor, whether it's me
>> or someone else adding that support. I wasn't aware that VisualEditor
Hi Yury,
I would definitely like to see SF support VisualEditor, whether it's me or
someone else adding that support. I wasn't aware that VisualEditor was
being used yet on Wikipedia (other than I guess in demo areas), or even
that it was in a usable state. Where is it being used?
-Yaron
On Mo
emantic Glossary and I see that
>> Jeroen is also a volunteer. I've added myself as a possible mentor here:
>> http://www.mediawiki.org/wiki/Outreach_Program_for_Women#Mentors , let's
>> see whether we'll be confirmed.
>> -
>> Yury Katkov, WikiVote
gt; Hi Edlira!
>
> I suppose that Yaron Koren is the one who can be your mentor in our
> community.
> -
> Yury Katkov, WikiVote
>
>
>
> On Fri, Apr 26, 2013 at 9:51 PM, Edlira Dushku wrote:
>
>> Hello all,
>>
>> I want to work with Semantic MediaWiki
Hi Niklas,
This sounds like a great idea. I can't really help, since I would think the
majority of the challenge would be in getting SMW queries to recognize
different property names as equivalent, so I would think this would require
assistance or at least advice from a core SMW developer; but hop
y own extension to semantify this
> information, following the Semantic Extra Special Properties and s13n
> approach.
>
> I guess there's no easier way to do it, rigth?
>
> Cheers,
> Marcelo.
>
>
> 2013/4/21 Yaron Koren
>
>> Hi,
>>
>&g
Hi,
This seems like a bad hack. I assume this is part of your effort to have
the page store the usernames of all its contributors? If so, the Semantic
Extra Special Properties extension may be the better approach - I believe
it stores that information using the "Page author" property:
https://www
Hi,
Thanks for the Semantic Forms appreciation. Just to clarify, though, the
person you quoted is trueskew, not James HK.
-Yaron
On Thu, Apr 4, 2013 at 11:50 PM, Al Johnson wrote:
> +1
>
> "All of that said, I would never select Mediawiki / Semantic Mediawiki if
> Semantic Forms and RunQuery
I've been following the discussion over there, though I haven't gotten
involved (though it seems to have died down by now). A lot of the
resistance to SMW is part of a longstanding dislike, or at least lack of
understanding, of SMW among core MediaWiki developers; though as Niklas
points out, it do
Hi Marcelo,
The simplest solution would be to change the line in the template from:
[[MyProperty::{{{pageData}}}]]
...to:
[[MyProperty::newNamespace:{{{pageData}}}]]
...and then, within the {{{field}}} tag in the form definition, add
something like "|values=pageA, pageB, pageC".
Basically, th
Hi Mary,
The easiest approach is to just have that template query the other values,
using #show.
-Yaron
On Thu, Mar 7, 2013 at 3:36 PM, Beebe, Mary J wrote:
> We have a form using more than one template. One of the templates is like
> an info-box. It displays all of the properties within the
Hi Dan,
Yes, a lot of what you're talking about (and discovering, I guess) was
discussed in two email threads yesterday, on the semediawiki-user list. It
would indeed be nice if the remaining untagged extensions were tagged, and
if SB started to have tagging as well. It wouldn't make a huge impact
Hi James,
Just to clarify: are you saying that the need to support older versions of
MediaWiki, and specifically 1.19, makes certain features in SMW impossible?
Or are you saying that it just makes adding them more difficult, because of
the need to add in a bunch of "if" statements and the like? T
;m also wondering what the criteria are for an
> extension to be part of the "SMW bundle"?
>
> thanks - john
>
> On 25.02.2013 12:01, Mark A. Hershberger wrote:
>
> On Mon 25 Feb 2013 02:12:41 PM EST, Yaron Koren wrote:
>
> It sounds like a good idea to me. What
te of tagging and
compatibility is definitely appreciated!
-Yaron
On Mon, Feb 25, 2013 at 1:56 PM, Stephan Gambke wrote:
> Hi Yaron,
>
> On 02/25/2013 07:24 PM, Yaron Koren wrote:
> > As to creating new Semantic Bundles on the fly that match some criteria
> > - i.e., using some s
Hi Mark,
It sounds like a good idea to me. What version of MediaWiki would you want
to start with - 1.20 (the current version), I assume? And where do you
think it makes sense to host and document these packages?
-Yaron
On Mon, Feb 25, 2013 at 1:31 PM, Mark A. Hershberger wrote:
> As Yaron sugg
le together, it's an interesting idea,
though it probably belongs in a separate thread.
-Yaron
On Mon, Feb 25, 2013 at 12:20 PM, Mark A. Hershberger wrote:
> On 02/25/2013 10:23 AM, Yaron Koren wrote:
> > I don't know if everyone's aware of it, but the WMF people have
&g
Hi Stephan,
There are a number of points to discuss here. In our case, I think
long-term support really refers to two things: support for older versions
of MediaWiki, and support for older versions of SMW. I don't know if
everyone's aware of it, but the WMF people have actually declared MediaWiki
u have received this
> communication in error, please return to the sender and delete from your
> computer system.*****
>
> ** **
>
> *From:* yaro...@gmail.com [mailto:yaro...@gmail.com] *On Behalf Of *Yaron
> Koren
> *Sent:* Monday, February 18, 2013 3:38 PM
> *To:* Beebe,
Hi Mary,
The query should instead be:
{{#ask: [[Research technologies::+]]**
| ?Research technologies=People
| ?Conducts research on=Technology
| format=table
| mainlabel=-**
|}
(Though I might call that column "Person" instead of "People".)
-Yaron
On Mon, Feb 18, 2013 at 3:09 P
Hi Yury,
You should separate the parts of the version string using #explode (from
the ParserFunctions extension), and then store the second half with a
property of type Number. If the version number can be 2.1 and the like,
then you can do something like turn the version number into parts "A" and
Hi Mark,
This doesn't seem like a Semantic Watchlist-related issue; neither
Special:Watchlist not Special:EditWatchlist come from Semantic Watchlist.
Semantic Watchlist (or SWL) defines its own, separate set of special pages;
it doesn't interact with the core watchlist functionality in any way.
-
Hi,
A few thoughts:
- Could it be that that call to SFUtils::getAllPagesForQuery() failed
because "picture" was misspelled? Stranger things have happened...
- If I understand it correctly, you're modifying SMW itself to add in that
query. If so, I'd say that's a bad idea - you're patching existi
Hi,
The only thing I would add to that is that it's possible to upgrade to SMW
1.8 while keeping the old database structure, by adding the following to
LocalSettings.php:
$smwgDefaultStore = 'SMWSQLStore2';
This isn't a good long-term solution, though, because support for SQLStore2
will presumab
7;t end up looking horrible on the page, I'd be
curious to see it.
-Yaron
> -
> Yury Katkov, WikiVote
>
>
>
> On Wed, Jan 16, 2013 at 9:59 PM, Yaron Koren wrote:
> > Hi,
> >
> > You can do that in Semantic Forms already with the "categ
Hi,
You can do that in Semantic Forms already with the "category" and
"categories" input types. Those require the CategoryTree extension to be
installed, and they only work with categories. However, you can create a
set of categories just for the sake of creating an SF input - the template
doesn't
Hi Michael,
I can think of a hack that might accomplish that: transclude the first page
in the second page, while keeping the first page's contents hidden. So
adding the following to page "object-B" might work:
{{:object-A}}
-Yaron
On Sat, Dec 15, 2012 at 3:54 PM, Michael Rau
> wrote:
> Hello
Hi Yury,
Yes - support for VisualEditor has been in the list of planned features for
a while:
https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Known_bugs_and_planned_features#Planned_features
I don't think VE is really usable yet, but I'm certainly looking forward to
when it gets official
Hi Jay,
DataImport is part of the SMW+ package - that extension's developers don't
always answer questions on this mailing list, so you might be better off
asking on the SMW+ forum:
http://forum.smwplus.net/index.php
-Yaron
On Mon, Dec 10, 2012 at 3:58 PM, jay johanson wrote:
> Hi all,
>
> I
That's great news! There are definitely a lot of neat features in this one.
My personal favorite is the addition of unnamed subobjects, which I think
makes them truly usable for the first time, but I'm sure others will have
other things that they really like.
This also seems to be the most profess
Hi,
I'm looking now into adding SMWSQLStore3 support to Semantic Forms,
finally. (I should note that, once this is done, I believe all of my
extensions will fully support SMWSQLStore3.)
I'm pretty sure that there's only one place in the SF code that needs to be
updated to support SMWSQLStore3 - i
Hi Frank,
You should definitely upgrade all your software. But to answer your
specific questions:
- for suggestions/autocompletion, you should change your input type to
"textarea with autocomplete".
- for having newlines as delimiters, just set "delimiter=\n".
-Yaron
On Tue, Nov 20, 2012 at 5:
, called in
> C:\xampp\htdocs\mediawiki-1.19.1\extensions\SemanticInternalObjects\SemanticInternalObjects_body.php
> on line 210 and defined in
> C:\xampp\htdocs\mediawiki-1.19.1\extensions\SemanticMediaWiki\includes\SMW_SemanticData.php
> on line 103
> So i guess it is a problem o
:
> Any help on this please?
>
>
> 2012/11/12 Marcelo Chiaradía
>
>> Im using SMW version 1.7.1
>>
>>
>> 2012/11/12 Yaron Koren
>>
>>> Hi Marcelo,
>>>
>>> 1.19 sounds like your MediaWiki version - what version of SMW are
Hi Leonard,
Semantic Internal Objects doesn't yet work with SMWSQLStore3; I'm hoping to
get that combination working before too long. Until then, you might be
better off using #subobject instead.
-Yaron
On Tue, Nov 13, 2012 at 7:09 AM, Leonard Wallentin <
leo_wallen...@hotmail.com> wrote:
> I
Hi Marcelo,
1.19 sounds like your MediaWiki version - what version of SMW are you using?
-Yaron
On Mon, Nov 12, 2012 at 6:10 PM, Marcelo Chiaradía <
chiaradiamarc...@gmail.com> wrote:
> The error I get in php is this:
>
> Catchable fatal error: Argument 1 passed to
> SMWSemanticData::__constru
Hi Marcelo,
To do that kind of query, I think you could do something like
"{{#ask[[-HasAnInternalObject.att1::SomeValue]]}}". Note the "-" in there.
-Yaron
--
Everyone hates slow websites. So do we.
Make your web apps fas
Hi Marcelo,
Yes, the first property goes from the internal object to the page - which
means that "hasAnInternalObject" is not an ideal name for it. but
nonetheless that query should work. Two questions:
- What is the full query you're calling? Maybe there's an error in the
syntax.
- Is "hasAnInt
SFAllowOnlyFormEdit - to disable "action=edit"
> - $wgSFValidatePossibleValues - to turn on the validation of
> possible values, mandatory fields etc
> - something with escaping (a bit complicated subject)
>
> -
> Yury Katkov, WikiVote
>
>
>
> On Tue, Oct 30, 2
;Four;Five;etc}}}
>
> Andru
>
>
> El 30/10/2012, a las 17:15, Yaron Koren escribió:
>
> Hi Andru,
>
> One has to register to see the form link you included, but I'm glad I did,
> because that form looks great! Turning a multiple-instance template form
> section
Hi Yury,
Yes, it's true that malicious (or inquisitive) users can turn off all of
SF's validation. SF's main validation is Javascript-based, and as far as I
know that one can be shut off by users just as easily as the HTML changes
you mentioned. I've made no effort to try to make SF more secure in
Hi Andru,
One has to register to see the form link you included, but I'm glad I did,
because that form looks great! Turning a multiple-instance template form
section into a spreadsheet-like interface is a fairly obvious enhancement
that I, and other people, have wanted for a long time. So however
new
design that felt the oddest to me.
-Yaron
On Wed, Oct 10, 2012 at 6:44 AM, Markus Krötzsch <
mar...@semantic-mediawiki.org> wrote:
> On 09/10/12 18:12, Yaron Koren wrote:
>
>> Hi,
>>
>> Nischay - thanks for that set of links. I don't think any of them cove
Hi,
Nischay - thanks for that set of links. I don't think any of them cover the
thinking behind the design decisions, but they're still all good to know
about.
Markus - thanks for all the clarifications. I was sure that the extra
tables were done to improve reading, but it sounds like they're mos
Hi,
I'm finally trying out SMWSQLStore3, and figuring out how to get my
extensions compatible with it, so I'm looking at the new table structure
for the first time.
First of all, is there any documentation about the design decisions that
went into this new structure? Because it could be that this
estrictions may not be defined from the
> beginning.
>
> Linking together pages inside the website section is typical example
> of such feature. Am I right that the most frighting thing here is
> making ask-queries in AJAX code?
> -
> Yury Katkov
>
>
>
> On Mon, Oc
listbox of all red flowers with genus
> Rosa:
>
> {{field|related flowers|values from
>
> query=[[Category:$1]][[Color::$2]][[Owner::+]]|substitute=Flowers[Genus],Flowers[Color]|input
> type=listbox}}
>
> -
> Yury Katkov
>
>
>
> On Mon, Oct 1, 2012 at 6
st
> noted can be three or four; and all of them can be dependent on what
> is currently entered in the form.
> -
> Yury Katkov
>
>
>
> On Mon, Oct 1, 2012 at 4:26 AM, Yaron Koren wrote:
> > Hi Yury,
> >
> > This sounds like a very different example
Hi Yury,
This sounds like a very different example - here the original, "source"
field is just a hidden field that gets its value from the query string. In
that case, I would think the ideal solution would be to use the
UrlGetParameters extension, to directly use the query string value:
https://w
Hi Yury,
Well, you bring up two proposed features for SF here: a standard "values
from query" parameter (which you submitted a patch for), and the ability to
include variables, representing the current content of some other form
field, in the field tag - which could go into a "values from query"
p
at, though, please let me know.)
-Yaron
On Mon, Sep 17, 2012 at 6:06 AM, Markus Krötzsch <
mar...@semantic-mediawiki.org> wrote:
> On 16/09/12 21:28, Yaron Koren wrote:
>
>> Hi James,
>>
>> You make a valid point about the importance of SF and SD supporting
>&
Hi James,
You make a valid point about the importance of SF and SD supporting
SQLStore3 in the near future. I plan to add support for the new database
structure to those extensions, as well as to Semantic Internal Objects,
which also has hardcoded calls to the SMW tables - ideally that can happen
Hi Gayathri,
There's no way to do that. The closest you can come is to put *everything*
on the first page, by only having one page for the form - see here:
https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Linking_to_forms#The_one-step_process
-Yaron
On Thu, Sep 6, 2012 at 11:04 AM, Gaya
Hi Yury,
By a staggering coincidence, I'm actually planning to release a new version
of Semantic Forms, either today or tomorrow (the first in five months) that
will have two more template layouts: one in which field names are section
headers, and one in which field names are just bolded text. In
Hi Yury,
For 1 and 2, see here:
http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Defining_forms#Reusing_form_elements
For 3, see here:
http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Linking_to_forms#Modifying_pages_automatically
-Yaron
On Wed, Aug 8, 2012 at 9:20 PM, Yury Katk
Hi everyone,
If you use Semantic Bundle, you've probably noticed that it's been a while
since the last release, which was on March 27 - that was over four months
ago, which I think is a record for the duration between SB releases. That
delay is mostly due to the fact that the extensions moved over
Yes, that's a good point.
On Wed, Jul 25, 2012 at 1:34 PM, Jeroen De Dauw wrote:
> For the formats we have nice internationalized names, we do not have such
> names or labels for parameters (yet), only their canonical system names.
> Using the descriptions seems like a bad idea as they are meant
ltip instead
> of the text.
>
> [1] https://gerrit.wikimedia.org/r/#/c/16634/
>
> Cheers
>
> On 7/25/12, Yaron Koren wrote:
> > Hi James,
> >
> > Thanks for putting those two images together. I actually think that 2nd
> > layout, with the descriptions in a smal
> Me neither but what else is there left, if this is not an option?
>
> Another option would be to introduce a user preference where one can
> opt-in/out of the text display but do we really want to do this?
>
> [1]
> https://github.com/mwjames/docs/raw/master/smw-core/special-ask-
Hi James,
I just tried this code out now, and I regret not having looked at it
before. I'm really not sure about that hover thing - as Jeroen notes, it
has usabiility issues, and beyond that, it just seems like too much work to
makes users do. It would be one thing if the hover were just clarifyin
Hi Markus,
Semantic Internal Objects still does direct storage of rows in the database
- that part of the code hasn't changed much from the beginning. If there's
a better way to store data now, I'd like to know about it.
-Yaron
On Tue, Jul 24, 2012 at 4:03 PM, Markus Krötzsch <
mar...@semantic-m
d non trivial
> changes to support 1.8 because of the store rewrite.
>
> AFAIK this code still needs to stabilize, so you cannot add in forwards
> compat just yet.
>
> Sent from my Android phone.
> On 23 Jul 2012 22:53, "Yaron Koren" wrote:
>
>> Hi,
>>
re3 instead uses DIHelper classes (interface SMWDataItemHandler) to
> access the DB.
>
> I also just looked at Semantic Internal Objects and saw that it extends
> Store2 and directly accesses db tables, these tables won't be
> there anymore in 1.8.
>
>
> On Mon, Jul 23, 2
Hi,
In the Semantic Internal Objects extension, I'm getting the "DB keys" for
an object of type SMWDataValue with the following code:
$dataItem = $value->getDataItem();
$keys = SMWCompatibilityHelpers::getDBkeysFromDataItem( $dataItem );
However, the file for the SMWCompatibilityHelpers says th
Hi Jeroen,
Ah, I was confused - your specific listing of extensions at the beginning
made me think that this was going to be a curated list of extensions, in
the manner of the Semantic Bundle. But if essentially any SMW-based
extension can get added, then I don't see what the big benefit is. It se
there could be something like
> a compatibility check. Wordpress for example has something like this, and
> even allows to install plugins directly. So I think something like a
> compatibility and dependency check would be better. But on mediawiki side,
> not especially for SMW.
> &g
Hi Jeroen,
I don't think this is a good idea as you've described it. It would
certainly increase convenience, for all the reasons you mention. But on the
other hand, it would automatically set up a "two-class system" for
extensions: those that are grouped in with Semantic MediaWiki, and those
that
Hi Marcelo,
I believe if you put the free text input between those templates in the
form, it will show up between them in the resulting page as well.
-Yaron
On Mon, Jul 2, 2012 at 5:19 PM, Marcelo Chiaradía <
chiaradiamarc...@gmail.com> wrote:
> Hello,
>
> I have question about the code generat
Hi Yury,
Very interesting. This certainly looks like a useful input, though I don't
know if it makes sense as a default input for the "Number" type.
Personally, I associate "spinners" with graphical applications like word
processors and illustration apps, where it lets you quickly try out small
va
Hi,
Try replacing {{{ClassificationList|No Instances}}} with
{{#if:{{{ClassificationList|}}}||No
Instances}} .
-Yaron
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
ágina
>> a continuación; si la página con ese nombre ya existe, será dirigido al
>> formulario para editar esa página.
>>
>>
>> {{#forminput:form=MyForm}}
>>
>>
>>
>>
>> ==Relations==
>>
>> {{{for template|Relaciones}}}
>&
mplete the data for A, and create several
> instances of B within A, using only one semantic form.
>
> Is that possible? If so, can you point me to an example of how to do it?
>
> Thanks in advance,
>
> Marcelo.
>
>
> 2012/6/29 Yaron Koren
>
>> Hi Marcelo,
>>
Hi Marcelo,
If I understand your question correctly - I would strongly recommend using
the Semantic Internal Objects extension to store the data in that
multiple-instance template, instead of just regular SMW property tags:
http://www.mediawiki.org/wiki/Extension:Semantic_Internal_Objects
That w
> Hi Yaron,
>
> It's great! Is it possible to see the diff somwhere? Please, send me link
> when it'll be ready.
>
>
> On Thu, Jun 21, 2012 at 2:13 AM, Yaron Koren wrote:
>
>> Hi,
>>
>> Okay, the code is now checked in to Git (which is where S
Hi Yury,
If I understand the question, you can already do that - the parameter
you're looking for is called "target".
-Yaron
On Thu, Jun 21, 2012 at 10:18 AM, Yury Katkov wrote:
> Hi everyone! I discover to my surprise that #formlink parser function
> doesn't have 'pagename' parameter.
> Such a
Hi,
Okay, the code is now checked in to Git (which is where SF is now, as of a
few days ago). And I'm pleased to say that I'm finally able to check code
in to the new system.
-Yaron
On Fri, Jun 15, 2012 at 11:46 AM, Yaron Koren wrote:
> Hi Vladimir,
>
> Sorry about the dela
Hi Niklas,
It would be hard indeed, because SF at the moment only supports the
editing of template calls.
I didn't know about the "incategory:" search option until now. That
sounds pretty cool - it's too bad that it (apparently) just checks the
category match via a text search, instead of actuall
gt;> Actually, I added support of default tag to "minor edits" just because it
>> was very simple and free. Probably you are right, users will never want to
>> make it checked by default.
>>
>>
>> On Tue, Jun 5, 2012 at 11:06 AM, Yaron Koren wrote:
&
Hi Kim,
The reason multiple free-text inputs aren't supported is that it
simply becomes untenable for the code to support them in all cases,
especially when there's more than one template involved. Let's say,
for instance, that a form is structured as:
{{{free text 1}}}
{{{template A}}}
{{{templa
sely.
>
> Turns out to have just been user error. (When I added the 'Publication
> Status' field to the form I failed to add a corresponding field in the
> template so no data was ever stored; accordingly, no selection was made to
> force the div to appear.)
>
> R,
>
Hi,
No, I'm not aware of any current problems with "show on select", so yes,
duplicating it on a public wiki would be helpful.
-Yaron
On Tue, Jun 5, 2012 at 6:13 AM, CWinDC wrote:
> Yaron,
> We're getting some odd behavior with the latest SMW/SF and the Show on
> Select. I haven't been watchin
the
> have contributed is very close to my heart:
> 1) frequent notifications about the activity on wikipages make users mare
> involved in the content creation process
> 2) enable notifications by default is a good decision for the most
> important pages because their changes should be as t
way
> make my mains entities checkbox checked by default. Its really important to
> users and to maintainers to watch this pages/forms.
>
>
> On Fri, Jun 1, 2012 at 3:17 AM, Yaron Koren wrote:
>
>> Hi Vladimir,
>>
>> Thanks for this patch. In theory, this sounds
Hi Vladimir,
Thanks for this patch. In theory, this sounds reasonable - and the code you
created looks fine. My one concern is that, as far as I know, currently in
MediaWiki the "watch this page" checkbox is never checked by default -
except in special cases like that the user is creating a new pa
Hi David,
That's a valid question, and you're definitely not the only one wondering
it. Hopefully someone from (what's left of) the SMW+ team is on this list,
and can respond.
-Yaron
On Tue, May 22, 2012 at 11:34 PM, David M. Cotter wrote:
> are the devs for this just gone? does nobody mainta
Katkov wrote:
>
>> Hi Yaron!
>> I found the answer to my question about the square brackets in form
>> input's name. It's done for PHP to know that all the values of the same
>> name must be collected in an array.
>>
>> Here is it : http://docs.php.net/
Hi Yury,
My answers are below.
On Thu, May 10, 2012 at 6:26 AM, Yury Katkov wrote:
> Hi everyone and especially SF/SFI developers!
>
> I've just finished the pre-alpha version of the new Semantic Form Input
> for selecting multiple items in a comfortable way.
> You can see the demo here:
>
> ht
I already created a news item about it this morning, actually - I was
excited about the win!
Joel and Sami were kind enough to invite me to the awards ceremony, so I
got to see the whole thing in person. It was both surreal and awesome to
see them get the big prize, especially after the parade of
101 - 200 of 531 matches
Mail list logo
