On Wednesday, January 29, 2003, at 04:45 PM, Rich Morin wrote:
PB isn't the real issue, as I see it - anyone who's at all serious about hacking Perl code will need the developer tools anyway. They include the headers you'll need to install CPAN modules, for instance.At 4:05 PM -0500 1/29/03, Dan Sugalski wrote:That's it, though I'm not sure avoiding the build is that big a deal.It isn't, as long as the programmer is working from a project. OTOH, I'll be distributing the Perl app and many users won't have PB. This means that they can still make changes to the "model" and at least some to the "view".
The real issue is users who want to make minor changes to your app, but don't have easy access to a copy of your project folder. Regardless of whether or not they have PB, they can't rebuild the app without having the original .pbprj document and everything else from the project folder.
Having said that - no, there shouldn't be any problems with working that way. No technical problems at any rate - as Dan said, it presents an organizational issue, as whatever changes you make in the .app bundle won't get copied back into your project folder.
As Dan also said, avoiding the build isn't that big a deal. The first build takes a while, because it's creating the executable and linking it with the framework. But subsequent builds happen in an eyeblink, because all they're doing is copying files into the .app bundle's Resources/ folder.
sherm--
If you listen to a UNIX shell, can you hear the C?
