hi, > -----Original Message----- > From: Malmqvist Mathias (Nokia-MS/London) > Sent: Sunday, December 19, 2010 2:18 AM > To: ext Kenneth Rohde Christiansen; Cunha Leo (Nokia-MS-Qt/Oslo) > Cc: qt-compone...@trolltech.com > Subject: RE: [Qt-components] [API Proposal] TextField & TextArea > > >> property int inputMethodHint > > Should be hint*s* > > Agree.
ok. > >> property bool passwordMode > > passwordMode doesnt sounds like a bool to me, what about > isPasswordField? > > Problem with putting "is" in front of any property is that 1) no core > QML property > does that already, and 2) you get an onIsPasswordFieldChanged signal > slot, which > is a bit of a mouth-full. yep, onIsPasswordFieldChanged looks pretty bad, so leaving it as passwordMode. > >> property bool acceptableInput // this is a read-only property > > What is this? > > It's the property that says whether the text that has been entered > passed the > validator's tests. The name is very unclear, but it's the same as the > TextInput and > TextEdit already use. Is it unclear enough to warrant aliasing as > another name? > > > Remember that you can select from right to left having start > end > > In WebKit we use Base and Extend instead of start and end. > > Good suggestion, but the again sticking to the names that TextInput and > TextEdit > use is probably a good thing. agreed, but we are trying to avoid changing the property names if qml already provides something similar in their QML elements (TextInput & TextEdit). we can review those later for qml 2.0. > Here's my 2p: The "placeholderText" should be called "userPrompt" (or > "userPromptText"), > because that's what it is; it's the text that prompts the user to enter > something and > hints at what to enter. mathias, we discussed this when you were here in oslo and we decided to settle on placeholderText, which is the name we use in qlineedit in qt. cheers, // leo > From: qt-components-bounces+mathias.malmqvist=nokia....@qt.nokia.com > [qt-components-bounces+mathias.malmqvist=nokia....@qt.nokia.com] On > Behalf Of ext Kenneth Rohde Christiansen > [kenneth.christian...@gmail.com] > Sent: Friday, December 17, 2010 5:02 PM > To: Cunha Leo (Nokia-MS-Qt/Oslo) > Cc: qt-compone...@trolltech.com > Subject: Re: [Qt-components] [API Proposal] TextField & TextArea > > Hi, > > On Fri, Dec 17, 2010 at 5:50 PM, > <leo.cu...@nokia.com<mailto:leo.cu...@nokia.com>> wrote: > hi, > > I updated the http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-200 > task with a proposal > of common apis for TextField (prev: LineEdit) and TextArea (prev: > MultiLineEdit). > > the names were extensively discussed and in the end we chose for using > the HTML reference (TextField&TextArea). > > below are the apis pasted (both are basically a simplified subset of > TextInput&TextEdit): > > TextField > --------- > Item { > property string placeholderText > property int inputMethodHint > > Should be hint*s* > > property font font // alias to textInput.font > > property int cursorPosition > property bool readOnly // defaults to false > property bool passwordMode > > passwordMode doesnt sounds like a bool to me, what about > isPasswordField? > > property bool acceptableInput // this is a read-only property > > What is this? > > property string inputMask > property Validator validator > property string selectedText // read-only > property int selectionEnd // read-only > property int selectionStart // read-only > > Remember that you can select from right to left having start > end. In > WebKit we use Base and Extend instead of start and end. > > -- > Kenneth Rohde Christiansen > Senior Engineer > Application and Service Frameworks, Nokia Danmark A/S > Phone +45 4093 0598 / E-mail kenneth.christiansen at > gmail.com<http://gmail.com> > > http://codeposts.blogspot.com ﹆﹆﹆ _______________________________________________ Qt-components mailing list Qt-components@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-components
