Joe Francis wrote:
>>>> In Internet Explorer (and Microsoft Office apps by default), if you
>>>> [snip]
>
> This is one of those times where my natural inclination is to agree with
> you, but experience is telling me otherwise. If we had a selection
> model that snapped into element mode the moment you crossed an element
> boundary, it would get in the way of things much like your grammer
> example. Just yesterday I was shameless copying ad material from
> websites to use to describe games I was selling on EBay, and there was
> someting like the following (psuedo html below):
>
> <h3> Mac OS System Requirements
> <ul>
> <li> blah blah blah
> <li> blah blah blah
> <li> blah blah blah
>
> I wanted to copy the whole list and the "System Requirements" portion of
> the header. I couldn't do that in an auto-element-selectin model. But
> it worked like a charm in our current model, and I got just what I
> wanted on paste in composer.
>
> I will (again) state that I do think we need some good way to do element
> selection. It just shouldn't be automagic. Maybe "option-select".
> Maybe an element heirarchy toolbar. Maybe a sidebar. UI folks, give me
> some love here! I'm just throwing out ideas.
We already have this. It's called "Show All Tags" mode in Composer. You
click on the yellow tags to do "structural" selection, or drag normally
for "content" selection.
It may not be the fanciest structural editor, but is an interesting
experiment in that direction.
Charley
