I would like to opt for input type"text" (single row) since I predominantly use(d) datatype "String" (90% +)
in comparison to "Text". Perhaps I am a bit egoistic here. However I have a feeling that input type "text"
will still be the better choice. Leaving the former pros and cons for both datatyps aside, for my usecases
dataype "String" (255 single byte chars maximum - that's already quite a lot to type) was more than sufficient.
I do not think that it is useful to have a variable, usage dependant, input type (list of values versus single
values) so I do not prefer option three at all.
Am 24.02.2013 22:17, schrieb Yaron Koren:
> Hi everyone,
> As you might have seen, the String property type is going away in Semantic
> MediaWiki 1.9 - the Text property type will basically be the best of both
> worlds: holding an unlimited number of characters like it did before, but
> queriable like the String property is.
> The question now is, what should the default input type in Semantic Forms
> be for this new type? When I first heard of the change, I was sure it would
> be the "text" input type - i.e., a single row - but now I'm thinking the
> "textarea" input type might make more sense. On the one hand, the String
> property is quite a bit more popular than the Text property - so most such
> text-based properties (the ones that don't have a pre-defined set of
> allowed values) are already editable using a single-row text input. On the
> other hand, a textarea input would more accurately reflect the fact that
> this property can hold an unlimited amount of text.
> By the way, a textarea input would also be better for
> backwards-compatibility, since that's already the default input type for
> the Text property - but I don't think that's a serious consideration, for
> this kind of long-term decision.
> There's also the option of a single-row text input for the regular Text
> property, and a textarea input for any field that holds a list of Text
> values. So, three different options in all.
> Any thoughts?