Re: [Development] [QtContacts] Add a new contact Type
Hi Renato,
Is an address book a contactable entity? It seems like it's just a
collection of contacts, rather than a contactable entity, in which case I
would prefer something like the QOrganizerItemCollection API to be added to
QtContacts instead, perhaps, or some other solution.
To be more precise: a contact group may be contactable (eg, a group may
have a mailinglist, an organization headquarters, and so on), which is why
I think it still makes sense to model a group as a type of contact (with
group membership denoted by QContactRelationship between the group and its
member contacts), but an addressbook is just a logical collection of
contacts.
In the qtcontacts-sqlite engine, we simply use different filters on the
QContactSyncTarget detail to determine which logical collection the contact
came from. So far, that has been adequate for our purposes, but admittedly
we have some rather complex code to deal with all of the edge-cases ;-)
Matt and I are still busy with other stuff for the next week, but hopefully
(I know I've been saying this for about a month now) after that, we'll turn
our attention to QtPIM API discussions and improvements. I've added this
to QTBUG-31824.
Cheers,
Chris.
On Tue, Mar 18, 2014 at 7:44 AM, Renato Araujo wrote:
> Hi guys,
>
> Today in QtContacts we can define a contact type using the enum
> QContactType::TypeValues which have the values { TypeContact, TypeGroup },
> this allow us to create/edit/list groups using the same functions used by
> the contacts.
> But I am missing a way to retrieve the available contacts address books,
> because of that I would like to propose to create a new contact type which
> ca be "TypeSyncTarget" this could be used to retrieve/edit/update "address
> books" and could be set as value for
> QContactSyncTarget.
>
> What do you think about that? Is that a valid solution?
>
>
> Thanks
> Renato Araujo Oliveira Filho
>
> ___
> 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] [QtContacts] Add a new contact Type
Hi guys,
Today in QtContacts we can define a contact type using the enum
QContactType::TypeValues which have the values { TypeContact, TypeGroup },
this allow us to create/edit/list groups using the same functions used by
the contacts.
But I am missing a way to retrieve the available contacts address books,
because of that I would like to propose to create a new contact type which
ca be "TypeSyncTarget" this could be used to retrieve/edit/update "address
books" and could be set as value for
QContactSyncTarget.
What do you think about that? Is that a valid solution?
Thanks
Renato Araujo Oliveira Filho
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New snapshot build from Qt 4.8.6 available
On 17 mars 2014, at 19:07, Salovaara Akseli wrote: > Hi all, > > New snapshot build from Qt 4.8.6 available: > http://download.qt-project.org/snapshots/qt/4.8/2014-03-17_517/ > > Packages are built against sha1 6ede9f99f98ed511b78935f7c6537470dce94239 > "network: fix doc typo in QNetworkConfigurationManager" (HEAD) and this build > also has MinGW4.8.2 upgrade from Mingw-Builds > i686-4.8.2-release-posix-dwarf-rt_v3-rev2 to Mingw-Builds > i686-4.8.2-release-posix-dwarf-rt_v3-rev3. If blocker issues for Qt 4.8.6 > release are found please report those to bugreports.qt-project.org and raise > issue also on releas...@qt-project.org. > > We would like to try freeze sha1 again and issue Release Candidate during > this week. If you have critical patch pending on codereview please act > according to that schedule in mind. All changes before "rebuild > configure.exe" (not yet in codereview, expected to be available on this > Wednesday) will be part of Qt 4.8.6 release. After that sha1 changes will be > considered case by case. > > Br, > Akseli > > Akseli Salovaara > Digia, Qt > Hi, There's currently a discussion about this potential issue https://bugreports.qt-project.org/browse/QTBUG-37514 so there's nothing in gerrit yet but it might worth to keep an eye on it. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Changes to QtPrintSupport merged for Beta 1
Thanks John et al. This is a great improvement. I am very happy that you got it in! Yours, Tuukka Lähettäjä: development-bounces+tuukka.turunen=digia@qt-project.org [development-bounces+tuukka.turunen=digia@qt-project.org] käyttäjän John Layt [jl...@kde.org] puolesta Lähetetty: 17. maaliskuuta 2014 18:05 Vastaanottaja: development@qt-project.org Aihe: [Development] Changes to QtPrintSupport merged for Beta 1 Hi, Thanks to some sterling work form the CI and Release teams, we've managed to finally get the QtPrintSupport changes merged in time for Beta 1 :-) If you run into any printing issues please let me know. I'll post a blog to Planet Qt detailing how the beta testers can help test the new code, but if you want to have a head start I've pasted the details below. Cheers! John. - Printing changes in Qt 5.3 Significant changes have been made to the internals of QtPrintSupport in Qt 5.3 in an effort to resolve many of the page layout bugs and inconsistent behaviour across platforms, as well as preparing the way for printing on mobile devices and cloud printing in Qt 5.4 or 5.5. These changes were not in Alpha 1, but have now been merged for the Beta 1 release and need thorough testing to ensure they work properly with the wide variety of print devices and drivers out there. The main changes on the painting side are: * A new QPageSize class in QtGui to abstract handling of page sizes and names, which supports 123 Postscript standard page sizes. * A new QPageLayout class in QtGui to abstract handling of page layout and paint rects in a consistent way, i.e. page size, orientation and margins. * QPdfWriter in QtGui uses QPageLayout to manage the PDF page layout, and you can now properly set the orientation of the PDF. * QPrinter in QtPrintSupport uses QPageLayout to manage the document page layout consistently between all platforms and the PDF file printer. The main changes on the printing side in QtPrintSupport are: * A new QPA class QPlatformPrintDevice to abstract the print device handling, which will make new platform implementations easier. * The existing Win/Mac/Cups platform plugins have new print device implementations which behave consistently and offer the same feature set on all platforms. * Mac now supports changing individual page orientation during a print job, and setting of Collate Copies and Document Name * Setting the Document Creator is now supported on all platforms * Mac and Win both now support setting of the Duplex Mode (in Beta 2) * QPrinterInfo has new api to expose more details about the print device. New api is provided to query for available printer names which should be faster than the old api that reurned QPrinterInfo instances and which could be slow when used across a network. You can query for the supported and default QPageSize, with the old page size and name api being deprecated. You can also query the printer state, if it is a remote printer, if it supports custom page sizes, what the minimum and maximum physical paper sizes are, and what physical print resolutions are supported. There have also been numerous other small fixes and code clean-ups. An important note for Linux packagers is that Qt now requires CUPS 1.4, which most distributions have been using since at least 2009, but this does mean that RHEL 5 will no longer be supported by QtPrintSupport. Optional support for CUPS 1.6 is planned for Qt 5.4. These changes in the backend are obviously significant, especially the full re-write of the platform code that talks to the physical print devices. While the code has been tested on a number of major-brand printers, the sheer variety of print devices and variable quality of print drivers (especially on Windows) means we need your help during the betas to make sure there are no regressions or crashes. In particular, I'd like some testing on printers attached to remote CUPS print servers, and older Windows printers. So how can you help? Firstly, use either Qt 5.2 or Qt 5.3 Alpha 1 to print out some "Before" documents for comparison purposes. Run the following test/example code at different page sizes and on all your available printers, as well as printing to PDF: tests/manual/dialogs examples/widgets/richtext/textedit Next copy the output of the following test to somewhere safe: tests/auto/printsupport/kernel/qprinterinfo Finally, run the main auto tests to make sure the old code passes testing with your printers (if you have multiple printers you'll need to set each one to be default before running the test for it): tests/auto/printsupport/kernel/qprinter Now build Qt 5.3 Beta 1 and repeat all the above steps, as well as the following new tests: tests/auto/printsupport/kernel/qprintdevice tests/manual/qprintdevice_dump Look at the qprintdevice_dump output: do all the reported details look correct?
[Development] New snapshot build from Qt 4.8.6 available
Hi all, New snapshot build from Qt 4.8.6 available: http://download.qt-project.org/snapshots/qt/4.8/2014-03-17_517/ Packages are built against sha1 6ede9f99f98ed511b78935f7c6537470dce94239 "network: fix doc typo in QNetworkConfigurationManager" (HEAD) and this build also has MinGW4.8.2 upgrade from Mingw-Builds i686-4.8.2-release-posix-dwarf-rt_v3-rev2 to Mingw-Builds i686-4.8.2-release-posix-dwarf-rt_v3-rev3. If blocker issues for Qt 4.8.6 release are found please report those to bugreports.qt-project.org and raise issue also on releas...@qt-project.org. We would like to try freeze sha1 again and issue Release Candidate during this week. If you have critical patch pending on codereview please act according to that schedule in mind. All changes before "rebuild configure.exe" (not yet in codereview, expected to be available on this Wednesday) will be part of Qt 4.8.6 release. After that sha1 changes will be considered case by case. Br, Akseli Akseli Salovaara Digia, Qt ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Problems pushing changes to Gerrit
Em seg 17 mar 2014, às 16:19:36, Dmitry Shachnev escreveu: > > git push ssh://mandri...@codereview.qt-project.org:29418/qt/qt > > HEAD:refs/for/4.8 > > > > then does this solve the problem? > > No, that does not work. Actually, when it works, it works without the port > number. It never works with the regular port 22. If it works for you without the port number, you must have configured ssh (~/.ssh/config) for that particular host. -- 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
[Development] Changes to QtPrintSupport merged for Beta 1
Hi, Thanks to some sterling work form the CI and Release teams, we've managed to finally get the QtPrintSupport changes merged in time for Beta 1 :-) If you run into any printing issues please let me know. I'll post a blog to Planet Qt detailing how the beta testers can help test the new code, but if you want to have a head start I've pasted the details below. Cheers! John. - Printing changes in Qt 5.3 Significant changes have been made to the internals of QtPrintSupport in Qt 5.3 in an effort to resolve many of the page layout bugs and inconsistent behaviour across platforms, as well as preparing the way for printing on mobile devices and cloud printing in Qt 5.4 or 5.5. These changes were not in Alpha 1, but have now been merged for the Beta 1 release and need thorough testing to ensure they work properly with the wide variety of print devices and drivers out there. The main changes on the painting side are: * A new QPageSize class in QtGui to abstract handling of page sizes and names, which supports 123 Postscript standard page sizes. * A new QPageLayout class in QtGui to abstract handling of page layout and paint rects in a consistent way, i.e. page size, orientation and margins. * QPdfWriter in QtGui uses QPageLayout to manage the PDF page layout, and you can now properly set the orientation of the PDF. * QPrinter in QtPrintSupport uses QPageLayout to manage the document page layout consistently between all platforms and the PDF file printer. The main changes on the printing side in QtPrintSupport are: * A new QPA class QPlatformPrintDevice to abstract the print device handling, which will make new platform implementations easier. * The existing Win/Mac/Cups platform plugins have new print device implementations which behave consistently and offer the same feature set on all platforms. * Mac now supports changing individual page orientation during a print job, and setting of Collate Copies and Document Name * Setting the Document Creator is now supported on all platforms * Mac and Win both now support setting of the Duplex Mode (in Beta 2) * QPrinterInfo has new api to expose more details about the print device. New api is provided to query for available printer names which should be faster than the old api that reurned QPrinterInfo instances and which could be slow when used across a network. You can query for the supported and default QPageSize, with the old page size and name api being deprecated. You can also query the printer state, if it is a remote printer, if it supports custom page sizes, what the minimum and maximum physical paper sizes are, and what physical print resolutions are supported. There have also been numerous other small fixes and code clean-ups. An important note for Linux packagers is that Qt now requires CUPS 1.4, which most distributions have been using since at least 2009, but this does mean that RHEL 5 will no longer be supported by QtPrintSupport. Optional support for CUPS 1.6 is planned for Qt 5.4. These changes in the backend are obviously significant, especially the full re-write of the platform code that talks to the physical print devices. While the code has been tested on a number of major-brand printers, the sheer variety of print devices and variable quality of print drivers (especially on Windows) means we need your help during the betas to make sure there are no regressions or crashes. In particular, I'd like some testing on printers attached to remote CUPS print servers, and older Windows printers. So how can you help? Firstly, use either Qt 5.2 or Qt 5.3 Alpha 1 to print out some "Before" documents for comparison purposes. Run the following test/example code at different page sizes and on all your available printers, as well as printing to PDF: tests/manual/dialogs examples/widgets/richtext/textedit Next copy the output of the following test to somewhere safe: tests/auto/printsupport/kernel/qprinterinfo Finally, run the main auto tests to make sure the old code passes testing with your printers (if you have multiple printers you'll need to set each one to be default before running the test for it): tests/auto/printsupport/kernel/qprinter Now build Qt 5.3 Beta 1 and repeat all the above steps, as well as the following new tests: tests/auto/printsupport/kernel/qprintdevice tests/manual/qprintdevice_dump Look at the qprintdevice_dump output: do all the reported details look correct? Play with the manual print dialog test: does changing the page sizes and other settings work, especially custom pages? Compare the Before and After samples, easiest done by overlaying one on top of the other and holding it up to a bright light. There may be small differences, use your judgement to decide if they are better or worse. If you have previously reported print layout bugs, then please retest these. If you have your o
Re: [Development] Problems pushing changes to Gerrit
Hi, On Mon, 17 Mar 2014 07:54:31 +, Andy Shaw wrote: > You seem to be missing the port, if you add: > > :29418 > > After the address so it is: > > git push ssh://mandri...@codereview.qt-project.org:29418/qt/qt > HEAD:refs/for/4.8 > > then does this solve the problem? No, that does not work. Actually, when it works, it works without the port number. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Problems pushing changes to Gerrit
> Gerrit seems to reject some of my changes with this error: > > $ git push ssh://mandri...@codereview.qt-project.org/qt/qt HEAD:refs/for/4.8 > error: error: invalid protocol: wanted 'old new ref' > fatal: internal server error > fatal: The remote end hung up unexpectedly > Counting objects: 30, done. > Compressing objects: 100% (6/6), done. > error: pack-objects died of signal 13 > error: failed to push some refs to 'ssh://mandri...@codereview.qt- > project.org/qt/qt' > > For example, today I successfully pushed a change to qtmultimedia, but failed > to > push a change to qt4. Some weeks ago I got a similar problem with qtwebkit, > but > resolved this by pushing from a different machine. Now I get this error from > two > different machines (with different SSH keys), one running Ubuntu and one > running > Debian GNU/Linux. > > Retrying from a fresh Git tree, adding different port numbers or URI schemes > does not help. > > Does anybody know what may cause this behavior? You seem to be missing the port, if you add: :29418 After the address so it is: git push ssh://mandri...@codereview.qt-project.org:29418/qt/qt HEAD:refs/for/4.8 then does this solve the problem? Andy ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
