WebBuilder 2008 - WYSIWYG + Web Forms?
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".
WebBuilder 2008 - WYSIWYG + Web Forms?
Hi,
I would like to see WYSIWYG support in webBuilder. This would make creating web forms so much easier! If you can't add it for 2008 then how about creating a form builder that we cab use to add forms to a form Library that we can drag and drop a web page. This way we can also edit the forms from the library when we need to.
I would like to see WYSIWYG support in webBuilder. This would make creating web forms so much easier! If you can't add it for 2008 then how about creating a form builder that we cab use to add forms to a form Library that we can drag and drop a web page. This way we can also edit the forms from the library when we need to.
Question....
* How long would it take you to create a form with over 200 input elements using pure html?
* How long would it take you to create a table with merged table cells?
* How long would it take you to find and adjust a sections of a web article and make some keyword bold?
If you can do it and read it all using <html> tag then I would say more power to you but as far as I am concern there are a lots of other developers who would like to spend a lot less time digging through <html> tags.
Dreamweaver and frontpage allows a developer to easily create webspages and manage websites but they don't have some of the features as does WeBuilder.
I believe the WSIWYG interface will only enhance the product and make it much easier and faster to do certain types of modification to a web page. You don't have to use the WSIWYG if you don't want to,. You can always stick to your <tags> if you so desire.
By adding a simple Design tab/button to the app will not hinder or prevent other developers from using the doing what they like doing best.
* How long would it take you to create a form with over 200 input elements using pure html?
* How long would it take you to create a table with merged table cells?
* How long would it take you to find and adjust a sections of a web article and make some keyword bold?
If you can do it and read it all using <html> tag then I would say more power to you but as far as I am concern there are a lots of other developers who would like to spend a lot less time digging through <html> tags.
Dreamweaver and frontpage allows a developer to easily create webspages and manage websites but they don't have some of the features as does WeBuilder.
I believe the WSIWYG interface will only enhance the product and make it much easier and faster to do certain types of modification to a web page. You don't have to use the WSIWYG if you don't want to,. You can always stick to your <tags> if you so desire.
By adding a simple Design tab/button to the app will not hinder or prevent other developers from using the doing what they like doing best.
- joemichaud
- Posts: 39
- Joined: Sat Sep 29, 2007 4:58 pm
-
- Posts: 32
- Joined: Tue Feb 05, 2008 4:40 pm
- Location: Amsterdam
- Contact:
* it would take me all of five minutes to convince the designer of said form it's too darn long and it'll scare off approx 70% of the usersraymond wrote:Question....
* How long would it take you to create a form with over 200 input elements using pure html?
* How long would it take you to create a table with merged table cells?
* How long would it take you to find and adjust a sections of a web article and make some keyword bold?
* for each merged pair it would take me 2.4 seconds (I just clocked it)
* ctrl+f, type word, alt+f till found, ctrl+b (since it's selected), all without leaving code view, no way on earth WYSIWYG would speed up said process.
[ /sarcasm ]

Having said that, some widget-like helpers COULD be usefull. I'm not at all averse to some kind of form builder, though it wouldn't be for WYSIWYG editing, more like a wizard kindof thing that'll leave me with a set of fields and labels. A bit like the first poster suggested as second choice..
You guy's ever heard of a proggy called "Metty"*? it's a simle metatag generator which I've been using for ages now. I defenetly woudn't mind seeing stuff like that implemented in WeBuilder.
*http://www.clickfire.com/tools/freeware/metty
Patrick Kanne - webmaniac
- as we fail to imagine, we are punished with reality
- as we fail to imagine, we are punished with reality
maravizzo wrote:
At one time I used DreamWeaver and coded mostly by hand, but I found the WYSIWYG interface so useful for immediately finding errors in the code that would have taken ages to find by reading through the code. What's more, in DreamWeaver, if you click on the WYSIWYG interface at the point where the error occurs and then return to the code, the cursor is in the correct position within the code. I would love to see something like that in the Blumentals editors.I really hope I'll never see a useless WYSIWYG interface in this great software.
WYSIWYG is for people that do not know the code, for the others is just something to slow down the work.
Re:
Exactly, absolutely, +1 for this.jerm wrote: At one time I used DreamWeaver and coded mostly by hand, but I found the WYSIWYG interface so useful for immediately finding errors in the code that would have taken ages to find by reading through the code. What's more, in DreamWeaver, if you click on the WYSIWYG interface at the point where the error occurs and then return to the code, the cursor is in the correct position within the code. I would love to see something like that in the Blumentals editors.
I don't miss Dreamweaver apart from this feature, esp. combined with sidebar CSS editing - if you click an element in the page you preview, you have a list of CSS properties referring to it in your sidebar and you can edit them right there, without getting back to CSS file and scrolling back and forth to find the property you need to correct.
It would be sweet to have it in Webuilder. I don't see the need to implement full WYSIWYG support though.
- syrupcore
- Top Contributor
- Posts: 917
- Joined: Thu Jul 21, 2005 12:58 am
- Location: Portland, Oregon, usa
- Contact:
Re: WebBuilder 2008 - WYSIWYG + Web Forms?
I would hate to see any wysiwyg anything in this editor.
Perhaps they're not developers.
...there are a lots of other developers who would like to spend a lot less time digging through <html> tags
Perhaps they're not developers.

Re: WebBuilder 2008 - WYSIWYG + Web Forms?
I come from a WYSIWYG background after using Namo WebEditor for the last 6 years, which has some great features for beginner to expert level. I only shifted to WeBuilder because the latest Namo editor is going backwards and woefully short of updated features, though it is still a good beginner's work horse, Plus, I don't use a lot of tables any more after getting more into styles. Though I am not reliant on WYSIWYG, it can be a very handy tool for quickly checking something I am unsure of; not yet being the l33t coder others here obviously are. I understand the experts decrying WYSIWYG as 'beginner's stuff' but for those who aren't gun coders, it can be useful.
The other way of looking at it is that sales would skyrocket due to the increase in the editor's popularity (most people start off using a WYSIWYG editor, a huge market Blumentals is not currently servicing). For the l33t guys, an option to turn it off (like in CoffeeCup's editor) would be all that's needed. That said, introducing WYSIWYG into an existing application opens a huge can of worms for the devs, so why break a perfectly good app doing that? Perhaps the answer would be a new, stand-alone product (Visual WeBuilder?) incorporating those features required to corner the WYSIWYG market.
Dave.
The other way of looking at it is that sales would skyrocket due to the increase in the editor's popularity (most people start off using a WYSIWYG editor, a huge market Blumentals is not currently servicing). For the l33t guys, an option to turn it off (like in CoffeeCup's editor) would be all that's needed. That said, introducing WYSIWYG into an existing application opens a huge can of worms for the devs, so why break a perfectly good app doing that? Perhaps the answer would be a new, stand-alone product (Visual WeBuilder?) incorporating those features required to corner the WYSIWYG market.
Dave.
Re: WebBuilder 2008 - WYSIWYG + Web Forms?
Some good points from davenz, but at the risk of showing my ignorance, what's an "l33t guy"?
- chrisjlocke
- Top Contributor
- Posts: 995
- Joined: Mon Aug 01, 2005 4:12 pm
- Location: Essex, UK
- Contact:
Re: WebBuilder 2008 - WYSIWYG + Web Forms?
Leet or Eleet (sometimes rendered l33t, 1337 or 31337), also known as Leetspeak or Leetzorz (1337Z0l2Z), is an alphabet used primarily on the Internet, which uses various combinations of ASCII characters to replace Latinate letters. The term is derived from the word "elite", and the usage it describes is a specialized form of symbolic writing.
It is also sometimes used as a script language.
http://en.wikipedia.org/wiki/Leet
So a 'l33t guy' is a nerd, geek, etc. Or 'syrupcore' as we call it here.
It is also sometimes used as a script language.

http://en.wikipedia.org/wiki/Leet
So a 'l33t guy' is a nerd, geek, etc. Or 'syrupcore' as we call it here.
