Попробую с другой стороны объяснить 
Есть два грандиозных каталога, каждый по несколько Гб. Тематика их разная, но структура — довольно схожая. Я бы привел их внешний вид, но сейчас я на тестовом диске — настраиваю новую для меня ОС и Firefox в числе некоторых других новых для меня приложений тоже, так что простите — но пока получится только на словах.
Для примера всё тот же Woodwork. В нем находится n-ное количество каталогов (страны). Их — немного, относительно. Внутри каждой страны находится уже много каталогов, по тематике. Я — плотник, и для меня важно что мм… скажем угловое соединение бруса, угловое соединение доски, поперечное соединение бруса, и доски, и еще десятки разных других. Для каждого — отдельный каталог. + Различные типы каркаса — американский, европейский, японский, русский… в общем — когда нужно что-то конкретно найти — находится очень легко, хотя и выглядит устрашающе. Думаю, общая схема понятна.
Теперь расскажу, как я сохранял это из Chromium и почему важен именно счетчик в самом диалоговом окне сохранения. Дело в том, что на одной странице одного и того же сайта, могут быть представлены разные изображения, т.е. разные тематики изображений. В контексте статьи — они связаны, но я сохраняю не страницу, а изображения и они должны попадать в разные каталоги. Так вот, я вызывал на изображении контекстное меню, выбирал "Сохранить как", появлялось окно в котором я либо выходил из каталога и выбирал нужный, либо там же сохранял. При этом — если файл 01.jpg уже был — Chromium предлогал уже готовое имя 01 (1).jpg, аналогично, если уже все файлы повторяли друг друга — 01.jpg, 01 (1).jpg — 01 (35).jpg, то он предлогал 01 (36).jpg. Согласитесь, если довольно большой объем одинаковых файловых имен, то листать и вручную изменять каждый раз — совсем неудобно, плюс — это занимает время, если это пару файлов — ерунда, если это сотни файлов — часть которых всё же придется переименовывать — уже занимает время.
В Firefox я столкнулся с тем, что он тупо хочет записать поверх имеющегося. Прежде чем обратиться на форум за помощью, я поискал самостоятельно аддоны. Которые мне казалось, что могут помочь, по их описанию, я устанавливал. Но то ли я глупый и не смог их настроить, то ли они не подходили, суть не изменилась — при сохранении из контекстного меню "Save Image As…" — какое либо дополнение к имени файла не появлялось.
Просто это, на мой взгляд, логично, когда при сохранении файла приложение обнаруживает такое же имя, то к имени сохраняемого файла добавляется номер, или время, или что-то что будет его отличать от уже имеющегося. И честно — для меня было неожиданностью, что такого — нет.
Приведенные выше два аддона мало чем помогли, сейчас попробую другие. Я понимаю, что никто мне ничего тут не должен, и я благодарен за любую оказанную поддержку. Просто то, что было предложено, не подошло к тому, что я хотел бы увидеть.
Добавлено 04-03-2012 03:00:27
Посмотрите, как это происходит в Chromium:
1. Вызвал контекстное меню. 2. Выбрал "Сохранить изображение". 3. Нажал ОК.
И так это в Firefox, с той же последовательностью сохранения:
Добавлено 04-03-2012 03:04:34
Ответ на запрос установки: Недоступно для вашей платформы.
Добавлено 04-03-2012 03:07:24
Совершенно верно — указываю путь 1 раз, а дальше все одноименные файлы при сохранении получают индекс наращивания.
Точно так! 
Отредактировано StopGoogle (04-03-2012 03:07:24)
forum.mozilla-russia.org
1. Before downloading the image, let’s write a method for saving bitmap into an image file in the internal storage in android. It needs a context, better to use the pass in the application context by getApplicationContext(). This method can be dumped into your Activity class or other util classes.
public void saveImage(Context context, Bitmap b, String imageName) { FileOutputStream foStream; try { foStream = context.openFileOutput(imageName, Context.MODE_PRIVATE); b.compress(Bitmap.CompressFormat.PNG, 100, foStream); foStream.close(); } catch (Exception e) { Log.d("saveImage", "Exception 2, Something went wrong!"); e.printStackTrace(); } }
2. Now we have a method to save bitmap into an image file in andorid, let’s write the AsyncTask for downloading images by url. This private class need to be placed in your Activity class as a subclass. After the image is downloaded, in the onPostExecute method, it calls the saveImage method defined above to save the image. Note, the image name is hardcoded as “my_image.png”.
private class DownloadImage extends AsyncTask<String, Void, Bitmap> { private String TAG = "DownloadImage"; private Bitmap downloadImageBitmap(String sUrl) { Bitmap bitmap = null; try { InputStream inputStream = new URL(sUrl).openStream(); // Download Image from URL bitmap = BitmapFactory.decodeStream(inputStream); // Decode Bitmap inputStream.close(); } catch (Exception e) { Log.d(TAG, "Exception 1, Something went wrong!"); e.printStackTrace(); } return bitmap; } @Override protected Bitmap doInBackground(String...
rams) { return downloadImageBitmap(params[0]); } protected void onPostExecute(Bitmap result) { saveImage(getApplicationContext(), result, "my_image.png"); } }
3. The AsyncTask for downloading the image is defined, but we need to execute it in order to run that AsyncTask. To do so, write this line in your onCreate method in your Activity class, or in an onClick method of a button or other places you see fit.
new DownloadImage().execute("http://developer.android.com/images/activity_lifecycle.png");
4. After the image is downloaded, we need a way to load the image bitmap from the internal storage, so we can use it. Let’s write the method for loading the image bitmap. This method takes two paramethers, a context and an image file name, without the full path, the context.openFileInput(imageName) will look up the file at the save directory when this file name was saved in the above saveImage method.
public Bitmap loadImageBitmap(Context context, String imageName) { Bitmap bitmap = null; FileInputStream fiStream; try { fiStream = context.openFileInput(imageName); bitmap = BitmapFactory.decodeStream(fiStream); fiStream.close(); } catch (Exception e) { Log.d("saveImage", "Exception 3, Something went wrong!"); e.printStackTrace(); } return bitmap; }
5. Now we have everything we needed for setting the image of an ImageView or any other Views that you like to use the image on. When we save the image, we hardcoded the image name as “my_image.jpeg”, now we can pass this image name to the above loadImageBitmap method to get the bitmap and set it to an ImageView.
someImageView.setImageBitmap(loadImageBitmap(getApplicationContext(), "my_image.jpeg"));
6. To get the image full path by image name.
File file = getApplicationContext().getFileStreamPath("my_image.jpeg"); String imageFullPath = file.getAbsolutePath();
7. Check if the image file exists.
File file = getApplicationContext().getFileStreamPath("my_image.jpeg"); if (file.exists()) Log.d("file", "my_image.jpeg exists!");
8. To delete the image file.
File file = getApplicationContext().getFileStreamPath("my_image.jpeg"); if (file.delete()) Log.d("file", "my_image.jpeg deleted!");
9. The image should be saved in /data/data/your.app.packagename/files/my_image.jpeg, check this post for accessing this directory from your device.
www.codexpedia.com
When you’re browsing the Web in Safari, you’ll often come across images that you want to save, copy, or link to. There are several ways to save and copy images from Safari depending on what you ultimately want to do with the image. Here’s a look at the various methods.
To get started, launch the Safari app and navigate to or search for an image you’d like to save or copy. Once the image is loaded in the browser window, right-click (or Control-click) on it to display the contextual menu of the various options at your disposal.
In the screenshot above, I’ve outlined in white the options that concern saving and copying the image, and we’ll discuss each one in the sections below.
Save Image to the Desktop
The first option in Safari’s contextual menu is Save Image to the Destkop. As its name describes, selecting this option will grab a copy of the image you’re looking at in Safari and save a copy of the file directly to your desktop.
This is a very handy method for when you have additional plans for your saved image, such as opening it in Photoshop. This gives you quick and easy access to the image from your desktop, even if the desktop isn’t the file’s final destination.
Save Image As
The second choice called out within that contextual menu is Save Image As. Just like the previous option, this will save a copy of the image to your Mac. Unlike the first option, however, it won’t just plop the file down on your desktop, and will instead ask you where to put the picture.
You could still manually select the Desktop as a destination, of course, but the point is that you have a choice of saving the image anywhere, including to external hard drives, USB thumb drives, or network attached storage devices.
Add Image to Photos
The next option is Add Image to Photos. This creates a copy of the image on your Mac, but instead of using a standalone image file, it automatically moves the file into the library of your Photos app.
From here you can edit the image using Photos’ built-in tools, catalog it with tags and custom albums, and easily share it with your friends and families.
Use Image as Desktop Picture
This one’s pretty self-explanatory: choosing this option will make the image your desktop background or wallpaper.
macOS will automatically use the “Scale Image” setting to make the image fill your Mac’s entire screen, even if the image isn’t the correct aspect ratio. This also means that macOS will stretch the image if the image’s resolution is less than your display. This stretching can cause the image to look blocky, so keep that in mind if you use this option on what turns out to be a tiny source image.
Copy Image Address
This option grabs the URL of the image itself and places it in your macOS clipboard. From here, you can paste the link into a document or email and any recipient can click on it to load the image from the source link.
One reason to use this option is when the image you’re working with is very large. For example, you could be looking at a 40MB image at the NASA website. Instead of saving that image to your Mac and then trying to email it to a friend, you could simply send the friend the link to the image. This saves you the bandwidth of sending it and helps avoid email attachment size limitations. Instead of downloading the image from you, the recipient downloads it directly from the source when they want to.
There’s one thing to keep in mind, however. When you save an image to your Mac, you have a copy of that image that will last as long as you want it to. When you save a link to an image, however, the operator of the website to which your link points has total control. They may leave the image up indefinitely, or they may remove it tomorrow, and once it’s gone, you’re out of luck. Therefore, consider saving the image using one of the other options here if it’s very important.
www.tekrevue.com
What is page weight?
Page weight is how large a webpage is in megabytes or gigabytes (size of all the combined files on the page); relevant to how long the page takes to load in browser.
“Photos and videos continue to be the bulkiest part of websites, making up almost three-fourths their size,”—CNN Money’s Hope King
How do I know if my images are optimized?
They may look like the right size because they are fitting in your website template like the designer told you they would. If they look nice and crisp, what could be the problem?
Likely, you won’t know if your images are too big just by looking with the naked eye; you will have to investigate the file size and image settings. Your site is most likely built in a way that conforms to fit a certain set of dimensions.
It’s great to have a working site, but if it’s loading slowly it might as well be broken.
The average web page has grown 151% in just 3 years.
“This gets talked about a lot, but it bears repeating: images are one of the single greatest impediments to front-end performance. All too often, they’re either in the wrong format or they’re uncompressed or they’re not optimized to load progressively — or all of the above.” —Tammy Everts, Web Performance Evangelist
The Typical Scenario – Everything Seems Fine
The typical scenario is that we check out our site, and everything seems to be working fine. If your page were loading very slowly, you would find reason for alarm. The problem with that typical scenario is that it’s not typical – most website owners only look at their sites on a desktop computer while using a dedicated high-powered wifi network.
The problem with that typical scenario is that it’s not typical – most website owners only look at their sites on a desktop computer while using a dedicated high-powered wifi network.
Consider your Mobile Users!
You have to consider mobile users who are in line for their take-out order, waiting for the bus, living in rural areas, or using the public library’s Internet connection.
Think about your mobile users first, since there are so many people using their mobile device to visit your website.
“Nearly two-thirds of Americans are now smartphone owners, and for many these devices are a key entry point to the online world.” —Pew Research Center
Pingdom has a great tool to measure your site’s load time, and you can see all the individual elements that are causing your page weight to be higher.
What are web optimized images?
This simply means that your image settings should indicate that your image resolution is 72, set to sRGB color space, and has a reduced file size for faster page load.
- Resolution – Most devices are only set up to display 72 pixels per inch, so make sure your image dimensions match that. Anything higher than 72 is a waste of space and your user’s bandwidth.
- sRGB – sRGB is the world’s default color space and should always be used for web images in order to ensure the best color quality and consistency. Avoid CMYK altogether since that mode is only used for printed materials.
- Reduced File Size/Optimization – Browsers don’t need the excess information stored in your images from the camera (ie. lens, model, etc), so make sure to remove the bloat!
Essentially we want to shrink file size without compromising the highest possible quality of your photo for the best user experience.
PRO TIP: You might have a similar page rank to a competitor, but if your page weight is larger, you will rank lower in Google results.
Saving Images for Web in Photoshop
1. Open Photoshop, and your image file.
2. Check image size to make sure it is set to 72dpi and color settings are set to sRGB mode. Most likely your team will have given you height and width dimensions for particular parts of your site. Double check those dimensions are correct and are in pixel format.
3. From the file menu choose File > Export > Save for Web, and you will presented with the screen below:
In the top left corner of the Save for Web window are a series of tabs labeled Original, Optimized, 2-Up and 4-Up. By clicking these tabs, you can switch between a view of your original photo, your optimized photo (with the Save for Web settings applied to it), or a comparison of two or four versions of your photo. Choose “2-Up” to compare the original photo with the optimized one. You will now see side-by-side copies of your photo.
Choose “2-Up” to compare the original photo with the optimized one. You will now see side-by-side copies of your photo. The second photo is the optimized photo – check to see that its not pixelated.
4. Click on the second photo. Choose “JPEG High” from the Preset menu. You can now compare your optimized photo (which will eventually be your final file) with your original. Depending on the quality of the photo, you may be able to use “JPEG Medium,” but double check that you aren’t pixelating your photo.
In the example above, you can see I decreased the file size from 2.62M to 126K – this is a HUGE difference and will increase productivity/load time on your site tremendously.
Adobe has a great video tutorial here if you would like to watch how its done.
www.orbitmedia.com