We're considering purchasing the ASP version of Cute Editor for a CMS application, and later the ASP.NET version. (Currently we use an editor that we wrote ourselves, so system flexibility is a new compromise for us.)

 

Forgive me if the first question is obvious, I have not seen how licence keys work with the demo system yet...

 

When using an application/redistribution licence does a single licence key work with all distributions of that application, or is there some registration process that needs to be followed for each installation?

 

Also, I notice that the redistribution licence is the same cost as a developer licence but allows unlimited developers. I assume this is because a developer licence would still need to be purchased if Cute Editor was used on any web site or product other than the licensed application. Is that right?

 

When redistributing the editor, is there a requirement to display Cute Editor branding or logos on the editor interface? What about user documentation? (Our preference is to credit third party products that we use in secondary locations within our product package, e.g. in a "credits" or "about" window.)

 

We notice some cross browser issues in the online demos. E.g. Firefox does not correctly lay out code in the HTML edit view in the same way as IE, and non breaking spaces are inserted inside tables when the user attempts to manually adjust the code layout. Is there an active program to remedy such issues as a priority, to provide patches or workarounds, or to provide bug related support, or a tackable bug resolution list, a user patch program, or must we wait for future product releases?

 

How often are patches and minor versions released?

 

We are pleased that accessibility and usability appear to be primary considerations in the development of Cute Editor. There are some outstanding accessibility issues for content generation such as limitations in the support of table headers, table cell and header scope definition. Are these issues being considered? Do you respond to community feedback or individual customers on these issues? Is there a publicly visible development roadmap?

 

Out of interest rather than requirement... We have noted a lot of positive results in usability tests about the provision of a pull-down menu interface as an alternative to icon toolbars. Have you considered implementing this option in Cute Editor?

Sorry, to clarify the original question about Mozilla... I did already check the editor in several different browsers on your site. I noticed there is a bug on Mozilla where the HTML layout is not correctly processed in the HTML window. And if you try to edit code inside a table in the HTML window, erroneous non breaking spaces are added. This appears to be quite a serious bug, and I wanted to know if there were remedies to such problems offered (since we can't program the editor ourselves, from what I can see), a trackable online bug list, or any other kind of formal support for such bugs?

 

I have a few more questions:

 

I have been looking everywhere for information about the API to Cute Editor for the ASP version, since there is no downloadable trial. All I can find is the developer deployment guide, which does not provide any information about interacting with Cute Editor for more advanced customisation. (It only covers the very basic case of adding a button.) Is there any documentation about the Cute Editor API?

 

I notice the ASP version provides context menu commands, but they're not enabled yet. Do you have a timeline for implementing the context menu in the ASP version?

Thanks for answering the other questions. :)

P.S. Regarding the API, I have seen this: http://cutesoft.net/asp/JavaScript-API.asp

 

It's not what I'm looking for, this is just a Javascript command reference for simple commands in the editor.

 

I'm more interested in customization issues like these with regards to the API:

Also another question, is there a way to set non-editable code within the ASP version of the editor?

 

I notice the tabledropdown command produces a Javascript error in IE6 on the API page, after which other functions also produce errors. Is this a known bug?

 

Sorry to ask so many questions, a trial download would make this easier.