Hi!
Just a short note about note about how you can make TinyMCE into
something pretty close to WymEditor: As I mentioned earlier I've tried
a "tightly configured" TinyMCE, by that I mean that I made available
only the few things that I felt that my customer needed... and those
pieces of functionality were also rather well behaved.
That being said, the customer of course managed to make the page look
inconsistent, even though the code remained valid. (The same kind of
problems are discussed in my thesis.) Up until now I haven't really
found a flexible solution that wouldn't require you to go cleaning up
a bit after the customer, at least in the beginning. (I also made the
bold-button produce <strong> instead of <b> and the italic-button <em>
instead of <i>, which some would argue is not quite accurate... but in
practise I think it more often produces sensible results that way,
since in most cases the semantics will be OK then.)
Here's the configuration that I used:
<script type="text/javascript" src="tinymce/jscripts/tiny_mce/
tiny_mce.js"></script>
<script type="text/javascript">
function mceToggle(id, linkid) {
element = document.getElementById(id);
link = document.getElementById(linkid);
img_assist = document.getElementById('img_assist-link-'+ id);
if (tinyMCE.getEditorId(element.id) == null) {
tinyMCE.addMCEControl(element, element.id);
element.togg = 'on';
link.innerHTML = 'disable rich-text';
link.href = "javascript:mceToggle('" +id+ "', '" +linkid+ "');";
if (img_assist)
img_assist.innerHTML = '';
link.blur();
}
else {
tinyMCE.removeMCEControl(tinyMCE.getEditorId(element.id));
element.togg = 'off';
link.innerHTML = 'enable rich-text';
link.href = "javascript:mceToggle('" +id+ "', '" +linkid+ "');";
if (img_assist)
img_assist.innerHTML = img_assist_default_link;
link.blur();
}
}
</script>
<script type="text/javascript">
tinyMCE.init({
mode : "exact",
theme : "advanced",
relative_urls : false,
document_base_url : "/",
language : "en",
safari_warning : false,
entity_encoding : "raw",
verify_html : true,
preformatted : false,
convert_fonts_to_spans : true,
remove_linebreaks : true,
apply_source_formatting : true,
theme_advanced_resize_horizontal : false,
theme_advanced_resizing_use_cookie : false,
plugins : "advimage,contextmenu,fullscreen",
theme_advanced_toolbar_location : "top",
theme_advanced_toolbar_align : "center",
theme_advanced_path_location : "bottom",
theme_advanced_resizing : true,
theme_advanced_blockformats : "h2,h3,p",
theme_advanced_buttons1 :
"undo
,redo
,separator
,formatselect
,bold
,italic
,numlist,bullist,separator,link,unlink,separator,fullscreen,code",
theme_advanced_buttons2 : "",
theme_advanced_buttons3 : "",
extended_valid_elements : "img[class|src|alt|title|hspace|vspace|
width|height|align|onmouseover|onmouseout|name],strong/b,em/i",
theme_advanced_styles : "",
elements : "updatedfile"
});
</script>
cheers, Simon
On Nov 19, 2008, at 20:21 , Casper Fabricius wrote:
I am happy my frustrations resulted in some discussion and good
ideas. The ideas for extensions for a scratch pad, filter toolbars
and som WymEditor + paperclipped would all be highly usable to me,
but I don't have the time to build any of them right now.
I have used TinyMCE filter for some projects, but it has - amongst
other things - resulted in me having to say to the customer: "No,
you have to let me edit the frontpage, if you edit it, it will get
messed up" (Because TinyMCE has a habit of messing HTML up). But
WymEditor might be more clean at that, so I think I'll try and use it.
The template extension can do many of the things you mention, such
as providing custom forms for different templates, and allowing the
user to select the appropriate template when clicking "Add Child".
I'll let you know if I make any interesting discoveries along the way.
Med venlig hilsen / Best regards,
Casper Fabricius
http://casperfabricius.com
On 19/11/2008, at 10.19, Simon Rönnqvist wrote:
Hi!
Yes some WymEditor + paperclipped combination could be really cool.
I've never really used WymEditor for any of my clients.. but I've
tried both Markdown and a tightly configured TinyMCE (which would
be pretty close to WymEditor). With Markdown I've seen that the
content remains largely unstyled, the client eg. just used
UPPERCASE-letters for headings and so on... maybe a Markdown-
toolbar would help stimulate the usage of Markdown-code? With the
TinyMCE solution again stuff got marked up a bit inconsistently,
and often using <strong> for some headings, even though it didn't
cause quite the mess that a normal 'liberal' WYSIWYG would have.
My guess is that using WymEditor would be a good way to give your
customer a way to try and express what she's looking for, but
chances are that you'll have to go in and clean up after her a few
times... but along with that you could also try to agree with her
on certain practices in the future, to retain consistency. I've
been searching for the perfect solution for quite some time, but
I've begun thinking that this last step of cleaning up and
educating can't really be avoided if you want perfect results... we
can just try to minimize this last task. Markdown+toolbar could
also be something to try out, but I fear it might still be
considered a bit too intimidating (and Textile I find even more
intimidating).
Another thing that I've been thinking that could be suitable for
some cases (but I haven't tried out) is in-place editing... but I
don't know how well that'd fit into Radiant. And yes forms (using
your own plug-in) or splitting content into many page parts could
definitely also in some cases be the right solution... but in cases
where we want to allow more flexibility, to allow the customer to
structure their content more freely... we're probably better off
going with some WymEditor-like solution + cleaning up and education.
Apart from the actual editing of content, it'd be really cool to
find and easy way to hide some stuff in Radiant from the customer.
Eg. some things such as the CSS and RSS things, and sometimes some
page-parts. And maybe in some cases even the popup menus: layout,
page type, status and filter.
cheers, Simon
PS. I begun the search for the perfect solution to this in my
thesis, if anyone's interested: http://simon.fi/en/thesis
On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote:
Casper Fabricius wrote:
However, I have a client whose content editor is very frustrated
with the system. She can only just tolerate using Markup, and she
refuses to write any kind of HTML - Radius tags falls into this
category from her point of view. According to her, a proper CMS
would hide all this "technical stuff" and provide custom forms
for all types of content.
Casper, my "solution" would be to find a slightly more technical
client :P
No, I'm joking (of course!)
Here's what I would recommend:
1. First, factor out as far as possible so that whatever is not
page specific is in snippets.
2. If all she needs is a few styles of pages, I would create
different page types or layouts.
3. Then tell her that the different parts that she wants need to
go into different page parts. It would be cool if you could
modify the "Add Child" behavior to allow you to select the kind of
child page you want and then give you a blank page with all the
different tabs created (page parts)... or it could be done with a
bit of Javascript that detects when you change the Layout/ page
and automatically adds in the different page parts? It could even
be a special drop down box next to the Page Type that triggers the
actions?
4. The problem: she still needs to use textile for some of the
things, such as images. I'm not sure if the Textile Helper will
help? It's been a while since I looked at it, but there's a hello
world guide on my blog:
http://notepad.onghu.com/2007/3/28/using-textile-editor-plugin-and-acts_as_textiled
It could make some things easier for her, I hope... without going
down the path of WYSIWIG.
If you do go down WYSIWIG, I hear good things about WymEditor -
and Benny's on the list!
Of course, Casper, you are more experienced than I am. Do let us
know what you eventually settle on :)
Cheers,
Mohit.
11/19/2008 | 2:45 AM.
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
