<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I’d be really happy to see the OSX GUI brought up to date!!<div><br></div><div>My $.02 is that backwards compatibility is not very important at all — if things only work on the most current OS and XCode version, that’s not a big tragedy. What’s much more important is <i>forward</i> compatibility — i.e., keeping things simple and avoiding using features that may lose support (like BWToolkit). </div><div><br></div><div>Best,</div><div><br></div><div> - Benjamin</div><div><br><div><br><div><div>On Apr 28, 2014, at 5:34 PM, Alan Shutko <<a href="mailto:ats@acm.org">ats@acm.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I'm interested in getting the UI working again on Mac. As mentioned in <a href="https://groups.yahoo.com/neo/groups/unison-users/conversations/topics/10918">https://groups.yahoo.com/neo/groups/unison-users/conversations/topics/10918</a> , Unison currently does not build on OS X 10.7 or higher, because it uses the BWToolkit and Interface Builder plugin, which are no longer supported in Xcode 4.<br><br>I currently have a visually unappealing codebase which will build and run on both Xcode 3 and 4. I'm working to clean it up for submission. After that, I am going to investigate some UI improvements: more clear display of conflicts in packages and the ability to click on a growl notification to open Unison.<br><br>Are there any other items that should be fixed for OS X? What is the oldest version of OS X that we should retain support for? <br>_______________________________________________<br>Unison-hackers mailing list<br><a href="mailto:Unison-hackers@lists.seas.upenn.edu">Unison-hackers@lists.seas.upenn.edu</a><br>http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers<br></blockquote></div><br></div></div></body></html>