[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [osmic] Rearrange command
- To: Bek Oberin <gossamer@xxxxxxxxxxxxxx>, OSMIC Mailing List <osmic@xxxxxxxxxx>
- Subject: Re: [osmic] Rearrange command
- From: Andrew Pam <xanni@xxxxxxxxxxxxxxxxx>
- Date: Sat, 20 Feb 1999 13:00:54 +1100
- In-reply-to: <19990218202336.G7368@xxxxxxxxxxxxxx>; from Bek Oberin on Thu, Feb 18, 1999 at 08:23:36PM +1100
- References: <19990218202336.G7368@xxxxxxxxxxxxxx>
On Thu, Feb 18, 1999 at 08:23:36PM +1100, Bek Oberin wrote:
> What's the point of having the rearrange command in the OSMIC
> protocol specification?
> It seems to me it's something you can accomplish with a few deletes
> and transcludes, and the client software should handle adding an
> explicit "rearrange" command if it wants to, translating the effect
> into the del/trans before it sends it to the server.
> Opinions, please!
You're right. That seems like a logical simplification to me. The only
drawback is an increase in the complexity of the client, but I think
the tradeoff is probably worth it. Try designing it with just the three
fundamental operations on the server side and see how it comes out.
Note that Ted and I discussed implementing "Delete" as just a special case
of "rearrange" last year (rearrange to a special destination signifying
"no longer part of this document"). That makes the three fundamental
operations Insert, Transclude and Rearrange.
*** Xanni ***
mailto:xanni@xxxxxxxxxx Andrew Pam
http://www.xanadu.com.au/ Technical VP, Xanadu
http://www.glasswings.com.au/ Technical Editor, Glass Wings
http://www.sericyb.com.au/sc/ Manager, Serious Cybernetics
P.O. Box 26, East Melbourne VIC 8002 Australia Phone +61 3 96511511