Xinha Discussion Forum

@adam, @cynthia

For me, Xinha gets an update when I need to update something.  The short version is, it works, so I don't do much work on it.

I don't use the EFM or the IM, those are horrid systems to maintain and won't be doing any work on those myself ever (since I don't use them), the MFM (MootoolsFileManager) is superior in every way.

Xinha development has always been like this, because (as you know adam) a tool made by developers for developers, it progresses when somebody has an itch to scratch.

Adam, I think you already have access to the svn, and trac, from memory.  Cynthia if you would like subversion access, send me the initial code you want to commit for verification and I'll set you up access.

Is that error with the example?

Are you using mod_security on the server?

For starters, use a recent Xinha or you are in for a world of hurt if you stick with such an old one.

Xinha Revision 961 is like 360 revisions old, the current trunk is revision 1325.
(I guess you are using the 0.96.1 release, which isn't quite so old, but you are better to use the trunk by far, 0.96.1 doesn't have IE9 fixes, has an old MFM etc...)

The current trunk can always be downloaded with the link on the bottom of this page: http://trac.xinha.org/browser/trunk

Your _editor_url should be absolute if at all possible, relative paths are always a PITA.

And finally, don't use ImageManager plugin (or ExtendedFileManager) at all, they are ancient and likely broken.

Use the MootoolsFileManager plugin instead, it can do both jobs, is modern, looks good, and works well, the current trunk includes a demo of the MootoolsFileManager in examples/mootools-file-manager.php which you can see the proper way to configure the plugin. 

All the configuration options for MootoolsFileManager can be read here... http://trac.xinha.org/browser/trunk/plu … ig.php#L84

NB: The plugin uses mootools of course, but it should be compatible with jquery running on the same page too even if the jQuery is not in compatible mode.

See Xinha.makeEditors() and Xinha.startEditors() in the XinhaCore.js

Pretty straightforward, make your textarea, insert it into the DOM, ensure the name & id of it are the same, supply this id to makeEditors, supply the result of makeEditors to startEditors.

You have put an extra slash by mistake

"/http://

You may use Xinha for anything you like, commercial included.

*cough* patches welcome *cough*

http://trac.xinha.org/wiki/Tickets

Patches Welcome! As the saying goes.

Xinha is now, and has always been, a tool driven by developers who have an itch to scratch, we use it in our own businesses, putting it to use in our own systems. 

The short version of this is, if it works for us, then our itch is scratched and that's the state it stays in, until we have a new itch (one of our clients asks for something to be added), or something stops working and so we have to fix it.

If you have an itch to scratch, please, go ahead and scratch it, then contribute it back for us all to benefit.

Err, if you don't know what a textarea is, then I dont' think Xinha is something you want to be using!

This is a textarea!
<textarea></textarea>

See the examples in the Xinha distribution.

Xinha does the job it sets out to do, when a new need arises then development would be done to meet that need.

In short, if somebody using Xinha needs a new feature, or a bug fixed, then they will do that.

New developers are always welcome.

Overriding the Xinha.prototype._clearFonts should work fine.

Xinha.prototype._clearFonts = function() { ... }

Of course, you must do this AFTER you load Xinha's file or it will be redefined to the default.