On 03/23/2011 09:10 AM, Daniel Heberl wrote: > I asked Richard Laing if he had ever considered contributing to the > MacPorts project > by providing the sources of Porticus and he replied favorably: > > >> I have thought about it many times! I keep hoping to find some time to get >> back to Porticus >> but that looks increasingly unlikely. If anyone is willing to take it on I >> am happy to contribute >> the source code, someone will have to sort out any licensing issues >> (mainly to check that things >> like the icons can still be used as I think everything else should be >> fine). The code at this point >> is quite out of date nut I haven’t compiled it with the latest Xcode tools >> at al. I would try and >> make sure it all compiled again before handlng it over. > > <http://alittledrop.com/blog/?p=46#comments>
Yes, we have developed our own GUI already which uses a real framework instead of screen scraping. It's meant to be much more robust that way, by using the API we provide. As far as I know, Porticus does not work with the preferred 'portdbformat sqlite' as it relies on information in the file hierarchy from the old flat registry. http://trac.macports.org/wiki/MacPortsGUI It has been developed as part of Google's Summer of Code in 2009 and 2010. The main problem is that outside this work from students almost nobody touched the code... Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
