Comments on: PHP components I would buy http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/ Rapid Signal: a micro-ISV venture Fri, 21 Nov 2008 04:43:46 +0000 http://wordpress.org/?v=2.6.1 By: New direction at Overview http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-196 New direction at Overview Sun, 08 Jan 2006 13:00:25 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-196 [...] Some posts by Ian Landsman and  Dimitris Giannitsaros confirmed my ideas about this so I decided to give it a go ! [...] [...] Some posts by Ian Landsman and  Dimitris Giannitsaros confirmed my ideas about this so I decided to give it a go ! [...]

]]> By: Anonymous http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-80 Anonymous Sun, 14 Aug 2005 14:23:44 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-80 Very useful comments - good to read <a href="" title="" rel="nofollow"></a> Very useful comments - good to read

]]> By: Dimitris Giannitsaros http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-38 Dimitris Giannitsaros Fri, 24 Jun 2005 10:09:54 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-38 Well there could be API categories. E.g. for all search engines it should just return you results with common attributes (link, title and maybe description). For ehsops it should support a link, description and maybe item category and price. For instance, if I want to embed search results in my product I would something on the lines of: $api = new CommonSearchAPI; $api->initEngine('Yahoo'); $api->initEngine('Google'); $results = $api->search($keyword); print_r($results); Well there could be API categories. E.g. for all search engines it should just return you results with common attributes (link, title and maybe description). For ehsops it should support a link, description and maybe item category and price.

For instance, if I want to embed search results in my product I would something on the lines of:

$api = new CommonSearchAPI;
$api->initEngine(’Yahoo’);
$api->initEngine(’Google’);
$results = $api->search($keyword);
print_r($results);

]]> By: Panayotis Vryonis http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-37 Panayotis Vryonis Fri, 24 Jun 2005 09:20:46 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-37 Regarding the APIs, you may want to check http://pear.php.net/ On the other hand, having a common abstraction layer for services like Google, Yahoo, Flickr, etc is not easy -they may seem like they are similar services, but they are not. Compare Google WEB APIs, Amazon Web Services and Yahoo! Search Web Services. (will they ever adopt, http://opensearch.a9.com/ ? I hope so...) Regarding the APIs, you may want to check http://pear.php.net/

On the other hand, having a common abstraction layer for services like Google, Yahoo, Flickr, etc is not easy -they may seem like they are similar services, but they are not. Compare Google WEB APIs, Amazon Web Services and Yahoo! Search Web Services. (will they ever adopt, http://opensearch.a9.com/ ? I hope so…)

]]> By: Ian http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-36 Ian Tue, 21 Jun 2005 17:24:30 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-36 Yeah, it might be confusing for potential customers of <a href="http://www.userscape.com/products/helpspot/" rel="nofollow">HelpSpot</a> when they wander around the site and find very technical developer oriented products. Also there would be work to get it into that type of shape, because the code is really built into HelpSpot right now and in no way designed for general use. So I'd have to pull out alot of logic and so on, but maybe down the road. What I'd probably do is take the feedback from v1 HelpSpot users and build a new component for email access from the ground up as a stand alone product. Yeah, it might be confusing for potential customers of HelpSpot when they wander around the site and find very technical developer oriented products. Also there would be work to get it into that type of shape, because the code is really built into HelpSpot right now and in no way designed for general use. So I’d have to pull out alot of logic and so on, but maybe down the road.

What I’d probably do is take the feedback from v1 HelpSpot users and build a new component for email access from the ground up as a stand alone product.

]]> By: Dimitris Giannitsaros http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-35 Dimitris Giannitsaros Tue, 21 Jun 2005 16:13:43 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-35 And your next sentence after the quote I copied is: "Hmm maybe UserScape product #2?????". Well, I would certainly consider it, especially with all the work you have (will) put in these two areas. The only downside is that it could be a little hard to support and market for two different markets (business users vs. developers) And your next sentence after the quote I copied is: “Hmm maybe UserScape product #2?????”. Well, I would certainly consider it, especially with all the work you have (will) put in these two areas. The only downside is that it could be a little hard to support and market for two different markets (business users vs. developers)

]]> By: Ian http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-34 Ian Tue, 21 Jun 2005 12:58:41 +0000 http://rapidsignal.com/blog/2005/06/21/php-components-i-would-buy/#comment-34 Yep I second these. Especially the first 2. I've already written #1 for HelpSpot and it was a huge pain and one of the areas I'm going to have to do tons of testing in. #2 is also on my list of things to build. As you say I would have happily paid for quality, well tested, components which do those 2 things. Yep I second these. Especially the first 2. I’ve already written #1 for HelpSpot and it was a huge pain and one of the areas I’m going to have to do tons of testing in. #2 is also on my list of things to build. As you say I would have happily paid for quality, well tested, components which do those 2 things.

]]>