What are extension tubes you ask? They sit between your lens and your camera body, reducing the minimum focus distance of your lens and magnify your images. Long story short, they help create macro images without a macro lens.
For more information, please visit EXTENTOOL.
Extension tubes have been around for awhile, and often get a bad reputation. I honestly believe they DO have a place in photography, but we also have to be realistic about the pros and cons of using them.
Macro lenses, like most good lenses, don’t come cheap. Extension tubes, by comparison, are quite cheap. If you wish to dabble with macro photography, but not quick ready to commit, you could purchase a set of extension tubes for about 10% of the cost of a macro lens.
I use Vello extension tubes. When I first switched over to Sony, I had to replace everything, including all my lenses. I just wasn’t sure whether to go for a 90mm or the 50mm macro. But I still wanted to take macro. So I decided to try extension tubes while I tried a few lenses.
The fact that the Vello retains autofocus and auto exposure due to the electronic contacts (some other brands are purely manual focus, so check specifications before purchasing), there are no optics in the tubes and they are lightweight. I love that I can throw them in my pocket and not worry about breaking any glass. I also adore that I can use them on ANY of my Sony lenses, even my 18-200mm. I am super impressed at just how close I can get with my standard lenses.
OK, so I am going to be honest here. Focusing even with the autofocus can sometimes be a bit hit and miss. I often use the autofocus to get in close, then fine-tune with the peak meter.
I have the 10mm and 16mm versions — you can use them separately or both together. You can get crazy close to your subject … not ideal when shooting stinging insects or spiders. It’s not great if trying to achieve non-interference with your subject as well. Also, I found they can be fiddly to get on and off at times, especially when you have cold stiff fingers, but that could just be me.
I think my biggest struggle was the focus and depth of field. I guess I was used to picking up my old 90mm macro and jumping straight to f/2.8 or higher and getting my bokeh on. But as it was pointed out to me quite some time ago, having a small subject and range means it is often a lot more difficult to work with such a high F/stop, so I pushed it down to f/9 or even f/11.
It is easier to learn with a larger DOF. This, of course, steals light and when you are working in confined space so close there is often the problem with minimal light and lots of shadows. A macro ring is a huge advantage when using extension tubes.
This page provides guidelines for designing a high-quality extension and Chrome Web Store listing. These recommendations may be updated as the store continues to grow and we learn from developers' experiences. We strongly encourage you to create extensions that meet standards for compliance, performance, security, and user experience, as described in the following sections.
Extensions that are available in the Chrome Web Store are required to adhere to the developer program policies. If you've received a policy violation warning or want to learn about common violations pitfalls, see Troubleshooting Chrome Web Store violations.
Manifest V3 is the most recent version of the Chrome extension platform and is the required version for submitting new items to the Chrome Web Store. See the Manifest V3 overview to learn about the platform changes. Existing extensions should consider migrating to Manifest V3, see Migrate to Manifest V3 for instructions on how to migrate.
Your extension should be safe for your users. For example, send user data securely via HTTPS or web services security. Check that your extension does not pose security threats and does not use deceptive installation tactics. See Stay secure for a more information.
An extension is required to disclose in the Privacy tab what user data it will collect and how it will handle user data. This information must be accurate, up-to-date, and match the extension's privacy policy. For more guidance on privacy, see Protecting User Privacy policies and the User Data FAQs.
Add end-to-end tests using testing libraries like Puppeteer to make sure your extension is performing as intended from start to finish. In addition, consider conducting thorough manual testing across different browser versions, OSs, and network conditions to ensure smooth functionality.
The company is the world’s best Extension Tool supplier. We are your one-stop shop for all needs. Our staff are highly-specialized and will help you find the product you need.
When you are releasing your extension, there are a number of common performance issues you should make sure to avoid.
The back/forward cache is an optimization built into Chrome that allows for instant loading of a page when a user returns to it. Given extensions can run on every page, its essential you make sure avoid code that prevents that caching, or else you risk substantially slowing down your users. Make sure you test if your extension invalidates the cache. Common causes of cache invalidation include
Unload Handler
The unload handler has been deprecated for a long time and should generally never be used. If you are using it, pagehide event is the most popular alternative. If you need to run code after the page closes, there is chrome.tabs.onRemoved.
WebSockets in content scripts
If you have a content script with a WebSocket or WebRTC connection, then the page cannot be cached. You can instead move these connections to your background service worker script. We have a guide on how to keep your connection in a background script, and then proxy the results to your content script with runtime.connect.
Design your extension with the user in mind by providing a simple, intuitive, and seamless user interface while also respecting user privacy.
Start onboarding your users as soon as they reach your store listing by providing screenshots and a video of how the extension works. We recommend following the permission warning guidelines to increase the chances of users installing your extension.
Avoid distracting users when implementing a persistent UI. For example, when designing a side panel for your extension, make sure it enhances the user's browsing experience by providing relevant information and useful functionality. A side panel should help users accomplish tasks with as little distraction as possible.
If your extension requires user login, we recommend that you support Sign in with Google, which provides a good user experience for Chrome Web Store users as they are likely to be logged in already. If you already have a login system, consider correlating the Google Account ID to the user account in your system. You can use the Chrome Identity API to support Google accounts in the following ways:
The purpose of an extension's Chrome Web Store store listing is to set the user's expectations. It should explicitly communicate what the extension does. See Listing requirements for a complete list of requirements.
The better your extension's store listing, the more users will discover and try your extension. Creating a great listing page provides guidelines for designing the best store listing experience. When choosing your extension's name, writing its description, and designing its logo, keep in mind Google's Branding guidelines.
Include all the required images (icon, tile, marquee, and screenshots). Images should not be blurry or too busy, as described in Images of a high-quality listing.
The developer console requires you to specify a category for your extension. Choose the most appropriate category:
In mid the categories changed. Most of the new categories match previous ones. Several were replaced by multiple categories. If you previously used one of the replaced categories, use the table below to decide which new category best suits your extension.
The developer console also asks you specify a category for your theme. Choose the most appropriate category:
Want more information on Telescopic Tree Pruner? Feel free to contact us.

Comments
0