You are not logged in.
Actually Xinha itself cannot do anything about this, it can only edit. You would have to setup Xinha in a HTML form and submit it to a server where you need some php or so script that does the saving
Sounds interesting. I'm keen on having a look at them
Yes, you are right. If you submit a link to the installation I can have a look at it
var editor = null;
HTMLArea.loadPlugin("ImageManager");
HTMLArea.loadPlugin("SuperClean");
var config = new HTMLArea.Config();
config.toolbar =
[
["bold","italic","createlink","insertimage","separator"],
["killword","removeformat"]
];
config.formatblock =
{
"— format —" : "",
"Heading 2": "h2",
"Normal" : "p"
};
function initEditor() {
editor = new HTMLArea("wer_text",config);
editor.registerPlugin(ImageManager);
editor.registerPlugin(SuperClean);
editor.generate();
}I have copied this from an old "HTMLarea-like" config. It shows the steps you have to take before you can call editor.generate(). (Thanks James for the simplification on this, btw
)
Xinha is not capable of editing any other than pure HTML. Try commenting out your ASP code.
right, right. Have a look at this working study I did http://foh.spilles.de/XinhaFD/ (click edit and use the context menu)
I fully agree with you. It would be great if we could push xinha really at the peak of UI design fashion!
I think it would be great if it was a config choice to choose between toolbar types, rows or tabs.
Here i would like to propose to go even farther and establish a plugin concept for the toolbar. In the moment the toolbar is anchored in the frame work which is quite unflexible. There were recently several threads in the forum about using one toolbar with several editors. another thing I was working on is no toolbar but only a context menu with all options. another possibility is a floating toolbar like in photoshop.
What I want to say is that there is, apart from the very good ideas you had how the tb could be organized, a range of ways a developer could want to implement the user interface.
So my idea is that the xinha core only implements the blank iframe and provides an object with all the icons and functions etc. for the toolbar (like there is already). Then there would be plugins that take the object and implement the actual representation of a toolbar or context menu or dropdown or whatever
Is the php directive file_uploads on?
I've thoroughly recreated your setup, and it works. I'm sorry but I really can't find the error
Have you you configured Xinha to be in fullpage mode by the FullPage plugin or config.fullPage? Otherwise Xinha cannot handle the <head> section
In wysiwyg mode it's line 4370: HTMLArea.prototype._editorEvent, but this is not text mode. That's just the plain old textarea, i.e. Xinha is disabled
There's a great firefox extension called View Formatted Source which can show you a HTML view of js generated pages and the source of linked css and js files (and more).
no matter
There's a function called HTMLarea.prototype.outwardHTML() that transforms the HTML the code on pageunload and switch to textmode that among others for the usage of <strong> instead of <b> (because it is supposed to be the 'better' style)
Try
<script type="text/javascript">
_editor_url = "/pag-site/cp/xinha/";
_editor_lang = "en";
</script>
<script type="text/javascript" src="/pag-site/cp/xinha/htmlarea.js"></script>
<script type="text/javascript" src="/pag-site/cp/xinha/my_config.js"></script>I assume that http://192.68.1.102 is the the server where your page is running on, otherwise it wont work
1. getHtml should be there
2. yes, it is enought to copy a plugin in the xinha plugin directory to activate it
3. don´t know, never been using flash
This is the the old HTMLarea sample config, isn't it
? You have got to explicitly load the the plugins you want to use by calling HTMLArea.loadPlugin("Stylist"); etc. before you call registerPlugin().
Anyway I suggest you to have a look at the Xinha Newbie Guide and consider using the way to load xinha like it´s proposed there. I think it´s easier and more stable, esp. the plugin-loading
This would be once again a browser internal behaviour. I'm just guessing, but what you say (happens after resizing) it sounds like xinha does put it like you want it when the image is inserted. Afterwards the image is left to the editing functions of the browser.
I'm shure it could be intercepted with an event handler (or so)
Several plugins you specify to use are not found:
Not Found
The requested URL /xinha/plugins/TableOperations/table-operations.js was not found on this server.
The requested URL /xinha/plugins/SuperClean/super-clean.js was not found on this server.
The requested URL /xinha/plugins/Stylist/stylist.js was not found on this server.
The requested URL /xinha/plugins/SpellChecker/spell-checker.js was not found on this server.
The requested URL /xinha/plugins/ListType/list-type.js was not found on this server.
If you uploaded xinha completely they should be there, please check that
If you see the actual html tags it sounds like this masking of the < or > 's happens two times. If understand that you are using xinha in a wiki context (as you mentioned the wiki formating). It is normal in this context that the server encodes the html special characters, just because it is supposed to receive the formatting information in wiki syntax, not html.
That's strange. Normally, different server software shoul not have any effect on js -- as long the same is sent to the client (HTML- and js-wise).
Do you have a sample page where on can have a look at your problem?
If this is really doing a good job you should create a patch and submit a ticket
Frankly, why do you need the entity when you have Unicode? It was designed to supply all these charakters you other wise have to call inderectly with the enities. The only character that have to be entitized are <>"" and &, because they have reserved functions in HTML.
1. the problem is that your page is not on the same server as your xinha installation. That's the reason why your test on http://69.36.178.177 is working and on http://lindyhopnyc.com/ it does not. Put it on the actual server and use _editor_url = "/xinha/";
2. Your markup is desastrous, especially as you specify doctype xhtml 1.0. I advise you to pay at least a little attention to that. Have a look at this extension which is a great help to write "good" html documents.
PS.: Your example neither worked in IE nor in FF
OK, got it!
I knew it had to have something to do with a differing htmlarea.js. The thing I didn't have in mind is that I'm using the code of the loading message which existed already some time as a patch. And this patch has introduced some new functions, that weren't there in your version!
So it meets well that the patch has just become official. You jast can update your version, rev 421 is abit datet anyway