custom image library

[Johnny Jazeix]

Hi,

yes, it would be nice to be able to load images from a local folder
(we already have a task for audio:
https://phabricator.kde.org/T10569).

This way, users can customize the images, potentially depending on the locale.

Johnny

Le jeu. 12 mars 2020 à 15:09, Timothée Giet <animtim at gmail.com> a écrit :
>
> Hi,
>
> Thanks Emmanuel for raising this question.
>
> First, about the "custom image directory", I think that's a good idea,
> that fits the plans we already discussed to bring back the feature from
> the old gcompris that allowed to easily change the pictures frome an
> activity by just placing some images in a specific folder.
>
> That part is quite agreed upon, the tricky bit is to integrate it.
>
> But about the proposal for "A private image directory containing all the
> GCompris official images", I don't think I would like this: I find it
> much more convenient when working on an activity to have the assets of
> that activity in the resource folder next to the code. Putting instead
> all images in the same place would make it much harder to work on my
> side... It's like if you proposed to put all the code files of every
> activities in the same place (imagine how messy it would be ;) ).
>
> Sure there are a few images which are used from one activity to another,
> but still I would not like to change the way they are ordered now.
>
> Timo.
>
>
> Le 12/03/2020 à 10:58, Emmanuel Charruau a écrit :
> > Hi everybody,
> > Would it make sens to have image libraries.
> > A place in gcompris where users could be placing their own images to
> > be usable through multipledataset.
> > And why not a private image library (in the sens of programming where
> > private says that you can not access it from outside, if you are not a
> > gcompris developper)?
> >
> > Lets take the mosaic example.
> > At the moment everything is hard coded in the js, image names and even
> > variables I don't understand so far "multipledataset1 and 2" but this
> > is an other story.
> >
> > Could we not tend to a more flexible architecture:
> >
> > A private image directory containing all the GCompris official images,
> > we place them here we know what they are, we know their licences for
> > sure and we test if they are present or not to be sure all activities
> > are working well"
> >
> > A custom image directory containing users images, we do not care what
> > they are, the content is up to the user and the content will be
> > controlled by the server.
> >
> > Why doing that now.
> >
> > 1-Robust and flexibility
> > If at the moment we want to change an image in mosaic we have to
> > modify the code, which is not a good idea. If we use a private image
> > library we would just have to add the image to the private library and
> > use its name in the multipledataset json file. Our mosaic activity
> > becomes more flexible and more robust.
> >
> > 2- planning the future server architecture
> > If we change now the way we access images, the mecanisme will already
> > be ready for a custom server mode where users could upload custom
> > images to a custom directory and use them in their own dataset
> >
> > 3- Sharing images
> > If we put all the images at the same place developpers could see all
> > of them and reuse images they even did not think they had within
> > gcompris.
> >
> > Thanks for your thoughts :)
> >
> > Emmanuel
>
>
>