Re: Annoying "font:" popup?? How to kill it?

Ian Smith wrote:
> 2009/3/30 Kees Epema <[email protected] <mailto:[email protected]>>
> 
>     i am no expert, but i think the style statement should work fine
>     without the semicolon. regards, kees
> 
> 
> I really wouldn't recommend that. It may work with some browsers, but
> not all.
> 
> For Dave Rankin, the simple answer is just to keep typing! Quanta is
> making a suggestion, assuming that you might want to add to your style
> statement. But if you ignore it and keep typing, it should go away.
> 
> In fact I just tried your script and got several suggestion while typing
> it - one after <, one after p, and one after style=
> 
> Each time, I could either select a suggestion and press "enter" or
> ignore it, keep typing and the box would go way. AFAIK, this is normal
> behaviour. If your popup is "modal" (i.e. won't let you continue until
> you deal with it), that seems very odd.
> 
> Cheers,
> Ian
> 

Ian,

	Thanks, I know quanta is just making suggestions, but 50% of the time, the
point where you stop typing is after the semi-colon and that's what makes the
font pop-up so annoying. Here is how it happens:

	(1) take any element, say for example the <ul> statement that you want to add
css to that will alter the default behavior you have set in your stylesheet for
the <ul> element;

	(2) you take the cursor and place it after the 'l', hit space and then start
typing 'sty     like this: " <ul sty ";

	(3) at that point quanta with its popup knows you want to enter the style
element and it is the only choice that remains in the popup, so you hit return;

	(4) quanta correctly fills in the style element with both double-quotes in
place as it should. Your now looking at this:

		<ul style="">

	(5) you then fill in the css property you want to use, say text-indent:1em;
--- *boom* as soon as you hit the semi-colon you get the 'font' annoyance.

	This is really a matter of execution logic at this point. 1/2 the time you are
done at the point of the semi-colon; half of the time you are not. Regardless,
with 94 odd css tags not including the pseudo-elements there is less than a 2%
chance that you will actually want the 'font' element next after the first
semi-colon and the chance that you now want it after the second, third and ...
so on semi-colon get statistically much much worse by orders of magnitude.

	The code is just making a default WAG here and should be fixed. The solution
is simple, quanta just needs to learn *not* to display *anything* popup-wise
after a semi-colon *until* the first

		[:alpha:] or isalpha (char *c)

	character is typed following a semi-colon. Then quanta can logically start
guessing. That would get rid of the blind guessing of 'font' that is currently
taking place after every semicolon, thus improving quanta's efficiency and
removing the annoyance all in one-fell-swoop.

	Now..., just where in quanta to stick that extra line of code. Dev's, that
gotta be you, I'm no help there.

	Also, if you want me to file it as a bug or feature request, just let me know
and I'll be hapy to do it. Thanks.

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com