Improved Auto Replace function

[FrankC]

Hello,

I sent this in to the Support email address already, but for reference purposes I will post it here, too.

I would like to see the Auto Replace editor work the same way as the Library editor, namely with a before & after caret option. This way, we will just have to type <a followed by a space, to get <a href="#">|</a>, with the caret in the place of the |.

Just imagine how much that speeds up the manual coding:

<d + space --> <div id="|"></div>
<s + space --> <span class="|"></span>

etc. etc. Anything that needs a value to be typed in will be created much easier.

With this, the Call Words function, which every time requires an additional Ctrl + j, could be deleted, keeping WeBuilder as lightweight as possible. The Call Words function is buggy now anyway (v. 2011), because it does not replace the call word, but adds to it. So a + Ctrl + j, created to produce a hyperlink as mentioned above, becomes a<a href="#">|</a>.

A work-around would seem to be to create Library snippets and click them. However, code-writing web developers like to keep their hands on the keyboard as much as possible (at least most of them do), and keep the panels hidden as much as possible to have an as big as possible preview pane.

[Edit Aug. 22nd.: With the Auto Replace function I described, the Auto Complete function could be taken out altogether as well, because users can create their own auto completes with such an Auto Replace. And the current Auto Complete function seems buggy, too, because the list of valid elements and attributes does not always appear while typing tags, even though the option Enable Auto Complete is ticked.]

[davenz]

+1

I agree with FrankC on this.

I use F4 to hide the panels because my monitor doesn't allow enough room for a decent preview window and all the panels I use open for easy access.

I have not noticed the call-words function being buggy, but now you mention it, it does do what you describe; do you know if WB2010 behaved like this?

As for the library snippets workaround you suggest; do you have to click them? Can't we assign keyboard shortcuts/callwords to them and insert them that way? The big problem I see with this is as implemented is depending on how many snippets one would have, we might run out of key combos for keyboard shortcuts (without taking away other functionality) so perhaps more possible key combinations would have to be added.

Thanks for the suggestions. I know the developers do look at these boards and take notice of these suggestions for possible inclusion in future versions. Being a small coding team though, they usually look at the easier-to-implement features first; any major new features suggested may be noted but postponed in favour of of other smaller features. They also have a brief to keep the editor slim and fast; already I see performance hits in 2011 and while this isn't a problem on my home machine, sometimes it does struggle on my work rig, especially after being open for many hours. That doesn't mean we should stop suggesting improvements though.

Cheers

[FrankC]

I have not noticed the call-words function being buggy, but now you mention it, it does do what you describe; do you know if WB2010 behaved like this?

Thanks for confirming that it does what I described. I don't know about WB 2010 cos' 2011 is the first version I've used.

Can't we assign keyboard shortcuts to [the library snippets] and insert them that way?

The way it works now, only functions that are listed under the WB (sub)menu(s) can get keyboard shortcuts, with a couple of exceptions. And the option of creating one's own keyboard shortcut assignment functions (plus the keyboard assignments) would seem a solution, but then you would have to remember a whole lot of keyboard shortcuts. A good Auto Replace/Call Words function would be much easier, because you'd only have to type in the < plus the first or first two letters of the tag + space to get the desired result. Much easier to remember.

[davenz]

I see what you mean now; I'm a bit slow the older I get. By the time I'm 60 I should be blissfully unaware of my surroundings.

Thanks for explaining it and yes, it would be great as you have described it.

Thanks

[FrankC]

The way it works now, only functions that are listed under the WB (sub)menu(s) can get keyboard shortcuts, with a couple of exceptions.

That in itself is not true. As I discovered today, Call Words can also get keyboard shortcuts. But it would still be a whoooooole lot of shortcuts to remember, if all the HTML tags would get one...