<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Comparing Collanos with Groove</title>
	<atom:link href="http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/</link>
	<description>- think out of the inbox -</description>
	<pubDate>Tue, 06 Jan 2009 12:58:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Franco Dal Molin</title>
		<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/#comment-18227</link>
		<dc:creator>Franco Dal Molin</dc:creator>
		<pubDate>Wed, 05 Sep 2007 13:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collanos.com/index.php/2007/05/31/comparing-collanos-with-groove/#comment-18227</guid>
		<description>Hi Ringo, thanks for your suggestions!

We do have a "mapping workspaces to file system folders" feature on our road map, but no release date yet. We are still in the process of researching alternatives, evaluating technical options and estimating efforts. If I am not mistaken, Groove differentiates between normal workspaces and a special file system folder workspace for Files only (it offers members/presence and a chat too, but no other tools). Keep in mind, Groove is a Windows only tool. These two facts make an OS folder-sync function relatively simple. BTW, there are many tools on the market that do just that: Syncing folders.

Our vision is to not restrict workspaces by content. With Collanos, you can mix and match any object types in virtual folders. You can put Files, Discussions, Tasks, Notes, etc. into the same virtual folder within a Collanos workspace. Compare this to Groove's "a tool = a tab" concept, which leads to content fragmentation and loosing context. To support our vision, we are considering a "partial mapping" approach that will map workspace folders in/out to file system folders. Objects of type File will be synced, but at the same time the Collanos workspaces will not be limited. They could still contain additional business objects, such as Tasks and Discussions. So the sync process would work something like this:

OS Folder A &lt;--local--&gt; Space A &lt;--P2P--&gt; Space B &lt;--&gt; OS Folder B

This concept will work also across different operating systems.

Best regards,
Franco</description>
		<content:encoded><![CDATA[<p>Hi Ringo, thanks for your suggestions!</p>
<p>We do have a &#8220;mapping workspaces to file system folders&#8221; feature on our road map, but no release date yet. We are still in the process of researching alternatives, evaluating technical options and estimating efforts. If I am not mistaken, Groove differentiates between normal workspaces and a special file system folder workspace for Files only (it offers members/presence and a chat too, but no other tools). Keep in mind, Groove is a Windows only tool. These two facts make an OS folder-sync function relatively simple. BTW, there are many tools on the market that do just that: Syncing folders.</p>
<p>Our vision is to not restrict workspaces by content. With Collanos, you can mix and match any object types in virtual folders. You can put Files, Discussions, Tasks, Notes, etc. into the same virtual folder within a Collanos workspace. Compare this to Groove&#8217;s &#8220;a tool = a tab&#8221; concept, which leads to content fragmentation and loosing context. To support our vision, we are considering a &#8220;partial mapping&#8221; approach that will map workspace folders in/out to file system folders. Objects of type File will be synced, but at the same time the Collanos workspaces will not be limited. They could still contain additional business objects, such as Tasks and Discussions. So the sync process would work something like this:</p>
<p>OS Folder A < --local--> Space A < --P2P--> Space B < --> OS Folder B</p>
<p>This concept will work also across different operating systems.</p>
<p>Best regards,<br />
Franco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ringo</title>
		<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/#comment-18219</link>
		<dc:creator>Ringo</dc:creator>
		<pubDate>Wed, 05 Sep 2007 08:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collanos.com/index.php/2007/05/31/comparing-collanos-with-groove/#comment-18219</guid>
		<description>Hi,

We are working with Groove as well and we checked out the Collanos solution since we have some replication problems and the synchronisation is alway's going via the internet connection, even if the 2 computers are on the LAN which consumes unnescessary all out bandwith.

The thing that is actually holding us back that the files can only be used via the Collanos workspace since there is no 1to1 relation with a folder on the harddrive. The files &#38; folders are renamed to %randomcharacters%.dat

In groove it's just a directory on a harddrive you add to the workspace.
That is actually the solution we like to use, since the application we use cannot read the "collanos workspace" only files and folders on the harddrive.

If the workspace files would just be files and folders on de harddrive, it would be a perfect solution for us instead of groove.

Maybe this could be an option in the future?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We are working with Groove as well and we checked out the Collanos solution since we have some replication problems and the synchronisation is alway&#8217;s going via the internet connection, even if the 2 computers are on the LAN which consumes unnescessary all out bandwith.</p>
<p>The thing that is actually holding us back that the files can only be used via the Collanos workspace since there is no 1to1 relation with a folder on the harddrive. The files &amp; folders are renamed to %randomcharacters%.dat</p>
<p>In groove it&#8217;s just a directory on a harddrive you add to the workspace.<br />
That is actually the solution we like to use, since the application we use cannot read the &#8220;collanos workspace&#8221; only files and folders on the harddrive.</p>
<p>If the workspace files would just be files and folders on de harddrive, it would be a perfect solution for us instead of groove.</p>
<p>Maybe this could be an option in the future?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gil Heiman</title>
		<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/#comment-14181</link>
		<dc:creator>Gil Heiman</dc:creator>
		<pubDate>Mon, 09 Jul 2007 16:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collanos.com/index.php/2007/05/31/comparing-collanos-with-groove/#comment-14181</guid>
		<description>Thanks Sam.
In the works, a Search function that will span across all your workspaces, including in the structured content such as Notes and Tasks. Stay tuned!</description>
		<content:encoded><![CDATA[<p>Thanks Sam.<br />
In the works, a Search function that will span across all your workspaces, including in the structured content such as Notes and Tasks. Stay tuned!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Brien</title>
		<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/#comment-13208</link>
		<dc:creator>Sam Brien</dc:creator>
		<pubDate>Thu, 21 Jun 2007 05:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collanos.com/index.php/2007/05/31/comparing-collanos-with-groove/#comment-13208</guid>
		<description>You called for "Suggestions" on how to dumbify the solution.

I would love a search function. As tree grow, 2 people will put the same data in different places in a tree. (The main reason things like Google Desktop are a must have these days.)

No need to search inside files, but searching inside notes, discussions and titles should be sufficient.

Any thoughts?

Cheers,

Sam</description>
		<content:encoded><![CDATA[<p>You called for &#8220;Suggestions&#8221; on how to dumbify the solution.</p>
<p>I would love a search function. As tree grow, 2 people will put the same data in different places in a tree. (The main reason things like Google Desktop are a must have these days.)</p>
<p>No need to search inside files, but searching inside notes, discussions and titles should be sufficient.</p>
<p>Any thoughts?</p>
<p>Cheers,</p>
<p>Sam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe schmo</title>
		<link>http://blog.collanos.com/2007/05/31/comparing-collanos-with-groove/#comment-13030</link>
		<dc:creator>Joe schmo</dc:creator>
		<pubDate>Sun, 17 Jun 2007 17:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collanos.com/index.php/2007/05/31/comparing-collanos-with-groove/#comment-13030</guid>
		<description>Please introduce a calendar feature ASAP.</description>
		<content:encoded><![CDATA[<p>Please introduce a calendar feature ASAP.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
