Link grabber macro
Rightclick link: menu option puts BBcode link in note & clipboard.
This macro assembles a BBCode link in the name field of a bookmark dialog (which provides a workspace with the added benefit that the link anchor is already in it), then copies it to clipboard and a note and dismisses the dialog.
There is a bug in Opera which must be understood to make this work: menu commands including Copy do not execute properly if no text is selected (Opera fails to execute everything up to the Copy). The trick, found by Judedon, is to include a dummy branch in the code - this fools the buggy parser. This is the "external function" branch ("external function" being a dummy function name Opera uses for anything it doesnt understand).
Item, "Grab link"=External function |Copy link & Add link to bookmarks & Previous character & Insert,"[URL=]" & Previous character & Paste & Go to line End & Insert,"[/URL]" & Select All & Copy & Paste to Note & Cancel
- because of the note, one can grab several links from a page for pasting in a batch - instead of being forced to scurry back and forth by the one-slot clipbaord.
- inspired by this request for something like the CoLT extension for Firefox. Not as polished, but it does grab links.
- it's easy to edit the format wrappers to make an HTML variant; I figure anyone with such needs will know how.
- related: note that in Opera 10 you can use Design mode to copy and paste HTML snippets, including links (into email, for example).
Installation Instructions:
It's a menu line to paste into Link Popup Menu. For an intro to menu file editing, see Tamil's blog.
Tested with Opera version(s):
10.0
Comments
Modifications
I've changed the file extension to .ini and edited the file a bit so users can click on the link and trigger Opera´s own autoinstall process.
Great work, btw. ;)
rethinking "seutps"
Thanks (and thanks for being a mod!)
Thing is, anyone likely to use this will have their own menu.ini - displaced if a one-menu INI is installed. INIs could be, maybe should be, incremental - but for for now they're mutually exclusive.
Which is something Opera never figured out with their "setups" zone, and why that never took off. The ini file is not the right unit; individual menus, toolbars and especially macros are what actual tweakers are interested in.
Buttons are a hit because they're a way to package and install single macros. A lot of people don't ever realize that's all they are, and that the macros could be attached to KB/mouse/menu gestures as well. This site will have a lot more potential if it sorts that out - for now, it's following Opera in two mistakes: dividing things superficially based on where one person puts them, and treating INIs as units.
If you think that the .ini
If you think that the .ini extension is not suitable for your file please feel free to change it. I don think users would like it very much if their entire menu got wiped ;-)
Yep, the way Opera handles
Yep, the way Opera handles the .ini files is a mess and defeats the whole purpose of sharing custom files.
That being said, since you also posted the whole code in the comments, I thought it would be nice to offer the autoinstall option to those users who don't want to mess with the .ini files, thus the change of the file extension.
Opera takes the default sections of standard_menu.ini and completes the missing sections of custom .ini files, so users who haven't edited their menu.ini will be on the safe side (your code will appear on top of the [Link Selection Popup Menu], the default menu sections will be used to complete the custom menu.ini) and those who have edited it, well, they will end up with a default menu.ini which includes your code... but they know what they are doing and how to revert it. ;)
Anyway, feel free to change it or contact me and I will do it for you. :)
All very true... I'll add a
All very true... I'll add a remark about how it really needs to be pasted, and how to get back to one's usual INI.
Xywrite used to permit incremental loading & unloading of customization files - that was great. But with exclusive INIs I think one just has to accept that there's an entry barrier, and people not ready to edit them are locked out of customizing beyond buttons & dialogs.
Post new comment