Re: Problem importing bookmarks.
Reply #6 –
@Frenzie, UserJS is a bit separate topic, so far I've not decided yet how it should work in our case.
Pretty much everything that applies to Opera UserJS also applies to Opera extensions. If you stick that script in an Opera extension it'll still have the same advantage over the same script in a Chromium extension. Of course the UserJS will have the advantage over both extensions of not needing all kinds of mental-barrier junk just to get started.
And is it really needed anyway (maybe except magic functions)?
It's hardly needed, but it's just so much more elegant. See e.g. here. Instead of simply stripping out one part from a function that I don't want:
e.element.text = e.element.text.replace(
'areas.click(function(){ NrcOnePageView.Articles.showArticle(this);return false; });',
''
);
Instead I have to do complex stuff like this:
article_divs.forEach(function(div) {
div.innerHTML = '<a href="'+getArticleHref(div)+'" style="display:block;width:100%;height:100%"></a>';
//killEventListeners(div);
jQuery(div).off('click');
});
Through magic functions I would've had to copy the entire function definition. Something that's quite workable in specific circumstances, but in a case like this that'd be a disaster. I used to do stuff like this with Proxomitron ten years ago, but UserJS is more elegant because it combines Proxomitron and GreaseMonkey insofar as modifying webpages is concerned. Well, actually Proxomitron could always do what GreaseMonkey did by adding an extra script at the very bottom of the page, of course.
Anyway, I don't think it's worthwhile adding any compatibility with a dead ecosystem. I'll live. It'd be much more worthwhile to be able to tap into the vast extension libraries of Chrome/Opera, even if they're more like GM than like UserJS.