Image aspect generation.


Using Guise Mesh () is working well to generate image galleries, but the problem is that even with scaled images (), the image files will still be too big for many connections for a large gallery page to download them all to show as previews. We need a way to generate image previews, but some general way that fits into the Guise Mummy system.




Garret Wilson
January 30, 2021, 4:38 PM

There is always the decision of singular or plural for the "collections", i.e. mummy.image.aspects.preview.scaleMaxLength or mummy.image.aspect.preview.scaleMaxLength. I almost went with mummy.image.aspect.preview.scaleMaxLength, but I think mummy.image.aspects.preview.scaleMaxLength is clearer that this is the point that the aspects are being defined, even though it could be confused with "withAspects".

When actually developing this, I found myself actually typing the form mummy.image.aspect.preview.scaleMaxLength}}—with the singular form—so perhaps that is more natural for the configuration key form. But it doesn't make as much sense in the configuration file, although I realize now that we are using the singular with the {{image and page sections. I'll switch to the singular and see how that goes.

I think the singular form seems more appropriate as a configuration key, because settings are thought of as "noun.setting=value". So if we identify the noun, we use "noun.adjective=value" or "noun.adjective.adjective=value". In this case we are setting the "scaleMaxLength". Which one? Of the "aspect". Which aspect? The preview aspect. Which preview aspect? Of the image. So …image.aspect.preview.scaleMaxLength. I suppose we aren't so much talking about a hierarchy of resources and subresources as we would be in RESTful API or in an URF graph. So here again I suppose the configuration model takes precedence over the underlying implementation.

Your pinned fields
Click on the next to a field label to start pinning.


Garret Wilson


Garret Wilson