what I would like to see in WB 2.8 final

[Kimmik]

Hi folks,

here's a list of things I think should be changed:

1. When integrating the WYMeditor (wysiwyg module) I had problems because I wasn't able to manipulate the save button via the module.
--
I would like to see the save button move in the module:

this (currently hardcoded in /modules/wysiwyg/modify.php)

<table cellpadding="0" cellspacing="0" border="0" width="100%" style="padding-bottom: 10px;">
<tr>
    <td align="left">
        <input type="submit" value="<?php echo $TEXT['SAVE']; ?>" style="width: 100px; margin-top: 5px;" />
    </td>
    <td align="right">
        </form>
        <input type="button" value="<?php echo $TEXT['CANCEL']; ?>" onclick="javascript: window.location = 'index.php';" style="width: 100px; margin-top: 5px;" />
    </td>
</tr>
</table>

should move into the show_wysiwyg_editor(); function of the wysiwyg-editor the user uses.

2.
I really would like to see global vars for templates that can be changed via the backend for every page individually and globally.

I would volunteer to do #1 (I don't have the skills for #2) , but I'm not involved in the development.


What do you think?

[erpe]

Hi

if you want to work for website baker project you could use this form:
http://start.websitebaker2.org/en/join-the-team.php

rgds

erpe

[Kimmik]

thx, erpe.

I signed up, and I already found a much simpler way to accomplish #1.
It would involve only minimal changes (just adding a class to the submit button of the wysiwyg-modul and the news-module [the newsmodule also uses the wysiwyg-module show-editor-function]).


// But I still think that the input and cancel button should be moved fully to the show-wysiwyg function (they just belong there imo).

[Kimmik]

or even better:

the show_wysiwyg_editor(); function call could specify if the buttons should appear (that way it wouldn't interfere with other modules that use the function.

But It still requires changes in every wysiwyg-editor module.

[ruebenwurzel]

Hello,

from the point the first RC was released we have a feature freeze. so i don't think this will be added to WB 2.8 final. Another reason is that this is not compatible to all modules wich uses an editor. They all needs to be adapted as far as i see.

Matthias

[Kimmik]

Yes, all wysiwyg-editors would have to be changed, which sucks. Maybe it's not worth it at the moment, but I think it would be an improvement in the future.

Luckily I found a way for the wymeditor to work without it for now.

Any thoughts on the global template variables?
It's a feature that's almost standard in every other CMS by now (for example Joomla, Modx, ExpressionEngine etc).

[WebBird]

I think the very best way would be to provide an API for module developers to get a WYSIWYG editor instead of including it directly. This way, any changes (like switching the core to a very new editor) would be inherited to all modules automatically, which would be a very nice feature. Also, it would help to get a nice, unique appearance of the admin backend.

Kind of ToDo for 3.x, I think.

[erpe]

Maybe it is a good idea to open a ticket for this?

rgds

erpe