Changes between Version 1 and Version 2 of Ticket #34433, comment 5
- Timestamp:
- Mar 10, 2013, 6:03:54 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34433, comment 5
v1 v2 1 1 Hi, I'm Zach. I'm one of the main developers of Colloquy. Someone just filed a ticket on our trac asking me to look here. 2 2 3 To Sam's original point of Growl, Colloquy links against a version of the Growl framework, but, that will not stop it from using a newer version if it is present on the system (since the Growl folks are kind enough to keep API compatibility here). Same goes for F-Script.3 To Sam's original point of Growl, Colloquy links against a version of the Growl framework, but, that will not stop it from using a newer version if it is present on the system (since the Growl folks are kind enough to keep API compatibility here). 4 4 5 5 As far as the rest of the frameworks that Colloquy uses are concerned… the SILC framework we use doesn't appear to be in MacPorts, nor is Acid (our Jabber framework) or AGRegex or, well, any of the dependencies of Colloquy. Some of them aren't even available in forms that work well as libraries (AsyncSocket, and our SASL code, for example). 6 6 7 Plus, Colloquy is built as a pretty standard Mac app. It assumes that most (aside from Growl and F-Script) non-system frameworks will be shipped within the app bundle. I'm not sure what the benefit of changing this is.7 Plus, Colloquy is built as a pretty standard Mac app. It assumes that most (aside from Growl) non-system frameworks will be shipped within the app bundle. I'm not sure what the benefit of changing this is. 8 8 9 9 Bottom line (as far as I can see) is that it seems like there would be a ton of work involved in making this happen for very little gain. And it's not like Colloquy is hard to download, or keep up to date.