On Tue, 2006-01-31 at 20:10, Matt Raible wrote: > I think the main problem with removing these is backwards > compatibility. If we remove them - will it break user's blogs? Are > you guys having a difficult time maintaining these? If so, we can > consolidate - but I know I haven't touched any of these in quite some > time. In fact, the drop-down to choose which one I want is broken on > my blog(s) and I've never had an inkling to change it.
I guess I don't know all the details about how each editor works, but my understanding is that they should be totally interchangable. I don't believe any of them actually store editor specific syntax in the blog entry. Someone correct me if i'm wrong. I would add in a bit of logic where it's necessary so that editors can safely be removed from the available list without breaking anything. It's not that we are having trouble maintaining them, we haven't been touching them either. But I believe they should be added by admins optionally, not enabled by default. There is also a lot of redundancy and some of them pretty much suck, so I don't see why we keep all of them. Probably the biggest reason is that I am going to try and add the extended entry field for weblog entries. This will allow the author to break their posting up into 2 sections so that if a posting is long they can show a simple excerpt/summary on their main page and only show the full posting in the permalink. The problem is that to do this all of the editors need to be changed to handle 2 entry fields and I am not willing to do that update on 7 editors. I will probably choose 2 or 3 to update and that's it, the others will continue to only support 1 entry field. I know that sucks a bit, but like I said, maintaining 7 editors is overkill if you ask me. -- Allen > > Raible > > On 1/31/06, Allen Gilliland <[EMAIL PROTECTED]> wrote: > > currently we allow quite a few editors in the list of editors that comes > > bundled in a default roller install ... > > > > editor-ekit.jsp > > editor-text.jsp > > editor-dhtml.jsp > > editor-text-js.jsp > > editor-wiki-js.jsp > > editor-rte.jsp > > > > i'd like to trim down the list to maybe 2 or 3 good editors? there are > > a few javascript based editors, which seems redundant anyways. i'm not > > even sure if we want to ship with the ekit editor installed anyways? > > obviously the text editor is going to remain. there is also a midas > > editor which is no longer used? can it be deleted? > > > > the motivation for this is 1) to keep us from having to maintain more > > editors than are needed and 2) some of these editors will likely break > > when we add the second "extended" entry field anyways. > > > > so basically what i am proposing is to choose just 1 javascript/dhtml > > based editor and try and keep that one updated and as comprehensive as > > possible. then have that editor combined with the text editor as the > > only editors shipped with roller. we can also optionally continue to > > include the ekit editor, but it's probably the least used editor. the > > ekit editor may also become problematic when we try and add the new > > extended entry publishing field because the editors would now need to > > cover 2 textareas. > > > > so, can we trim down the editors list a bit? > > > > -- Allen > > > > > >
