Support forums » Products » Cute Editor for .NET » Re: Questions about CuteEditor 6.1

Questions about CuteEditor 6.1

Last post 09-05-2007, 2:54 PM by afroblanco. 2 replies.
Sort Posts: Previous Next

  •  09-04-2007, 11:26 AM 33213

    Questions about CuteEditor 6.1

    Reply Quote
    Hello all,

    About a month ago, I recall Adam mentioning that CuteEditor 6.1 will be released in September.  I have a number of questions about CuteEditor 6.1, as I am evaluating whether or not I should continue to use CuteEditor as my rich text editor.

    1)  When will CuteEditor 6.1 be released?
    2)  Will it be stable?  I noticed that, since its release, CuteEditor 6.0 has been updated on a weekly basis.  To me, this is not acceptable.  Will 6.1 be stable enough so that, say, a month or more will go by before I have to update?
    3)  When changes are made to version 6.1, will the version number be updated?  I've noticed that, with the numerous updates to 6.0, the version number has stayed the same throughout.  I and others find this unacceptable.  Will 6.1 use commonly accepted best practices in regards to versioning?

    Thanks.
    Filed under: ,

  •  09-05-2007, 9:47 AM 33259 in reply to 33213

    Re: Questions about CuteEditor 6.1

    Reply Quote
    >>)  When will CuteEditor 6.1 be released?
     
    V 6.1 will be released within this month. This depends the development of the PDF parser.
     
    >>2)  Will it be stable? 
     
    The Cute Editor project is pretty stable already.
     
    If you don't need the PDF parser, you can just download the version 6.0.
     
    >>3)  When changes are made to version 6.1, will the version number be updated?  I've noticed that,
     
    We struggle to make their software better. We add functionalities, we improve performance, we fix bugs based on developer's feedback and do the improment as fast as web can.
     
    We know there are still many developers prefer using the version number approach. But we think using build numbers would complicate/slow down the update process.
     
    Because many developers are still using asp.net framework 1.1. Once we make the changes, the developers need to update the DLL or client files right away without recompile the whole project. So we don't change the cntrol version number. However we do update the control description and update the change log:
     
     
    Hope it makes sense to you. I do hope you can download and install the version 6.0.
     
    Keep me posted
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  09-05-2007, 2:54 PM 33279 in reply to 33259

    Re: Questions about CuteEditor 6.1

    Reply Quote
    Adam, with all due respect, I do not plan on installing version 6.0, since you have had to update it so frequently.  I think that you are asking too much from your customers.  I should not have to check your website every week to see if you put a new version up.  My impression is that 6.0 was a buggy release, which is why you have had to update it so frequently.  If 6.1 is going to be updated as frequently as 6.0, I will no longer use CuteEditor as a component in my software.  I will find a new rich text editor, one that follows a reasonable update schedule.

    You have not answered my second question.  What I want to know is this - will 6.1 be updated as frequently as 6.0 has been?

    As for your resistance to version numbers - yes, I understand that you have reasons for not using them.  However, I ask that you please take a look around you at what other companies do.  You will realize that nearly all of them use version numbers.  This is the industry standard, and is considered a best practice.  Thus, it is not unreasonable for me to ask that you do the same.

    I understand that you want to accommodate customers that use an old version of the framework.  However, if you didn't publish an update to your software every few days or so, this wouldn't be a problem.  Your customers would update their DLLs once every few months, and that would be the end of it.
View as RSS news feed in XML