> Well sure, all you need to do is to visit some random sample, right?
Apparently :-) Thank you!
Well, Otto /does/ seem to handle XSLT fine. Fine. Maybe it's the wrong approach but I thougth it should be possible to do the arrangement thing via XSLT, without touching the program's code. If buried in some .xsl file, "folders first" would be the standard behaviour. Not configurable via say a toolbar button, right?
Just another thing (slightiy OT): I wrote a user JS to filter out any (annoying) HTML-styling, revealing working links instead of JS-onclick-quasilinks (my default is JS: Off). Currently it's just a test script about how to manipulate the document tree, it has to be (de)activated via the plugins-panel, requiring a restart of the browser to work. Hmm.
Question: How can I make a user JS into something that works on the current window/current document context - on demand/if some setting is 'set' only? - How do I call a script via a toolbar button/context menu entry, providing the current document's URL as a parameter? - Is there any documentation of the "parameters" , "hints" etc. for custom actions, e. g. placed in webWidget.json? - Is there any documentation on how to read/set/unset Otter's settings via JS?
using Otter v1.0.81 weekly 272 (WebKit-Backend 602.1), I successfully imported 5.000+ bookmarks/600+ folders from Opera (with quite a long history...), well organized into folders.
Usability in Otter was far from good - folders + bookmarks wildly mixed, blindly sorted by whatever column I chose.
So I wrote a Q&D Perl script to rearrange the bookmarks file to have folders put first (recursively). Drawback: Sorting bookmarks in bookmarks panel will return the mixup - you will have to run the script again.(In Don't-Sort-Anything-mode, if you want to preserve your sort order.)
One can specify the source + target file (.xbel expected) and opt for (not) sorting folders and/or bookmarks separately. Just run the script in a command prompt window to see how to run it.
any problems with "putting the style sheets in the knowledge"? Ok, it is a bit frightening that "The style sheet also defines it as being devastating Widget Graphics". But, "The whole block is commenting on", so what?
as the look & feel of an UI is impotant to me, I did some styling of "my" Otter-browser. Looks really outdated now ...
1 CSS file + a bunch of icons, mostly stolen from Opera 12.x ... "Skinning" /is/ available for Otter, obviously :-) Skin is not perfect yet (see e.g. feed/bookmark properties dialog - OK-button w/o border), so it will take some further investigation to solve these problems - hints are welcome!
