so this is the next request and it makes more sense to me:
you (the designer) like to have an Hype-exportscript that handles AdWords-Exports in a way that the @2x-files would not appear
Why not but ads could not be the only case where we would like to have assets being the smallest possible.
just to mention: tools like imageOptim have a much better compression for images than Hype does
It's amazing that I need to make a video to explain why it's an issue and why designers waste time optimising manually in Photoshop a source image and creating a version for each size of an ad.
They could just
– use one source, crop/resize all instances of the image at will on all the sizes,
– enable the optimisation,
– and disable an option generating @2x versions of the images so only the standard version is exported.
everybody got your point (even before the video 
)
possible solutions:
- Hype creates an extra option in its UI
- an exportscript is used that handles it
- just add @MarkHuntes script to the ads an delete the @2x-file in the export
//////
if it comes to a condition for best optimized images i'd never rely on photoshop (you did not even use the special webexport for PS-Optimization) or hype alone.
as mentioned imageOptim will reduce the size much better and in very good quality.
////
cropping in Hype does not exist. so it'll never export a cropped image
2 Likes
Thank you but I didn't use it because he didn't explain what to do.
I think I understood I needed to put the code in the Head of the document but he didn't explain that we can then freely remove the @2x versions in the exported folder.
Problem with that technique:
- We need to unzip the folder.
- Reach the @2x file and delete it.
- Rezip the folder.
Doing that for all sizes? Not efficient.
That's it.
As @h_classen says,
Pretty sure we understood what you wanted way back in the thread.
You did NOT need to make a video!. to be honest you are inmo bordering on insulting.
And you dont need to keep explaining... and maybe try to understand that it has been taken on board.
This community does not always leave it at ' ok understood', we often try and give work arounds in the mean time
The code I actually posted would work in a Hype function. But was actually intended to go in the export script it was written as as a proof of concept while I had a spare minute and is half the code possibly needed.
The second half would be for the export script to auto remove the 2x files. This may come if I or someone else chips in.
Which would give you a workaround which would not have you manually doing the full workflow.
1 Like
The whole point of export script is to put the individual pipeline and workflow requirements into external places. I have seen Hype in very custom setups and workflows at this point, so people are using Hype as a drop in IDE for individual production chains. Hence, every idea and change surely needs to be considered carefully as not everyone is using Hype the same way. Not judging or referencing this feature request in particular. In general with an upcoming package 
approach this will become much more modular, but it still will require installing stuff. But as a designer one doesn’t need to understand what is installed as most anyway don’t understand the code that is behind their daily apps. Installing stuff is only necessary on the machine building the animation and clients don’t have to install anything apart from a browser 
2 Likes
Topic open in January 2017, 4 years ago.
Yes it was and in 2017 is was made clear that it was understood.
I am specifically talking about your attempts to explain again and again..
There is nothing wrong with refreshing a request for a feature if it appears there is no movement.
It often does illicite a response from the Hype team to responed one way or another.
And from my perspective you have had that in buckets.
Please lets take a step back and see if someone picks up on the coding for the export script.
If not from the community then at some point and in some form possibly from the Hype Team.
And note I do not speak for them but I have read the response you have had.
1 Like
added @MarkHuntes snippet to the adWords and excluded placing the '2x'-file to the zip.
may work, not well tested ... (just in Desktopsafari responsive tests ...)
AdWords_nonRetina.hype-export.py.zip (3.9 KB)
please avoid having the '2x.' within a filename you'll like ti include though
2 Likes
Thank you!
On my side, it works and it's a major step forward in making Hype a great tool to produce Google Ads.
Can this be shared?
1 Like
oh no, please not those heavily tears of joy 
at own risk ... i'd say
2 Likes