[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    [Bug 142196] ooosvn for revision control
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2007-02-28 2:43:37
Message-ID: 20070228024337.330.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=142196         




------- Additional Comments From mail dipe org  2007-02-28 03:43 -------
 Richard

I see multiple problems with the oosvn-implementation;
1. we can't use it since it's written in OOo basic as OOo-package and \
therefore accesses OOo/UNO-API functionality. 2. it is not portable since \
it uses shell-scripts 3. it's just a wrapper around the svn-commandline \
tools (ok, propably not really a point or at least it's open for \
interpretation if that's an advantage or a disadvantage :)

So, im(h)o 1. already disqualifies it since to provide a "compatibility \
layer" to wrap such basic scripts wouldn't only mean a lot of work and a \
lot of additional code but we would need to get a to OOo-basic compatible \
basic-interpreter done. That sounds much more work then writting an own \
solution, to reuse portable code that already exist e.g. at KDevelop4 or to \
improve the already (at least partly?!) existing code in KOffice ( \
http://code.google.com/soc/kde/appinfo.html?csaid=D2A89C79513DB3E5 and \
http://dot.kde.org/1157452184/ ).

 Raúl

KWord is able to save uncompressed OpenDocument Text files since ages ;) I \
agree about the joint effort part but currently OOoSVN looks strong like \
OOo-only :-( ____________________________________
koffice mailing list
koffice@kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice


[prev in list] [next in list] [prev in thread] [next in thread]