Pallet and MacPorts.Framework

less than 1 minute read

A brief note on the status of Pallet and the MacPorts.Framework:


Pallet continues to have some user-interface weirdness that I have not really figured out (nor have I spent much time trying to figure it out either) and is dependent on getting the MacPorts.Framework completed


The framework has one two major issues:

  1. It needs to be capable of posting asynchronous notifications from the Tcl Framework to the Objective-C classes that are wrapping the Tcl code. I have found some reference code that may help me write an implementation, but have not begun doing so.
  2. I am now thinking that I might need to write a MacPorts Application Kit Framework that would provide applications (which should run their user interfaces as the console user, not as root) an API that calls an authenticated helper for certain tasks. This may further push back Pallet development.

I have just moved and am starting a new job next week, so I will probably not be picking these tasks up quickly, but if anyone wants to work these issues or projects with me, drop a line.