Closed liamks closed 12 years ago
It's cool, but just being devil's advocate for the second - would anybody want these turned off?
I.e. what's the point of being able to configure something that everybody wants enabled?
Personally I think they should all just be enabled. The plist might provide utility to someone debugging an app?
I think when you give developers more options they tend to create things which one could hardly conceive of initially. I think providing options is positive. On the other hand, opinionated software tends to reduce the options in favour of defaults... I suppose the question is, is MacGap opinionated?
I'd want developer tools turned off if I was distributing an app to others that I didn't want them casually poking around in.
I obviously realise more clued in user's could turn it on.
We don't enable any dev features atm, as you can easily test stuff in the browser.
@maccman I've found developer tools to be very useful. I can't test MacGap only features in a browser. When adding new features I found the developer tools indispensable. As a result I added them to WebPreferences.plist (disabled by default though).
Developer tools are enormously helpful. The browser is a hugely different env.
For example, you can't test stuff that comes with the macgap api such as growl.
As to users who can poke around, there is no source code protection for macgap anyways since anyone can just look at the code in the www folder.
Ok, what if I only have developer tools and WebGL on the WebPreferences, since the other options will most likely be always enabled?
I was thinking we could always enable webgl, and enable the dev tools with an env variable. How about that?
Good compromise. Should I toss them in Constants.h, or create a new header file?
Fixed in #aed75f91bf9ee717a2372334dd48286453c46329
You can switch it on by running:
settings write com.MacGap developer 1
Developers can now enable WebGL & Developer tools via the WebPreferences.plist.