The demo has two "panels". The left, a tree list, is used to select
a job item. The right displays the job.
The problem is that when you select or browse the tree list,
the corresponding job is automatically launched. I find this
behaviour irritating, especially if you have a long list of items
and you are browsing it with the PageUp/Down keys or if
you are searching for a job item with the arrows keys.
I propose to separate the two tasks.
1) Select a job item with the arrows keys or with a mouse click.
2) Fire the corresponding job with an 'enter' or a (double) click
That seems to me to be more logical. All applications using this
type of diplay are using the proposed behaviour, IE, Mozilla,
chm help file viewer, ...
The demo has two "panels". The left, a tree list, is used to select
a job item. The right displays the job.
The problem is that when you select or browse the tree list,
the corresponding job is automatically launched. I find this
behaviour irritating, especially if you have a long list of items
and you are browsing it with the PageUp/Down keys or if
you are searching for a job item with the arrows keys.
I propose to separate the two tasks.
1) Select a job item with the arrows keys or with a mouse click.
2) Fire the corresponding job with an 'enter' or a (double) click
That seems to me to be more logical. All applications using this
type of diplay are using the proposed behaviour, IE, Mozilla,
chm help file viewer, ...
That's worth looking into, but maybe we should defer this until after we get
2.5 available.
A little background (and this will be a suprise to Robin too): I'm planning
on continuing my work with the demo to update *all* code that requires
updating, get it more modernized, so on and so forth. Right now we're
working on a lot of that, but there's a lot that isn't being done simply
because it's a big digression from the primary task of having a working demo
for the 2.5 release.
As Robin says, this is a teaching too, so it's actually quite a valid
assumption to consider that someone might simply want to browse the
overviews or sample code without invoking the demo.
'course, it's Robin's baby so we'll see what he thinks about all that too
The demo has two "panels". The left, a tree list, is used to select
a job item. The right displays the job.
The problem is that when you select or browse the tree list,
the corresponding job is automatically launched. I find this behaviour irritating, especially if you have a long list of items and you are browsing it with the PageUp/Down keys or if you are searching for a job item with the arrows keys.
I propose to separate the two tasks.
1) Select a job item with the arrows keys or with a mouse click.
2) Fire the corresponding job with an 'enter' or a (double) click
How about this: When an item in the tree is selected the existing demo is cleaned up and removed as it currently is, but instead of showing the next we leave the user on the overview page. Then there is a "Run Sample" button added to the overview page, either above the HTML window displaying the overview text, or perhaps even embedded into the html.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
That's worth looking into, but maybe we should defer this until after we get
2.5 available.
Or at least until the current batch of changes in the demo are done.
A little background (and this will be a suprise to Robin too): I'm planning
on continuing my work with the demo to update *all* code that requires
updating, get it more modernized, so on and so forth.
Cool!
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I think we should differentiate (or clarify) selection in terms of both keyboard and mouse navigation. I think on a single-click or on keyboard select and ENTER, it should show the module's overview page, demo code, and a "Run Sample" button. Double-click in Finder/Explorer is mostly restricted to execution, so maybe it would make sense to have a double-click emulate the "Run Sample" behavior and load the demo.
Also, this reminds me of an idea I had regarding the demo that I thought I would throw out. Don't know if this would be 'featuritis', but as I work with wxPython more I find myself wanting to 'play' with the demos when learning new classes or debugging. What would be really cool (IMHO) is if you could edit the code that is displayed in the "code view" and then when you click on "Run Sample", it loads the code with your edits. Of course, the edits aren't permanent, but just like the Python interpreter the purpose would be to make it easier to explore and fiddle with the wxPython classes. It could also probably be helpful when trying to isolate a bug in your own code. (i.e. see if you can modify the sample to reproduce it) I don't think this would be difficult to do (turn off read-only in wxSTC, then load the text from wxSTC rather than from disk). You can, of course, do this by editing the sample file from disk, but then you'd have to locate it, then make a copy or rollback the changes when you're finished.
What do you guys think? Is this 'too much' or do you think it's useful?
Thanks,
Kevin
···
On Nov 28, 2003, at 3:07 PM, Robin Dunn wrote:
Jean-Michel Fauth wrote:
Changing the demo behaviour.
The demo has two "panels". The left, a tree list, is used to select
a job item. The right displays the job.
The problem is that when you select or browse the tree list,
the corresponding job is automatically launched. I find this behaviour irritating, especially if you have a long list of items and you are browsing it with the PageUp/Down keys or if you are searching for a job item with the arrows keys.
I propose to separate the two tasks.
1) Select a job item with the arrows keys or with a mouse click.
2) Fire the corresponding job with an 'enter' or a (double) click
How about this: When an item in the tree is selected the existing demo is cleaned up and removed as it currently is, but instead of showing the next we leave the user on the overview page. Then there is a "Run Sample" button added to the overview page, either above the HTML window displaying the overview text, or perhaps even embedded into the html.
How about this: When an item in the tree is selected the existing demo is cleaned up and removed as it currently is, but instead of showing the next we leave the user on the overview page. Then there is a "Run Sample" button added to the overview page, either above the HTML window displaying the overview text, or perhaps even embedded into the html.
I think we should differentiate (or clarify) selection in terms of both keyboard and mouse navigation. I think on a single-click or on keyboard select and ENTER, it should show the module's overview page, demo code, and a "Run Sample" button. Double-click in Finder/Explorer is mostly restricted to execution, so maybe it would make sense to have a double-click emulate the "Run Sample" behavior and load the demo.
Sounds good.
Also, this reminds me of an idea I had regarding the demo that I thought I would throw out. Don't know if this would be 'featuritis', but as I work with wxPython more I find myself wanting to 'play' with the demos when learning new classes or debugging. What would be really cool (IMHO) is if you could edit the code that is displayed in the "code view" and then when you click on "Run Sample", it loads the code with your edits. Of course, the edits aren't permanent, but just like the Python interpreter the purpose would be to make it easier to explore and fiddle with the wxPython classes. It could also probably be helpful when trying to isolate a bug in your own code. (i.e. see if you can modify the sample to reproduce it) I don't think this would be difficult to do (turn off read-only in wxSTC, then load the text from wxSTC rather than from disk). You can, of course, do this by editing the sample file from disk, but then you'd have to locate it, then make a copy or rollback the changes when you're finished.
What do you guys think? Is this 'too much' or do you think it's useful?
I've thought about that a few times too. It would be nice to have.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
> That's worth looking into, but maybe we should defer this until
after we get
> 2.5 available.
Or at least until the current batch of changes in the demo are done.
Guess it depends; I personally don't know if it would be worth holding up
release on, if all else was ready. It's a lot of work in that all demos will
have to be retested using the new framework (well, actually it's not much
work but more like 'a lot of time')
> A little background (and this will be a suprise to Robin too):
I'm planning
> on continuing my work with the demo to update *all* code that requires
> updating, get it more modernized, so on and so forth.
I think we should differentiate (or clarify) selection in terms of both
keyboard and mouse navigation. I think on a single-click or on keyboard
select and ENTER, it should show the module's overview page, demo code,
and a "Run Sample" button. Double-click in Finder/Explorer is mostly
restricted to execution, so maybe it would make sense to have a
double-click emulate the "Run Sample" behavior and load the demo.
That sounds pretty good.
Also, this reminds me of an idea I had regarding the demo that I
thought I would throw out. Don't know if this would be 'featuritis',
Nah
the demos when learning new classes or debugging. What would be really
cool (IMHO) is if you could edit the code that is displayed in the
"code view" and then when you click on "Run Sample", it loads the code
with your edits.
That would probably be fairly straightforward to implement, actually. A bit
of jiggery pokery to get all the support code in place, but once it's in
place I think it would be doable, either loaded from the editor itself or
from a temp file that self-destructed when the demo was terminated (this
would also make the edits persistent during the demo session, even if you
went to a different demo then back to the one you edited).
