Re: [Interest] [Development] Short/medium term evolution of the Assistant?

11.11.2017, 02:49, "Oleg Shparber" : > Hi, > > On 10 November 2017 at 15:06, René J.V. Bertin wrote: >> Last but not least: Zeal is indeed very closely related to Dash. So close in >> fact that it cannot advocate Mac compatibility for licensing/legal

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

Hi, On 10 November 2017 at 15:06, René J.V. Bertin wrote: > Last but not least: Zeal is indeed very closely related to Dash. So close > in fact that it cannot advocate Mac compatibility for licensing/legal > reasons, and that it would probably be delicate even to provide it

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Fri, Nov 10, 2017 at 11:03:46PM +0100, René J.V. Bertin wrote: > > > are there plans to retire QtWebKit support, migrate to using QtWebEngine > > > or > > > to improve QTextBrowser's HTML support? > > > > WebEngine is plainly inacceptable as dependency for QTextBrowser which is > > part > >

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Fri, Nov 10, 2017 at 01:10:26PM -0800, Thiago Macieira wrote: > On Friday, 10 November 2017 11:41:56 PST André Pönitz wrote: > > > are there plans to retire QtWebKit support, migrate to using QtWebEngine > > > or to improve QTextBrowser's HTML support? > > > > WebEngine is plainly inacceptable

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Friday November 10 2017 20:41:56 André Pönitz wrote: > > are there plans to retire QtWebKit support, migrate to using QtWebEngine or > > to improve > > QTextBrowser's HTML support? > > WebEngine is plainly inacceptable as dependency for QTextBrowser which > is part of the QtWidgets module.

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Friday, 10 November 2017 11:41:56 PST André Pönitz wrote: > > are there plans to retire QtWebKit support, migrate to using QtWebEngine > > or to improve QTextBrowser's HTML support? > > WebEngine is plainly inacceptable as dependency for QTextBrowser which > is part of the QtWidgets module.

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Fri, Nov 10, 2017 at 04:02:02PM +0100, René J.V. Bertin wrote: > On Friday November 10 2017 13:19:39 Samuel Stirtzel wrote: > > >(switched mailing list to interest since this post is not about qt > >development per se) > > Where Qt development does come in is with this: > > are there plans

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Friday November 10 2017 13:19:39 Samuel Stirtzel wrote: >(switched mailing list to interest since this post is not about qt >development per se) Where Qt development does come in is with this: are there plans to retire QtWebKit support, migrate to using QtWebEngine or to improve

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

On Friday November 10 2017 13:19:39 Samuel Stirtzel wrote: Hi, > are you aware of the Qt based Zeal [1] documentation browser project? > The project shares code with Dash [2] (basically the same thing for MacOS). > > IMHO it is a good alternative to Qt Assistant and IIRC there also was > a

Re: [Interest] [Development] Short/medium term evolution of the Assistant?

2017-11-10 12:40 GMT+01:00 René J.V. Bertin : > Hi, > > I've been tinkering a bit with building the Assistant from the 5.9 branch > head against my installed Qt 5.8.0, using a static lib build of the QtHelp > library. That requires only a few trivial patches and the first

Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

On 09/11/17 15:00, Konstantin Tokarev wrote: 09.11.2017, 12:16, "Nikos Chantziaras" : On Windows, I use this:    void func(const wchar_t*);    QString s;    // ...    func(reinterpret_cast(s.utf16())); This saves an allocation, a copy and a free since I don't have to

Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

On 09/11/17 14:56, Giuseppe D'Angelo wrote: Il 09/11/2017 10:15, Nikos Chantziaras ha scritto: This saves an allocation, a copy and a free since I don't have to use QString::toWCharArray(). However, is this actually safe? "It seems to work," and AFAIK, QString::d->data() is already in the

Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

On 10/11/17 00:07, André Pönitz wrote: On Thu, Nov 09, 2017 at 11:15:28AM +0200, Nikos Chantziaras wrote: On Windows, I use this: void func(const wchar_t*); QString s; // ... func(reinterpret_cast(s.utf16())); This saves an allocation, a copy and a free since I don't have to use