I'm as big a fan of overcomplication as anybody, but I think that
this might be getting away from my original intention with the
command. It's really just supposed to figure out into what context
you've dropped an image and give it the appropriate "decoration".
It's not supposed to do all your coding for you ;-). The problem is
that the techniques are being revised and improved every couple of
months and you can never account for all of the IE hacks required for
some techniques. The amount of inserted code gets out of hand and
everybody has different preferences that you'd waste a lot of time
accounting for. Best, in my opinion, to let people create their own
code and just provide tools to speed up the repetitive tasks.
My suggestion would be to create snippets for the different IFR
techniques and tab stop the entire background, width and height
section so that you can delete it if you have intentions of dragging
an image in. Then have the drag command set up so that when dropped
into the property value scope it inserts background url, width and
height properties. Then you could just type ifr[tab] or mezzo[tab]
etc. and get the technique you want, and have the image ready to drop
On Oct 28, 2006, at 5:30 PM, pierre pracht wrote:
Well text-indent: -9000px; overflow: hidden; doesn't work with span
So we must put : display:block;
Then why not change text-indent: -9000px; to width:0; height:0;
The whole code can be tan stopped so you let people put there
image replacement technique in it (better idea later).
and that the "span" be tab-stopped in
(that's 10 tab stops! might be excessive).
For me using a mirror for the selector is a big win.
Drop the whole IFR code can save a lot of time.
In this case, tab stop the background is not useful.
Why not split the drag command for the two scope :
meta.property-list.css : unchanged. (Just first part)
source.css, source.css.embedded.html : multiple command for each image
So lazy people like me, would not stick with wrong technique ;)
Best, pierre pracht