Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Communication while Editing.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Gregory Haynes  
View profile  
 More options May 30, 5:05 pm
From: Gregory Haynes <g...@greghaynes.net>
Date: Sat, 30 May 2009 07:05:26 +0000
Local: Sat, May 30 2009 5:05 pm
Subject: Re: Communication while Editing.

On Saturday 30 May 2009 05:42:55 Roger Pixley wrote:

> Sending this out to the list to garner some mindmash. Currently libinfinity
> (and hence libqinfinity) supports communication by Jabber on a server
> level.

I did some digging around in the libinfinity API for communication features,
and AFAICT there are no document or server level user to user chat facilities
in the library.  This could be (relatively) easily added on a document level
via a note plugin without having to modify libinfinity.  Ill send out a message
to Armin to make sure this is correct.

> For quite a few reasons I think that having an option to have it on
> a document level is a good idea. If you think of a large assembly such as
> Akademy or GCDS (Side Thought: How do you abstract that? *DS?)  where you
> would like an easy one connect server for remote collaborators but then
> having all the chatter for the various projects and problems being
> discussed broadcast to everyone is unbearably confusing. Or further down
> the line when this is KDE wide and many types of clients can connect to it
> (also FOSS now rules the world cause the others ignored then laughed then
> fought ) A fairly large business would want to use something like this
> internally to tie together teams. Even if there is one server per
> department you would want discussions to be more localized to say a group
> or a document.

> So having said that I think that a proposal currently to implemt proper
> channels and identifucation would be thrown out right away as something too
> disruptive to do now.

On a server level this would certainly mean a major API change, but I dont see
why this would be difficult to implement on a document level.  User information
is already provided when joining a document, so maybe a chat facility could be
retrieved after joining a session?

> My proposal is to allow messages which are sent to be
> optionally tagged then clients can read the tags on the messages and react
> as they see fit. Clients who have no idea about the tags will just drop
> them Clients who know but don't really care can possibly simply display the
> tags Clients that know and care can create channels or drop entire messages
> of the user doesn't care about them etc.

> If anyone has another solution to the issue or sees the issue in a
> different light please reply and lets have a discussion :)

> Roger Pixley
> Sharer of Sentiments
> Kollaborator of Konsiderations

--
Gregory Haynes

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google