Fully Modularised Toolbar about textangular HOT 7 CLOSED

Hello Simeon,

Thank you for accepting my feature request. Some years ago I have made the same feature request for the free WPF RichTextBox from Microsoft which is used by the WPF toolkit on codeplex. It got also implemented and the people liked it so they will like your control when you have implemented it :)

I really vote for the convenience functions ;-) about the rest I agree.

About what UX issues do you speak?
like
"should all other text areas be disabled" when the user has clicked in one certain text area" ? or
"should a "Bold" button have a pressed state when in multiple text areas is selected text and to which text selection does the active Bold button refer" ?

from textangular.

No I was thinking more around if you use multiple toolbars, say if you wanted editor instances 1 and 2 to have ability to toggle HTML then editors 3 and 4 to only have bold/italics then there is the possibility for user confusion on which toolbar is active for my current editor.
I think the best way to deal with this is to make sure that for every state change there is a corresponding class change in all relevant places.

As to your second point, as we use contenteditable areas I don't think you can select text in more than one editor at a time (I haven't tested this thou).

from textangular.

"I don't think you can select text in more than one editor at a time "

True just checked it.

"...then there is the possibility for user confusion on which toolbar is active for my current editor...."

Well I would say I have to operate on the one toolbar placed over the text editor?

from textangular.

"Well I would say I have to operate on the one toolbar placed over the text editor?"

I was getting at this change has the potential to have toolbars placed in funny places relative to editors (for whatever reason). Also even if the toolbars are sensibly placed we'd still want to make a class change to the active toolbar so that the developer can make a visual update via css/js if they want.
In thinking it through, all UX issues that could be introduced can be mitigated by the developer if we put enough transparency and clarity in events being fired.

from textangular.

Yes Yes Yes think it throught you can do it man. If you need free beer lemme know ;-)

from textangular.

How about more time, I could do with that :). In all likely-hood it will take me until Feb 2014 to look into this as I'm on leave very soon. If anyone else does this @fraywing should be able to look into it as a pull request if he gets the time. Otherwise it'll take some time before I start.

from textangular.

Implemented in 1.2.0 branch.

from textangular.