updates

61 views
Skip to first unread message

Patty CaSandra

unread,
Jul 11, 2013, 6:39:42 AM7/11/13
to patchwo...@googlegroups.com
any new update. I think u have a good program here
 

Mike Brown

unread,
Jul 11, 2013, 8:23:11 AM7/11/13
to patchwo...@googlegroups.com
Hi Patty,

Thank you for the interest. This project was completed several years ago.

Context:
The project was an extension to the Mobwrite project. It's aim was to bring the collaborative framework of mobwrite to the programming environment of Gedit.

Update:
A gedit plugin was created; Along with an Apache plugin which provided HTTP PATCH support (which was not a HTTP standard at the time). The gedit plugin is no longer functional as Gedit has since had some heavy changes.

This google-group did host all of the code, but seems to have vanished. The HTTP PATCH support for APACHE might be of some use to someone so I will try and fish it out.

Conclusion:
At th time, the mobwrite protocol suffered from a "Complete overwritting" issue, so while attempting to fix this, HTTP PATCH method as also investigated. The change from the mobwrite protocol to the HTTP PATCH method was considered a success, however at the time HTTP PATCH was up in the air and not standardised, and was never integrated into mobwrite.

Actually having a collaborative environment for programming was considered a failure. What we concluded is that the information that it was giving the programmer was in-fact useless information E.g. Where is the other programming typing, How far along is the other programmer on his requirements-design-implementation thread? (Which tends to have no relevance to yours) etc

The real -practical- solution was to have a CVS style system, in which the programmer builds his changes into a grouped set of patches on his own, which are then shared once complete. The realtime-collaborative way of programming simply did not add anything to the way the programmers worked.

Hope this helps!
Mikey
Reply all
Reply to author
Forward
0 new messages