Re: [Interest] Ashamed bug :)

[Ilya Diallo]

Le sam. 4 sept. 2021 à 00:14, Thiago Macieira  a
écrit :

> On Friday, 3 September 2021 14:04:01 PDT David M. Cotter wrote:
> > there's also the rather daunting barrier to entry for folks who COULD fix
> > it:
> >
> > getting the qt sources on your local computer, getting them to compile,
> > getting your project to use the build libraries for testing, getting it
> all
> > connected to git so you can submit changes, actually submitting
> changes...
> >
> > the above "simple" things are in fact very, very difficult if you've
> never
> > done it before. even for an expert.
>
> You also forgot the need to write unit tests.
>
> You're proving my point. It's not easy. If it were, anyone could do it.
>

He's not proving your point, he's describing the barrier to entry for a
newcomer. The actual bug fix can be easy nonetheless.

Ilya.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] L Word

[Ilya Diallo]

Le lun. 3 mai 2021 à 17:36, Matthew Woehlke  a
écrit :

> On 29/04/2021 15.24, Ben Haller via Interest wrote:
> > If I'm not mistaken, not a single person has posted to this "L Word"
> > thread in defense of Roland's right to act as he has been acting,
> > have they?
> Given that we live in a culture where anyone doing so is likely to get
> banned right alongside Roland, is that really so surprising?
>
> We live in a world where dissent from certain positions is simply not
> tolerated.
>

Come on. The problem with Roland is not "dissent". It's ad hominem attacks,
disparaging others and shameless advertising.
There's plenty of dissent here otherwise.

Ilya
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] L Word

[Ilya Diallo]

Easy solution: create the rol...@qt-projet.org list and send him and his
(surely numerous) followers there.
Think "separation of concerns" rather than "ban"

Le jeu. 29 avr. 2021 à 13:46, Tuukka Turunen  a
écrit :

> Hi,
>
>
>
> Perhaps we have been too long tolerant for the behavior that many see
> problematic (myself included). The challenge is the mix of valid and
> invalid items. It is easier to react to things that are clear violations to
> our CoC: http://quips-qt-io.herokuapp.com/quip-0012-Code-of-Conduct.html
> and nothing else.
>
>
>
> On the positive side, we have not had that much of these over the years.
> We have not been banning people regularly, so we also lack a bit of
> precedence with this. Technically it is a trivial thing to remove someone
> from a mailing list. The challenging part is to decide when it is time to
> do that.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
>
>
>
>
> *From: *Interest  on behalf of
> Massimiliano Maini 
> *Date: *Thursday, 29. April 2021 at 14.23
> *To: *Bernhard Lindner 
> *Cc: *interest@qt-project.org 
> *Subject: *Re: [Interest] L Word
>
> Yeah, maybe that's part of the problem but, as you said, the solution
> should be simple: he leaves the mailing list
> or, if that's not possible, the admins "make him leave".
>
> On top, with his ramblings and often totally wrong assertions (the
> "April's fool link"-gate scandal has been absolutely
> hilarious, almost as the subsequent attempt to regain some
> credibility, yeah .. nice try) he has now managed to scare
> the hell out of me the next time I'll be tied to a medical device: the
> mere chance he may be behind it now makes me
> extremely nervous. Even if it's only a blood pressure monitor.
>
> Losing valuable people in the mailing list and, at some point, the
> mailing list at all is like throwing away a Ferrari
> because a pidgeon keeps shitting on it. I'd argue that getting rid of
> the pidgeon is a more sensible solution.
>
> On Thu, 29 Apr 2021 at 12:05, Bernhard Lindner
>  wrote:
> >
> > The main problem isn't trolling. The main problem is: Roland comes from
> a completely
> > different world. The world of functional safety. This world is difficult
> and a completely
> > different from conventional software development. It is particularly
> different from
> > smartphone and web development. And it doesn't have much to do with
> desktop software
> > development. I have also been in this world for more than 3 years. A
> world where
> > programming is the least important thing. Where documentation is
> important. And the law.
> > And prison. And accuracy and multi-level tests and reliability and
> verification and
> > validation and standards. And many years of support. And certifications.
> A person who has
> > worked in this world for a long time has different priorities. Roland
> calls this "True
> > Software Engineering".
> >
> > Obviously, Qt has nothing to do with this type of software engineering.
> And it's obviously
> > not suitable for functional safety (at least not if you take it
> seriously).
> >
> > What I don't understand is why Roland doesn't just leave the mailing
> list and forget about
> > Qt. Qt is not suitable for use in his industrial sector, so I can't
> understand why he
> > spends so much time writing about the conflict between the reality of Qt
> and the reality
> > of his industrial sector. If I were him, I would have given up trying to
> influence Qt's
> > strategy a long time ago.
> >
> > (Actually, I'm about to give up my hopes for desktop development with
> Qt).
> >
> > So, Roland, why are you keeping the conflicts going?
> >
> > --
> > Best Regards,
> > Bernhard Lindner
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] L Word

[Ilya Diallo]

The other part of the problem is that he doesn't come from the world of
well-adjusted, well-behaved people. This could answer your question.

Le jeu. 29 avr. 2021 à 12:05, Bernhard Lindner 
a écrit :

> The main problem isn't trolling. The main problem is: Roland comes from a
> completely
> different world. The world of functional safety. This world is difficult
> and a completely
> different from conventional software development. It is particularly
> different from
> smartphone and web development. And it doesn't have much to do with
> desktop software
> development. I have also been in this world for more than 3 years. A world
> where
> programming is the least important thing. Where documentation is
> important. And the law.
> And prison. And accuracy and multi-level tests and reliability and
> verification and
> validation and standards. And many years of support. And certifications. A
> person who has
> worked in this world for a long time has different priorities. Roland
> calls this "True
> Software Engineering".
>
> Obviously, Qt has nothing to do with this type of software engineering.
> And it's obviously
> not suitable for functional safety (at least not if you take it seriously).
>
> What I don't understand is why Roland doesn't just leave the mailing list
> and forget about
> Qt. Qt is not suitable for use in his industrial sector, so I can't
> understand why he
> spends so much time writing about the conflict between the reality of Qt
> and the reality
> of his industrial sector. If I were him, I would have given up trying to
> influence Qt's
> strategy a long time ago.
>
> (Actually, I'm about to give up my hopes for desktop development with Qt).
>
> So, Roland, why are you keeping the conflicts going?
>
> --
> Best Regards,
> Bernhard Lindner
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.15 pull out of open source?!

[Ilya Diallo]

Le jeu. 7 janv. 2021 à 18:30, Benjamin TERRIER  a
écrit :

>
> So basically for open source users the support of Qt 5.15 has stopped 9
> months before a usable version should be available.
>

Totally agree, but that point has already been made in the dev mailing list.
So we can assume that Tuuka is fully aware of that problem. In that context
his "it's business as usual" response could be translated to "la-la-la
can't hear you".


> Dropping the LTS for open source users would not have been an issue this
> big if you had done it for any other version.
> But doing it for 5.15, the last Qt 5 version is the worst timing. If
> anything Qt 5.15 should have had an extended support time
>

It's the worst timing unless the purpose is to push (drag ?) users to the
commercial license - in that case the timing is perfect.
It's a business decision, time will tell if it's a good one or not.

Ilya.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt Creator licensing for companies with Qt, Commercial developers

[Ilya Diallo]

Hi,

What I get from the explanations from Tuukka is that the commercial
contract includes what amounts to legal carpet-bombing aiming to prevent
bad faith actors to use loopholes to their advantage.
The unfortunate consequence is that good faith actors can feel unsafe if
they try to read the legal terms.
There's some concerns about the definition of a "project" or "product" but
most important terms are ill-defined if you think about it:
- what does "using" means exactly ?
- what does "depends" means exactly ?
- what does "affecting" means in the context ?
- and so on

You can't escape that increasingly anything tends to depends on everything,
so the dual-licensing model is more and more complicated to get right.

The general intent of the Qt license is somewhat clear, but someone said
that the "get a lawyer" advice is FUD, and it's tempting to agree. I think
it's even worse for the QtC because a lawyer may advise to not use the
commercial license if he tries to get to the bottom of it and fails (as he
should).

Ilya

Le mer. 1 avr. 2020 à 09:04, Tuukka Turunen  a écrit :

>
> Hi,
>
> I think you are now twisting and mixing things incorrectly.
>
> For example, working in a company who has a commercial license of Qt does
> not in any way hinder contributing to Qt.
>
> Yours,
>
> Tuukka
>
> On 1.4.2020, 9.32, "Interest on behalf of Roland Hughes" <
> interest-boun...@qt-project.org on behalf of rol...@logikalsolutions.com>
> wrote:
>
>
> On 3/30/20 1:03 PM, Andy wrote:
> > That makes no sense. Your license prevents a company from using an
> > open-source tool? It says "if you license our stuff you cannot use
> the
> > open-source tool X"?
> >
> > This whole thread is yet another great example of where the Qt
> Company is
> > totally tone-deaf.
> >
> > Nobody understands your licensing. You have fewer people using Qt and
> > Qt-based things because of this.
>
> I've honestly been expecting KDE to kick Qt to the curb any day now if
> they are reading this.
>
> Medical device companies have been running screaming away from Qt over
> the past year. Many moving to Rust. Some are even moving to Zinc which
> really kind of surprised me.
>
> Some companies in other markets are abandoning embedded Linux for
> embedded DOS so they can use other GUI tools. Before you Guffaw at
> that,
> AGCO uses a lot of embedded DOS and they make an awful lot of Ag heavy
> equipment. Last I heard they were moving away from Qt as well.
>
> What is impressive is how "company" and "project" get thrown around
> interchangeably. So, if one tiny little project in GE in some remote
> location is using a commercial license, from what was stated, every
> person in every GE location around the world __must__ have a
> commercial
> Qt license to use QtCreator even if they are just using C++. I guess
> everyone has to move to Emacs, CodeLite, KDevelop, and VSCodium.
>
> https://www.gnu.org/software/emacs/
>
> https://codelite.org/
>
> https://www.kdevelop.org/
>
> https://vscodium.com/
>
> I suppose if they didn't want free they could pay $299 for SlickEdit.
>
> https://www.slickedit.com/
>
> or a $100/yr annual subscription to UltraEdit.
>
> Just be aware that UltraEdit like many other PC originating editors
> gets
> tabs wrong. When you set tabs to spaces and set their width to 4,
> hitting  when cursor is in first column of the line has to put
> the
> cursor in column 4, not 5 like far too many PC editors.
>
>
> https://www.logikalsolutions.com/wordpress/information-technology/most-text-editors-get-tabs-wrong/
>
> Having followed this "discussion" for a bit now I have a relevant
> question.
>
> Assuming Intel, given all of the locations it has around the globe,
> owns
> a single commercial Qt license at any one of them, by what has been
> said
> here, Thiago not only has to have a commercial license to work on Qt,
> he
> technically can't work on the OpenSource version. He has to commit his
> code to the commercial version where it may or may not ever find its
> way
> into the OpenSource version, if there ever is to be an OpenSource
> version again.
>
> Cause that's what I've been hearing in this conversation. The new new
> new new licensing "strategy" is once anyone in an organization has
> touched a commercial version they must perpetually pay forever and
> ever
> for everyone. It almost sounds like a person couldn't even leave a
> company and go work on OpenSource.
>
> I went back tot he archive.
>
> Vyacheslav Lanovets actually asked:
>
> =
>
> A company has a few developers with Qt Commercial subscription who
> write applications in Qt for iOS.
> There are many other developers, who work on other projects and don't
> use Qt libraries.
> They talk to each other and sometimes even work on the same code.

Re: [Interest] Licensing

[Ilya Diallo]

It would maybe be useful to clarify what his mistake is ?
>From what I understand Uwe mixes "contributing to open source project" and
"using open source Qt for a closed project". In the former case, of course
he's welcome to buy commercial licences for whatever project he'll be
working on. In the latter case, the rational is (I guess) to prevent a
company, say, to work with 20 developers for 3 years on an OSS Qt license,
then switch to commercial when it's time to ship the product and the team
is reduced to a core maintenance crew. That late switch is unfair to
companies that are playing by the rule, but it's probably hard to police
for the Qt company.

Best regards

Ilya

Le mar. 8 oct. 2019 à 15:30, Melinda Seifert  a
écrit :

> Uwe,
> You are completely mistaken!  I'm more than happy to discuss this with
> you. My phone number is listed below. In the meantime please view
> https://www.qt.io/faq/
>
> 2.13. If I have started development of a project using the open source
> version (LGPL), can I later purchase a commercial version of Qt and move my
> code under that license?
> "This is not permitted without written consent from The Qt Company. If you
> have already started the development with an open-source version of Qt,
> please contact The Qt Company to resolve the issue. If you are unsure of
> which license or version to use when you start development, we recommend
> you contact The Qt Company to advise you on the best choice based on your
> development needs."
>
> Best Regards,
>
> Melinda Seifert
> Regional Director of the Americas
> The Qt Company
> O: 617-377-7918 | M: 617-413-4479
> Qt Customer Case Studies - https://resources.qt.io/customer-stories-all
>
>
> On 10/8/19, 3:54 AM, "Interest on behalf of Uwe Rathmann" <
> interest-boun...@qt-project.org on behalf of uwe.rathm...@tigertal.de>
> wrote:
>
> On 10/8/19 1:21 AM, Melinda Seifert wrote:
>
> > You can use commercial if you previously used Open Source but it’s on
> > a case by case basis and you need to get approval from the Qt
> > company.
>
> Like you need to get approval from the Qt company when not having been
> Open Source before - it is the basic right of any seller not to sell.
>
> But your statement implies, that the Qt Company is blacklisting users
> because of contributing to Open Source projects. Am I already
> blacklisted because of offering code under an Open Source license ?
>
> How does this all fit to the Qt project, that is in parts based on
> contributions from Open Source developers. Am I invited to contribute
> to
> the code base, while not being allowed to buy my own contribution
> afterwards ?
>
> Uwe
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] JS numbers to qint64

[Ilya Diallo]

2017-07-12 12:00 GMT+02:00 Konrad Rosenbaum :

> On Wed, July 12, 2017 11:53, Shantanu Tushar wrote:
> > and I see this output-
> >
> > qml: Opening 5762702576189441
> > Opening 5762702576189442
> >
> > As you can see the number changes. What am I doing wrong?
>
> ...you are using JavaScript numbers. All numbers is JS are 32bit floats,
> so naturally when you get to high numerical values you lose precision.
>

That's 64bits actually. For integers you're safe up to (2^53 -1), so the
OP's value should be ok as it's below that value.

Ilya.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Moving from Parse

[Ilya Diallo]

I'm using IBM Bluemix
<https://developer.ibm.com/clouddataservices/2016/01/29/parse-on-ibm-bluemix/>
for production, and a local server for testing. The local server is not
necessary, but it's very nice to have that option.

2016-03-29 11:10 GMT+02:00 Nuno Santos <nunosan...@imaginando.pt>:

> Ilya,
>
> Yes, there are a lot of Parse Server hosting options now. Which provider
> have you chosen? Or are you hosting your own server?
>
> Thanks,
>
> Nuno
>
> On 29 Mar 2016, at 09:16, Ilya Diallo <ilya.dia...@gmail.com> wrote:
>
> Hi,
>
> I use Parse Server <https://github.com/ParsePlatform/parse-server>, and this
> C++/QML client lib <https://github.com/a-team-fr/QtQML-BaaS>.
> There's tons of Parse Server hosting options available, and the Qt client
> lib  has served me well for getting data from the (also retiring) Qt Cloud
> Services db to Parse Server. It's in early stages but mostly working,
> contributions are welcome.
>
> Cheers,
>
> Ilya.
>
> 2016-03-28 23:03 GMT+02:00 Nuno Santos <nunosan...@imaginando.pt>:
>
>> Jason,
>>
>> What I really want to avoid is to manage my own servers. That takes me a
>> lot of time. I want to focus myself on doing development and not server
>> management.
>>
>> I also want that basic stuff such as users registration, registration
>> emails, etc to be provided by the backend already, otherwise I would need
>> to invest time in making my own.
>>
>> Regards,
>>
>> Nuno
>>
>> On 28 Mar 2016, at 20:55, Jason H <jh...@gmx.com> wrote:
>>
>> I'm not sure I see your problem. You're using Qt, you can use QJson*
>> classes, QNAM, and interop with these without issue.
>> I believe you can just use MongoDB, as a JS object store. I've not done
>> that though, but that seems the path of most resistence. I personally just
>> roll my own using Node/Express/Postgres (since the newer Prostgres has
>> JSONB datatype)
>>
>> *Sent:* Monday, March 28, 2016 at 2:12 PM
>> *From:* "Nuno Santos" <nunosan...@imaginando.pt>
>> *To:* interest <interest@qt-project.org>
>> *Subject:* [Interest] Moving from Parse
>> Hi,
>>
>> Since Parse announced it’s shutdown I have been looking for a pain free
>> and scaling solution.
>>
>> The most difficult problem is to find a baas/daas that has a C++ client
>> lib. All platforms out there only provide REST API as an alternative to iOS
>> and Android libs.
>>
>> Question: what are you people using for baas/daas of your Qt based
>> applications?
>>
>> Thanks,
>>
>> Regards
>>
>> Nuno
>> ___ Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>>
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>>
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Moving from Parse

[Ilya Diallo]

Hi,

I use Parse Server , and this
C++/QML client lib .
There's tons of Parse Server hosting options available, and the Qt client
lib  has served me well for getting data from the (also retiring) Qt Cloud
Services db to Parse Server. It's in early stages but mostly working,
contributions are welcome.

Cheers,

Ilya.

2016-03-28 23:03 GMT+02:00 Nuno Santos :

> Jason,
>
> What I really want to avoid is to manage my own servers. That takes me a
> lot of time. I want to focus myself on doing development and not server
> management.
>
> I also want that basic stuff such as users registration, registration
> emails, etc to be provided by the backend already, otherwise I would need
> to invest time in making my own.
>
> Regards,
>
> Nuno
>
> On 28 Mar 2016, at 20:55, Jason H  wrote:
>
> I'm not sure I see your problem. You're using Qt, you can use QJson*
> classes, QNAM, and interop with these without issue.
> I believe you can just use MongoDB, as a JS object store. I've not done
> that though, but that seems the path of most resistence. I personally just
> roll my own using Node/Express/Postgres (since the newer Prostgres has
> JSONB datatype)
>
> *Sent:* Monday, March 28, 2016 at 2:12 PM
> *From:* "Nuno Santos" 
> *To:* interest 
> *Subject:* [Interest] Moving from Parse
> Hi,
>
> Since Parse announced it’s shutdown I have been looking for a pain free
> and scaling solution.
>
> The most difficult problem is to find a baas/daas that has a C++ client
> lib. All platforms out there only provide REST API as an alternative to iOS
> and Android libs.
>
> Question: what are you people using for baas/daas of your Qt based
> applications?
>
> Thanks,
>
> Regards
>
> Nuno
> ___ Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtScript to QJSEngine migration

[Ilya Diallo]

Hi Julien,

A long thread on this list last march on this subject was concluded by
an answer from Frederik Gladhorn (copy below). For now (5.5), the best
is probably to postpone your migration if you want to avoid
unofficial workarounds. QtScript is not going anywhere until feature
parity is (more or less) achieved, with a porting guide for
incompatibilities.
Your proposals could be part of a porting documentation, though.

Ilya.


 Hello all,

 thanks for all the feedback, it's very much appreciated.
 The discussion has sparked quite a few discussions here in Oslo and we see
 that we have some way to cover when it comes to getting QJSEngine up to the
 level of what QtScript offers currently.

 We think being able to run non-gui applications is important, that's why we
 have a clean separation between the QML and Quick libraries. Using only the
 QML library there are no UI dependencies and QJSEngine is available as a pure
 JS engine without forcing any QML on anyone.

 We still think it's the right way forward - maintaining one engine and keeping
 it running well, instead of trying to deal with JSC, see Thiago's mails for
 the reasoning behind that (plus the one in WebEngine which is unrelated to
 this discussion).

 The deprecation is just the label that reflects reality for QtScript. There is
 no work being done on the module actively.

 The focus will now be to get the missing features in place in QJSEngine. Most
 of them hopefully by the time of the 5.6 release, to get the offering on par.
 It would be helpful to get a list of features that really need to be there,
 currently from what I understand the most urgent ones are:
 - instantiating QObjects from JS
 - exposing individual native functions to JS
 - debugging API
 The good thing is that a lot of the work is already done in QJSEngine, it's
 simply not exposed in the API yet.

 To re-iterate: QtScript is not going away, especially not before we have a
 full replacement including more porting documentation. But don't expect active
 development of the module to happen either. For many simple use cases,
 QJSEngine can act as drop in replacement by the way, so we do care about the
 migration path and try to keep API compatible where it is possible.

 Greetings,
 Frederik


2015-06-22 17:17 GMT+02:00 Julien Cugnière julien.cugni...@gmail.com:
 Hi all,

 With QtScript deprecated in Qt 5.5, and likely removed in a future
 version, I'm looking at how to migrate to QJSEngine. There are some
 things I'm not sure how best to achieve with the new minimalist API :

 1. Exposing a global function to Javascript from C++.

 In QtScript, one could write a C++ function with the signature 
 QScriptValue f(QScriptContext*, QScriptEngine*) , and expose it
 directly in a global variable. I found no equivalent in QJSEngine. If
 I understand correctly, I can only expose QObjects, so the best I
 could come up with is the following :

  * write my functions as Q_INVOKABLE members in a QObject.
  * expose that QObject using QJSEngine::newQObject.
  * iterate over the object with QJSValueIterator, and copy the
 function properties to the global object.

 Is there a better way available, or planned ? If not, would a merge
 request to add the above to the documentation be accepted ? (probably
 somewhere in Making Applications Scriptable).

 2. Writing a variadic function from C++.

 In QtScript this could be done with the QScriptContext* parameter.
 With QJSEngine, the best I've come up with is this :

  * write a wrapper function in javascript forwarding the arguments object :
 function foo() { return Foo.foo_impl(arguments); } 
  * write foo_impl in C++ as a Q_INVOKABLE member taking a single
 QJSValue parameter.

 Is there a better way ? And again, is this worth adding to the documentation ?

 3. How to raise a Javascript error from a function implemented in C++.

 This is basically https://bugreports.qt.io/browse/QTBUG-39041, which
 has seen no comment for the past year. Is something similar planned ?
 Otherwise the only solution I see is again a wrapper function written
 in Javascript. Something like this :

 function foo() {
var res = foo_impl();
if (Object.getPrototypeOf(res) === Error)
 throw res;
else
return res;
 }

 --
 Julien Cugnière
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] double-buffering, quality drop

[Ilya Diallo]

Not sure it's related, but that reminds me of that old issue:
https://bugreports.qt.io/browse/QTBUG-25896
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Report designer for Qt

[Ilya Diallo]

Hi Muhammad,

Feel free to ask me if you have questions about OpenRPT (code or usage).
The docs are a little bit outdated, some features are not listed.
And please tell me if you start a Qt 5 port, i was planning to work on it
too.

Ilya.


2013/4/8 Muhammad Bashir Al-Noimi mbno...@gmail.com

  On 04/04/2013 04:33 PM, Bo Thorsen wrote:

 There are literally thousands of different types of components that
 could be useful in some projects. It's impossible for Qt to try and
 deliver all of them. That's the reason it won't happen.

  As I said to André before, Report designer is an important tool in many
 database based application for that many commercial environment ship it by
 default (ex. Microsoft Visual Studio and Embarcadero Delphi)

 Every report designer has two major parts, report engine and GUI designer
 so I think it can embedded in Qt project as following:

- Report engine as Qt Add-on works with Qt SQL and Qt Print Support
 - GUI designer as Qt tool works as Qt Creator plug-in in same way of
Qt Designer works.

 eXaro https://sourceforge.net/projects/exaro/ and 
 OpenRPThttps://sourceforge.net/projects/openrptthe most respect open source 
 solution in this field.

 PS
 Currently I'm do some tests on OpenRPT and eXaro and I'm planning to
 convert one of them to Qt5.

 --
 Best Regards,
 Muhammad Bashir Al-Noimi


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Report designer

[Ilya Diallo]

2013/1/5 M. Bashir Al-Noimi mbno...@gmail.com

  On 04/01/2013 10:42 م, M. Bashir Al-Noimi wrote:

 Well I used OpenRPT before with PostBooks and it has two problems:

1. It works with Postgresql only (I think).

 No, it works with other databases as well. It can even work without any
external database, by embedding the data into the report, or by adding xml
data during the document rendering.
In that case, it creates a SQLite database in memory.


1. It's complicated for end user (in case comparing with CrystalReport
of FastReport).

 It depends of the use case and your SQL knowledge (you might have to
create complex requests).
The documentation is not up to date, but if you have specific questions or
problems i can help you.

Ilya.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Report designer

[Ilya Diallo]

Hi,

NCReport is a commercial product. For a well tested open source tool, see
for instance OpenRPT (http://www.xtuple.com/openrpt).
NB OpenRPT is now bundled in the xTuple ERP installer, but you can select
only the standalone OpenRPT during the install.

Ilya.

2013/1/3 Tony Rietwyk t...@rightsoft.com.au

 Hi Muhammad, 

 ** **

 We use http://www.nocisoft.com/ncreport.html.   It integrates easily and
 does basic reports well.   We use some of the advanced features
 (scripting), but not master-detail so can't comment on that.   The support
 is first class - problems are usually addressed within 24 hours!  

 ** **

 Regards, 

 ** **

 Tony

 ** **

 ** **

 *From:* interest-bounces+tony=rightsoft.com...@qt-project.org [mailto:
 interest-bounces+tony=rightsoft.com...@qt-project.org] *On Behalf Of *Muhammad
 Bashir Al-Noimi
 *Sent:* Thursday, 3 January 2013 7:22 PM
 *Cc:* developm...@qt-project.org; interest@qt-project.org
 *Subject:* Re: [Interest] Report designer

 ** **

 On 01/02/2013 06:13 PM, Muhammad Bashir Al-Noimi wrote:

 Hello guys,

 Could anyone guide me to best open source database report designer for Qt?

 PS
 I found many designers but I want a tested designer.

 I found these designers but I'm not sure what's best or what if there is
 better
 http://sourceforge.net/projects/qtrpt
 http://exaro.sourceforge.net/


 


 -- 

 Best Regards

 Muhammad Bashir Al-Noimi


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest