Josh Lewis wrote:rgg wrote:This works pretty fast, especially because having only one image eliminates the need to browse.
For a single image that is. Many of us work with lots of pictures. As a result the old editor is still easier to work with.
I work with lots of pictures too, but that's beside the point. The key is that, provided you already know the id of the image you want to use, you enter it the image # as search criterion, and then you always get exactly one single image.
However, I hear you think, "But I don't have the image id!".
Perhaps you don't. I don't know the way you work on a page. However, with the way I work, I often do. When writing a mountain or route page, I typically consider both my own images as well as any relevant other ones on SP. Now, the key is that I don't search for those from within the page I'm editing. Instead, I just browse through [urlhttp://www.summitpost.org/image/]images[/url], using the Advanced Search option and entering the name of the mountain, route, alpine refuge or any other relevant feature. The result would be something like this:
http://www.summitpost.org/object_list.php?object_type=3&object_name_3=Hochwilde&sort_select_3=score
I then look at the individual images. I learned that the best time to do this is after writing most of the text, because that way, when I see a good image, I usually know where in the page it could be relevant. As a bonus, this method automatically provides the image id. I might add that a good image in this context is not necessarily one with a high score, but one that adds something to the text.
Oh, and I like the new editor much better than the old one, even though there are a few minor annoyances with it (if I copy and paste a fragment of HTML code, it annoys me that the editor modifies it slightly, instead of just accepting it exactly as is).
Rob