Hi,
I am thinking about upgrading to WB 2014. However, I find the price high for an upgrade -- I paid the full price only two years ago. So it should really be worthwhile, and there are four issues important to me.
The first is essential, namely that the Preview mode does not remember the scroll position in WB 2011. Every time you change from Preview to Code Editor and back, the Preview page goes back to the top. Saving or not makes no difference. That makes the Preview mode as good as useless to me, no matter how up to date the Chrome preview rendering. If I load the page in an actual browser, save the code after having made changes and click the browser's F5, the position is remembered. So it is possible. Has this issue been resolved in WB 2014? If not, would it be possible to tell when it will be?
The second concerns this. If you are working on the CSS and want the Inspector to show, you must have the cursor inside a CSS property section in a style block or sheet. If you put it outside it, just before a { or after a }, the Inspector panel goes blank. As does it when having the cursor inside an inline style declaration. I would like the Inspector to stay as long as I have my cursor anywhere in an inline style declaration, a style block or a style sheet. Is this the case in WB 2014?
The third issue is whether the unstable file list in the File Explorer panel has been resolved.
The fourth is whether a Save Copy As option has been added.
Thanks in advance.
[By the way: has the url option deliberately been set to OFF in the signature form of this forum? I need to update the url in my sig.]
Have these issues been improved in WB 2014?
Moderator: kfury77
Forum rules
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
- Do not create new topics for already requested features. Add your comments to the existing feature request topics instead;
- Create separate topic for each feature suggestion. Do NOT post a number of non-related feature suggestions in a single topic;
- Give your topic a meaningful title. Do NOT create topics with meaningless titles, such as "My Suggestion" or "My Problem".
Re: Have these issues been improved in WB 2014?
The preview bug is still there, but it's very high on our list now.
The inspector behavior hasn't changed. Consider this: a { ... }|b { ... } - if cursor is in the marked position, which one should inspector display - rule a or b? I suppose we could cheat in some cases but until now I didn't even know this was a problem.
The file explorer issue has indeed been resolved.
Save Copy As hasn't been added but I can write a simple plugin for this if you want.
Url's have been turned off because of SEO spammers. PM me, I can try updating it via administration panel.
The inspector behavior hasn't changed. Consider this: a { ... }|b { ... } - if cursor is in the marked position, which one should inspector display - rule a or b? I suppose we could cheat in some cases but until now I didn't even know this was a problem.
The file explorer issue has indeed been resolved.
Save Copy As hasn't been added but I can write a simple plugin for this if you want.
Url's have been turned off because of SEO spammers. PM me, I can try updating it via administration panel.
Blumentals Software Programmer
Re: Have these issues been improved in WB 2014?
Thanks for the speedy reply, Aivars.
I would suggest to focus the Inspectors function on general coding help in case of uncertainty and have it switch to the CSS help sub function whenever the cursor is anywhere inside an inline style property, a style block or a style sheet. I don't even need it to read out the declared value like it does know when I have my cursor on a CSS declaration, because I can see that in the file. If in doubt, just create a small customer poll to see if I'm right.
Please let me know when you have succeeded. I would even suggest to send out a global e-mail if you have, because I would think that many potential customers have stuck with their other editor because of this. For me, it is a breaking point and a point that would make WB the Best Editor at the same time. And I have really tried them all.The preview bug is still there, but it's very high on our list now.
I only use the Inspector if I'm not sure about something, in case of CSS about the (pseudo-)selector, property or possible values. As I would think most of us manual coders do. I know that that entails a whole different way of thinking for you, but if we are sure about matters, we don't need the Inspector, do we? Then we just type or use the Library or keyboard shortcuts.The inspector behavior hasn't changed. Consider this: a { ... }|b { ... } - if cursor is in the marked position, which one should inspector display - rule a or b? I suppose we could cheat in some cases but until now I didn't even know this was a problem.
I would suggest to focus the Inspectors function on general coding help in case of uncertainty and have it switch to the CSS help sub function whenever the cursor is anywhere inside an inline style property, a style block or a style sheet. I don't even need it to read out the declared value like it does know when I have my cursor on a CSS declaration, because I can see that in the file. If in doubt, just create a small customer poll to see if I'm right.
OK, good. Is it useful to update (not upgrade) my 2011 version for this, or has it been resolved only with the 2014 version?The file explorer issue has indeed been resolved.
If you would, yes please. Could that also be used for WB 2011?Save Copy As hasn't been added but I can write a simple plugin for this if you want.
Will do, thanks.Url's have been turned off because of SEO spammers. PM me, I can try updating it via administration panel.
Re: Have these issues been improved in WB 2014?
To fix the File Explorer issue we had to make major changes in the file explorer so it's fixed for 2014 not 2011.
Plugins are supported in 2014 only, sorry.
There is a reward program going on for free upgrade if you review WeBuilder or link to the site. I don't know if that program is for everyone or just newsletter subscribers so I won't publish the details here yet. I'll let you know in PM once you contact me about the URL.
Plugins are supported in 2014 only, sorry.
There is a reward program going on for free upgrade if you review WeBuilder or link to the site. I don't know if that program is for everyone or just newsletter subscribers so I won't publish the details here yet. I'll let you know in PM once you contact me about the URL.
Blumentals Software Programmer
Re: Have these issues been improved in WB 2014?
I wrote the plugin for if you decide to upgrade. If not, it might be useful to someone else, too.
http://forums.blumentals.net/viewtopic.php?f=33&t=6018
http://forums.blumentals.net/viewtopic.php?f=33&t=6018
Blumentals Software Programmer