I love the diigo ie toolbar, but after one day's trying, I find I really can't stand the other foolish aspects of ie. Firefox is out of the question, because little Chinese sites are compatible with it. I tried to use the ie toolbar on maxthon, but it just doesn't work. I tried the diigolet on chrome, but then you have to first show the favorite bar and then click the diigolet button to get its toolbar to appear. It takes too many steps and occupies too much space, which negates much of the remarkable advantages of chrome. Besides, the diigolet bar takes the place of the first line of the page, so you can't see the original first line, but that's where the most important links usually reside, just as in this page. I tried the diigolet on maxthon. The problems are similar to the chrome case. Besides, I just got this script error message: '0.draggable' is empty or not an object. So, I still think diigo is great, but I have to find a way to make at least one browser co-operate with it. Is it possible for you to make the diigo toolbar compatible with maxthon? Since maxthon is just a shell of ie, I assume it is not unrealistic. Or, can you recommend something for me to do? Thank you very much!
Hi Betty, It seems maxthon 2.X supports more IE toolbars. What's maxthon version you use? BTW, you can go to maxthon forum http://forum.maxthon.com/viewthread.php?tid=70694&extra=page%3D1 to ask them support diigo toolbar. We will try to contact them after you initiate some requests there.
Well, I just realized that my maxthon was very old. So I downloaded and installed the newest version of maxthon. This time, diigo does not even show up in maxthon's plugin management page. (It was there in the older version. ) I reinstalled the diigo toolbar but still had no luck. I checked maxthon forum. It seems that newer version might be worse for some plugin, since people haven't had time to add support. Anyway, I'll try to ask them to support diigo toolbar. Thank you.
> … I tried the diigolet on chrome, but then you have to first > show the favorite bar and then click the diigolet button to get > its toolbar to appear. It takes too many steps …
I haven't tried Webkit-based Chrome but on at least three Webkit-based browsers:
* if I make Diigolet the first item within my bookmarks bar, then command-1 will present Diigolet
* if I make Diigolet the second item within the bar, then command-2 will present the second item
* and so on
-- all _without_ revealing the bookmarks bar.
That is: one single step to presentation of Diigolet :)
In Chrome, you might experiment with this approach. If using Windows, then the key combination will be something other than 'command-'.
----
> … occupies too much space … diigolet bar takes the place of the > first line of the page …
Diigo developers: there's a usability issue. Re screen shots below please note that the icons to hide then re-present Diigolet toolbar are at opposites with each other; extreme right and extreme left.
A set of actions that effectively toggle should be iconised in identical positions.
(Metaphor: we do not find lighting-on and lighting-off switches at opposite ends of a room; there's a single switch in a predictable place :)
In fact, the #1 (far left) placement of a Diigolet button effectively means that there may be three extremes, in this order:
1) Diigolet button typically at exreme left
2) Hide Diigolet toolbar icon at extreme right
3) Re-represent Diigolet toolbar icon at extreme left
Second postcript: battling again with HTML in the forums :/
Third postscript: curs-ed HTML :(
Fourth postscript: HTML, drat, drat and double drat
Umpteenth postscript: images are wrong but I'm too tired of editing raw HTML to care any more ;)
Thank you, Graham. I'm using Windows, so there is no "command" key. I tried control/shift/alt and the combinations of them, but none worked as you described... (control-number brings up the numbered tab, and others do nothing.)
Maybe we should suggest to Chrome developer community that key strokes should be assignable to selected items within the bookmarks/favourites bar/menu.
Thank you Graham. You are so nice. :) I think there are other ways to assign a script to a keyboard shortcut, such as AutoHotKey. So I'm going to try it, while waiting for a more native solution. :)
I confess, there's an element of selfishness - appreciating a fine set of improvements (thanks to Diigo team) before a more widespread push/encouragement to researchers and other colleagues at my place of work.
Right now, Diigo is to me like a ball of wool, with catnip and other surprises at its core. Like a kitten, I'm unravelling, playing, chewing, scratching, purring.
> I think there are other ways to assign a script to a keyboard > shortcut, such as AutoHotKey. So I'm going to try it, while > waiting for a more native solution. :)
Firefox is out of the question, because little Chinese sites are compatible with it.
I tried to use the ie toolbar on maxthon, but it just doesn't work.
I tried the diigolet on chrome, but then you have to first show the favorite bar and then click the diigolet button to get its toolbar to appear. It takes too many steps and occupies too much space, which negates much of the remarkable advantages of chrome. Besides, the diigolet bar takes the place of the first line of the page, so you can't see the original first line, but that's where the most important links usually reside, just as in this page.
I tried the diigolet on maxthon. The problems are similar to the chrome case. Besides, I just got this script error message: '0.draggable' is empty or not an object.
So, I still think diigo is great, but I have to find a way to make at least one browser co-operate with it.
Is it possible for you to make the diigo toolbar compatible with maxthon? Since maxthon is just a shell of ie, I assume it is not unrealistic. Or, can you recommend something for me to do?
Thank you very much!
It seems maxthon 2.X supports more IE toolbars. What's maxthon version you use? BTW, you can go to maxthon forum http://forum.maxthon.com/viewthread.php?tid=70694&extra=page%3D1 to ask them support diigo toolbar. We will try to contact them after you initiate some requests there.
> … I tried the diigolet on chrome, but then you have to first
> show the favorite bar and then click the diigolet button to get
> its toolbar to appear. It takes too many steps …
I haven't tried Webkit-based Chrome but on at least three Webkit-based browsers:
* if I make Diigolet the first item within my bookmarks bar, then command-1 will present Diigolet
* if I make Diigolet the second item within the bar, then command-2 will present the second item
* and so on
-- all _without_ revealing the bookmarks bar.
That is: one single step to presentation of Diigolet :)
In Chrome, you might experiment with this approach. If using Windows, then the key combination will be something other than 'command-'.
----
> … occupies too much space … diigolet bar takes the place of the
> first line of the page …
Diigo developers: there's a usability issue. Re screen shots below please note that the icons to hide then re-present Diigolet toolbar are at opposites with each other; extreme right and extreme left.
A set of actions that effectively toggle should be iconised in identical positions.
(Metaphor: we do not find lighting-on and lighting-off switches at opposite ends of a room; there's a single switch in a predictable place :)
In fact, the #1 (far left) placement of a Diigolet button effectively means that there may be three extremes, in this order:
1) Diigolet button typically at exreme left
2) Hide Diigolet toolbar icon at extreme right
3) Re-represent Diigolet toolbar icon at extreme left
Second postcript: battling again with HTML in the forums :/
Third postscript: curs-ed HTML :(
Fourth postscript: HTML, drat, drat and double drat
Umpteenth postscript: images are wrong but I'm too tired of editing raw HTML to care any more ;)
> selected items within the bookmarks/favourites bar/menu.
Log of discussion: http://echelog.matzon.dk/logs/browse/chromium/1226358000
I think there are other ways to assign a script to a keyboard shortcut, such as AutoHotKey. So I'm going to try it, while waiting for a more native solution. :)
Right now, Diigo is to me like a ball of wool, with catnip and other surprises at its core. Like a kitten, I'm unravelling, playing, chewing, scratching, purring.
Meow.
Betty Lu wrote:
> I think there are other ways to assign a script to a keyboard
> shortcut, such as AutoHotKey. So I'm going to try it, while
> waiting for a more native solution. :)
AutoHotKey also suggested at
http://sheenonline.biz/2008/09/quick-diigo-bookmarking-for-chrome/
Thanks to Oliver S. for the link :)
To Top