On 6/30/11 6:33 AM, Ken Ray wrote:
I just gave a presentation last weekend at the LiveCode Live event on the MC
IDE and one of the things I brought up was the fact that a great benefit to
the MC IDE vs the LiveCode IDE is that it really tries to "get out of the
way of the developer."
And although it currently does a pretty good job of that, there are a few
places that IMHO still need to be changed. The two that immediately come to
mind are the Preferences and Properties stacks, both of which prevent you as
a developer from being able to name *your* stacks "Preferences" or
"Properties", and there are probably other stack name conflicts as well.
For the next build of the IDE, I'd like to change the IDE stack names to
have an "mc" prefix (like "mcPreferences"), but since this affects anything
that runs as a plugin, etc., I wanted to bring it up for discussion first.
What are your thoughts on this? Good idea? Bad idea? ...?
I like it for several reasons:
1. "Preferences" is such a common name that not changing the IDE's stack
name is too likely to result in conflict.
2. The proposed prefix solution follows RunRev's convention, long
established and well understood.
3. It's simple to implement, and as a volunteer project I appreciate the
impact on your time.
Thanks for taking that on -
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
metacard mailing list