On Mar 1, 3:56 am, "Roger Pixley" <skree...@gmail.com> wrote:
> Google has the SOC up. Should we submit for some tasks under KDE?
Sounds like a great idea
Someone has already put up ideas for KWord [1] and a new project
called Kobby[2].
Both are a step in the right direction but could do with a touch up.
Also something for Kate would be fantastic.
Hmm looking at the details the KWord description is a little short on
details and Kobby is trying to tackle Kate and Kdevelop in one go
while ignoring current developments like libinfinote which is done by
the gobby guys. :)
Well I think what we need to do is really pinpoint what someone can start working on. That should be more attractive than these which basically say "This is a good idea. Jump to it!"
On Wed, Mar 5, 2008 at 1:10 AM, <psychobr...@gmx.net> wrote:
> On Mar 1, 3:56 am, "Roger Pixley" <skree...@gmail.com> wrote: > > Google has the SOC up. Should we submit for some tasks under KDE?
> Sounds like a great idea > Someone has already put up ideas for KWord [1] and a new project > called Kobby[2].
> Both are a step in the right direction but could do with a touch up. > Also something for Kate would be fantastic.
> Hmm looking at the details the KWord description is a little short on > details and Kobby is trying to tackle Kate and Kdevelop in one go > while ignoring current developments like libinfinote which is done by > the gobby guys. :)
On Mar 6, 2:52 am, "Roger Pixley" <skree...@gmail.com> wrote:
> Well I think what we need to do is really pinpoint what someone can
> start working on. That should be more attractive than these which
> basically say "This is a good idea. Jump to it!"
So what would be the best way forward?
Just thinking out loud, extending the existing katepart or even the
ktexteditor class would probably go a long way. Using a library like
libinfinote should make that a feasible target for a soc project.
Well here is where I get fuzzy on the structure. Is MateEdit a fork of kate that remerges every now and again or do we work directly on kate? and then pull funky breaking stuff into MateEdit to break in a fantastic manner then to return with a chorus and fireworks to the embracing arms of KDE?
On 3/6/08, psychobr...@gmx.net <psychobr...@gmx.net> wrote:
> On Mar 6, 2:52 am, "Roger Pixley" <skree...@gmail.com> wrote: > > Well I think what we need to do is really pinpoint what someone can > > start working on. That should be more attractive than these which > > basically say "This is a good idea. Jump to it!"
> So what would be the best way forward?
> Just thinking out loud, extending the existing katepart or even the > ktexteditor class would probably go a long way. Using a library like > libinfinote should make that a feasible target for a soc project.
MateEdit currently has no shared code with Kate. It also is based on
KDE3 so not much use for current development.
What it should do is use the underlying KDE classes such as
ktexteditor for it's editing component, spice it up with collaborative
editing using libinfinote and then once it all works merge it all back
with the fireworks you mention :)
Having said that all this can of course be done straight inside the
KDE repository without the need for MateEdit in the mix so that would
be a good SOC project.
I will go and get in touch with the person who put the orignal kobby
entry up to see what his thoughts are.
On Mar 7, 3:53 am, "Roger Pixley" <skree...@gmail.com> wrote:
> Well here is where I get fuzzy on the structure. Is MateEdit a fork of
> kate that remerges every now and again or do we work directly on kate?
> and then pull funky breaking stuff into MateEdit to break in a
> fantastic manner then to return with a chorus and fireworks to the
> embracing arms of KDE?
> On 3/6/08, psychobr...@gmx.net <psychobr...@gmx.net> wrote:
> > On Mar 6, 2:52 am, "Roger Pixley" <skree...@gmail.com> wrote:
> > > Well I think what we need to do is really pinpoint what someone can
> > > start working on. That should be more attractive than these which
> > > basically say "This is a good idea. Jump to it!"
> > So what would be the best way forward?
> > Just thinking out loud, extending the existing katepart or even the
> > ktexteditor class would probably go a long way. Using a library like
> > libinfinote should make that a feasible target for a soc project.
> MateEdit currently has no shared code with Kate. It also is based on
> KDE3 so not much use for current development.
> What it should do is use the underlying KDE classes such as
> ktexteditor for it's editing component, spice it up with collaborative
> editing using libinfinote and then once it all works merge it all back
> with the fireworks you mention :)
> Having said that all this can of course be done straight inside the
> KDE repository without the need for MateEdit in the mix so that would
> be a good SOC project.
> I will go and get in touch with the person who put the orignal kobby
> entry up to see what his thoughts are.
> On Mar 7, 3:53 am, "Roger Pixley" <skree...@gmail.com> wrote:
> > Well here is where I get fuzzy on the structure. Is MateEdit a fork of
> > kate that remerges every now and again or do we work directly on kate?
> > and then pull funky breaking stuff into MateEdit to break in a
> > fantastic manner then to return with a chorus and fireworks to the
> > embracing arms of KDE?
> > On 3/6/08, psychobr...@gmx.net <psychobr...@gmx.net> wrote:
> > > On Mar 6, 2:52 am, "Roger Pixley" <skree...@gmail.com> wrote:
> > > > Well I think what we need to do is really pinpoint what someone can
> > > > start working on. That should be more attractive than these which
> > > > basically say "This is a good idea. Jump to it!"
> > > So what would be the best way forward?
> > > Just thinking out loud, extending the existing katepart or even the
> > > ktexteditor class would probably go a long way. Using a library like
> > > libinfinote should make that a feasible target for a soc project.
If he is going to do a document management interface it would make sense to have that in conjunction with the open session dialog but how would that work with respect to real KIO document sessions and collaborative sessions? Let me think on it in bed a bit. Night!
On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com> wrote: > Hi Just checking ig Greg is on this list. Been a little bit since he > updated his blog
The main issue here is that Kate has a notion of sessions can contain a number of documents. Inside infinote each document is managed through a session so there might be a bit of confusion here. The problem is that it probably isn't all that optimal to open a new infinote session for every document inside a Kate session on startup.
I would think for opening, there could be some KIO interface to enumerate documents on the other side, but that needs a fair amount of investigation to see how a KIO->Kate Document Session handover could be done.
> Datum: Tue, 22 Jul 2008 03:16:33 -0500
> Von: "Roger Pixley" <skree...@gmail.com>
> An: kollaborative-frame@googlegroups.com
> Betreff: Re: Google SoC
> Ok So incase anyone is following this and not following Gregs Blog he has
> an
> issue in his latest post
> That he is musing about
> http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/ Anyone have
> any
> comments?
> If he is going to do a document management interface it would make sense
> to
> have that in conjunction with the open session dialog but how would that
> work with respect to real KIO document sessions and collaborative
> sessions?
> Let me think on it in bed a bit. Night!
> On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com> wrote:
> > Hi Just checking ig Greg is on this list. Been a little bit since he
> > updated his blog
Yes aware of that. Which is why I was saying how would that the current
structure. If someone opens up kate session management they will expect that
a collaboration session would be there as well. However that session can
have possibly many documents which are each a session for the framework. At
this point do we start a new interface?
Hmm just had a thought what does the interface to save a collaboration
session look like? You could possibly select only those that you want. Or
mark the priority docuements so when the session is resumed these update.
Good saving of a session could make restoring one easier.
On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net> wrote:
> The main issue here is that Kate has a notion of sessions can contain a
> number of documents. Inside infinote each document is managed through a
> session so there might be a bit of confusion here. The problem is that it
> probably isn't all that optimal to open a new infinote session for every
> document inside a Kate session on startup.
> I would think for opening, there could be some KIO interface to enumerate
> documents on the other side, but that needs a fair amount of investigation
> to see how a KIO->Kate Document Session handover could be done.
> > Ok So incase anyone is following this and not following Gregs Blog he has
> > an
> > issue in his latest post
> > That he is musing about
> > http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/ Anyone have
> > any
> > comments?
> > If he is going to do a document management interface it would make sense
> > to
> > have that in conjunction with the open session dialog but how would that
> > work with respect to real KIO document sessions and collaborative
> > sessions?
> > Let me think on it in bed a bit. Night!
> > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com>
> wrote:
> > > Hi Just checking ig Greg is on this list. Been a little bit since he
> > > updated his blog
I think you are onto something when you say "good saving of a session could make restoring one easier". Maybe you could also leave a comment on his blog.
> Yes aware of that. Which is why I was saying how would that the current
> structure. If someone opens up kate session management they will expect
> that
> a collaboration session would be there as well. However that session can
> have possibly many documents which are each a session for the framework.
> At
> this point do we start a new interface?
> Hmm just had a thought what does the interface to save a collaboration
> session look like? You could possibly select only those that you want. Or
> mark the priority docuements so when the session is resumed these update.
> Good saving of a session could make restoring one easier.
> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net> wrote:
> > The main issue here is that Kate has a notion of sessions can contain a
> > number of documents. Inside infinote each document is managed through a
> > session so there might be a bit of confusion here. The problem is that
> it
> > probably isn't all that optimal to open a new infinote session for every
> > document inside a Kate session on startup.
> > I would think for opening, there could be some KIO interface to
> enumerate
> > documents on the other side, but that needs a fair amount of
> investigation
> > to see how a KIO->Kate Document Session handover could be done.
> > > Ok So incase anyone is following this and not following Gregs Blog he
> has
> > > an
> > > issue in his latest post
> > > That he is musing about
> > > http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/ Anyone
> have
> > > any
> > > comments?
> > > If he is going to do a document management interface it would make
> sense
> > > to
> > > have that in conjunction with the open session dialog but how would
> that
> > > work with respect to real KIO document sessions and collaborative
> > > sessions?
> > > Let me think on it in bed a bit. Night!
> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com>
> > wrote:
> > > > Hi Just checking ig Greg is on this list. Been a little bit since he
> > > > updated his blog
> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley <skree...@gmail.com>
> > > wrote:
> > > > > And first word turns up at
> > > > > http://gregarei.com/2008/06/introducing-libinfinitymm/ :-) Nice to
> > > > > have you on board Greg
> > > > > On Thu, Apr 24, 2008 at 4:48 PM, <psychobr...@gmx.net> wrote:
> > > > >> Just an update collaborative editing got a slot filled by Greg
> > Haynes
> > > > >> for this years summer of code and I will be mentoring.
Ha ha I just came here to post about his new blog :) Some of this may
be a bit longer term as I don't know if we want him to take on things
which are out of scope for his project or would make him run over
schedule. Another thing that occurred to me is that we could keep the
MRU documents and restart session connections for a threshold while
leaving the others until they are needed.
On 7/22/08, Andreas Ramm <psychobr...@gmx.net> wrote:
> I think you are onto something when you say "good saving of a session could
> make restoring one easier". Maybe you could also leave a comment on his
> blog.
>> Yes aware of that. Which is why I was saying how would that the current
>> structure. If someone opens up kate session management they will expect
>> that
>> a collaboration session would be there as well. However that session can
>> have possibly many documents which are each a session for the framework.
>> At
>> this point do we start a new interface?
>> Hmm just had a thought what does the interface to save a collaboration
>> session look like? You could possibly select only those that you want. Or
>> mark the priority docuements so when the session is resumed these update.
>> Good saving of a session could make restoring one easier.
>> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net> wrote:
>> > The main issue here is that Kate has a notion of sessions can contain a
>> > number of documents. Inside infinote each document is managed through a
>> > session so there might be a bit of confusion here. The problem is that
>> it
>> > probably isn't all that optimal to open a new infinote session for every
>> > document inside a Kate session on startup.
>> > I would think for opening, there could be some KIO interface to
>> enumerate
>> > documents on the other side, but that needs a fair amount of
>> investigation
>> > to see how a KIO->Kate Document Session handover could be done.
>> > > Ok So incase anyone is following this and not following Gregs Blog he
>> has
>> > > an
>> > > issue in his latest post
>> > > That he is musing about
>> > > http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/ Anyone
>> have
>> > > any
>> > > comments?
>> > > If he is going to do a document management interface it would make
>> sense
>> > > to
>> > > have that in conjunction with the open session dialog but how would
>> that
>> > > work with respect to real KIO document sessions and collaborative
>> > > sessions?
>> > > Let me think on it in bed a bit. Night!
>> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com>
>> > wrote:
>> > > > Hi Just checking ig Greg is on this list. Been a little bit since he
>> > > > updated his blog
>> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley <skree...@gmail.com>
>> > > wrote:
>> > > > > And first word turns up at
>> > > > > http://gregarei.com/2008/06/introducing-libinfinitymm/ :-) Nice to
>> > > > > have you on board Greg
>> > > > > On Thu, Apr 24, 2008 at 4:48 PM, <psychobr...@gmx.net> wrote:
>> > > > >> Just an update collaborative editing got a slot filled by Greg
>> > Haynes
>> > > > >> for this years summer of code and I will be mentoring.
Yeah the current project scope will be more than enough for the remaining time of the soc.
The most recently used idea is excellent. Just connect the last 5 used document and leave the others for later. I think it would actually be great for Kate to keep that information through session restarts anyway.
> Ha ha I just came here to post about his new blog :) Some of this may
> be a bit longer term as I don't know if we want him to take on things
> which are out of scope for his project or would make him run over
> schedule. Another thing that occurred to me is that we could keep the
> MRU documents and restart session connections for a threshold while
> leaving the others until they are needed.
> On 7/22/08, Andreas Ramm <psychobr...@gmx.net> wrote:
> > I think you are onto something when you say "good saving of a session
> could
> > make restoring one easier". Maybe you could also leave a comment on his
> > blog.
> >> Yes aware of that. Which is why I was saying how would that the current
> >> structure. If someone opens up kate session management they will expect
> >> that
> >> a collaboration session would be there as well. However that session
> can
> >> have possibly many documents which are each a session for the
> framework.
> >> At
> >> this point do we start a new interface?
> >> Hmm just had a thought what does the interface to save a collaboration
> >> session look like? You could possibly select only those that you want.
> Or
> >> mark the priority docuements so when the session is resumed these
> update.
> >> Good saving of a session could make restoring one easier.
> >> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net>
> wrote:
> >> > The main issue here is that Kate has a notion of sessions can contain
> a
> >> > number of documents. Inside infinote each document is managed through
> a
> >> > session so there might be a bit of confusion here. The problem is
> that
> >> it
> >> > probably isn't all that optimal to open a new infinote session for
> every
> >> > document inside a Kate session on startup.
> >> > I would think for opening, there could be some KIO interface to
> >> enumerate
> >> > documents on the other side, but that needs a fair amount of
> >> investigation
> >> > to see how a KIO->Kate Document Session handover could be done.
> >> > > Ok So incase anyone is following this and not following Gregs Blog
> he
> >> has
> >> > > an
> >> > > issue in his latest post
> >> > > That he is musing about
> >> > > http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/ Anyone
> >> have
> >> > > any
> >> > > comments?
> >> > > If he is going to do a document management interface it would make
> >> sense
> >> > > to
> >> > > have that in conjunction with the open session dialog but how would
> >> that
> >> > > work with respect to real KIO document sessions and collaborative
> >> > > sessions?
> >> > > Let me think on it in bed a bit. Night!
> >> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com>
> >> > wrote:
> >> > > > Hi Just checking ig Greg is on this list. Been a little bit since
> he
> >> > > > updated his blog
> >> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley
> <skree...@gmail.com>
> >> > > wrote:
> >> > > > > And first word turns up at
> >> > > > > http://gregarei.com/2008/06/introducing-libinfinitymm/ :-) Nice
> to
> >> > > > > have you on board Greg
> >> > > > > On Thu, Apr 24, 2008 at 4:48 PM, <psychobr...@gmx.net> wrote:
> >> > > > >> Just an update collaborative editing got a slot filled by Greg
> >> > Haynes
> >> > > > >> for this years summer of code and I will be mentoring.
I just joined the list, so if there are any questions regarding
Kobby's design thus far, the current development, or life in
general :) i'll be here to add in the discussion.
It was interesting reading about the sessions issue with infinote +
kate, and this was something I wrestled with a lot. I thought it was
pretty obvious that if I created the interface for Kobby to mimic Kate
sessions the terminology could get very confusing, and it would not be
nice for future developers. If, on the other hand, Kobby sessions
were treated properly in infinote terms (where joining a session would
mean editing a document) im sure users would not be very happy. As a
result, I decided to leave the term session out of the kobby user
interface, and in turn use terms like 'connection manager' and
'document browser' among other things. I think this might actually be
less confusing to users than the term 'session' when dealing with
connecting to a server.
Another interesting idea is having kobby hand over the document data
to KIO. I really like this idea, and was actually thinking of taking
this route instead of writing a document manager. The reason I am not
for the time being, is that I would really like to get a working
plugin together as soon as possible, and this path presents too many
unknowns for development time. After getting a solid code base under
my feet this will certainly be high on the to do list.
Hope I answered some of your questions, and hope to be hearing some
more feedback.
On Jul 23, 6:04 am, "Andreas Ramm" <psychobr...@gmx.net> wrote:
> Yeah the current project scope will be more than enough for the remaining time of the soc.
> The most recently used idea is excellent. Just connect the last 5 used document and leave the others for later. I think it would actually be great for Kate to keep that information through session restarts anyway.
> > Ha ha I just came here to post about his new blog :) Some of this may
> > be a bit longer term as I don't know if we want him to take on things
> > which are out of scope for his project or would make him run over
> > schedule. Another thing that occurred to me is that we could keep the
> > MRU documents and restart session connections for a threshold while
> > leaving the others until they are needed.
> > On 7/22/08, Andreas Ramm <psychobr...@gmx.net> wrote:
> > > I think you are onto something when you say "good saving of a session
> > could
> > > make restoring one easier". Maybe you could also leave a comment on his
> > > blog.
> > >> Yes aware of that. Which is why I was saying how would that the current
> > >> structure. If someone opens up kate session management they will expect
> > >> that
> > >> a collaboration session would be there as well. However that session
> > can
> > >> have possibly many documents which are each a session for the
> > framework.
> > >> At
> > >> this point do we start a new interface?
> > >> Hmm just had a thought what does the interface to save a collaboration
> > >> session look like? You could possibly select only those that you want.
> > Or
> > >> mark the priority docuements so when the session is resumed these
> > update.
> > >> Good saving of a session could make restoring one easier.
> > >> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net>
> > wrote:
> > >> > The main issue here is that Kate has a notion of sessions can contain
> > a
> > >> > number of documents. Inside infinote each document is managed through
> > a
> > >> > session so there might be a bit of confusion here. The problem is
> > that
> > >> it
> > >> > probably isn't all that optimal to open a new infinote session for
> > every
> > >> > document inside a Kate session on startup.
> > >> > I would think for opening, there could be some KIO interface to
> > >> enumerate
> > >> > documents on the other side, but that needs a fair amount of
> > >> investigation
> > >> > to see how a KIO->Kate Document Session handover could be done.
> > >> > > Ok So incase anyone is following this and not following Gregs Blog
> > he
> > >> has
> > >> > > an
> > >> > > issue in his latest post
> > >> > > That he is musing about
> > >> > >http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/Anyone > > >> have
> > >> > > any
> > >> > > comments?
> > >> > > If he is going to do a document management interface it would make
> > >> sense
> > >> > > to
> > >> > > have that in conjunction with the open session dialog but how would
> > >> that
> > >> > > work with respect to real KIO document sessions and collaborative
> > >> > > sessions?
> > >> > > Let me think on it in bed a bit. Night!
> > >> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley <skree...@gmail.com>
> > >> > wrote:
> > >> > > > Hi Just checking ig Greg is on this list. Been a little bit since
> > he
> > >> > > > updated his blog
> > >> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley
> > <skree...@gmail.com>
> > >> > > wrote:
> > >> > > > > And first word turns up at
> > >> > > > >http://gregarei.com/2008/06/introducing-libinfinitymm/:-) Nice
> > to
> > >> > > > > have you on board Greg
> > >> > > > > On Thu, Apr 24, 2008 at 4:48 PM, <psychobr...@gmx.net> wrote:
> > >> > > > >> Just an update collaborative editing got a slot filled by Greg
> > >> > Haynes
> > >> > > > >> for this years summer of code and I will be mentoring.
> I just joined the list, so if there are any questions regarding
> Kobby's design thus far, the current development, or life in
> general :) i'll be here to add in the discussion.
So about life in general what do you make of it ?? and would it be
better with cmake?
Thanks for joining hope you stick around :) Those are some interesting
challenges you face and fully support hiding confusing naming brought
about by integration from users. We just need to make sure that's
documented properly for future developers.
We don't want to hamper your schedule but road bumps you hit hurt our
bums too so we are all looking for ways to cushion them for future
trips :)
On 7/23/08, greghaynes <g...@greghaynes.net> wrote:
> I just joined the list, so if there are any questions regarding
> Kobby's design thus far, the current development, or life in
> general :) i'll be here to add in the discussion.
> It was interesting reading about the sessions issue with infinote +
> kate, and this was something I wrestled with a lot. I thought it was
> pretty obvious that if I created the interface for Kobby to mimic Kate
> sessions the terminology could get very confusing, and it would not be
> nice for future developers. If, on the other hand, Kobby sessions
> were treated properly in infinote terms (where joining a session would
> mean editing a document) im sure users would not be very happy. As a
> result, I decided to leave the term session out of the kobby user
> interface, and in turn use terms like 'connection manager' and
> 'document browser' among other things. I think this might actually be
> less confusing to users than the term 'session' when dealing with
> connecting to a server.
> Another interesting idea is having kobby hand over the document data
> to KIO. I really like this idea, and was actually thinking of taking
> this route instead of writing a document manager. The reason I am not
> for the time being, is that I would really like to get a working
> plugin together as soon as possible, and this path presents too many
> unknowns for development time. After getting a solid code base under
> my feet this will certainly be high on the to do list.
> Hope I answered some of your questions, and hope to be hearing some
> more feedback.
> On Jul 23, 6:04 am, "Andreas Ramm" <psychobr...@gmx.net> wrote:
>> Yeah the current project scope will be more than enough for the remaining
>> time of the soc.
>> The most recently used idea is excellent. Just connect the last 5 used
>> document and leave the others for later. I think it would actually be
>> great for Kate to keep that information through session restarts anyway.
>> > Ha ha I just came here to post about his new blog :) Some of this may
>> > be a bit longer term as I don't know if we want him to take on things
>> > which are out of scope for his project or would make him run over
>> > schedule. Another thing that occurred to me is that we could keep the
>> > MRU documents and restart session connections for a threshold while
>> > leaving the others until they are needed.
>> > On 7/22/08, Andreas Ramm <psychobr...@gmx.net> wrote:
>> > > I think you are onto something when you say "good saving of a session
>> > could
>> > > make restoring one easier". Maybe you could also leave a comment on
>> > > his
>> > > blog.
>> > >> Yes aware of that. Which is why I was saying how would that the
>> > >> current
>> > >> structure. If someone opens up kate session management they will
>> > >> expect
>> > >> that
>> > >> a collaboration session would be there as well. However that session
>> > can
>> > >> have possibly many documents which are each a session for the
>> > framework.
>> > >> At
>> > >> this point do we start a new interface?
>> > >> Hmm just had a thought what does the interface to save a
>> > >> collaboration
>> > >> session look like? You could possibly select only those that you
>> > >> want.
>> > Or
>> > >> mark the priority docuements so when the session is resumed these
>> > update.
>> > >> Good saving of a session could make restoring one easier.
>> > >> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net>
>> > wrote:
>> > >> > The main issue here is that Kate has a notion of sessions can
>> > >> > contain
>> > a
>> > >> > number of documents. Inside infinote each document is managed
>> > >> > through
>> > a
>> > >> > session so there might be a bit of confusion here. The problem is
>> > that
>> > >> it
>> > >> > probably isn't all that optimal to open a new infinote session for
>> > every
>> > >> > document inside a Kate session on startup.
>> > >> > I would think for opening, there could be some KIO interface to
>> > >> enumerate
>> > >> > documents on the other side, but that needs a fair amount of
>> > >> investigation
>> > >> > to see how a KIO->Kate Document Session handover could be done.
>> > >> > > Ok So incase anyone is following this and not following Gregs
>> > >> > > Blog
>> > he
>> > >> has
>> > >> > > an
>> > >> > > issue in his latest post
>> > >> > > That he is musing about
>> > >> > >http://gregarei.com/2008/07/gsoc-phase-2-kobby-development/Anyone >> > >> have
>> > >> > > any
>> > >> > > comments?
>> > >> > > If he is going to do a document management interface it would
>> > >> > > make
>> > >> sense
>> > >> > > to
>> > >> > > have that in conjunction with the open session dialog but how
>> > >> > > would
>> > >> that
>> > >> > > work with respect to real KIO document sessions and collaborative
>> > >> > > sessions?
>> > >> > > Let me think on it in bed a bit. Night!
>> > >> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley
>> > >> > > <skree...@gmail.com>
>> > >> > wrote:
>> > >> > > > Hi Just checking ig Greg is on this list. Been a little bit
>> > >> > > > since
>> > he
>> > >> > > > updated his blog
>> > >> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley
>> > <skree...@gmail.com>
>> > >> > > wrote:
>> > >> > > > > And first word turns up at
>> > >> > > > >http://gregarei.com/2008/06/introducing-libinfinitymm/:-) Nice
>> > to
>> > >> > > > > have you on board Greg
>> > >> > > > >> Just an update collaborative editing got a slot filled by
>> > >> > > > >> Greg
>> > >> > Haynes
>> > >> > > > >> for this years summer of code and I will be mentoring.
On Thu, Jul 24, 2008 at 12:38 AM, Roger Pixley <skree...@gmail.com> wrote:
> > I just joined the list, so if there are any questions regarding
> > Kobby's design thus far, the current development, or life in
> > general :) i'll be here to add in the discussion.
> So about life in general what do you make of it ?? and would it be
> better with cmake?
> Thanks for joining hope you stick around :) Those are some interesting
> challenges you face and fully support hiding confusing naming brought
> about by integration from users. We just need to make sure that's
> documented properly for future developers.
> We don't want to hamper your schedule but road bumps you hit hurt our
> bums too so we are all looking for ways to cushion them for future
> trips :)
> On 7/23/08, greghaynes <g...@greghaynes.net> wrote:
> > Hello all,
> > I just joined the list, so if there are any questions regarding
> > Kobby's design thus far, the current development, or life in
> > general :) i'll be here to add in the discussion.
> > It was interesting reading about the sessions issue with infinote +
> > kate, and this was something I wrestled with a lot. I thought it was
> > pretty obvious that if I created the interface for Kobby to mimic Kate
> > sessions the terminology could get very confusing, and it would not be
> > nice for future developers. If, on the other hand, Kobby sessions
> > were treated properly in infinote terms (where joining a session would
> > mean editing a document) im sure users would not be very happy. As a
> > result, I decided to leave the term session out of the kobby user
> > interface, and in turn use terms like 'connection manager' and
> > 'document browser' among other things. I think this might actually be
> > less confusing to users than the term 'session' when dealing with
> > connecting to a server.
> > Another interesting idea is having kobby hand over the document data
> > to KIO. I really like this idea, and was actually thinking of taking
> > this route instead of writing a document manager. The reason I am not
> > for the time being, is that I would really like to get a working
> > plugin together as soon as possible, and this path presents too many
> > unknowns for development time. After getting a solid code base under
> > my feet this will certainly be high on the to do list.
> > Hope I answered some of your questions, and hope to be hearing some
> > more feedback.
> > On Jul 23, 6:04 am, "Andreas Ramm" <psychobr...@gmx.net> wrote:
> >> Yeah the current project scope will be more than enough for the
> remaining
> >> time of the soc.
> >> The most recently used idea is excellent. Just connect the last 5 used
> >> document and leave the others for later. I think it would actually be
> >> great for Kate to keep that information through session restarts anyway.
> >> > Ha ha I just came here to post about his new blog :) Some of this may
> >> > be a bit longer term as I don't know if we want him to take on things
> >> > which are out of scope for his project or would make him run over
> >> > schedule. Another thing that occurred to me is that we could keep the
> >> > MRU documents and restart session connections for a threshold while
> >> > leaving the others until they are needed.
> >> > On 7/22/08, Andreas Ramm <psychobr...@gmx.net> wrote:
> >> > > I think you are onto something when you say "good saving of a
> session
> >> > could
> >> > > make restoring one easier". Maybe you could also leave a comment on
> >> > > his
> >> > > blog.
> >> > >> Yes aware of that. Which is why I was saying how would that the
> >> > >> current
> >> > >> structure. If someone opens up kate session management they will
> >> > >> expect
> >> > >> that
> >> > >> a collaboration session would be there as well. However that
> session
> >> > can
> >> > >> have possibly many documents which are each a session for the
> >> > framework.
> >> > >> At
> >> > >> this point do we start a new interface?
> >> > >> Hmm just had a thought what does the interface to save a
> >> > >> collaboration
> >> > >> session look like? You could possibly select only those that you
> >> > >> want.
> >> > Or
> >> > >> mark the priority docuements so when the session is resumed these
> >> > update.
> >> > >> Good saving of a session could make restoring one easier.
> >> > >> On Tue, Jul 22, 2008 at 4:34 AM, Andreas Ramm <psychobr...@gmx.net
> >> > wrote:
> >> > >> > The main issue here is that Kate has a notion of sessions can
> >> > >> > contain
> >> > a
> >> > >> > number of documents. Inside infinote each document is managed
> >> > >> > through
> >> > a
> >> > >> > session so there might be a bit of confusion here. The problem is
> >> > that
> >> > >> it
> >> > >> > probably isn't all that optimal to open a new infinote session
> for
> >> > every
> >> > >> > document inside a Kate session on startup.
> >> > >> > I would think for opening, there could be some KIO interface to
> >> > >> enumerate
> >> > >> > documents on the other side, but that needs a fair amount of
> >> > >> investigation
> >> > >> > to see how a KIO->Kate Document Session handover could be done.
> >> > >> > > Ok So incase anyone is following this and not following Gregs
> >> > >> > > Blog
> >> > he
> >> > >> has
> >> > >> > > an
> >> > >> > > issue in his latest post
> >> > >> > > That he is musing about
> >> > >> > > If he is going to do a document management interface it would
> >> > >> > > make
> >> > >> sense
> >> > >> > > to
> >> > >> > > have that in conjunction with the open session dialog but how
> >> > >> > > would
> >> > >> that
> >> > >> > > work with respect to real KIO document sessions and
> collaborative
> >> > >> > > sessions?
> >> > >> > > Let me think on it in bed a bit. Night!
> >> > >> > > On Thu, Jul 10, 2008 at 5:56 PM, Roger Pixley
> >> > >> > > <skree...@gmail.com>
> >> > >> > wrote:
> >> > >> > > > Hi Just checking ig Greg is on this list. Been a little bit
> >> > >> > > > since
> >> > he
> >> > >> > > > updated his blog
> >> > >> > > > On Thu, Jun 19, 2008 at 1:57 AM, Roger Pixley
> >> > <skree...@gmail.com>
> >> > >> > > wrote:
> >> > >> > > > > And first word turns up at
> >> > >> > > > >http://gregarei.com/2008/06/introducing-libinfinitymm/:-)
> Nice
> >> > to
> >> > >> > > > > have you on board Greg
> >> > >> > > > >> Just an update collaborative editing got a slot filled by
> >> > >> > > > >> Greg
> >> > >> > Haynes
> >> > >> > > > >> for this years summer of code and I will be mentoring.
Roger Pixley wrote: > Just a bump. I was swamped for a month. What's been going on behind > the scenes?
A nice amount of work has been getting done: I'm preparing for the final development run before posting for people to do testing. I set up trac sites for Kobby and Libinfinitymm, they are at:
The doxygen docs on these sites is out of date so I suggest generating your own from source if you want to take a look at that.
These sites also reference the location of the current repositories for each of these projects: git://git.greghaynes.net/kobby.git git://git.greghaynes.net/libinfinitymm.git
I try to keep the tickets fairly up to date on the Kobby trac website, so this should give you a better idea of where development is at than I am capable of explaining. To sum it up: I am working on connecting the libinftext buffer to the KTextEditor::Document interface, which handle the inserting and removing of text from the document and sending this data over the network. Aside from this, all the work that needs to be done before people can begin testing is complete as far as I can tell.
If you need any help getting these projects set up just let me know - It will give me more data to add to the install page if nothing else.
> Roger Pixley wrote: > > Just a bump. I was swamped for a month. What's been going on behind > > the scenes?
> A nice amount of work has been getting done: I'm preparing for the final > development run before posting for people to do testing. I set up trac > sites for Kobby and Libinfinitymm, they are at:
> The doxygen docs on these sites is out of date so I suggest generating > your own from source if you want to take a look at that.
> These sites also reference the location of the current repositories for > each of these projects: > git://git.greghaynes.net/kobby.git > git://git.greghaynes.net/libinfinitymm.git
> I try to keep the tickets fairly up to date on the Kobby trac website, > so this should give you a better idea of where development is at than I > am capable of explaining. To sum it up: I am working on connecting the > libinftext buffer to the KTextEditor::Document interface, which handle > the inserting and removing of text from the document and sending this > data over the network. Aside from this, all the work that needs to be > done before people can begin testing is complete as far as I can tell.
> If you need any help getting these projects set up just let me know - It > will give me more data to add to the install page if nothing else.
There was a change in design plans after trying to implement libinfinitymm as a KTextEditor plugin. The KTextEditor::plugin interface does not have all the features needed to implement a working kobby prototype. Rather than start up a third project in adding to this interface I decided it better to make the initial Kobby prototype a standalone editor. I also took all the work so far on the editor and moved it into a new library - libqinfinitymm - which provides a Qt style interface for libinfinitymm, and a lot of nifty widgets. This, along with some issues with the Trac system, caused me to switch to redmine which has woked wonderfully thus far.
Please feel free to initiate some discussion on any of these topics, some input always helps. Maybe this shoud be moved out of the GSoC thread, though (seeing as its now long gone)?
On Wed, Oct 22, 2008 at 12:32:44PM -0500, Roger Pixley wrote: > I like the new site http://libinfinitymm.greghaynes.net/ Anyone want to give > some feedback on it? :)
> On Thu, Sep 25, 2008 at 12:18 PM, Gregory Haynes <g...@greghaynes.net>wrote:
> > Roger Pixley wrote: > > > Just a bump. I was swamped for a month. What's been going on behind > > > the scenes?
> > A nice amount of work has been getting done: I'm preparing for the final > > development run before posting for people to do testing. I set up trac > > sites for Kobby and Libinfinitymm, they are at:
> > The doxygen docs on these sites is out of date so I suggest generating > > your own from source if you want to take a look at that.
> > These sites also reference the location of the current repositories for > > each of these projects: > > git://git.greghaynes.net/kobby.git > > git://git.greghaynes.net/libinfinitymm.git
> > I try to keep the tickets fairly up to date on the Kobby trac website, > > so this should give you a better idea of where development is at than I > > am capable of explaining. To sum it up: I am working on connecting the > > libinftext buffer to the KTextEditor::Document interface, which handle > > the inserting and removing of text from the document and sending this > > data over the network. Aside from this, all the work that needs to be > > done before people can begin testing is complete as far as I can tell.
> > If you need any help getting these projects set up just let me know - It > > will give me more data to add to the install page if nothing else.
> > Cheers, > > Gregory Haynes
> --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups "Kollaborative Frame" group. > To post to this group, send email to kollaborative-frame@googlegroups.com > To unsubscribe from this group, send email to kollaborative-frame+unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/group/kollaborative-frame?hl=en > -~----------~----~----~----~------~----~------~--~---
On Wed, Oct 22, 2008 at 3:13 PM, Gregory Haynes <g...@greghaynes.net> wrote: > Thanks, I like it as well :)
> There was a change in design plans after trying to implement libinfinitymm > as a KTextEditor plugin. The KTextEditor::plugin interface does not have > all the features needed to implement a working kobby prototype. Rather than > start up a third project in adding to this interface I decided it better to > make the initial Kobby prototype a standalone editor. I also took all the > work so far on the editor and moved it into a new library - libqinfinitymm - > which provides a Qt style interface for libinfinitymm, and a lot of nifty > widgets. This, along with some issues with the Trac system, caused me to > switch to redmine which has woked wonderfully thus far.
> Please feel free to initiate some discussion on any of these topics, some > input always helps. Maybe this shoud be moved out of the GSoC thread, > though (seeing as its now long gone)?
> On Wed, Oct 22, 2008 at 12:32:44PM -0500, Roger Pixley wrote: > > I like the new site http://libinfinitymm.greghaynes.net/ Anyone want to > give > > some feedback on it? :)
> > On Thu, Sep 25, 2008 at 12:18 PM, Gregory Haynes <g...@greghaynes.net > >wrote:
> > > Roger Pixley wrote: > > > > Just a bump. I was swamped for a month. What's been going on behind > > > > the scenes?
> > > A nice amount of work has been getting done: I'm preparing for the > final > > > development run before posting for people to do testing. I set up trac > > > sites for Kobby and Libinfinitymm, they are at:
> > > The doxygen docs on these sites is out of date so I suggest generating > > > your own from source if you want to take a look at that.
> > > These sites also reference the location of the current repositories for > > > each of these projects: > > > git://git.greghaynes.net/kobby.git > > > git://git.greghaynes.net/libinfinitymm.git
> > > I try to keep the tickets fairly up to date on the Kobby trac website, > > > so this should give you a better idea of where development is at than I > > > am capable of explaining. To sum it up: I am working on connecting the > > > libinftext buffer to the KTextEditor::Document interface, which handle > > > the inserting and removing of text from the document and sending this > > > data over the network. Aside from this, all the work that needs to be > > > done before people can begin testing is complete as far as I can tell.
> > > If you need any help getting these projects set up just let me know - > It > > > will give me more data to add to the install page if nothing else.
|
