<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com.au/group/kollaborative-frame</id>
  <title type="text">Kollaborative Frame Google Group</title>
  <subtitle type="text">
  Discussion forum for KDE related concurrent collaborative content creation technologies.
  </subtitle>
  <link href="/group/kollaborative-frame/feed/atom_v1_0_msgs.xml" rel="self" title="Kollaborative Frame feed"/>
  <updated>2009-11-16T16:12:13Z</updated>
  <generator uri="http://groups.google.com.au" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-11-16T16:12:13Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/f8b13c06430a018f?show_docid=f8b13c06430a018f</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/f8b13c06430a018f?show_docid=f8b13c06430a018f"/>
  <title type="text">Re: Kobby Interest</title>
  <summary type="html" xml:space="preserve">
  Forwarded from Kollaborative-frame group: &lt;br&gt; Im completely open to this idea, but from what I can tell about &lt;br&gt; gitorious it lacks a couple features that we currently use on github &lt;br&gt; (website hosting and issue tracking). It seems like KDE will inevitably &lt;br&gt; end up on gitourious, so it would still probably be a good idea to make
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-11-16T16:10:53Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/b9dc0670b8a44741?show_docid=b9dc0670b8a44741</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/b9dc0670b8a44741?show_docid=b9dc0670b8a44741"/>
  <title type="text">Re: Kobby Interest</title>
  <summary type="html" xml:space="preserve">
  Im completely open to this idea, but from what I can tell about &lt;br&gt; gitorious it lacks a couple features that we currently use on github &lt;br&gt; (website hosting and issue tracking). It seems like KDE will inevitably &lt;br&gt; end up on gitourious, so it would still probably be a good idea to make &lt;br&gt; the move. &lt;br&gt; Well need to find replacement hosting for these features before this can
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-11-16T00:38:21Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/7c4c263cf13b0fe3?show_docid=7c4c263cf13b0fe3</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/57b362ee5c1b3cad/7c4c263cf13b0fe3?show_docid=7c4c263cf13b0fe3"/>
  <title type="text">Kobby Interest</title>
  <summary type="html" xml:space="preserve">
  Hello I&#39;ve been trying to feel out receptivity to kollaborative-frame and of &lt;br&gt; course the implementations currently of kobby and libqinfinity. It seems &lt;br&gt; that some people are blissfully unaware of it and some others have heard of &lt;br&gt; it but it&#39;s a little off the radar. One thing I have heard from quite a few
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-11-05T20:31:32Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/b8f63d8e6c3d3190?show_docid=b8f63d8e6c3d3190</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/b8f63d8e6c3d3190?show_docid=b8f63d8e6c3d3190"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  Ok I&#39;ll make an announcement for it for sprints and general tests. What &lt;br&gt; other filters have been done for infinote other than Text? Would it be too &lt;br&gt; forward to say that if a Suite of programs handles formats in a particular &lt;br&gt; way they should write a filter to allow remote kollaboration throughout the
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-11-05T18:24:27Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/c977628bf561b803?show_docid=c977628bf561b803</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/c977628bf561b803?show_docid=c977628bf561b803"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  I figured the server had fallen off everyone&#39;s radar. It definitely &lt;br&gt; would be useful for me if it were to be used so I just put it back up: &lt;br&gt; infinote.greghaynes.net
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-11-05T05:37:31Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/13c153fb4fc83b18?show_docid=13c153fb4fc83b18</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/13c153fb4fc83b18?show_docid=13c153fb4fc83b18"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  Wow I&amp;quot;m late on jumping in on this :-) Ok here are my thoughts at least on a &lt;br&gt; desktop level I&#39;ve already pitched my concept of clients being able to be &lt;br&gt; light or heavy servers. I also don&#39;t see any reason why they cannot be light &lt;br&gt; and heavy clients. A heavy client would be one that tries to tie together
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-06-09T21:14:48Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/fc3956cdedd3f64f?show_docid=fc3956cdedd3f64f</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/fc3956cdedd3f64f?show_docid=fc3956cdedd3f64f"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  I have also been researching this new technology and trying to determine its &lt;br&gt; possible impacts on existing collaborative applications. While Wave seems to &lt;br&gt; offer a slew of collaborative features, it seems like it would be very difficult &lt;br&gt; to integrate all of these in a client-side feature-rich editor, like Kate.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Fair</name>
  <email>mich...@daclubhouse.net</email>
  </author>
  <updated>2009-06-08T21:48:40Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/55347e2d98485c85?show_docid=55347e2d98485c85</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/55347e2d98485c85?show_docid=55347e2d98485c85"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  Creating and joining a MUC (a channel in XMPP speak) is pretty trivial &lt;br&gt; and definitely should be worked into the architecture. &lt;br&gt; &lt;p&gt;I just saw a demo of Google WAVE recently and really liked what they &lt;br&gt; had implemented. &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://wave.google.com/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; It really inspired me on a few fronts for what collaboration could be like.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-05-31T05:17:08Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/9044aedfab9d72d2?show_docid=9044aedfab9d72d2</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/9044aedfab9d72d2?show_docid=9044aedfab9d72d2"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  That makes sense. Something else that could be done, is creating a chat &lt;br&gt; plugin for libinfinity similar to the InfText plugin, but with chat operations &lt;br&gt; instead of insert/remove text operations. I dont see any reason why this &lt;br&gt; wouldnt work, and clients which dont recognize the plugin would not be
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-05-31T03:53:05Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/aa9492cdf72febb7?show_docid=aa9492cdf72febb7</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/aa9492cdf72febb7?show_docid=aa9492cdf72febb7"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  Just had a light chat with the devs and they had wanted caht removed from &lt;br&gt; the API altogether. I have yet to speak to the person (ck) who has final &lt;br&gt; word on this but I&#39;m thinking that it falls more in ine with the original &lt;br&gt; submission that I had made of having a light serer that focuses solely on &lt;br&gt; the document and sharing it and a heavier specification that is much more
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-05-30T19:18:57Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/d5fdf3b655dff4a6?show_docid=d5fdf3b655dff4a6</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/d5fdf3b655dff4a6?show_docid=d5fdf3b655dff4a6"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  I was speaking from a purely API standpoint, my knowledge of jabber is &lt;br&gt; somewhat lacking. Creating chat outside of a document would mean major &lt;br&gt; changes to the libinfinity API because user information is specified on a per- &lt;br&gt; document basis, so im not sure the libinfinity devs would go for this. Maybe a
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-05-30T07:54:16Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/f06f720c266f3fdc?show_docid=f06f720c266f3fdc</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/f06f720c266f3fdc?show_docid=f06f720c266f3fdc"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  On a server level this would certainly mean a major API change, but I dont &lt;br&gt; see &lt;br&gt; why this would be difficult to implement on a document level. User &lt;br&gt; information &lt;br&gt; is already provided when joining a document, so maybe a chat facility could &lt;br&gt; be &lt;br&gt; retrieved after joining a session? &lt;br&gt; &lt;p&gt; So simply spawn a new Channel? I know it&#39;s all Jabber based so technically
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-05-30T07:05:26Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/94d9fbd49b97cab9?show_docid=94d9fbd49b97cab9</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/94d9fbd49b97cab9?show_docid=94d9fbd49b97cab9"/>
  <title type="text">Re: Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  I did some digging around in the libinfinity API for communication features, &lt;br&gt; and AFAICT there are no document or server level user to user chat facilities &lt;br&gt; in the library. This could be (relatively) easily added on a document level &lt;br&gt; via a note plugin without having to modify libinfinity. Ill send out a message
  </summary>
  </entry>
  <entry>
  <author>
  <name>Roger Pixley</name>
  <email>skree...@gmail.com</email>
  </author>
  <updated>2009-05-30T05:42:55Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/b9d5018cd573a588?show_docid=b9d5018cd573a588</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/78c789f753a010a2/b9d5018cd573a588?show_docid=b9d5018cd573a588"/>
  <title type="text">Communication while Editing.</title>
  <summary type="html" xml:space="preserve">
  Sending this out to the list to garner some mindmash. Currently libinfinity &lt;br&gt; (and hence libqinfinity) supports communication by Jabber on a server level. &lt;br&gt; For quite a few reasons I think that having an option to have it on a &lt;br&gt; document level is a good idea. If you think of a large assembly such as &lt;br&gt; Akademy or GCDS (Side Thought: How do you abstract that? *DS?) where you
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gregory Haynes</name>
  <email>g...@greghaynes.net</email>
  </author>
  <updated>2009-04-25T22:07:22Z</updated>
  <id>http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/403199fc431510f4/29af7017da99afb6?show_docid=29af7017da99afb6</id>
  <link href="http://groups.google.com.au/group/kollaborative-frame/browse_thread/thread/403199fc431510f4/29af7017da99afb6?show_docid=29af7017da99afb6"/>
  <title type="text">Re: Kobby</title>
  <summary type="html" xml:space="preserve">
  Sorry for the slow reply. The meeting-attend.png icon is part of the Oxygen &lt;br&gt; icon set, so I think it should come with your KDE install?
  </summary>
  </entry>
</feed>
