It's good to hear that people will pay for a good product, even with the availability of free alternatives. Of course, we would have to offer a superior product.
We already have the ability to add different classes than H1, H2, etc. and we can do this very elegantly. In fact, we support something called named styles. Here's a few definitions.
Title: div.title > Subtitle
Subtitle: div.subtitle > Normal
This tells us that we have a named style called "Title" that is represented by a DIV element with class "title" and that after you hit enter at the end of it, it will end up in the "Subtitle" named class. This is already implemented but not exposed because we haven't built the UI for selecting Named Styles as a dropdown in the beta. This will be in there for the production release though.
We will most likely have sets of "Named Styles" that are compatible with Twitter Bootstrap and other common frameworks at some point. You will also be able to easily create your own Named Styles, probably in an online UI that will build your editor for you.
Note that once you define the Named Styles, the editor whitelists to them so you can't get "illegal" element/class combinations which lets you (the developer) keep the HTML consistent for your needs instead of hoping your users won't break your styles.
We'll keep in mind the ability to add a target for links. We hadn't thought about the need for this until you mentioned it.
It's good to hear that people will pay for a good product, even with the availability of free alternatives. Of course, we would have to offer a superior product.
We already have the ability to add different classes than H1, H2, etc. and we can do this very elegantly. In fact, we support something called named styles. Here's a few definitions.
Title: div.title > Subtitle
Subtitle: div.subtitle > Normal
This tells us that we have a named style called "Title" that is represented by a DIV element with class "title" and that after you hit enter at the end of it, it will end up in the "Subtitle" named class. This is already implemented but not exposed because we haven't built the UI for selecting Named Styles as a dropdown in the beta. This will be in there for the production release though.
We will most likely have sets of "Named Styles" that are compatible with Twitter Bootstrap and other common frameworks at some point. You will also be able to easily create your own Named Styles, probably in an online UI that will build your editor for you.
Note that once you define the Named Styles, the editor whitelists to them so you can't get "illegal" element/class combinations which lets you (the developer) keep the HTML consistent for your needs instead of hoping your users won't break your styles.
We'll keep in mind the ability to add a target for links. We hadn't thought about the need for this until you mentioned it.
TheSunny
[edited for spacing]