> > There are a number of changes building up
> for
> > both qtlocation and qtconnectivity that I would like to see integrated.
> I was hoping that this would get in:
> https://codereview.qt-project.org/#change,38790
> That should fix both of those failing jobs.
> If that won't happen during next
The example under qt5\qtbase\examples\widgets\richtext\textedit seems OK.
It could input Chinese characters, opens a text file contains Chinese
characters and displays correctly.
On Thu, Nov 22, 2012 at 10:34 PM, Konstantin Ritt wrote:
> Hi,
>
> Plz check if the rich text editor example shows t
Yes, I checked this issue on Windows 7, Mac OSX 10.6.8 and Ubuntu 12.10,
only Windows version has this problem, so I indicated it on Windows in the
mail subject.
I didn't create a bug report, since I think there may be some setting items
of Qt/QtWebkit could resolve this problem.
On Thu, Nov 22,
On Nov 22, 2012 11:39 PM, "Alan Alpert" <4163654...@gmail.com> wrote:
> On the new features category, we had discussed a bit the next
> generation QtDemo in Brisbane. What would be really cool for the QML
> demos at least would be to have an editable code pane next to the
> running example in the l
On Thu, Nov 22, 2012 at 12:44:02PM +, Rutledge Shawn wrote:
> On 22 Nov 2012, at 1:18 PM, Sorvig Morten wrote:
>
> > On Nov 22, 2012, at 1:08 PM, Konstantin Tokarev
> > wrote:
> >>
> >> 22.11.2012, 16:04, "Rutledge Shawn" :
> >>> Yeah I know, and that's very convenient, but I've seen install
On Nov 22, 2012, at 1:44 PM, Rutledge Shawn wrote:
>
> Well if our binary compatibility guarantee is true, then what conflicts do we
> worry about? If an app depends on new features which were added in a
> point-release, then it will not work with an older Qt, but an application
> which was s
22.11.2012, 16:46, "Rutledge Shawn" :
> On 22 Nov 2012, at 1:18 PM, Sorvig Morten wrote:
>
>> On Nov 22, 2012, at 1:08 PM, Konstantin Tokarev
>> wrote:
>>> 22.11.2012, 16:04, "Rutledge Shawn" :
Yeah I know, and that's very convenient, but I've seen installers
sometimes too.
>
On quinta-feira, 22 de novembro de 2012 07.44.24, Koehne Kai wrote:
> > When I was doing the lib renaming, I thought we had concluded that
> > frameworks on Mac were not going to be supported anymore.
>
> Can't find it anything on qt-development@. Maybe you are referring to this
> thread on qt-int
On Thu, Nov 22, 2012 at 7:04 AM, Charley Bay wrote:
> Maurice spaketh:
>>
>> >,
>>
>> > My question is, what are the benefits compared to picking the example
>> > source code from the source package directly. Does anybody really want to
>> > have prebuilt binaries in the examples directory? Curren
At least for me, browser could display simplified Chinese characters correctly
on mac. BTW, all the old text codecs are in QtCore 5.0 now. Maybe someone with
your configuration could verify it works or not.
Have you created bug report?
Regards,
Liang
From: deve
Maurice spaketh:
> >,
> > My question is, what are the benefits compared to picking the example
> source code from the source package directly. Does anybody really want to
> have prebuilt binaries in the examples directory? Current assumption is
> that you go through the list via Qt Creator and bu
On Thu, Nov 22, 2012 at 1:52 AM, Kalinowski Maurice
wrote:
> Hi,
>
> We are currently going through the examples for the final Qt 5 packages and
> as mentioned before, there are some differences compared to Qt 4 packaging.
>
> Most prominently, examples are packaged via make install and then take
Hi,
Plz check if the rich text editor example shows these Chinese
characters correctly.
Konstantin
2012/11/22 Yang Fan :
>
> Hi All,
>
> Maybe it's not so suitable to ask here, since there's no reply in the
> Interest maillist.
> I built Qt5 from Git with MSVC2010 SP1 by myself, I used ICU5.0 t
On 22 Nov 2012, at 1:18 PM, Sorvig Morten wrote:
> On Nov 22, 2012, at 1:08 PM, Konstantin Tokarev
> wrote:
>>
>> 22.11.2012, 16:04, "Rutledge Shawn" :
>>> Yeah I know, and that's very convenient, but I've seen installers sometimes
>>> too.
>>>
>>> We could even offer a way to make it easy for
On Nov 22, 2012, at 1:08 PM, Konstantin Tokarev
wrote:
>
> 22.11.2012, 16:04, "Rutledge Shawn" :
>> On 22 Nov 2012, at 12:06 PM, Volker Götz wrote:
>>
>>
>> Yeah I know, and that's very convenient, but I've seen installers sometimes
>> too.
>>
>> We could even offer a way to make it easy for
Am 22.11.2012 um 13:03 schrieb Rutledge Shawn:
>>
>> The regular way is to have application bundles (directories with a certain
>> structure; the name ends on .app and is treated like a single file in the
>> Finder) that contain everything that is needed to run the program, including
>> all li
22.11.2012, 16:04, "Rutledge Shawn" :
> On 22 Nov 2012, at 12:06 PM, Volker Götz wrote:
>
>> Hi,
>>
>> Am 22.11.2012 um 11:42 schrieb Rutledge Shawn:
>>> I don't understand either; I thought that frameworks have the advantage of
>>> being shared between applications. If one application inclu
On 22 Nov 2012, at 12:06 PM, Volker Götz wrote:
> Hi,
>
> Am 22.11.2012 um 11:42 schrieb Rutledge Shawn:
>
>> I don't understand either; I thought that frameworks have the advantage of
>> being shared between applications. If one application includes Qt 5.0.0 in
>> the .app bundle and anothe
I think we should keep the frameworks and we can add plugins into the framework
bundle.
(eg. qjpeg, qtiff, qaccessibility into the QtGui.framework and character and
general plugins into QtCore.framework)
It will simplify probably the deploy process.
Raul
On Nov 22, 2012, at 1:06 PM, Volker Götz
Hi,
Am 22.11.2012 um 11:42 schrieb Rutledge Shawn:
> I don't understand either; I thought that frameworks have the advantage of
> being shared between applications. If one application includes Qt 5.0.0 in
> the .app bundle and another includes 5.0.1, and you run both of them, does it
> mean t
On 22 Nov 2012, at 9:08 AM, Sorvig Morten wrote:
>
> On Nov 22, 2012, at 6:52 AM, Thiago Macieira
> wrote:
>>
>> That's the point: the conclusion was that the default on Mac is to *not*
>> have
>> frameworks anymore. It might have been the case in the past, but recently
>> the
>> trend has
Hi,
We are currently going through the examples for the final Qt 5 packages and as
mentioned before, there are some differences compared to Qt 4 packaging.
Most prominently, examples are packaged via make install and then taken from
the prefix directory. This has two problems:
a) We need to ada
On Nov 22, 2012, at 6:52 AM, Thiago Macieira
wrote:
>
> That's the point: the conclusion was that the default on Mac is to *not* have
> frameworks anymore. It might have been the case in the past, but recently the
> trend has been to have regular libraries. Apple themselves are now preferring
23 matches
Mail list logo
