Recent Posts

Grazie per il tuo feedback. Ci fa sempre piacere sentire utenti soddisfatti. Per ora, non esistono dei plug-in esterni o 3rd party. Tutto e contenuto nel sistema base. Le prossime versioni di Workplace conterranno dei nuovi features, per esempio calendario ed anche nuovi tipi di Task objects etc. Spero che troverai presto le funzioni che necessiti. In futuro può darsi che offriremo un API per sviluppatori di plug-ins, però e troppo presto per dire quando o come.

Здравствуйте,

В автономном режиме вам будет доступно только ваше приложение. Интернет необходим для возможности коммуникации с другими участниками. В частности если у вас уже есть участники в space вам необходимо перманентно выходить одновременно в Интернет для обмена новыми данными. Так как на данные момент реализована методология FFA вы скачивать новые данные по кусочкам от любого находящегося в он лайн режиме участника или от нескольких параллельно, опрашивая их и сравнивая на наявность не имеющейся у вас реплики.

Hi Murugan,
drag and drop within a workspace works for all objects, drag and drop between workspace and operating system file system works in both directions (with the exception of workplace specific objects mentioned - back from OS to workspaces they do not properly change format yet from xml back to Collanos object). The one missing feature I mentioned is drag and drop from one workspace to another workspace within Collanos Workplace. This will be implemented in one of the next releases (as well as above "bug" will be fixed).
Hello to Hawaii
Peter

Hi Murugan,
global spaces are always used, enabling them only means to make them visible.
Each user has at least one global space containing all his workspaces. And they are synchronized with all other team members. So as a user you have at least as many global spaces as team members from which you at least got invited to one workspace.
Enabling global spaces means to make this structure visible and to get the ability to create new global spaces within a workplace. The only reason to do so might be to get an additional superstructure for workspaces on one workplace.
In the future it might be used by Collanos Workplace to create global spaces that can consist of workspaces with their own custom objects. We do not plan to launch this feature in the next releases though.
Regards
Peter

I could have sworn that I *did* drag and drop some task and other things from one folder to another within a given workspace, but today it does not seem to be working... is there some drag and drop functionality and if so what are it's limits. Peter, you referred to this in the Global spaces thread, but I thought it might be wise to make it it's own thread for clarity sake.

if Global Workspaces is *not* enabled. does this mean that there is only a single database for the user?  Even if he is invited to another user's work spaces? or the user-specific Global workspaces automatically implemented for each user whether or not Global work spaces is enabled (i.e. if not enabled, in only means they are hidden)

Hi, many thanks for bringing this point up.
1. Global spaces are technically seen completely separate database structures for workplace data. This is implemented in Collanos to be able to support custom database structures of teams. Like that in theory each team can create its own object. A tool to design custom objects is available for internal use but we actually do not plan to roll it out in the near future. We tend to roll out new objects to all users.
If you use Collanos and invite new users to spaces a new global space is created within their Collanos Workplace. So every workplace sets up a global space structure (its database structure) and in there the users workspaces are created. If you enable your workplace to display global spaces you actually can decide to create additional global spaces and structure them. It looks then like a superstructure for workspaces. I actually as a user like this to categorize workspaces. The disadvantage of using global spaces like that is that it needs additional resources, it creates a database structure for each global space. I suggest not to use this element or only to use it if you have a very high number of workspaces that you need to structure further.
2. You mention an old issue - global spaces cannot be deleted! This is an old issue that has been fixed in version 1.3 (if not earlier). We need to take this comment from the forum.
3. Moving objects and directory structure from workspace to workspace with drag and drop is not yet supported in Collanos Workplace. This is a feature on the list for one of the next releases. Franco Dal Molin will soon inform on our release plans. I also miss this feature a lot. The workaround is to move workplace content from a space via drag and drop to an operating system folder and then via drag and drop into the new space. I agree this is not really what we all want and it will be addressed soon.
Also a problem has been reported with regard to that workaround. When you move pure workplace objects like notes or appointments like that to the op system folders and back these objects are imported again as xml files and not as workplace objects. This problem will be addressed asap.
In short: global spaces are implemented in Collanos Workplace as the foundation for future new functionality. They can be used to structure the workplace. But they also increase resource consumption. You will find a global space in your workplace for each user that has invited you to a space.
Regards
Peter

OK I'm head over heels for Collanos already. So, checking advance feature I see Global Space and object folder will be very useful for us. But looking on the forums I don't want to move to fast if the limitations that are posted still exist in the current version:

1) Can I move a work space from one Global Work Space to another?
 # I tried drag and drop in the "All My Workspaces" Pane, but it would not allow me to do that.

Scenario: I enable Global Workspaces.. suddenlyl all my work spaces are under the main user, ME... I think "Great... I will just make one or two other global work spaces and move workspaces under the main user into their appropriate Global works space.

But can't do it. Is there another way to reassign a work space to a different Global WS? Since drag and drop did not work, would expect to see the Global Workspace be a "parent" property of any "child" workspace within it, but it is not. But that could be one way to implement this if this feature is not available. (have a pop up for all global work spaces in the property dialog for each "child" work space where you choose which parent/Global work space he should belong too...)

2) I sawthat last year some users were unable to remove a global work space from which they had been previously invited into and which later they were no longer involved in. They were uninvited to the individual work spaces, which then disappeared from their drives, but the Global Workspace label persisted in their own "All My Workspaces" pane. Is this resolved yet?

We will need all that kind of flexibility and before advising the rest of our team to turn on Global Workspaces, I wanted to check.

Is there a way to set automatic file updates? For instance, I have a document saved in a workspace. When I open the document and make changes, save it again, the changes are saved to the original file in its original location on my hard drive. But when I open the file from the Collanos workspace, the changes are not there. They still appear in the original location on my hard drive. Right now I just have to delete the file from Collanos and add it again. Is there a way to make the workspace check for those changes? Thanks.

got it Thanks! Sorry I wasn't paying attention earlier:

<jxta:seeds ordered="false">
<jxta:RA>
<Dst>
<jxta:APA>
<EA>tcp://194.126.200.14:9701</EA> etc.

[snip]

I think we are "ready to roll" now..

Take care.