I think what Mark meant was not to use mc but instead MetaCard as a whole
word. to make it even more obvious.
On 30 Jun 2011, at 16:49, Ken Ray wrote:
Using a prefix implies that there is the possibility of extending the MC IDE
in the future and a potential getting-in-the-way. This is
On 30.06.2011 at 8:33 Uhr -0500 Ken Ray apparently wrote:
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
Hey all,
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
On 6/30/11 6:33 AM, Ken Ray wrote:
Hey all,
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.
Using a prefix implies that there is the possibility of extending the MC IDE
in the future and a potential getting-in-the-way. This is something we don't
want.
I clearly agree that the getting in the way is something we don't want,
but can you clarify what you mean by extending the MC IDE?
On 6/30/11 8:33 AM, Ken Ray wrote:
Hey all,
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.
