> I didn't know who to assign it to or even that I should assign it to
someone.
I am sure I have not assigned anyone explicitly, and it worked out of the
box. Perhaps I was just lucky.
http://qt-project.org/wiki/Creating-a-new-module-or-tool-for-Qt#6a17de784cf6db9124e9844959ec8ace
In my opinion o
> From: Ahumada Sergio
> To: development
> Sent: Wednesday, December 12, 2012 2:19 AM
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>
>>
>> As I know others have expressed interest in helping out, here's the
>> bug
>
> As I know others have expressed interest in helping out, here's the
> bug report in case you want to join/watch:
>
> https://bugreports.qt-project.org/browse/QTQAINFRA-584
>
> Ben
>
>
> Does it usually take this long? I understand the RC is being released,
> but it doesn't
On Wed, Nov 28, 2012 at 11:11 AM, BRM wrote:
> > From: BRM
>
> > Sent: Monday, November 26, 2012 9:39 PM
> > Subject: Re: [Development] Qt Playground - Updating Daemon/Service
> Support
> >> From: Matt Broadstone
> >> Subject: Re: [Developmen
> From: BRM
> Sent: Monday, November 26, 2012 9:39 PM
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>> From: Matt Broadstone
>> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>> On Mon, Nov 26, 2012 at 1:4
> From: Lukas Geyer
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
> Am 27.11.2012 11:03, schrieb Sascha Cunz:
>> [...]
>>> The difference is that 'operate' and 'configure' are
> two different tasks
>>> and
Am 27.11.2012 11:03, schrieb Sascha Cunz:
> [...]
>> The difference is that 'operate' and 'configure' are two different tasks
>> and thus usually require two different interfaces.
>>
>> The 'operate' interface of an anti-malware service is to monitor data
>> and network traffic. The 'configure' int
On 27/11/12 8:03 PM, Sascha Cunz wrote:
>> Qt already allows to serialize any datatype known to the meta type
>> system, provides means for IPC (D-Bus is just one example) and has a
>> code generator which implements our objects (moc) and allows for
>> handling asynchronous signals and slots.
>>
>>
[...]
> The difference is that 'operate' and 'configure' are two different tasks
> and thus usually require two different interfaces.
>
> The 'operate' interface of an anti-malware service is to monitor data
> and network traffic. The 'configure' interface is most probably a
> seperate application
Am 27.11.2012 08:50, schrieb Sascha Cunz:
>> Yes. Each service which needs to interact with the user requires some
>> sort of IPC to provide a graphical interface, as interactive services
>> are not allowed on most modern operating systems (not to mention design
>> considerations).
> As you said: t
Am Dienstag, 27. November 2012, 08:16:20 schrieb Lukas Geyer:
> Am 27.11.2012 06:15, schrieb Sascha Cunz:
> >> A daemon/service has two interfaces: (i) user/system-API oriented, and
> >> (ii)
> >> one internal.
> >>
> >> The first presents the interface to the outside world on how to control
> >>
Am 27.11.2012 06:15, schrieb Sascha Cunz:
>> A daemon/service has two interfaces: (i) user/system-API oriented, and (ii)
>> one internal.
>>
>> The first presents the interface to the outside world on how to control the
>> service. This interface needs to integrated into the system - e.g. Windows
>
m Montag, 26. November 2012, 20:36:47 schrieben Sie:
> - Original Message -
>
> > From: Sascha Cunz
> > Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
> >
> >> All services/daemons must be able to interface with other pr
- Original Message -
> From: Sascha Cunz
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>
>> All services/daemons must be able to interface with other processes:
> Here, I almost agree :-)
>
>> (a)- a "client-process&quo
> All services/daemons must be able to interface with other processes:
Here, I almost agree :-)
> (a)- a "client-process" can "request-a-client-operation" to occur on that
> service/daemon
But this is totally orthogonal to the application being a daemon/service. To
some daemons your applicatio
> From: Matt Broadstone
>Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>On Mon, Nov 26, 2012 at 1:48 PM, BRM wrote:
>> From: Charley Bay
>Is there any word on whether you guys get a spot in playground?
Since Thiago +1'd, I think I'm g
> From: Charley Bay
>Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>
>
>Hi, Matt--
>
>
>thoughts:
>>
>>
>>a) I think the only reason the old QtService uses a template based approach
>>is to support the different
Hi, Matt--
thoughts:
>
> a) I think the only reason the old QtService uses a template based
> approach is to support the different types of Q*Application. It would be
> quite useful to have someone who worked on the original solution discuss
> why they went with this approach rather than subclassi
On Mon, Nov 26, 2012 at 1:48 PM, BRM wrote:
> > From: Charley Bay
>
> >On Mon, Nov 26, 2012 at 10:40 AM, Matt Broadstone
> wrote:
> >
> >On Mon, Nov 26, 2012 at 12:01 PM, Charley Bay
> wrote:
> >>
> > " Component >,
> >> I would like to open a new Qt Playground project to create a new
> From: Charley Bay
>On Mon, Nov 26, 2012 at 10:40 AM, Matt Broadstone wrote:
>
>On Mon, Nov 26, 2012 at 12:01 PM, Charley Bay wrote:
>>
> " Component >,
>> I would like to open a new Qt Playground project to create a new
>> equivalent
>>>
>>>
>>>+1
>>>
>>>IMHO this would be a cr
On Mon, Nov 26, 2012 at 10:40 AM, Matt Broadstone wrote:
> On Mon, Nov 26, 2012 at 12:01 PM, Charley Bay wrote:
>
>> >>> " Component >,
>> >>> I would like to open a new Qt Playground project to create a new
>> equivalent
>>
>> +1
>>
>> IMHO this would be a cross-platform useful module that I'd vo
> From: Matt Broadstone
>On Mon, Nov 26, 2012 at 12:01 PM, Charley Bay wrote:
>
" Component >,
> I would like to open a new Qt Playground project to create a new
> equivalent
>>
>>
>>+1
>>
>>IMHO this would be a cross-platform useful module that I'd vote to ultimately
>>end-up w
On Mon, Nov 26, 2012 at 12:01 PM, Charley Bay wrote:
> >>> " Component >,
> >>> I would like to open a new Qt Playground project to create a new
> equivalent
>
> +1
>
> IMHO this would be a cross-platform useful module that I'd vote to
> ultimately end-up within "Qt-proper".
>
> Disclosure: I tr
>>> " Component >,
>>> I would like to open a new Qt Playground project to create a new
equivalent
+1
IMHO this would be a cross-platform useful module that I'd vote to
ultimately end-up within "Qt-proper".
Disclosure: I traded emails with BRM off-list, and would like to help.
--charley
__
> From: Matt Broadstone
>On Mon, Nov 26, 2012 at 10:13 AM, Thiago Macieira
>wrote:
>
>On segunda-feira, 26 de novembro de 2012 06.59.23, BRM wrote:
>>> I am following up to some e-mails I sent on the feedback/interests/dev
>>> lists[1] and blogs[2] over a year ago for updating the QtService Com
On Mon, Nov 26, 2012 at 10:13 AM, Thiago Macieira wrote:
> On segunda-feira, 26 de novembro de 2012 06.59.23, BRM wrote:
> > I am following up to some e-mails I sent on the feedback/interests/dev
> > lists[1] and blogs[2] over a year ago for updating the QtService
> Component.
> >
> >
> > I would
On segunda-feira, 26 de novembro de 2012 06.59.23, BRM wrote:
> I am following up to some e-mails I sent on the feedback/interests/dev
> lists[1] and blogs[2] over a year ago for updating the QtService Component.
>
>
> I would like to open a new Qt Playground project to create a new equivalent
>
I am following up to some e-mails I sent on the feedback/interests/dev lists[1]
and blogs[2] over a year ago for updating the QtService Component.
I would like to open a new Qt Playground project to create a new equivalent for
Qt5 that is more natively integrated.
Synopsis: QtService Componen
28 matches
Mail list logo
