moodle style and javascript in plain text editor

MOODLE STYLE AND JAVASCRIPT IN PLAIN TEXT EDITOR CODE

It needs to be local as there are too many possibilities to include in a theme and local authors may need to implement their local styles e.g. The styles drop down list would then have a 'spanish style' defined which would apply things like lang, dir (if necessary) etc. similar to additional html for the site) could be implemented for a language course to be able to style any, say, spanish text to distinguish it from the surrounding english text. a place to add css on, say, a course level. also looking at doing this) and my use of this is why I came across a bug in the 'styles' plugin which I'm currently trying to get fixed, and beefing up it's functionality.Ī 'local theme' (e.g. There is a styles plugin but this is a bandaid (and needs improving. And then people wonder why author's want to have buttons to style their text red, large etc! or in Moodle generally for any local styling ( css). While 'themes' were introduced, there is no support in atto to 'really' make use the themes (one can't easily add to the 'headings' drop down menu, for example). in word) - this is in relation to authors / teachers rather than, say, forum posts. A related 'bee in my bonnet' is the lack of a focus on atto being organised around the use of 'styles' (classes) to style text (which could be used in language / direction situations) similar to styles in any word processor (headings etc. though not being a user of a screen reader (or anything similar) I'm not sure of exactly the impact here. I'm assuming this also has the potential to improve accessibility?. In that sense there should really then be a lang drop down list to add a lang attribute to an element / span if it differs from the surrounding text (just as a dir button).

MOODLE STYLE AND JAVASCRIPT IN PLAIN TEXT EDITOR CODE

dependent on whether anyone can convince me otherwise (always happy to be convinced by reasonable argument).įor now, I'll be using a modified version of the code which removes the added attributes - none of my existing content has them, and it's something someone can always do manually anyway.Īctually, thinking about it more, not only should a user-content wrapper include the 'dir' attribute, but it should also include the 'lang' attribute - which could relate to things like spell checking. I may open a new issue / re-open this issue in tracker. someone could have produced it in RTL but it could be being read in an LTR setting). Though there would still be an issue for viewing legacy content (as there is not indication of the language in which the content was produced i.e. when content is retrieved for editing a check could be made and the wrapper added where necessary, based on the language setting of the editor. My suggested solution also potentially deals better with legacy content (which they mention as a problem) i.e. I'm guessing it would be pretty clear to users (and there could be tool tips, making it even more clear) what the various indicators mean. The process of editing html is different to using a 'regular' word processor.Ģ. While this might not be identical to some word processors:ġ. This could be solved by having a separate rtl/ltr indicator and the buttons simply responding to the style in the text. Some of the contributors also seem to have an issue with the behaviour of the buttons. Then someone logged in using an RTL language and viewed that, it would be OK because the English post would be wrapped in an LTR element.Ĭreating overly verbose html to solve the problem doesn't seem like a reasonable solution. if someone logged into Moodle in English and posted something. While someone pointed out the issue was not just about email, a similar solution could be implemented for all user generated content i.e. It would seem simpler to wrap any user generated text in a div / section (whatever makes sense) which has the dir specification.Īt one point in the issue this is effectively suggested by Nadav where he mentions that the email issue would be solved by using a template for the outgoing email. However, I can't say I agree with their solution.

Moodle style and javascript in plain text editor