[Interest] FW: Qt Service Framework- Will it ever be a part of Qt again?

[Miller, Doug]

I was time contrained in my last response so here are more comments about it.

The other advantages we saw to using the SFW technology was the: 

---service discovery mechanism (same mechanism for in-process services and out-of process, and we did not have to invent our own)

---QObject based plug-in concept (services appear as QObjects to the application)

---Sevice communication transport mechanism is transparent to application (communication is via signal/slot, invokable method, or porperty just like any other QObject)

---Transport mechanisms have the potential to expand from QLocalSockets/DBus to types that could be across machine boundaries.

---services can easily be private or shared to support whatever the context of the application may require.

We initially decided to build our product on the SFW when we saw that it went from two rounds as the Mobility Project to Qt mainstream.   Now we are considering using SFW in a new version of the product that would be at an enterprise level.  The new products key requirement  is to  have an Open System Architecture which I think a plug-in technology like SFW would help us achieve.  Having SFW outside the of the Qt of the mainstream does not help us in our claim that we should use it.

In my opinion, having this products as mainstream again will increase use of it.


Thanks,

Doug Miller


________________________________________
From: Miller, Doug
Sent: Thursday, July 18, 2013 5:04 PM
To: Lorn Potter
Cc: interest at qt-project.org
Subject: RE: [Interest] Qt Service Framework- Will it ever be a part of Qt again?

We have a large GUI application that is developed with Qt for portability.  Before we ported to a pure Qt solution our GUI application was based on KDE.  We used the KPart technology to componentize our dialogs.  Dialogs were loaded dynamically to support the context in which the main GUI was executing.

Now we use Qt Service Framework technology to componentize our dialogs and we load them in dynamically as out-of-process services.  This frees up the event thread and gives us better fault tolerance.
The number of components we have is about 30 and we too have commericial licenses.

Thanks for asking,

Doug Miller

________________________________________
From: Lorn Potter [lorn.potter at gmail.com]
Sent: Thursday, July 18, 2013 4:21 PM
To: Miller, Doug
Cc: interest at qt-project.org
Subject: Re: [Interest] Qt Service Framework- Will it ever be a part of Qt again?

On 09/07/2013, at 4:46 AM, "Miller, Doug" <dmiller at JFTI.com> wrote:

> Since Qt5 Alpha we have been working with the Qt Service Framework.  By the time Qt5 Beta 2 came out our whole product base (which is large) was using it.  We saw many advantages to using it.

I'd like to hear more about this.

>  If it had been able to stay with the Qt mainstrean I'm sure there would been additional improvenments to it.  But now Qt5.1 has been released without it and I see no plans in the near future to add it back into the mainstream.  I know that, for sure, that there are business reasons (i.e. lack of manpower/money) why it has not been picked up again.
>
> Here are my questions.  Does Digia see an added value in having the Service Framework? If manpower/money were not an issue would the Service Framework be brought back in or would there be anther implementation to provide it functionality?  I'm thinking that if it has business and technical merit then there is hope for it, and therefore I will continue using it.
>
> Please provide some feedback that I can use in my decision making.
>


Alex has started making backlogs for the modules not included. Perhaps you want to start one for serviceframework?
See this one for QSystemInfo:
https://bugreports.qt-project.org/browse/QTBUG-31624

I don't see one for service framework yet.

https://bugreports.qt-project.org/issues/?jql=component%20%3D%20%22Systems%3A%20ServiceFramework%22%20AND%20project%20%3D%20QTBUG


It's really a question of developer interest and finding someone to maintain/work on it.
I'm glad to hear someone is using this module, and I am glad you spoke up about it before it really went away.


> Thanks.
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

Lorn Potter
QtSensors/QtSensorGestures/QtSystemInfo
llornkcor technologies / Jolla Mobile