Re: Some programming questions about Cute Editor

  •  03-06-2008, 4:22 PM

    Re: Some programming questions about Cute Editor

    Adam, thanks again for your prompt response.  Now, about the source code for the demos, what I meant was this...
     
    You have a page on your web site with all of the demos and test programs for CuteEditor here: http://richtextbox.com/test/. I want to know if there is a page or an FTP directory where I can peruse the source code for all of these demos under the categories listed: Properties, Events, Methods, JavaScript API, Ajax and Three-state buttons.  That way, I can figure out on my own a lot of how the CuteEditor control API works (both client and server) and reserve this forum for resolving any genuine problems I might encounter.  Is the source code to all of these demos and tests (not just the two I mentioned earlier) available for download somewhere?
     
    >> Can you tell me what you are trying to achieve? So I may have other ideas.
     
    The objective of my web application is to make the user interaction look and feel as much like a regular desktop application as possible.  My web application has page layout functions where the user can drag-and-drop various types of objects to position and edit them.  One of the object types we have contains editable text.  On a desktop application, all of the text formatting controls usually reside at the top of the window in toolbars and menus.  To edit one of the text objects in place, the user just double-clicks on it to activate the text editor.  Ideally, I don't want a modal dialog type of a thing to pop up, but I want to have the text become editable in the page object itself, with the toolbars at the top of the page for the formatting controls.
     
    I have been able to get the CuteEditor (minus the toolbars) to position and size right over my text objects so it looks like the static text magically became editable just by double-clicking on it.  It looks good.   What I want to do now is to provide the controls for all the formatting and editing from the toolbars at the top of the page--as opposed to having them attached to the object being edited.  This has two advantages: 1) having the toolbars out of the way makes the editing more WYSIWYG since they don't obscure other parts of the page and 2) users get used to having the controls in the same spot which makes their interaction with the applicaion more fluid.
     
    I was initially attracted to the ComponetArt editor control because the demo they had, which I mentioned earlier in this thread, did exactly what I wanted.  Unfortunately, their basic editing functions are very buggy so I was not able to use their control.  The CuteEditor control is a much more mature product that does not have the issues I ran into with the control from ComponentArt.  However, I would ideally like to have the toolbars for the editor detached from the editing window itself to achieve the user experiece I described in the previous paragraphs.
     
    You told me that version 7.0 of CuteEditor is supposed to have this feature.  That's fine, but I would like to get something like this working now, if possible.  I saw that all of the command functions in CuteEditor's toolbars are available from its JavaScript API.  This makes it possible for me to implement my own detached toolbar controls and then use JavaScript to communicate with the CuteEditor.  So far, so good, but there is one crucial piece missing: when the user changes the location of the cursor in the editor I would like the controls to reflect what the CSS attributes are (e.g font-family, font-style, font-weight, color, etc.) at the cursor.
     
    I can see that the current version of CuteEditor has the capability of showing the formatting attributes of the text at the cursor location in its own toolbars.  Now, I want to know if there is any way available for a programmer like me to read these attributes also?
     
    >> Dynamically creating editor in the server side is same as creating other controls.
     
    Yes, I understand this.  However, it would be very helpful for your customers to have the server-side functions unique to your control documented.  It saves everybody time and frustration in the long run.
View Complete Thread