Re: [Development] 5.7 feature freeze
On Friday 26 February 2016 19:07:53 Nurmi J-P wrote: > Hi Lars, > > > On 27. jan. 2016, at 09.30, Knoll Lars > > wrote: > > > > If anybody else has a feature he believes absolutely has to make it to > > 5.7, get it done until Monday or talk to me :) > I would like to ask for an exception for text selection handles. It's a > crucial feature to make the new editor controls usable on mobile and > embedded. There's a task for qtquickcontrols2 > (https://bugreports.qt.io/browse/QTBUG-51010), but the groundwork needs to > be done in qtbase and qtdeclarative. > > I'm aware of the following WIP patches: > - qtbase: Add support for ImhAnchorRectangle: > https://codereview.qt-project.org/#/c/142132/ - qtbase: Android selection > handles: https://codereview.qt-project.org/#/c/142466/ - qtdeclarative: > WIP: Add support for input method selection handles: > https://codereview.qt-project.org/#/c/142133/ > > I would imagine that we may need some new API in such areas as QInputMethod, > Qt::InputMethodHint, and QStyleHints. Would it be acceptable to finish off > this work in the 5.7 branch? > I agree that we need to do something on this matter. But ... :) Are you sure this is the right approach? Isn't better (or easier) to handle it in Qt side and don't rely on platform? What will you do on embedded devices where you don't have any platform support for such things. Cheers, BogDan. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Ok, go for it. Cheers, Lars On 02/03/16 09:54, "Development on behalf of Eskil Abrahamsen Blomfeldt" wrote: > > >Den 26.02.2016 20:07, skrev Nurmi J-P: >> Hi Lars, >> >>> On 27. jan. 2016, at 09.30, Knoll Lars wrote: >>> >>> If anybody else has a feature he believes absolutely has to make it to 5.7, >>> get it done until Monday or talk to me :) >> I would like to ask for an exception for text selection handles. It's a >> crucial feature to make the new editor controls usable on mobile and >> embedded. There's a task for qtquickcontrols2 >> (https://bugreports.qt.io/browse/QTBUG-51010), but the groundwork needs to >> be done in qtbase and qtdeclarative. >> >> I'm aware of the following WIP patches: >> - qtbase: Add support for ImhAnchorRectangle: >> https://codereview.qt-project.org/#/c/142132/ >> - qtbase: Android selection handles: >> https://codereview.qt-project.org/#/c/142466/ >> - qtdeclarative: WIP: Add support for input method selection handles: >> https://codereview.qt-project.org/#/c/142133/ >> >> I would imagine that we may need some new API in such areas as QInputMethod, >> Qt::InputMethodHint, and QStyleHints. Would it be acceptable to finish off >> this work in the 5.7 branch? > >+1 from me. > >-- Eskil > >___ >Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Den 26.02.2016 20:07, skrev Nurmi J-P: Hi Lars, On 27. jan. 2016, at 09.30, Knoll Lars wrote: If anybody else has a feature he believes absolutely has to make it to 5.7, get it done until Monday or talk to me :) I would like to ask for an exception for text selection handles. It's a crucial feature to make the new editor controls usable on mobile and embedded. There's a task for qtquickcontrols2 (https://bugreports.qt.io/browse/QTBUG-51010), but the groundwork needs to be done in qtbase and qtdeclarative. I'm aware of the following WIP patches: - qtbase: Add support for ImhAnchorRectangle: https://codereview.qt-project.org/#/c/142132/ - qtbase: Android selection handles: https://codereview.qt-project.org/#/c/142466/ - qtdeclarative: WIP: Add support for input method selection handles: https://codereview.qt-project.org/#/c/142133/ I would imagine that we may need some new API in such areas as QInputMethod, Qt::InputMethodHint, and QStyleHints. Would it be acceptable to finish off this work in the 5.7 branch? +1 from me. -- Eskil ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Am Freitag, 26. Februar 2016, 19:07:53 CET schrieb Nurmi J-P: > I would like to ask for an exception for text selection handles. It's a > crucial feature to make the new editor controls usable on mobile and > embedded. There's a task for qtquickcontrols2 > (https://bugreports.qt.io/browse/QTBUG-51010), but the groundwork needs to > be done in qtbase and qtdeclarative. > > I'm aware of the following WIP patches: > - qtbase: Add support for ImhAnchorRectangle: > https://codereview.qt-project.org/#/c/142132/ - qtbase: Android selection > handles: https://codereview.qt-project.org/#/c/142466/ - qtdeclarative: > WIP: Add support for input method selection handles: > https://codereview.qt-project.org/#/c/142133/ > > I would imagine that we may need some new API in such areas as QInputMethod, > Qt::InputMethodHint, and QStyleHints. Would it be acceptable to finish off > this work in the 5.7 branch? +1 It is a shame that you still can't copy/paste properly on Android. -- Olivier Woboq - Qt services and support - https://woboq.com - https://code.woboq.org ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Hi Lars, > On 27. jan. 2016, at 09.30, Knoll Lars wrote: > > If anybody else has a feature he believes absolutely has to make it to 5.7, > get it done until Monday or talk to me :) I would like to ask for an exception for text selection handles. It's a crucial feature to make the new editor controls usable on mobile and embedded. There's a task for qtquickcontrols2 (https://bugreports.qt.io/browse/QTBUG-51010), but the groundwork needs to be done in qtbase and qtdeclarative. I'm aware of the following WIP patches: - qtbase: Add support for ImhAnchorRectangle: https://codereview.qt-project.org/#/c/142132/ - qtbase: Android selection handles: https://codereview.qt-project.org/#/c/142466/ - qtdeclarative: WIP: Add support for input method selection handles: https://codereview.qt-project.org/#/c/142133/ I would imagine that we may need some new API in such areas as QInputMethod, Qt::InputMethodHint, and QStyleHints. Would it be acceptable to finish off this work in the 5.7 branch? -- J-P Nurmi ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
On Monday 01 February 2016 18:53:18 Olivier Goffart wrote: > > What sense does it make to feature-freeze 5.7 before 5.6 is even out yet? > > It means we don't delay the release of 5.7 too much even tough 5.6 was > delayed. 5.7 already contains all the features developed since the 5.6 > feature freeze which was long ago. We do need that 5.7 branch now, though. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
On Montag, 1. Februar 2016 15:26:57 CET Kevin Kofler wrote: > Knoll Lars wrote: > > we’re slightly past the originally planned date for the feature freeze, > > for various reasons (new stuff being open sourced, license change and > > being late with 5.6). But I believe most things should be in place now to > > do the feature freeze for 5.7 next Monday. > > What sense does it make to feature-freeze 5.7 before 5.6 is even out yet? It means we don't delay the release of 5.7 too much even tough 5.6 was delayed. 5.7 already contains all the features developed since the 5.6 feature freeze which was long ago. > Distributions out there are still shipping (at best) 5.5 (which is still the > latest stable release series you have to offer), and all new features > (except the 3 you listed) are already being pushed back to 5.8, i.e., 3 > branches later than what is actually shipped. This is irrelevant > This means any improvements you make take really long to get to your users. It would take longer without the feature freeze. -- Olivier Woboq - Qt services and support - https://woboq.com - https://code.woboq.org ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Knoll Lars wrote: > we’re slightly past the originally planned date for the feature freeze, > for various reasons (new stuff being open sourced, license change and > being late with 5.6). But I believe most things should be in place now to > do the feature freeze for 5.7 next Monday. What sense does it make to feature-freeze 5.7 before 5.6 is even out yet? Distributions out there are still shipping (at best) 5.5 (which is still the latest stable release series you have to offer), and all new features (except the 3 you listed) are already being pushed back to 5.8, i.e., 3 branches later than what is actually shipped. This means any improvements you make take really long to get to your users. Kevin Kofler ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 5.7 feature freeze
Lars:
I am sure I am not the only newcomer to QT who would love to add code
to the 5.7 feature list,
but barely have time to contribute bugs to debug 5.6.0 beta let alone
look ahead to 5.7
Now we are faced with waiting until 5.8 to even think about a set of
key missing functions in Qt QML.
I am still firmly planted on the interest list and not on the development list.
One major problem lies with QQmlEngine design:
It has the following functions defined:
QQmlEngine->trimComponentCache()
QQmlEngine->clearComponentCache() (https://bugreports.qt.io/browse/QTBUG-50500)
But it is absolutely missing:
QQmlEngine->addComponent("MyComponentLib",1,0,"MyComponentName",QQmlComponent&
gcomp) -> error code
QQmlEngine->removeComponent("MyComponentLib",1,0,"MyComponentName") ->
error code
QQmlEngine->isComponentLoaded("MyComponentLib",1,0,"MyComponentName") -> bool
Devs are stuck using a QMLDIR file based import pattern that has the
flexibility of an ice cube.
We really need qml files to be able to execute: import MyComponentLib
1.0 without using QMLDIR files!
The other major problem is that QQuickItem does not allow for
QSGTextRect, so updatePaintNode CANNOT have text rendering
in coordination with QSGGeometry. The current recommendation is to
try to coordinate using signals between 2 different QQuickItems, 1
with text, the other
with graphical geometry. This is a restriction that appears to have
occurred by chance.
This cripples custom controls capabilities and forces me to explain to
customers about Qt limitations.
So how can we get the header file for QQmlEngine changed for 5.7
feature freeze to add those 3 function declarations and un-sandbox
QSGTextRect
and still pass maintainer acceptance all by Monday?
Cheers,
md
On Wed, Jan 27, 2016 at 2:30 AM, Knoll Lars wrote:
> Hi everybody,
>
> we’re slightly past the originally planned date for the feature freeze, for
> various reasons (new stuff being open sourced, license change and being late
> with 5.6). But I believe most things should be in place now to do the feature
> freeze for 5.7 next Monday.
>
> There are currently three exceptions to the freeze:
>
> * ok to finish the printing support in web engine
> * ok for BTLE support for Linux in qtconnectivity (merge neard branch)
> * Modules that are flagged as TP can also have some more time
>
> If anybody else has a feature he believes absolutely has to make it to 5.7,
> get it done until Monday or talk to me :)
>
> Cheers,
> Lars
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
[Development] 5.7 feature freeze
Hi everybody, we’re slightly past the originally planned date for the feature freeze, for various reasons (new stuff being open sourced, license change and being late with 5.6). But I believe most things should be in place now to do the feature freeze for 5.7 next Monday. There are currently three exceptions to the freeze: * ok to finish the printing support in web engine * ok for BTLE support for Linux in qtconnectivity (merge neard branch) * Modules that are flagged as TP can also have some more time If anybody else has a feature he believes absolutely has to make it to 5.7, get it done until Monday or talk to me :) Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
