I can understand how it would be rude for me, a complete newbeginner, (note: n000b) already coming here and requesting things.
Thing is, I've been around trying different kinds of authorware like Quest, and so far Quest seems to be the closest to perfection that I've tried.
However, there's a few things I'd like to suggest. Only suggest of course, I can't very well expect the programmer to drop everything he's doing and obey all my wishes.

Also note that these wishes are written from the perspective of a (very) casual programmer / author, and not hardcore in either of the two.


Simpler connection between the non-coding editor and script commands

I think that Alex talked about this when announcing Quest 5.0. I don't know any specifics, so I'll throw this in anyway.

One of the main problems I have with Quest right now, is that if I am to specify something a bit more advanced than the built-in easily-accessible functions that don't need coding, I have to go into the ASL file and edit everything from there. For an author point of view, this is fairly tedious, at some points completely unfathomable.

What I'm suggesting is a "Execute script" function, much like the "other script function" but that handles multiple lines of code, so I don't need to scout through the entire ASL file to find the proper object or room, and then put in the right code in the right spot... to be honest, I'm not really that good a programmer, but I'm good enough to handle smaller bits and pieces of code .

Pros
Makes it easier for non-programmers to acheive more advanced functions and coding options

Cons
None that I can think of for the author him/herself, but it's quite possibly quite a bit of work for Alex.

Objectifying of Music/sounds
I suggest making sound files an object, much like "objects" or "rooms". This would allow potentially more methods and functions to control music in a game.
Why? Well, considering that Quest is aiming to modernize the 80's text adventure game, a better control on the music could be excellent in several ways:

[*]Several pieces of music/sounds playing simultaneously. For example if you want background music with your game at the same time as you're adding sound effects like doors, creaking or even full speech.

[*]Easier control-functions. An object name could be defined for the music. Let's say that have a certain area in my game consisting of a few-four rooms. All the while the player are in these rooms, a certain piece would be playing. Let's say I add this said piece and called it "scarymusic". With the name I could then check if the certain music was playing in every of these rooms, and if it wasn't, it could start.

[*]Possibility for simple effects. I'm thinking very simple things like fading in and out music and the likes.

Pros: Gives games a much more multimedia and accessible feed. Adds more layers of emotion into a game
Cons Again none for the authors, but probably a chore to program into the engine.


Ok. That's the things I can think of so far. I might add more things as they come up in my mind. I hope for feedback from everyone, and by all means, if you think I have a proper nerve to come here and suggest things like a besserwisser, feel free to say that too:)

Thanks for the suggestions, please keep them coming!

Regarding the script suggestion, I'm starting work on the editor for Quest 5.0 now, and my plan is that you will be able to switch back and forth between code view and "friendly" views of things like object definitions and scripts.