I love it. I agree with Ryan, I think a portfile Editor/IDE should be a separate MacPorts.framework project from Pallet.
—Mark _______________________ Mark E. Anderson <[email protected]> On Wed, May 6, 2015 at 8:40 PM, Ryan Schmidt <[email protected]> wrote: > > On May 6, 2015, at 5:14 PM, Kyle Sammons wrote: > > > My name's Kyle Sammons and I've been accepted into this years GSoC. I > was also a GSoC participant for MacPorts last year working on Project > "Clean-up Stuff", which created the "port doctor" and "port reclaim" > commands. > > > > My project for this year is to get Pallet, the MacPorts GUI, up and > running with the support for newest versions of OS X and XCode. After that, > I intend to give it, and the Framework, some more modern-day-MacPorts > features. No features are set in stone as of yet, but I'm considering > adding doctor, reclaim, rev-upgrade, a progress bar, or possibly even the > ability to edit portfiles. > > > > Once again, none of these potential features are set in stone so if you > guys would like to suggest any that would be nice to have, or have some > questions/concerns about the project, feel free to shoot me an email. > > Great idea! I would only propose that you *not* pursue the idea of letting > people edit portfiles, as that opens up lots of possibilities for problems. > Pallet should be the utility for users who are not comfortable using the > command line. Those users don't need to be editing portfiles. > > > > _______________________________________________ > macports-dev mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-dev >
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
