IDE Requests

[SirWobbyTheFirst]

So, as you probably all know, the Kickstarter was a success and thus I thought it would be cool to list a couple of feature requests I have for the IDE for the next gen engine, these are a few things I think wouldn't be too hard to implement into the IDE and whilst not completely needed, I think they would be nice additions to the IDE:

1) Could we possibly have some project management features integrated into the IDE? One thing I definitely like about Xcode and Visual Studio (Blasphemy I know) is the solution feature and whilst I know you can make a plugin, of which I am doing so, it would just be awesome to have it integrated instead of having to go through File > Open for each stack in a big project, which if you're OCD like me, means you tend to have them in their own folders, is kinda tiresome.
2) A property or function which states whether or not a stack has been modified or not. I know the IDE as is does something to discern modified stacks from unmodified but the code behind the IDE scares me, this kind of ties into number 1 for me, because of the plugin I am working on.
3) A shortcut key like Ctrl+Shift+B to build a stack into a standalone, it's a shortcut key I really miss when I've spent a lot of time in Visual Studio. Well more shortcut keys in general for the IDE.

I also think this would be a cool thread for other people to drop down their own requests for the IDE, also I would just like to remind you all that we do now have a sub-reddit http://www.reddit.com/r/livecode, so feel free to drop by so we can make memes out of LiveCode. XD

[davek]

I would like to have profiles for standalone application settings. These should be saved into the mainstack as standalone settings are now and would enable rapid reconfiguration of properties before building executables.

Thanks

[mwieder]

Regarding #1, I'd really like LC to have the concept of a project. This goes beyond just IDE changes, and I'd envision it something like:

Code: Select all

Project
  Main Stack
  Substack 1 -> this would be a pointer to a separate file
  Substack 2 -> this would be a pointer to a separate file
  Image
  Sound file
  Etc

That way Substacks and other included objects would just be references to other files. You could use Substack 1 (a standard library, say) in several different projects, and just have to change it once to have the changes propagate to all the referencing projects. Sort of the way other environments use the concept of "Assets".