At 11:40 AM -0600 11/22/00, Karl Fogel wrote:
>Also, we're starting to think about GUI clients for Macintosh/Windows.
>The command-line client currently under development will run under
>Windows, but many users will naturally want something like WinCVS.
>And I doubt the command-line client will even work on a Mac. :-)
For what it's worth, note that the upcoming MacOS 10 is also
unix-based. I assume your command-line client should work on it,
as long as it works on the other BSD's (freebsd, netbsd, openbsd).
It also MIGHT be true that the command-line version would work
OK in some environment like MPW, with some minor tweaking. I
haven't tried to do anything with MPW in many years, though.
>I've checked in an item about this in TASKS:
>
> 4. Macintosh/Windows GUI clients.
>
> Once libsvn_client API is finalized (which, for a sufficiently
> loose definition of "final", should be by Milestone 2 on Dec 7th),
> it will be usable by any client, not just the command-line client.
>
> I'm not sure this argues definitively for native clients written in
> C for Mac and Windows, though that's certainly one way to get it
> done. Perhaps one client could be written for both platforms,
> using a Java class that links to the C libsvn_client API?
>
>Thoughts? Interested parties?
MacOS 10 should have excellent Java support, but MacOS 9 (and
earlier) will probably never be updated to 'Java 2' spec.
Anyone writing a java-based client should keep that in mind.
If one was to do a MacOS native client, they should probably
write to the 'carbon' API, which is supposed to be workable
for MacOS 8 thru 10 (and beyond), if I recall correctly.
[disclaimer: so far I'm just a lurker here. I'm interested in
the project but won't have any time to commit to it until it is
"somewhat usable" as a CVS replacement)
--
Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Received on Sat Oct 21 14:36:15 2006