You are not logged in.
to remove unwanted html tags, it may still be in the config object, but once again, i cant say, i never managed to find a valid regexp
// remove tags (these have to be a regexp, or null if this functionality is not desired)
this.htmlRemoveTags = null;it is declared in the config object and only used once in the function HTMLArea.getHTMLWrapper
if (outputRoot)
outputRoot = !(editor.config.htmlRemoveTags && editor.config.htmlRemoveTags.test(root_tag));but yes, as gogo said, do it on server side. More secure to remove unwanted tags from your scripts on server than on clients.
i havent tested (yes, still on holidays lol, turned from 1 week holiday to 3 weeks holidays now, and keep running :D ) but what about the fonction hideSomeButtons() in the Config object ? (line 568 changest 287)
HTMLArea.Config.prototype.hideSomeButtons = function(remove)
Isnt it exactly what is needed ? I havent used it yet, because i always create the new toolbar the way i want, but i think it is exactly the method needed here.
/** Call this function to remove some buttons/drop-down boxes from the toolbar.
* Pass as the only parameter a string containing button/drop-down names
* delimited by spaces. Note that the string should also begin with a space
* and end with a space. Example:
*
* config.hideSomeButtons(" fontname fontsize textindicator ");
*
* It's useful because it's easier to remove stuff from the defaul toolbar than
* create a brand new toolbar ;-)
*/
in almost all the popups used, we can find some XHTML markup. For instance, in changeset [254], the file plugins/Forms/popups/select.html has added some XHTML markup (<p />, <input />, etc.), but this file IS NOT a xhtml document because it is NOT using any DTD and as a result it is falling in quirks mode which is HTML not XHTML.
Yes i have said it a lot already and i'll keep saying it until
1) we decide to use a valide markup
2) or someone stop ignoring my argue on this point
3) or someone explain me the reason why this choice has been made. Even if i dont think it is a choice at all but just a very old mistake we keep from htmlarea.
This is a real issue with the way we communicate between the javascript and the document, see ticket #318
You can update the button like this
var xinha_config = new HTMLArea.Config();
xinha_config.btnList['insertimage'][3] = function(e) {
alert('my own javascript');
};http://mokhet.com/xinha/examples/ownjs.html
or you may prefer to update the _insertImage function
HTMLArea.prototype._insertImage = function(image) {
alert('my own insert image');
};http://mokhet.com/xinha/examples/owninsertimage.html
Hope one of thoses 2 ways of doing your own javascript is what you looking for.
You dont need to update the editor.config.btnList unless you want to update the whole button, which in the case here dont seems to be what you want to do. You want to update the destination link on the image button, to accomplish this, just add this line in your config file :
xinha_config.URIs["insert_image"] = 'url to your insert image html page';or you can use the ImageManager plugin and update the 'backend' link defined in the config. I am not sure at all how it is working but looking at the code, i think it may be done this way
xinha_config.ImageManager.backend = 'url to your own back end';People using this plugin may know better how to change the backend file.
Hello gocher, in case you dont get my mail quick enough (i have qmail issues
) , here is what i found. Hope it helps you
The trick seems to be in the uppercase O in the object.readOnly ![]()
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<script>
function on() {
var el = document.getElementById('abc');
// el.removeAttribute("readonly");
el.readOnly = true;
}
function off() {
var el = document.getElementById('abc');
// el.setAttribute("readonly",true);
el.readOnly = false;
}
</script>
</head>
<body>
<form>
<input type="text" id="abc" value="AZERTYUIOP" readonly="readonly">
<input type="button" onclick="on();" value="readOnly = true">
<input type="button" onclick="off();" value="readOnly = false">
</form>
</body>
</html>hello
@agoetz
on the url you provided, there is the following
<script type="text/javascript" src="/xinha/htmlarea.js"></script></head>
<script type="text/javascript" src="/xinha/my_config.js"></script>
<body>the </head> is not in correct position inside the HTML document, script tag is not allowed in this place. Anyway, i dont think this is relevant to your actual issue. I think it is probably because in your file http://shabbosgoy.com/xinha/my_config.js we have 2 ID set in the variable xinha_editors
xinha_editors = xinha_editors ? xinha_editors :
[
'myTextArea',
'anotherOne'
];Try to remove the 'anotherOne' ID from the config file to see if it fixes your problem.
@aeon
i have a simple example based on newbie guide code, http://mokhet.com/xinha/examples/simple_example.html
it is not my fav way to init Xinha, but it seems to work fine on my side.
http://xinha.python-hosting.com/ticket/232
http://xinha.python-hosting.com/wiki/Do … BasicUsage
http://xinha.python-hosting.com/ticket/304
with the actual skin system (which is not loaded by Xinha itself but by a link on the HTML page), you have to write the link tag AFTER the <script src="/xinha/htmlarea.js">
problem solved.
I think this is the phrase i love the most to read.
Did you read the NewbieGuide before trying your own version ?
You need to make sure the textarea you want to convert has the "id" set, such as
<textarea id="newbiearea1" name="newbiearea1" rows="10" cols="50" style="width: 100%"></textarea>
it can be the same as the name - just make sure there is only one thing on the page with that ID though!
The problem is not related to the table layout. It is in the javascript and the ID of the textarea.
/** STEP 2 ***************************************************************
* Now, what are the names of the textareas you will be turning into
* editors?
************************************************************************/
xinha_editors = xinha_editors ? xinha_editors :
[
'myTextArea'
];
<textarea id="textarea" name="myTextArea" style="width:100%;height:320px;">The javascript is looking for a textarea with the ID myTextArea but doesnt find it. The name is not used, only the ID is meaning something for Xinha.
change your textarea to
<textarea id="myTextArea" name="MyNameIsNotRelatedToXinha_Only_my_ID_is" style="width:100%;height:320px;">can we use this patch to avoid another confusion of this kind ?
Index: full_example-body.html
===================================================================
--- full_example-body.html (revision 235)
+++ full_example-body.html (working copy)
@@ -39,7 +39,7 @@
xinha_config = null;
xinha_plugins = null;
- // This contains the names of textareas we will make into Xinha editors
+ // This contains the ID of textareas we will make into Xinha editors
xinha_init = xinha_init ? xinha_init : function()
{
/** STEP 1 ***************************************************************
@@ -64,7 +64,7 @@
if(!HTMLArea.loadPlugins(xinha_plugins, xinha_init)) return;
/** STEP 2 ***************************************************************
- * Now, what are the names of the textareas you will be turning into
+ * Now, what are the ID of the textareas you will be turning into
* editors?
************************************************************************/
@@ -181,4 +181,4 @@
</body>
-</html>
+</html>
\ No newline at end of fileAs usual, can you provide an url where we can look what's happening on your version ? thank
Are you sure the CharacterMap plugin is located in the plugin directory ?
hello, can you please provide an url where we could test (and see) the problem ? thank
I think there's a moment where it's better to give up trying to find a solution for IE, i dont think we can do anything about it. For instance, try the tool (drip) on this page http://mokhet.com/x.html
it is an iframe calling a page y.html, which contains just nothing. No javascript, just an empty iframe, the memory usage keep increase. Well of course all this memory loose is far from by understanding, but if IE is not able to open and close a document with an iframe without having memory issues, well, sounds hard to fix.
x.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>title</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body>
<iframe src="y.html"></iframe>
</body>
</html>y.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
</head>
<body>
Y
</body>
</html>http://www.shaunakelly.com/word/trackch … Works.html
http://www.cof.orst.edu/net/software/ms … kchngs.php
http://continuinged.uml.edu/online/tuto … rackingxp/
Microsoft Word 2002 includes features that allow you to track the changes made by multiple users, as well as a review function that allows reviewers to insert their comments within a document. These features are very useful when you are part of a peer group assigned to work on a project together. They also provide a means for instructors to comment on your work. It allows a peer editor or the instructor to keep track of the comments and changes made by various reviewers.
I may have misread but as far i can understand it, it looks like a versioning system inside msword
I dont think it is Xinha goal to implement such thing ![]()
xiha_editors.etxt1 is null or not an object probably because it is too early to access them (settimeout to init iframes, plugins not all loaded, etc)
there's a "secret" function _onGenerate() called once the initialisation is completed
HTMLArea.prototype.initIframe = function()
{
...
...
// specific editor initialization
if(typeof editor._onGenerate == "function") {
editor._onGenerate();
}
}I have made a quick page doing this, probably need some tweakings but i think it is one of the available ways to do it.
http://mokhet.com/xinha/examples/simple … otext.html
Basically, with your function my_init() it could look somethings like that
function my_init() {
xinha_init();
}
HTMLArea.prototype._onGenerate = function() {
// editor generated, we can switch to textmode
this.setMode('textmode');
return true;
}It may work also with a simple setTimeout(), but I think you may have troubles if the initialisation is not completed.
function my_init() {
xinha_init();
setTimeout('xinha_editors.text1.setMode()', 1000);
}But i also got the feeling Niko knows a much better way to do it ![]()
the directory /popups/ (blank.html, editor_help.html, select_color.html, popup.js, insert_table.html, insert_images.html, etc) is not found on your installation.
This directory is very required to make Xinha popups work, because required popups are in the /popups/ directory ![]()
3 plugins used by default on the example (ListType, Stylist, TableOperations) cant be found on your xinha installation. the full example is working as intended when we remove them from the plugin to use.
for your integration inside your actual system, are you sure about the _editor_url you set ?
I cant find a /public_html/xinha/ on your server, but i can access /xinha/, so try to replace /public_html/xinha/ to /xinha/
<script type="text/javascript">
_editor_url = "/public_html/xinha/" ;
_editor_lang = "en";
</script>
<script type="text/javascript" src="/public_html/xinha/htmlarea.js"></script>
<script type="text/javascript" src="/public_html/xinha/my_config.js"></script>to
_editor_url = "/xinha/" ;
_editor_lang = "en";
</script>
<script type="text/javascript" src="/xinha/htmlarea.js"></script>
<script type="text/javascript" src="/xinha/my_config.js"></script>Then, in your my_config.js, try to use plugins you have on your server (again, those 3 plugins cant be found on your server : ListType, Stylist, TableOperations) so dont use them in my_config.js
and everything should be better after that.
Hello,
The skin system is still a very new feature and i'm sure gogo and others have billions of idea in mind to improve it.
The current plugin system applies images from the plugins own folder, how will this affect the skins? I mean, if we are to have a buttonskin altleast all the official plugins should be supported for the skins. Anyone checked this?
I am not sure about the question (damn english) but if you mean : are the buttons added in toolbar from plugins get the skin applied ?
Then the answer is yes ![]()
I think the text "Xinha" should not appear anywhere in the logo. I like the chakram of hyp0r but i really dont like the text, well dont get me wrong, the text as it is on hyp0r proposition would fit good on the top left wiki pages, but with the text it is not a logo, it is a xinha ads, some kind of slogan.
Imo the logo should be just the chakram (eventually with a X inside). All the text can be later added on the wiki pages next to the logo. After seeing all the proposals so far, it seems like everyone want to fit all the space available on wiki pages, I think we should focus on a graphical representation but with absolutly NO text to explain (well "we" except me cause I have no talent and I dont understand Gimp2
A logo should not need a text to explain what the logo is. Again dont get me wrong, i am NOT saying you guys you must do that this way not this way. Just trying to give my 0.02 cents.
Keep up the good work guys
Hello,
does a README file like the following text, in the directory /skin/inditreuse/ would be what is needed ?
Skin inditreuse
Author: Kyle Kochis (http://completesiteservices.com/)
Creative Commons
Attribution-ShareAlike 2.0
You are free:
* to copy, distribute, display, and perform the work
* to make derivative works
* to make commercial use of the work
Under the following conditions:
* by Kyle Kochis
* If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.
* For any reuse or distribution, you must make clear to others the license terms of this work.
* Any of these conditions can be waived if you get permission from the copyright holder.
Your fair use and other rights are in no way affected by the above.
This is a human-readable summary of the Legal Code.
Get the full license at http://creativecommons.org/licenses/by-sa/2.0/legalcodehi, added in changeset 201.
I am wondering about the "creatice commons" licence and the file cc.html provided with inditreuse.zip, as far i can understand the licence, it must be added with the skins.
But should we add one licence file in every directory of the 3 skins, or is it enough if completesite name is mentioned (as required from licence) and a link to the online CC licence added in a generic licence.txt in the directory /skins/ (where we could add a link to every licence used and author's name for every skins in the directory) ?
http://creativecommons.org/licenses/by-sa/2.0/legalcode
I didnt add any licence file yet until everyone is agree on what should be done with it, because i dont want to pollute the SVN (so scared to mess something in this, would result you hating me and i dont want that ![]()
If someone is wondering, it can be found here http://www.studiogdo.com/xinha/multi.html and it is very interesting.
I always loved the comments we can find in almost every source code. Oui guillaumed, je suis 100% d'accord avec toi, non mais ![]()
_editor_lang = "fr"; // yep, there are other languages than "en"...Hello, sorry for the long time before this post (just got my internet connection back after 2 weeks without it... yeah ... 2 full weeks and they didnt gave any valid answers to explain it, anyway, let's move on i have internet back ... wooohooo :)
I have updated the tut2 to let it be more readable, and grab some infos from the forums to make it more acurate to reality, and as you suggested, i insert some comments from the source to to the tut. I hope you didnt changed too much Xinha since the 2 weeks ago :p Or better, i hope you changed Xinha a lot and stayed acurate with what i write :D Humm, just noticed a skin directory
concerning htmlRemoveTags, here are some litte tests i can remember
var config = new HTMLArea.Config();
config.htmlRemoveTags = /h1/;
config.htmlRemoveTags = /<h1>/;
config.htmlRemoveTags = /<h1>.<\/h1>/;
config.htmlRemoveTags = /<h1>.*<\/h1>/;but i never succeed to remove any H1 from my text sample. This was with revision 87, i just updated to 177 (lol) and will make some more tests tonight when i'll be back from my weekly meeting (yeah, of course i got a meeting the day i have internet back. grrrr) and probably after reading the forum and all the update from the last 2 weeks.
<h1>nibh euismod tincidunt</h1>
<h2>sed diam nonummy</h2>
<p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit</p>
<h1>n vulputate velit esse molestie</h1>homesite got a BOM (Byte Order Mark) bug : http://www.macromedia.com/cfusion/knowl … d=tn_19059
byte order is meaningless for UTF8 and is optional. And i dont really want to see "" (EF BB BF) at the beginning of my documents ehe
My opinion is without BOM.