2009/1/12 Kevin Ball <[email protected]>: > > On Sun, Jan 11, 2009 at 11:22 PM, François Vaux <[email protected]> wrote: >> >> 2009/1/12 Kevin Ball <[email protected]>: >> > [...] > > Cool, thanks! Absolutely you can reuse it. I'm happy that my tinkering can > be of use. I was thinking on the train to work this morning about IDE-like > features, I've now cloned solylace and am looking forward to playing with it > on my ride home.
Well, I think an IDE is missing for all Shoes beginners, something that can help them with their first steps with the toolkit. Having useful tools like a reference (Shoes already have this, but not a Ruby reference for exemple), instant run, preview window, a console for experimenting stuff,... all of it can be really helpful for novice programmers, even for experienced ones actually. I'm working on a feature list and trying to set the specs for the app, but if you want to contribute you're welcome! (as is everyone on this list) >> > [...] > Mm, I like this idea, though I'm not sure if it will work if there are > conflicts between e.g. keypress event handlers in the code and in the main > preview application. > I don't really have straight in my head the distinction between an app > object vs a window, vs a flow really. They all have overlapping properties, > but each has some slightly different details. Hopefully as I play with this > more it will start to jell better. I think keypresses are bound to a window, so the window that has focus is where the events occur. The difference between app / window and flow is pretty blurry but I think I'm not wrong if I say that: - An app is a window with no parent - A window created with the window method is a window bound to the caller app (it has a parent method) - A flow is simply a slot. >> > [...] > > If the edit_box is selected, the keypress events don't seem to make it up to > this handler. I think this is because the edit_box is handling them itself > and not passing them on. Trying > > @e.keypress do |k| > #stuff > end > > doesn't seem to work either though. Well, that is a problem indeed, I didn't know about it and it seems weird. Looks like keyboard event handling isn't supported that well, maybe this could be one of the issues to fix for the next release. -- François
