On sexta-feira, 19 de outubro de 2012 22.18.25, Shawn Rutledge wrote: > So pos is bad because it's abbreviated. And I suspect we may have > problems with renaming windowState to state, because in QML that > usually refers to the state-machine state (driving animated > transitions etc.) Should we be inconsistent and leave that one as > windowState then?
The name "state" is also very generic, so that's a candidate for not being used. We need descriptive names that convey meaning and aren't ambiguous. That one doesn't fit the bill. For example, QAbstractSocket has a state() property that returns an enum of type SocketStatus. To be honest, socketState() might have made more sense, as QSslSocket later overloads that with the "encryption state". Whether the other ones like "title" make sense without the "window" prefix, you need to decide. Is it unambiguous what that title is referring to? How about the modality? Do people usually refer to it as the "window modality"? Food for thought. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
