14
Jul
FinkCommander: not dead.. yet.
14
Jul
The problem with the current FinkCommander is that I’m trying to interface a Perl program (fink) with python. The only way to do this properly is to call the perl command a bunch and hope that it doesn’t cause your processor usage to spike like no tommorrow. So, the best and most logical thing is to rewrite FinkCommander with CamelBones. This way, I can interact directly with fink’s classes and display them with a cocoa window! The other problem is, I don’t know perl all that well, but then again, I didn’t know pyobjc/objc that well either.
furies said,
Wrote on August 2, 2007 @ 2:45 pm
Good luck with the new framwork!
Koutarou Ishikawa said,
Wrote on September 14, 2007 @ 7:03 pm
Great wonderful decision!
May force be with you.
Ilgaz said,
Wrote on December 22, 2007 @ 10:09 am
Sorry for a bit late response but I am one of the guys that Fink _needs_ a freeware GUI to serve its purpose, especially on Mac land where people purchase Shell stuff doing packaged Applescripts (which I don’t critique).
I did a mad experiment. I just got the CVS version via SF stock CVS commands and clicked “Build” on XCode 3 on Leopard. There seems to be a massive performance increase, it is like that 100% CPU dropped to 25% levels at most.
Perhaps there was also a problem about how Fink Commander.app generated by earlier XCode versions?
So, if one actual developer (not me) just builds a Fink Commander Tiger/Leopard edition, it will save a lot of users and those users may also help with their feedback. Not everyone of us are “point and click” guys, for example, I use Fink Commander as a browser while doing Fink things at Terminal.
David Coppit said,
Wrote on June 27, 2008 @ 4:17 am
Do you have access to the python library? Could something like the Inline module help? Or maybe SWIG?
Keep up the good work with the new Fink Commander! I’d help if I had the spare cycles…