Comments on: Krugle http://terrychay.com/blog/article/krugle.shtml You tell that other boy, not to touch the woodwork... Fri, 21 Nov 2008 07:24:50 +0000 http://wordpress.org/?v=2.7-hemorrhage hourly 1 By: The Woodwork » Blog Archive » Stories about my wallet http://terrychay.com/blog/article/krugle.shtml#comment-126617 The Woodwork » Blog Archive » Stories about my wallet Thu, 19 Jul 2007 00:26:52 +0000 http://terrychay.com/blog/article/krugle.shtml#comment-126617 [...] cappuccino (yes, that was what the chalkboard told me to order). I then pulled out my wallet to get the Starbucks card (I’m the only person in my family who isn’t a coffee drinker, I just keep the card refreshed so [...] [...] cappuccino (yes, that was what the chalkboard told me to order). I then pulled out my wallet to get the Starbucks card (I’m the only person in my family who isn’t a coffee drinker, I just keep the card refreshed so [...]

]]> By: The Woodwork » Blog Archive » “Out-Googling” Google http://terrychay.com/blog/article/krugle.shtml#comment-18060 The Woodwork » Blog Archive » “Out-Googling” Google Mon, 01 Jan 2007 12:16:21 +0000 http://terrychay.com/blog/article/krugle.shtml#comment-18060 [...] How does my dad get my coffee now and how did he get his coffee then. Somewhere along the way, Starbucks came and broke off coffee from McDonald’s, Dunkin’ Donuts and all-night diners. [...] [...] How does my dad get my coffee now and how did he get his coffee then. Somewhere along the way, Starbucks came and broke off coffee from McDonald’s, Dunkin’ Donuts and all-night diners. [...]

]]> By: Krugle Blog » We need to make our UI less mysterious http://terrychay.com/blog/article/krugle.shtml#comment-11329 Krugle Blog » We need to make our UI less mysterious Tue, 21 Nov 2006 17:24:56 +0000 http://terrychay.com/blog/article/krugle.shtml#comment-11329 [...] I just responded to a thoughtful blog post by Terry Chay. He had given Krugle a try, and then wrote up his impressions. [...] [...] I just responded to a thoughtful blog post by Terry Chay. He had given Krugle a try, and then wrote up his impressions. [...]

]]> By: Ken Krugler http://terrychay.com/blog/article/krugle.shtml#comment-11328 Ken Krugler Tue, 21 Nov 2006 17:15:15 +0000 http://terrychay.com/blog/article/krugle.shtml#comment-11328 Hi Terry, Thanks for taking the time to give Krugle a try! A few comments about specific comments you made in your post... 1. Using special strings to narrow the search. Actually you can do that, in two different ways. First, you can use special terms such as language:xxx, project:xxx, site:xxx, etc.. Grant wrote a nice <a href="http://blog.krugle.com/?p=187" rel="nofollow">blog post</a> about this. Or, for some languages, you can just enter the language name in the query as a shortcut. For example, searching on "php ecard" will return PHP source files that contain the term "ecard". 2. AJAX & the tabbed interface. Yes, this is a common complaint we get. The problem is that for exploratory search, having a tabbed interface can be a real win. See <a href="http://blog.krugle.com/?p=146" rel="nofollow">here</a> for more discussion on this. But to help alleviate the problems this causes, our most recent release adds support for static pages in most UI elements. Just about everywhere that you see a link, there will also be a "static page" icon that you can click on to open the page in a new browser tab/window, instead of a Krugle internal tab. All links are also "link masked", where you can control/right-click the link to get the standard browser popup menu (which typically includes items to copy the link, open the link in a new tab/window, etc). 3. Back button. Sigh. Yeah, that's been a persistent bummer. Especially if you want it to work properly on Safari. But fixing this is on the roadmap. 4. IDE integration. Yes, that would be a beautiful thing. We actually implemented the entire site using a RESTful back-end service, which the web UI leverages to create a browser-based interface. So it's fairly straightforward, once we've resolved the monitoring/throttling issues, to open up the API. Our big challenge is figuring out the "right" way to integrate...something more than just a lookup box with static search results comes to mind. 5. Search via URL. It is possible, with the most recent release. The URL format is: http://krugle.com/kse/files?query=xxx For example, try <a href="http://krugle.com/kse/files?query=php+ecard" rel="nofollow">this search</a>. There are also plugins available for Firefox 1.5/2.0 and IE7 <a href="http://corp.krugle.com/downloads/plugins.html" rel="nofollow">here</a>. Chris Burmester, our AJAX dude, wrote a lengthy <a href="http://blog.krugle.com/?p=185" rel="nofollow">blog post</a> with the gory details. Anyway, hope this helps - thanks again for taking the time to try out <a href="krugle.com" rel="nofollow">Krugle</a>, and let us know if you have other questions or suggestions. Hi Terry,

Thanks for taking the time to give Krugle a try!

A few comments about specific comments you made in your post…

1. Using special strings to narrow the search. Actually you can do that, in two different ways.

First, you can use special terms such as language:xxx, project:xxx, site:xxx, etc.. Grant wrote a nice blog post about this.

Or, for some languages, you can just enter the language name in the query as a shortcut. For example, searching on “php ecard” will return PHP source files that contain the term “ecard”.

2. AJAX & the tabbed interface. Yes, this is a common complaint we get. The problem is that for exploratory search, having a tabbed interface can be a real win. See here for more discussion on this.

But to help alleviate the problems this causes, our most recent release adds support for static pages in most UI elements. Just about everywhere that you see a link, there will also be a “static page” icon that you can click on to open the page in a new browser tab/window, instead of a Krugle internal tab.

All links are also “link masked”, where you can control/right-click the link to get the standard browser popup menu (which typically includes items to copy the link, open the link in a new tab/window, etc).

3. Back button. Sigh. Yeah, that’s been a persistent bummer. Especially if you want it to work properly on Safari. But fixing this is on the roadmap.

4. IDE integration. Yes, that would be a beautiful thing. We actually implemented the entire site using a RESTful back-end service, which the web UI leverages to create a browser-based interface. So it’s fairly straightforward, once we’ve resolved the monitoring/throttling issues, to open up the API.

Our big challenge is figuring out the “right” way to integrate…something more than just a lookup box with static search results comes to mind.

5. Search via URL. It is possible, with the most recent release. The URL format is:

http://krugle.com/kse/files?query=xxx

For example, try this search.

There are also plugins available for Firefox 1.5/2.0 and IE7 here.

Chris Burmester, our AJAX dude, wrote a lengthy blog post with the gory details.

Anyway, hope this helps - thanks again for taking the time to try out Krugle, and let us know if you have other questions or suggestions.

]]>