[Development] Qt3D Examples

Oswald Buddenhagen oswald.buddenhagen at theqtcompany.com
Tue Oct 14 11:19:01 CEST 2014

On Tue, Oct 14, 2014 at 09:34:47AM +0100, Sean Harmer wrote:
> On 14/10/2014 08:01, Koehne Kai wrote:
> >
> >> -----Original Message-----
> >> From: development-bounces+kai.koehne=theqtcompany.com at qt-
> >> [...]
> >> I don't have an "authoritative" answer, but one possible option would be an
> >> sub-module that contains the assets for examples or (easier?) separate the
> >> Qt 3d examples and their assets into a standalone git repository.
> > Keep in mind though that this will only help users that clone & build from git. People using the tar balls, prebuilt binaries , will still suffer, because (at least so far) we split up only the toplevel repositories .
> >
> > I'm not sure how 'big' big is in your case, but if it's an issue I'd rather go for another toplevel module . IMO there's a much better chance also e.g. Linux distributions will package this separately.
> Good point. This would then be analogous to the webkit-examples repo 
> too. It also means we can keep some simple light-weight examples in the 
> main Qt3D repo.
> Could I kindly propose, and if approved, request the creation of a 
> qt3d-examples module please? Is it sufficient to do that here or do I 
> also need to file a sysadmin JIRA task?
i'm not such a fan of the whole idea. it's basically a zero-sum game -
when it's linked in the supermodule, people will have to download it
anyway. the one thing that would work is *not* making it part of the
default checkout, which implies that it would not be part of CI, and
thus also not part of releases. that sounds entirely backwards to me.

what would be closer to being sensible would be externalizing only the
data, and making it an optional submodule of the qt3d repo. of course
that means that you'd have to provide minimal data sets in the main
repo, so the examples would be sufficiently self-contained, even if not
looking all that great.

also, about how much data are we actually talking here?

More information about the Development mailing list