H,
>
>Thanks Casper. You didn't mention examples, but the wiki says they go to
>the examples directory.
>
I explicitly left out mentioning examples, because they are a mess.
Most of the current examples/example documentation need to be re-written,
since they all link to widgets, or their document
Hi all,
Laszlo wrote:
>
>> I am missing the recommendation for certain folders in there, like
>> 1) doc: probably most important since modules should be documented.
>> 2) examples: this is probably also important because examples would be
>> nice to have for the add-on modules as well.
Casper wr
Hi,
> I am missing the recommendation for certain folders in there, like
> 1) doc: probably most important since modules should be documented.
> 2) examples: this is probably also important because examples would be
> nice to have for the add-on modules as well.
I edited the location for doc to b
On sexta-feira, 20 de abril de 2012 18.40.15, Laszlo Papp wrote:
> Hi,
>
> Sorry for bringing this thread up again, and my sincere apologize, if
> this is not the best way to come up with a new realization.
>
> [...]
>
> > https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
>
> http://
Hi,
Sorry for bringing this thread up again, and my sincere apologize, if
this is not the best way to come up with a new realization.
[...]
> https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt#The_structure_of_a_new_mo
rover Status (David Laing)
--
Message: 1
Date: Tue, 13 Dec 2011 17:54:01 +0200
From: Laszlo Papp
Subject: Re: [Development] How to create new Qt modules or tools
To: Rohan McGovern
Cc: development
Message-ID:
Content-Type
On Tuesday, 13 de December de 2011 17.54.01, Laszlo Papp wrote:
> Hi Rohan,
>
> > Security is a potential issue for providing the same test resources
> > used for the main Qt modules to be also used against playground
> > modules. These test machines are Internet-connected[1], and arbitrary
> > co
Hi Rohan,
> Security is a potential issue for providing the same test resources
> used for the main Qt modules to be also used against playground
> modules. These test machines are Internet-connected[1], and arbitrary code
> can be set up to run on them; lowering the barrier for getting this
> ar
hi,
On Tue, Dec 13, 2011 at 3:41 PM, wrote:
> It makes sense to have the discussion on the development mailing list, and
> then create a JIRA task for the new Gerrit project. This makes the process
> independent from anybody's email addresses or new mailing lists. Do you think
> this would wo
unces+marius.storm-
>> olsen=nokia@qt-project.org] On Behalf Of ext Laszlo Papp
>> Sent: Monday, December 12, 2011 5:08 AM
>> To: craig.sc...@csiro.au
>> Cc: development@qt-project.org
>> Subject: Re: [Development] How to create new Qt modules or tools
>>
>&
On Monday, 12 de December de 2011 16.27.40, Laszlo Papp wrote:
> This topic brings my next question: what about projects migrating to
> Qt Playground, but had been using doxygen rather than qdoc?
qdoc is recommended, of course.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Archit
On Mon, Dec 12, 2011 at 3:09 PM, wrote:
> What is it that you require to upload the results to a cdash, and why
> wouldn't qmake be able to do so?
> I thought cmake simply ran cdash to upload the results, and certainly qmake
> can easily add the rules for doing the same?
>
> What's the command
...@qt-project.org] On Behalf Of ext Laszlo Papp
> Sent: Monday, December 12, 2011 5:08 AM
> To: craig.sc...@csiro.au
> Cc: development@qt-project.org
> Subject: Re: [Development] How to create new Qt modules or tools
>
> > I really like the model of enabling the community to sub
> I really like the model of enabling the community to submit build results to
> a central dashboard. It allows those with an interest in a particular
> platform/compiler combination to put in the initial setup work and have their
> combination included in the automated build/test infrastructure
On 12/12/2011, at 4:59 PM, Rohan McGovern wrote:
> Laszlo Papp said:
>>
>> 1) Build and software testing service
>> Is there a build and software testing service provided for projects in
>> the Qt Playground repositories ? I have not seen any mentionings about
>> that so far. and it is an import
Laszlo Papp said:
>
> 1) Build and software testing service
> Is there a build and software testing service provided for projects in
> the Qt Playground repositories ? I have not seen any mentionings about
> that so far. and it is an important question in my case, for instance.
> I have been using
Hi Henry,
Thank you for your quick reply.
> The instructions were written with brand new projects in mind, but I agree we
> need to consider existing projects that move to Qt Project. The contribution
> agreement needs some special consideration here, so I'll work with Cristy on
> making that
Hi,
>>> Send your request for a new Playground project (including project name
>> and description) to the Qt maintainer from whom you have pre-approval.
>>> CC to sergio.ahumada at nokia.com and Gerrit Expert Group (email address
>> TBD).
>>
>> I think I'd prefer to see this on an infra@ type list
> From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of ext
> Just to clarify what I mean here - I don't envisage most of these will require
> much discussion. It just provides the capability for it if it's necessary.
> Just look
> at the approver nominations so far - there's not rea
On Fri, Dec 9, 2011 at 6:16 PM, wrote:
>> Having these on a list also mirrors the structure for approval nomination.
>>
>
> I think it'd be important to keep the barrier very low. It should be possible
> to start competing or crazy projects. So this approval from a Maintainer
> shouldn't usuall
Hi Robin,
> From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of ext
> Robin Burchell
> > Agree with a Qt maintainer that s/he will approve your new playground
> > project
>
> Can we agree that this approval should be done on development@? That
> way, the discussion around the sugg
Hi Laszlo,
> If a developer would like to move a project that is started as "QtX", I should
> rename it to "Y" or something like that, and then back again to "X" ?
> Practical
> example: QtOpenaL (coming for instance from a KDE
> repository) -> "3D Audio" (Qt Playground) -> QtOpenAL (Qt Final)
T
On Friday, December 09, 2011 14:00:13 Laszlo Papp wrote:
> > https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
> >
> > Choose a descriptive playground project name. The name should not
> > include "Qt". For example "Extra Effects", "Mime Types"
> If a developer would like to move a
Hi Henry,
On Fri, Dec 9, 2011 at 10:18 AM, wrote:
> This page introduces the Qt Project playground (a low-barrier area for
> experimenting with new ideas), gives some naming guidelines for modules
> and tools, and documents the module repository structure.
Thanks for getting this started. I hav
Hi Henry,
> https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
> Choose a descriptive playground project name. The name should not include
> "Qt". For example "Extra Effects", "Mime Types"
If a developer would like to move a project that is started as "QtX",
I should rename it to
Hi all,
So far it has not been clear how you could start working on a new module
or tool in the Qt project. We've now created a wiki page for this
information here:
https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
This page introduces the Qt Project playground (a low-barrier are
26 matches
Mail list logo
