Guild Launch News
UPDATE: Guild Description Editor Change
In light of recent input and user observation we have changed the behavior of the guild description. The WYSYIWYG is now off by default, but can be enabled by clicking "Enable WYSIWYG" below the text box.
Essentially, we've noticed that alot of people have funky HTML they want to use, or JavaScript or Flash files, etc. In addition, alot of people seem to get their HTML/JavaScript/Flash from other sources. So, though they don't know exactly how the HTML/JavaScript/Flash works they know *that* is the HTML/JavaScript/Flash they want to use.
The position this puts us in is that we want to allow any HTML for the advanced people, and we want to provide a nice WYSIWYG for the non-advanced people. Then we have sort of these in-betweeners who have advanced wants and may have gotten more advanced HTML from some other source and have some somewhat complex HTML needs, but when it comes to editing the HTML to work within another system, they don't know how to edit it.
So, until I can find/write/create/discover a 100% bulletproof WYSIWYG that creates nice looking code, behaves how a reasonable person expects it to behave, will format and clean up people's code, but won't change their code unecessarily, and that will work in all the major browsers we will be defaulting the editor to being off on the guild desription.
I do believe the current WYSIWYG can be made to do what we want, but we need to configure and tweak it more internally and figure out some of it's internals a bit further.
So, now you have both options available to you: use the WYSIWYG if your needs are simple formatting or you want to have your HTML cleaned up for you. If the WYSIWYG won't do something you want it to, turn it off, but you will need to make sure you give it valid HTML.
-Stephen
Essentially, we've noticed that alot of people have funky HTML they want to use, or JavaScript or Flash files, etc. In addition, alot of people seem to get their HTML/JavaScript/Flash from other sources. So, though they don't know exactly how the HTML/JavaScript/Flash works they know *that* is the HTML/JavaScript/Flash they want to use.
The position this puts us in is that we want to allow any HTML for the advanced people, and we want to provide a nice WYSIWYG for the non-advanced people. Then we have sort of these in-betweeners who have advanced wants and may have gotten more advanced HTML from some other source and have some somewhat complex HTML needs, but when it comes to editing the HTML to work within another system, they don't know how to edit it.
So, until I can find/write/create/discover a 100% bulletproof WYSIWYG that creates nice looking code, behaves how a reasonable person expects it to behave, will format and clean up people's code, but won't change their code unecessarily, and that will work in all the major browsers we will be defaulting the editor to being off on the guild desription.
I do believe the current WYSIWYG can be made to do what we want, but we need to configure and tweak it more internally and figure out some of it's internals a bit further.
So, now you have both options available to you: use the WYSIWYG if your needs are simple formatting or you want to have your HTML cleaned up for you. If the WYSIWYG won't do something you want it to, turn it off, but you will need to make sure you give it valid HTML.
-Stephen
Woothdye wrote:
Nah, doesn't have anything to do with the JavaScript issues you were having (I know how to fix that one). So nothing to be sorry about. We're making this application for you all, and the WYSIWYG needs to either work or be put in as an optional feature. We're making it optional until we can get it to behave predictabley doing the things our customers want it to do within reasonable boundaries.
-Stephen
I feel I may be somewhat responsible for this so I'm saying sorry
Nah, doesn't have anything to do with the JavaScript issues you were having (I know how to fix that one). So nothing to be sorry about. We're making this application for you all, and the WYSIWYG needs to either work or be put in as an optional feature. We're making it optional until we can get it to behave predictabley doing the things our customers want it to do within reasonable boundaries.
-Stephen