Hey TheDO, Generally the best way to build apps around other apps is to include their functionality with programming libraries they provide. That way you can access all the functions right in the programming language which has the least overhead and is usually less error prone.
Another way to build an app like Versions would be communicating with the command line program. That means that you have to "manually" send text commands to the app and parse it's output (this is called piping). This way it would be possible to replace the binary that Versions communicates with, but as we would really rely on the input and output it will break easily. Plus, we could never get the app as fast as it is now. Hope that explains it :-) Koen On Mar 28, 9:58 pm, TheDO <webmas...@thedigitalorchard.ca> wrote: > It's great to hear 1.6 support is coming. I want to put out my concern > around the bundling of the subversion client into Versions.app, and > not supporting external subversion clients. I know this has been > discussed before, but can someone in the know remind me (and possibly > others) why Versions is built this way? Is there something special > about the built-in subversion client? > > Can't wait to see the next release of Versions. I'd be happy to join a > beta-testing group, if you need some more help in that respect. > > On Mar 23, 4:50 am, Koen Bok <k...@madebysofa.com> wrote: > > > > > Hey guys, > > > We're looking at adding 1.6 asap (just like we did with 1.5) but want > > to wait until we're sure it's stable enough. > > > - Koen > > > On Mar 23, 12:03 pm, Kez <circle...@gmail.com> wrote: --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
