Which features specifically would you like to see?

Tables, anchors, and floating.

At least the tables.

The problem with complex HTML is that we'd still need BBCode counterparts.

Basic tables are fine, but there's no real way to convert something complex like:

<table style='width:95%'> <tr> <td style='width:10%'>...</td> </tr> </table>

Into BBcode without losing the inline style information.

If we remove BBCode from the public interface, it'll be possible to do.

Tables would be great...

I'm having an issue correctly displaying the terms and conditions of usage & privacy policy for my site, wich are basically in the form:
1. [tab] [title]
1.1 [tab] [paragraph]
1.2 [tab] [paragraph]
etc.

This would be much easier if tables could be used in the editor, so +1 for using tables.

The problem with complex HTML is that we'd still need BBCode counterparts.

Basic tables are fine, but there's no real way to convert something complex like:

<table style='width:95%'>
<tr>
<td style='width:10%'>...</td>
</tr>
</table>

Into BBcode without losing the inline style information.

If we remove BBCode from the public interface, it'll be possible to do.

Can you not ignore me please? now that we are in alpha, I grow increasingly concerned that anyone can post basically anything without regards to area or groups with merely the correct manual input. Is your lack of any direct answer to this security and spam issue a sign, or does control remain here?

Marcher,

I wasn't ignoring you. Someone else raised this point via the bug tracker and I had fixed it. Apologies for not updating you.

....Not the first time i've looked a fool, but thank you for confirmation, this has been rambling in the back of my mind since asking like a miniature black hole.

You're certainly not a fool. :)

We appreciate the amount of help you give to others and your thoroughness in testing.

I want a basic editor with half the junk and control over what buttons show.

I want a basic editor with half the junk and control over what buttons show.

....That is actually I think what the totally of 3.4 changes means. Disabling x means that it will both not be shown as an option in editor, *and* will not parse.

This thread confuses me a little concerning the function to post tables.

Is this function available nowadays? (3.4)

My vbulletin big board has many instances of tables in posts. Its a very popular way to present information.

totality* typo’s FML, edit time passed. :P

From what has been said here, and marked as fixed in the tracker, we will have the same(more even) control of the editor interface as we had in 3.1. :)

This thread confuses me a little concerning the function to post tables.

Is this function available nowadays? (3.4)

My vbulletin big board has many instances of tables in posts. Its a very popular way to present information.

:) No tables in 3.4. Matt seems to not want to approach supporting tables until he can fully move away from bbcode. I think the idea is innovative, but as always I'm a bit reluctant to change. :)

....That is actually I think what the totally of 3.4 changes means. Disabling x means that it will both not be shown as an option in editor, *and* will not parse.

Where says that? Gimme, gimme, gimme!

Sadly I guess it won't allow for an admin to add a spoiler button, but close.

Where says that? Gimme, gimme, gimme!

Sadly I guess it won't allow for an admin to add a spoiler button, but close.

Ehhhh you could add your own button if you decided to try and tackle the ckeditor config and learn it. I managed to successfully add a latex ckeditor plugin.

Naturally, the whole bbcode thing broke it down the road.

Where says that? Gimme, gimme, gimme!

Sadly I guess it won't allow for an admin to add a spoiler button, but close.

Testing something

Ehhhh you could add your own button if you decided to try and tackle the ckeditor config and learn it.

That would take years.

:) Took me ten minutes. It's pretty straightforward. :)

So if BBCode is being phased out what happens to custom BBCode?

Custom tags will always be an option, but really something like:

[mytag option="value]Text[/mytag]

Could just as easily be expressed as:

<mytag option="value">text</mytag>

Especially if you use the button on the editor's toolbar.

Will the editor ever support tables?

Will the editor ever support tables?

Yes, I'd like it to. But right now we have to fall back to BBCode when switching editing modes, which means introducing new table, tr and td tags. I'd rather wait until 4.0 and look at dropping BBCode as we know it which will free up what we can do with the RTE.

Custom tags will always be an option, but really something like:

[mytag option="value]Text

Could just as easily be expressed as:

<mytag option="value">text</mytag>

Especially if you use the button on the editor's toolbar.

Which was exactly why the 'tag' never bothered me.... tis just string operations.
at such time the editor is able to *actually* insert, for example,

<quote name="Matt" post="2323784" time="1350979730">some text</quote>

And one is just 'describing' the difference between the html 'tag' inserted and the html to be stored, buttons in STD mode become quite feasible, and everything becomes more consistent/manageable rather than being 'in the middle'.

Custom tags will always be an option, but really something like:

[mytag option="value]Text[/mytag]

Could just as easily be expressed as:

<mytag option="value">text</mytag>

Especially if you use the button on the editor's toolbar.

:) I guess I just don't understand it and I'll actually have to see it to get it, but it seems very promising and frankly the way you talk about it makes me look forward to the elimination of bbcode. :)

Ehhhh you could add your own button if you decided to try and tackle the ckeditor config and learn it. I managed to successfully add a latex ckeditor plugin.

Naturally, the whole bbcode thing broke it down the road.

Are you willing to share this tip? :)

Are you willing to share this tip?

:) Nope. In the end I could only get the latex to display after posting. If you quoted the post with the latex or edited it then it broke. :)