I’m hanging on to the info of the freshest update here, first without forgetting to mention that I really appreciate your work on Foundry 3. But I would also like to mention that the reworking of many of my projects will cost me a lot of work - even if Foundry 2 still exists - but it makes no sense at all to use both versions in the long run - too different in approach and not practical in day-to-day business. In german there is a saying: “I swallowed the toad”.
To the actual reason for my contribution here. Like many of us, I am in the learning phase of Foundry 3 (Weaver since version RW 3). First of all I had a look at your extensive starter sets (partly 120 MB each) - and then - BANG - my CPU started up and I found over 200 images in my AppSupportFolder/Stacks5 which immediately grew up to 1 GB. Hardly any of these pictures I found in your Kits, partly pictures over 7 MB of playing children in school…?
Ok, in Isaiah’s announcement in the old forum to beta-version 5 we had this discussion about the multiple bloated folders - which are still not corrected - but we know why it happens…!
It is the “SharedPluginData/Contents.plist” file, which has grown up to 6 GB for me due to transferred Partials/Externals.
So my question, does this only happen to me? (MPB2016, RW8, Stacks5 - latest) I can not imagine this! So why do these starter sets have this file size? I cleaned them up in the ProgramSandwich and used “remote” images instead of drag and drop everywhere I could - since I don’t think it’s contemporary anymore - especially since the images get a different name. All starter sets now have only 1/10 of the file size, the fan stays off, peace returns and I can concentrate on the learning phase.
So if possible, I would like to wish two things for an upcoming update? When first working on the starter sets, I found it surprising, since such an important tool as for the images, has now been divided into three stacks, and why so complicated…?
Example: If I leave out the Drag&Drop version, I find a “Remote” with link to .jpg and its Retina and a new stack “Webp” with .webp, webpRetina and a fallback to .jpg and FallbackRetina…
Wouldn’t it be possible to get by with one version? In one of my cases I now have the task to enter a link 400x for 100 pictures, which I would like to avoid. Here a link is enough, e.g. to “…picture.webp” and if desired, there is also the retina version “…picture2x.webp” and should the browser not be able to display this, the fallback “…picture.jpg” and its retina version “…picture2x.jpg” This has worked in the past and the files can all be processed in batch and stored side by side on the server in one folder.
Ok, I’m not a programmer for web programs, but my experience from complex filemaker-scripts go like this - either/or…!
If I could express one more wish. There was in Foundry 2 the stack “Hover”. This already had a remote function - now I find in Foundry 3 the wonderful extension “Whimsy”. But where is the remote function gone? I like this overlay function, especially when presenting teams or projects, but if the drag&drop properties change the image names, both the optimizations (webp/jpg) are obsolete and it limits the possibilities, e.g. via “QuickEditor” of 1LD to exchange images and names/titles.
Sorry, my contribution has become longer - but I’ve been carrying my thoughts around with me for a few days now and it shouldn’t come across as criticism here. As I said, I - as well as many here - we appreciate your work very much, but website creation is often a very lonely work, since the thoughts turn sometimes only in circles…