SMF Development > Applied or Declined Requests

Better icon for WYSIWYG toggle

<< < (4/8) > >>

:
Here's the thing, it's not just the parser, you also need to rewrite the preparser as well, with all the warts attached to doing that.

And that's also before you get into things like the html exclusion for non-admins or indeed any bbcode with any database component (there aren't any in SMF itself, but it's certainly something I have to consider for Aeva Media)...

Like so many things, this is not something I am discussing theoretically ;)

MrPhil:

--- Quote from: emanuele on June 24, 2012, 12:07:45 PM ---MrPhill, what you are proposing is a kind of rewrite of parse_bbc in javascript.

--- End quote ---
It could be done in JS, to avoid a round trip back to the server when switching in and out of Visual mode. If you're going to do that, consider sending just the tagged text to the browser and let it do the work of formatting tags into HTML not only for Visual editing but also for post display. Are there any cases where the necessary information for doing this formatting is not going to be available when the tagged text is thrown over the wall to the browser? I.e., requiring a database lookup, or getting other general data (not normally in the post itself)?

Relieving the server PHP parser of the burden of BBCode->HTML processing could certainly ease the load on the server and help many forum operators who are struggling with server load limits to breathe easier. Do you think it would be noticeably slower than the current server-side processing? It's worth thinking about, if done in such a way as to integrate it with Visual editing mode and Preview.

emanuele:
Oh I know there would be *a lot* of things to do before... that's why i didn't even touch it yet, otherwise at least a branch would already exist. :P

:

--- Quote ---Are there any cases where the necessary information for doing this formatting is not going to be available when the tagged text is thrown over the wall to the browser? I.e., requiring a database lookup, or getting other general data (not normally in the post itself)?
--- End quote ---

Well, a list of enabled tags (not just the ones that have buttons for them!) and whether the user is an admin would be required to be sent to the JS side.

That's just in the base SMF package. There are a ton of mods that do something else which require a lookup of some description

Marcus Forsberg:

--- Quote from: MrPhil on June 24, 2012, 09:52:33 AM ---I think most users would have no idea what "bbc" means. They might even think it has something to do with the British Broadcasting Corporation! I would suggest "[tags]" or something like that.

--- End quote ---

Indeed, I only meant it fits on the button without being impossible to read. <html> does not and and still makes no sense. And I agree BBC is confusing, it sure had me stumped when I first started using forums years ago. :P

I do think an eye would be the way to go for WYSIWYG. Calling it "visual" makes sense since that's what it should be but since it isn't I wouldn't go with it. Besides, I think WYSIWYG is common enough for most people to understand it. If not, I for one would die to poke a button in the eye - literally, almost! - and I'm sure I'm not alone so those who don't know what WYSIWYG is will learn by simply trying it out. :P

Part of me does think that a brain would be cool to symbolise the BBC editor since it actually takes some thinking, especially before you've learned to use the tags. But part of me knows it's not a good idea since it will obviously be confusing ("Will this button blow my brain out and attach it to the post??? AWESOME!!!!").

Fugue has an icon called edit-code.png (<> basically) which could work along for tags along with the eye for WYSIWYG, but I can see it being confused as the code-tag, too.

application-terminal.png for BBC vs application-wave.png or application-image.png or application-blog.png for WYSIWYG is another idea.

Could go the simple way with document-text.png (or document-tag.png) vs document-text-image.png

tag-hash.png works for BBC, since... Well, it's a tag, with a # on it. Or just tags.png

slide.png might look cool for WYSIWYG. Still, an eye might be the best way to go in general.

projection-screen-presentation.png? Might be confused with the img-tag, though. Not likely, to me, however.

Took the liberty to attach all the suggestions above, too. O:)

Edit: image-saturation-up.png is another WYSIWYG alternative. Not that clear, maybe, but if you think about it it makes some amount of sense.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version