Ok, so I sometimes check URL referrals to my site and this one caught my eye... it seems to be a description, help and detailed information on my extension... written on Japanese! :D nice!
They even took the time to post some URLs to use on Japanese sites (I'll add them to my links list)...
The screenshot, with Japanese links on my extension, also surprised me since it's got a gazillion links!... i wonder how many links does everyone use? y only use 4 or 5 links... I might run a poll about it, maybe there's something I'm not considering when someone uses many links?
I cannot tell who posted this, so I don't have anyone in particular to say thanks... so at least, thank you GigaFree.net!
There's a few other places where the extension is mentioned... but this of course, is the coolest... cuz it's in Japanese, obviously.
Hi
Chrome extension which allows you to right click on selected text and search on multiple sites at the same time.
Thursday, April 19, 2012
Tuesday, April 17, 2012
TY Amazon! :D
Yay! I'm getting richer by the hour! Last week I got my first 0.73 USD from Amazon!
To the one extension user that bought Been There, Should've Done That: 995 Tips for Making the Most of College and How to Study, I don't have a way to know who you are, but thank you! Feel free to comment on this post so I get to know your name, and by the way, tell us about those books... and for the looks of it, good luck studying!
Don't pay attention to my amigo Guillermo, who says (I'll roughly translate this) "Formal education will destroy your brain"... he's only partially right :D
No, seriously, thank you!! ! :D
In case you're wondering, this is related to this post.
To the one extension user that bought Been There, Should've Done That: 995 Tips for Making the Most of College and How to Study, I don't have a way to know who you are, but thank you! Feel free to comment on this post so I get to know your name, and by the way, tell us about those books... and for the looks of it, good luck studying!
Don't pay attention to my amigo Guillermo, who says (I'll roughly translate this) "Formal education will destroy your brain"... he's only partially right :D
No, seriously, thank you!! ! :D
In case you're wondering, this is related to this post.
Sunday, April 8, 2012
Support this humble extension developer
Of course, this extension is for free -I built it for me, actually-... but if you really enjoy using it, and you'd like to show your appreciation, here's a list of things that might make me happy :)
Thanks again for following
- Show me the money: Hit the donate button at the top right of this page... and send me a few bucks!
- Make Amazon pay me: Use any of the Amazon links featured on the options page, search stuff using my extension and buy it! If I had the links set up properly and my affiliate account is working -haven't tested it yet-, I might get a few bucks from Amazon... and it costs you zero! (Thanks to Daniel Costas for the idea :D).
- Guerrilla advertising: Share on Twitter, post on Facebook, G+ or wherever you feel this extension might be well received.
- More Guerrilla advertising: Now that you're reading my blog, follow it -I don't write that much- post a comment and link to any of these posts. G+ the posts you like.
- Boost my self esteem: Rate the extension on Google's webstore, say how much you love it!
Thanks again for following
0.1.7.3 is out
Hey there, a few days ago I published 0.1.7.3, which has a few code fixes and one new feature called "Search on all!" which will basically search your selection on all your configured search engines at the same time, opening a tab for each result...
I'm not sure how useful this is... is it?
I had plans to do this for a while, and a comment from Jon to my last post (thanks again!) made me remember it.
As per Jon's request, to enable some kind of "bulk search" if you select multiple lines, I'm working on it... I'll have to change the way the selection is analyzed, so far I was working with some default context menu option (selectionText), which will always return a string of text, with no break lines, so there's no way to tell if there's multiple lines on the selection.
The trick is to parse the selection as HTML (using x.Selector.getSelected()), decide which HTML tags I'll parse as line breakers, and try and iterate through the line breaks, strip the text of other HTML tags, and perform search queries per each line...
I still have a few things to figure out before I do this, such as how will all this work from an UX perspective... but it's a nice challenge.
I hope next version will include this feature...
As for this one, the only other change was on the options page. I removed the "ToDo list" since there was little there remaining... and I will be posting it here...
In its place, I included a few "suggestions" on how you could support this extension's developer (aka me), which I'll also be posting here.
Ps: if you're interested on x.Selector.getSelected(), here's my question at stack overflow and its answer (Thank you Richard)
I'm not sure how useful this is... is it?
I had plans to do this for a while, and a comment from Jon to my last post (thanks again!) made me remember it.
As per Jon's request, to enable some kind of "bulk search" if you select multiple lines, I'm working on it... I'll have to change the way the selection is analyzed, so far I was working with some default context menu option (selectionText), which will always return a string of text, with no break lines, so there's no way to tell if there's multiple lines on the selection.
The trick is to parse the selection as HTML (using x.Selector.getSelected()), decide which HTML tags I'll parse as line breakers, and try and iterate through the line breaks, strip the text of other HTML tags, and perform search queries per each line...
I still have a few things to figure out before I do this, such as how will all this work from an UX perspective... but it's a nice challenge.
I hope next version will include this feature...
As for this one, the only other change was on the options page. I removed the "ToDo list" since there was little there remaining... and I will be posting it here...
In its place, I included a few "suggestions" on how you could support this extension's developer (aka me), which I'll also be posting here.
Ps: if you're interested on x.Selector.getSelected(), here's my question at stack overflow and its answer (Thank you Richard)
Labels:
Change-log,
New Features
Location:
Montevideo, Uruguay
Thursday, February 9, 2012
OMG I got my first donation! :D
In this humble post, I wanted to officially thank Winston K. for his generosity in helping me get cool stuff by donating (see the big donate button at the right of this post...).
Thank you Winston, I really hope other fellow users share your enthusiasm! :D
I'm really happy for the feedback I've been getting... As I said, this I did this extension for myself, mostly, so this is a big bonus.
Thanks again!
Thank you Winston, I really hope other fellow users share your enthusiasm! :D
I'm really happy for the feedback I've been getting... As I said, this I did this extension for myself, mostly, so this is a big bonus.
Thanks again!
Wednesday, February 8, 2012
Oops :P
Been breaking stuff lately.
First I tried to use "Open Sans" with my Blogger Template, and broke it... it stills look a bit funky... it seems that if you choose that font on the Advanced Options, it doesn't really work and all you see is an ugly serif font... well... found a way to fix it -need to add the CSS code by hand-, so I'll be doing it soon.
The most important broken stuff is that by trying to fix the %s & %S issue on version 0.1.7 I took the fast track, and "lowercased" the hole search string... which is bad, you know :)
Thanks to Keith for letting me know that I was forcing the whole search string to lower case... now I've fixed it and quick published a fix on version 0.1.7.1
Sorry about that :)
First I tried to use "Open Sans" with my Blogger Template, and broke it... it stills look a bit funky... it seems that if you choose that font on the Advanced Options, it doesn't really work and all you see is an ugly serif font... well... found a way to fix it -need to add the CSS code by hand-, so I'll be doing it soon.
The most important broken stuff is that by trying to fix the %s & %S issue on version 0.1.7 I took the fast track, and "lowercased" the hole search string... which is bad, you know :)
Thanks to Keith for letting me know that I was forcing the whole search string to lower case... now I've fixed it and quick published a fix on version 0.1.7.1
Sorry about that :)
Monday, February 6, 2012
What's new on v 0.1.7
Long time, no update...
I'm glad I got a few requests... it feels nice to know people use what I did.
I have 3 special thanks for this publication: Ahmed, Damien and Theodor. All three of them are using the extension and contributed to part of what I've updated.
Damien requested a cool thing, that unfortunately for now, I haven't been able to figure out completely:
Have you noticed how the "Search on Google" menu link works?...
I'll try and describe: It has a pretty weird way of opening your search result on a new tab (right next to the original tab), gives it default focus, you close it and then get back to the original page... so it goes back one tab... which is not a standard behavior for tab closing (when you close a tab, you get to the next one).
If instead of closing the new tab, you then move to another tab, and then back to the new one, then the closing behavior applies: the next tab will show up when you close the "new" one...
(mmmh I don't know if you get my meaning, please, try it and you'll get it...)
Well, I tried to imitate the Search on Google's way, but couldn't so far. :(
Opening the results on the next tab is not a big deal. What's complicated is having Chrome remember how to get back to the previous tab...
What I've done so far, is to allow the user to decide where to open the new tab (First, Last, Next Previous)... and if they don't mind a weird config, they can select "Previous" as an option, their new tab will get focus, before the "old" tab... they can read whatever they want, and then close it and get the "next" tab, which is the "old" one :P ugly... but does the trick... hope Damien likes it...
Other stuff I've done on this publication: you'll now get a notice whenever a new update is loaded (the options page will pop-up and the new version id should appear).
Also loved the "Open sans" font on some of the new options pages for Chomre (on Dev version, at least), so I decided to update the font type on the options page... I like it much more now.
Fixed a few typos and minor bugs and finally, I added a "donate" button :)
I don't make a living of this, and as I said before, I built this extension for me, mostly, so I don't expect to earn money out of it... but if you're on a generous mood, and feel like showing your appreciation, now you can do so :) heh...
Well, that's it... here's the full change log, have fun.
New on v 0.1.7
- Added "New tab position" parameter: You can now select where you want your new tabs to open (Thanks Damien, I know this doesn't work exactly as you wanted, but it's something).
- Fixed little bug on "Featured Search Engines" list, where some search engines wouldn't work.
- %s on search URL now supports %S (Thanks Ahmed!)
- Fixed typo on Help (thanks Theodor!)
- Using "Open sans" as a default font for options -nicer, right?-.
- Added Update notification
- New Donate button... I hope you like it :)
I'm glad I got a few requests... it feels nice to know people use what I did.
I have 3 special thanks for this publication: Ahmed, Damien and Theodor. All three of them are using the extension and contributed to part of what I've updated.
Damien requested a cool thing, that unfortunately for now, I haven't been able to figure out completely:
Have you noticed how the "Search on Google" menu link works?...
I'll try and describe: It has a pretty weird way of opening your search result on a new tab (right next to the original tab), gives it default focus, you close it and then get back to the original page... so it goes back one tab... which is not a standard behavior for tab closing (when you close a tab, you get to the next one).
If instead of closing the new tab, you then move to another tab, and then back to the new one, then the closing behavior applies: the next tab will show up when you close the "new" one...
(mmmh I don't know if you get my meaning, please, try it and you'll get it...)
Well, I tried to imitate the Search on Google's way, but couldn't so far. :(
Opening the results on the next tab is not a big deal. What's complicated is having Chrome remember how to get back to the previous tab...
What I've done so far, is to allow the user to decide where to open the new tab (First, Last, Next Previous)... and if they don't mind a weird config, they can select "Previous" as an option, their new tab will get focus, before the "old" tab... they can read whatever they want, and then close it and get the "next" tab, which is the "old" one :P ugly... but does the trick... hope Damien likes it...
Other stuff I've done on this publication: you'll now get a notice whenever a new update is loaded (the options page will pop-up and the new version id should appear).
Also loved the "Open sans" font on some of the new options pages for Chomre (on Dev version, at least), so I decided to update the font type on the options page... I like it much more now.
Fixed a few typos and minor bugs and finally, I added a "donate" button :)
I don't make a living of this, and as I said before, I built this extension for me, mostly, so I don't expect to earn money out of it... but if you're on a generous mood, and feel like showing your appreciation, now you can do so :) heh...
Well, that's it... here's the full change log, have fun.
New on v 0.1.7
- Added "New tab position" parameter: You can now select where you want your new tabs to open (Thanks Damien, I know this doesn't work exactly as you wanted, but it's something).
- Fixed little bug on "Featured Search Engines" list, where some search engines wouldn't work.
- %s on search URL now supports %S (Thanks Ahmed!)
- Fixed typo on Help (thanks Theodor!)
- Using "Open sans" as a default font for options -nicer, right?-.
- Added Update notification
- New Donate button... I hope you like it :)
Subscribe to:
Posts (Atom)