You are not logged in.
why don't you create wiki-pages here at xinha.python-hosting.com ?
Would be great :) I have started at home because i have old documents i had write in french for my company to explain how HTMLArea was working. I am not allowed to put thoses documents online because unfortunatly there is also private information inside.
But since i want (and i am sure it has the potential to be) Xinha to run better and be THE best, one of the way is to give back what i dig out of open source community. The quicker way was to make them at home until someone gives me wiki access, who should I send a mail ? :P
I have a few questions about the Config object.
can the property Config.lang be manually updated ? Is it used internally only to keep the _editor_lang between plugins ?
I have no clue if thoses properties can be manipulated, I think they are private only, are they ?
Config.baseHref
Config.stripBaseHref
Config.stripSelfNamedAnchors
Config.specialReplacements
Config.baseURL
Config.charSet
I understand the concept behind htmlRemoveTags, but can someone show me an example ? I tried again and again to find a valid regexp to remove all headers tags (H[1-6]) but never succeed.
http://xinha.python-hosting.com/wiki/Licence
the licence page say not much things, which is good, but i would like to have a few explanations if possible.
1) Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.2) Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.3) Neither the name of interactivetools.com, inc. nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
I dont think anyone is using Xinha in a binary version and i dont consider my use as a binary version, so this point is quite easy to check ![]()
For the (3) , it is asked me to not use the name interactivetools to sell my products, well ehehe ok, that's not a problem at all. Noone of my colleagues even known the name of IT, so there's no chance our customers hear about it. So again, this point is checked.
But I wonder what i have to do exactly to legally check point (1) . My use of xinha, as a lot of us here i think, is to provide an easy way to our customers to update some content on their website via a backoffice. In this case, to be legally allowed to sell my tools, am I supposed to :
1) drop the licence in the xinha directory ?
2) send the licence to my customers ? I doubt email is valid enough ![]()
3) add a link on every page that's use Xinha ?
4) not allowed to remove the about icon from iconbar ?
or perhaps all of them, or perhaps something else.
Also, is there something specific to check when code is sold or when only the right to use the final tool is sell ?
Thank in advance for any information, my boss asked me today and I was not able to give him a straight answer.
- NewbieGuide obviously ![]()
http://xinha.python-hosting.com/wiki/NewbieGuide
- Basic utilisation
http://xinha.python-hosting.com/wiki/Do … BasicUsage
- Config variables list
http://xinha.python-hosting.com/wiki/Do … iablesList
- Manage many editors
http://xinha.python-hosting.com/wiki/Do … pleEditors
- Some initialisations methods
incoming
- Manual start
incoming
- Add plugins
incoming
- Update the iconbar
incoming (waiting further discussion before release)
- How to correctly submit content
incoming (in progress)
- Plugin creation
incoming (waiting further discussion before release)
Plugin updating existing Xinha function
- incoming
- Add icon to iconbar from plugin
incoming (waiting further discussion before release)
- PHP class to control Xinha
incoming
If you dont want or cant alter the onload, something like the following should do the trick correctly.
<body onload="alert('hi');">
...
...
<script type="text/javascript">
var oldOnLoad = window.onload;
window.onload = function(e) {
if (oldOnLoad) oldOnLoad(e);
xinha_init();
}
</script>
1. The concept of plugin is very important to have a dedicated or evolving editor
Yes, the concept of plugin is required. We all need an editor but none of us need the same behavior and features. Plugins are answering to this concern.
To my point of view Niko, you should load the code only when necessary so when clicking the button...
gogo's oppinion is to load it on generate (if i can speak for him here)
of course it's going smoother when everything is preloaded, but the core is already 146Ko, it's a lot of javascript to transfer. Loading also the plugins logic is too much i think.
Of course this "argue" of the actual size of core will not be valid when the discussion about the separation by navigators will be complete, but that's bring me to an interrogation. Perhaps the structure of plugins could be separate in two files. One init file which could be preloaded by core, and the other one with the remaining code that would be loaded on demand only. Well, as always it's pure js speculation ehe
please some comments for my patch:
http://xinha.python-hosting.com/ticket/139
well, as always i wonder how the hell you all can do such amazing things with javascript. As far i can understand, there's no need for HTMLArea.init() anymore and when generating first editor you test if scripts are loaded and if they are not,well load them. For me the code is clear and it does the job. I'm not a js expert but i think it's better to have a unified way to load scripts than two functions. And i am sure you know what you doing, so for me if ever it worst anything, i think the patch should be applied.
and if we could remove the old built-in-fullscreen-page.
Cant the fullscreen.html that's loading scripts be updated with HTMLArea._loadback() ?
If no or not in an easy way, well, why again keep two ways of doing the job ? The built-in fullscreen has never been efficient for me and as far i know, none of ppl around me playing with editor have ever used it. But since xinha and the fullscreen plugin, i use it and ppl around me are using it too.
Having a built-in system and a plug-in should be imo turned into plug-in only. The plug-in is better, at least looks better from my side of view, and it is easier to use. Also the plug-in doesnt need another download of scripts when it is called. It is far better i think.
well, my 2 cents ![]()
Just add this translation at the and of the FAQ page and make a link at the head for that...
Hurm, dont laugh at me but I have no clue of what you just said.
my first little french translation of FAQ is available at http://mokhet.com/xinha_faq.html
guillamed, feel free to send me a mail at mokhet@mokhet.com if needed.
Okay man but you will noticed than english is not my mother language.
Is there any volonteer to reread (and rewrite..) the FAQ
English is not my mother language neither, but i'm up to translate it in french and reread by the same way ![]()
I think drbigfresh is talking about ticket #74
http://xinha.gogo.co.nz/punbb/viewtopic.php?id=48
http://xinha.python-hosting.com/ticket/74
do you have a webserver running or do you access xinha through file:///?
the i18n will only work if you have a webserver! (some plugins will have the same problem)
dont worry niko, i'm using a webserver and everything working fine. But yup, it's what i've noticed with the new system, not translated anymore with local files. I think this should be said somewhere in the documentation.
Another question for the incoming FAQ ? (without grammar errors of course ![]()
Q: I have done everything explained in newbie document but the texts are always in english, how can i use my language file ?
A1: Make sure your language file is up to date.
A2: The translation system (i18n) will only work if you have a webserver.
yes, _editor_lang is used!
Hello everyone, finally managed to get all this working. The problem i had was quite simple, the translation system is working only with online documents. When testing in local, the texts are always in english.
local urls i have tested (and not working, but it's only local so i dont think it's required to fix by now, but it had make me ponder a lot ![]()
_editor_url = '../';
_editor_url = 'file:///c:/Documents%20and%20Settings/mokhet/Bureau/SVN/xinha/';
_editor_url = '/home/laurent/cvs/makeai/js/xinha/';none of them worked in local, but worked PERFECT at the moment i dropped the test file online.
after a lot more of investigation, you are of course right
but in fact, it is missing some texts and some of the backslashes, i'll send you an updated one when i'll have understood how the new system is working.
are you sure _editor_lang = "fr"; is used at all ? Even with this line, my texts (correctly translated in revision 58) are not translated at all anymore in revision 60 and remains in english.
no, the "," is correct!
Damn, i knew my javascript knowledge were poor but not as much.
var mytab = {
"keyA": "valueA",
"keyB": "valueB1", "valueB2", "valueB3",
"keyC": "valueC"
};
alert(mytab["keyB"]);==> missing : after property id
this kind of thing is valid in the actual context ??? That's doesnt make any sense for me, looks totally invalid. damn.
Well, you know better than me so oki, but it perturbs me A LOT.
Yeah i already checked the NewbieGuide, but a FAQ is a totally different thing.
For now the forum is not crowded with always the same questions, but it will happens soon or later.
this question : How to hide status bar ? is the perfect example for a FAQ. It's not answered nor by the NewbieGuide neither by the newbie thread.
hi, just update my local version to svn version and i have two little things ![]()
humm, where are the files en.js now ? cant find one anywhere, all have been removed in #60, there must be somewere, but where, i cant say
looking at /lang/fr.js, i find this code (i cut it a bit, cause it would not be readable)
"You are in TEXT MODE. Use the [<>] button to switch back to WYSIWYG.": "Vous êtes en ...",
"The full ...",It's supposed to be
"You are in TEXT MODE. Use the [<>] button to switch back to WYSIWYG.": "Vous êtes en ..." +
"The full ...",I just checked the file /lang/de.js and it gots the same problem.
The problem is located in the ending char which needs to be a + and not a ,
This text is for a dialog box and is kinda long, it has been truncated on multiple lines.
There's also some utf-8 problems in /lang/es.js dont think it's police problem as the one i have in he.js or ja.js
Because i use spanish documents with not encoding issue usually, so it's probably a problem on this file.
with actual code when xinha is started, the button "justifyleft" is clicked.
When I remove the code as described in ticket #93, no buttons are clicked, it waits for the user input to update it.
I think it's related to the commented line a bit above in htmlarea.js
// editor.focusEditor();
after editor gets focus, updateToobar probably get called to have icons clicked in relation with content. Sounds logical.
Fix in #93 works fine for me too.
config.statusBar = false;
there is tons of way to init xinha and tweak one or more editors, but a very basic sample to make it works could be
<!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 type="text/javascript">
_editor_url = '/js/xinha/';
_editor_lang = "en";
</script>
<script type="text/javascript" src="/js/xinha/htmlarea.js"></script>
<script type="text/javascript">
function init() {
var config = new HTMLArea.Config();
config.statusBar = false;
var xed = HTMLArea.makeEditors(['mytextarea'], config);
HTMLArea.startEditors(xed);
}
</script>
</head>
<body onload="init();">
<form>
<textarea id="mytextarea" name="mytextarea" rows="10" cols="80" style="width:100%"></textarea>
</form>
</body>
</html>Is there any kind of FAQ around ? cant find anything else than the tracFaq which in this case is not really what is wanted ![]()
oh, didnt noticed the RSS feed but think it's because it doesnt appear on custom query (of course eheh, dumb me), and yeah i'm using only custom querys
/bonk me
Thanks niko for gmane.org, wasnt aware of such great thing, sounds like the perfect solution for most of my disliked mailinglists.
yeah, it's a good idea. I have no clue about how it can works, but it would be nice. I personally prefer to use newsgroups but sounds a lot more complex to do than a mailing list.
What about a RSS ? looks easier, could be done quite easily with php or any other server side language.
humm, i'm using version #58 with multiple editors on same page between a layout with <div>, <form>, <ul>, <dd> and such, but i didnt noticed this issue. What version are you using, any basic example online ?
Though i didnt try within a <table>. Perhaps it's some issue with configuration.
yeah, what i though. Instead of keeping them in local version, better have them on repository even with updates incoming, and some words and sentences could probably be tweaked out.
Hi,
Is it possible to add some components when creating tickets. Actually there is 4 available components (FullScreen, Linker, Stylist, Core)
I think it is missing a component for each available plugin and also a component to hold all translations issues.
what are you thinking about it ?
thank.
hi, in ticket 98 you asked me to wait for future translation, but i already have the files, so i created a ticket #118 and attached all missing files for fr version. If any updates in the structure of the files are needed, of course i'll submit updated files more acurate with .
in #99, should the Linker-plugin display a alert-box, or is it enough to display the error-message in the tree?
(imho the alert-box isn't needed...)
I agree, the alert box is not needed at all. i dont like it, my customers dont like it and after reading the forums, it seems everyone want to turn actual alert box to inline panel (color chooser, etc.)
and for the #98 (new-i18n-system) - what should happen if a language-file contains a parse-error?
Should we show a alert-box? (i don't know any other place to display the error) - otherwise we could just ignore the error and fall back to english.
Humm, the fall back to english is a great solution but sounds a bit of pain for no real benefits in this situation, because, humm, why the language file would contain any parse error ?
If there is a parse error in this file, then it's not xinha to correct it, it should be a community goal to keep them error free.
In an other case, when the language file is correct but not up to date with english version, then it would be great to fallback to english for missing entrys but not an annoying dialog box please.