You are not logged in.
...abut the xinha-ie and xinha-gecko:
i like the idea too - but doesn't get reading the code much more complicated? (and writing too ofcourse)
Well, I don't think so, as long as it's abstracted in the right way. Sure for small differences just roll them togethor, but I'm thinking for the large bits of code (whole methods) that are specific to one or the other, to cut down on the weight for loading into a single browser.
...i just tried out the paste-solution for mozilla FCKeditor has...
VERY, VERY nice i must say!
we should copy the idea imhoin short:
if a FF-user clicks the paste-as-text-button, a popup opens with a textarea where the user can paste (using ctrl+v) and then click ok. then the editor will insert the pasted-content as text!
Didn't think of doing it that way, simple and effective I guess.
I've fixed the problem with David's logo displaying. I like this one too ![]()
adam is correct, you'll have to make it a single button (not in the combined file) and modify htmlarea.js in some way so you can have buttons of different sizes (it is necessary to specify a size, simply removing the sizes isn't going to work).
The problem I face is that there are no server side scripting like PHP or Perl, available.
Could I insert an equivalent JavaScript regex search into the HTMLarea f.onsubmit to break it down into smaller pieces prior to it being submitted back to the textarea ?
Yes,
<form ... onsubmit="this['myTextArea'].value = this['myTextArea'].value.replace(/(<\/?[a-z0-9]+>)/ig, '\1\r\n');return true">(I'm just not sure on the backreference format in javascript regex off the top of my head, it might be $1 instead of \1)
I'd still like to see the artistic talents of some more members, and have a vote, but my personal favorite at the moment is hyp0r's first one (with the tagline), my reason (compeletly subjective!) is
1. I like logos to have something graphical and not necessarily related, a mascot if you like, I think this is reflected in many open source motifs, eg Tux, the BSD Daemon, etc.. The use of a Chakra satisfies that goal
2. I also like products to have a tagline, again that's satisfied
3. I like the plain but bold typeface, and especially the dropped leg on the X just giving it a bit of interest
4. completly off the topic, but being a blatantly biased Kiwi, the Chakra (well, the fact that Xena uses a Chakra) gives it a small link to New Zealand :-D
But don't get me wrong, the others are also very good, the reason I prefer hyp0r's over them is just...
* rift's: I think that the dimensions of rift's are perhaps not right for a logo at the top of the trac which would better suit a landscape dimension rather than the portrait of his design
* mattia's: I'm not sure about having the chinese character there, for the simple reason is that it would be a bit of an "in joke" as it were, unless you were privvy to this thread (or whatever) you wouldn't know why we had this character as the logo, I also think it would look better in black ![]()
* macatak's: I quite like it, but I just prefer hyp0r's probably because it's simple black-on-white and it has that graphical component, I don't know, it's actually pretty close in "how much James likes them" points ![]()
But like I said, it's not my decision, this is a community driven open source project and the community shall decide.
We must have some other artistically inclined members out there somewhere to have a crack at it!
The simplest method would be for you to insert the linebreaks yourself when the text is submitted to you, eg in php
$text = $_POST['myXinhaField'];
$text = preg_replace('/(<\/[a-z0-9]+>)/i', '$1\r\n', $text);Will,
Xinha is much quicker (thought much less developed at this point).
could you perhaps write a list (just post here) of things that FCK has that we don't (and should)?
I wonder if xinha would get more development being on sourceforge?
I doubt it, SF doesn't support subversion repositories, or trac or anything nice like that anyway. There are a number of developers (including myself) who have access to commit to the subversion repository for Xinha, anybody who wants to do so need only ask me (and show me a patch they want to commit first so I know they are at least a little bit conversant with Javascript).
You can't, Guillaume's solution is to progressivly load the plugins, but once loaded they are there for good I believe
Interesting. It would be nice if we could support Safari too, but it won't be before V1.0 (of Xinha), by which time hopefully the browser specific code might be able to be split out into separate scripts - I want xinha.js, xinha-ie.js and xinha-gecko.js, and one day then xinha-safari.js (or xinha-khtml.js if that functionality is passed back to khtml for konq etc).
I do have PearPC around here somewhere so I *could* at a pinch do that development, but it would be better for somebody who has a real (much faster) Mac to do that.
Yes, that's now correct, since we use XMLHTTPRequest for more and more things, and it's XML-HTTP-Request, not XML-FILE-Request
I don't see it as a problem though, because you obviously need a webserver to do anything useful with Xinha anyway.
The only way of doing it would be to snapshot the html before the paste, paste, then diff the snapshot and the current to work out what was added, pull that out, strip it appropriatly, put it back in etc... in other words, it's just not realisitically possible.
The problem with paste (plain text or otherwise) is that you won't be able to do it in Firefox from a toolbar button, the only way (without adjusting browser settings manually) is to CTRL-V or select edit>paste
hyp0r, maybe you should try making the word Xinha go "through" the middle of the chakram (the circly thing for those who are not familiar with the Warrior Princess) or something to bring them togethor somehow (perhaps the chakram could be "part of" the X in Xinha).
I like the tagline
The only thing with the drop on the X is we wouldn't be able to have it over the grey bar like that unfortunatly.
wouldn't it be possible to make fast popups by opening a "about:blank"-popup and then write the html-code into it? (that might be allready preloaded)
No, I mean the actual action of creating the popup window is quite slow, once it's open it doesn't matter how the content gets into it. Displaying a layer/iframe is much much quicker (and memory friendly) than opening a window.
i didn't look at that in detail - does that really work? can i work with the editor while in background the linker-dialog gets loaded?
To tell you the truth, I don't actually know. The transfer should be asynchronous, so actually downloadin the data from the server should work "in the background", but I expect that actually manipulating that data happens in the foreground (ie all Javascript within a window runs in a single thread), otherwise it would mean that the JS engine would have to multi-threaded, and I'm pretty sure that it's not.
Are you using the latest nightly?
See line 2248 in htmlarea.js (rev 64). Try re-enabling that code and see how it goes for you.
- if we would do that we need a popup-dialog.js replacement for inline-dialog.js - so that everyone can decide what he wants to use
(who will write this?)
I would, although I havn't really thought too much about it when I hacked togethor Linker and inline-dialog, I expect it might take some work to figure it out. I don't however have very much time right now so if somebody wants to do it, by all means go ahead. What I would say is that it would be *much* preferable to use layers (eg a positioned iframe) as "faux popups" rather than real popup windows, this would be much faster to open the popups ( I find opening the dialogs quite slow at the moment) and avoid possible popup-blocker problems.
- when should the dialogs (html-files) be loaded, the linker-plugin loads the html-file when generating the editor, is it a good idea to load ALL dialogs - although the end-user might not open any dialog?
Well, two sides to the coin, if we load them at the start then it will be more responsive to users when using it, if we load the files on demand then perhaps the initial loading will be a bit faster. I prefer preloading them when starting Xinha so that it's more responsive when you want to use them, but others might feel differently. If they were loaded at the start, then they should be loaded asynchronously (ie use _getback or something) rather than hold up the rest of the process while it's loading the file from the server - see Linker for example.
as some allready may have noticed.. there are no more en.js files.
This is because when calling the HTMLArea._lc('text to translate')-function the first argument is allready the english text.i see now two possibilities:
1. parse all source-files and find every call of _lc('')
...this gives only back a few, it will not work in:
- htmlarea.js line 447 when translating the buttons (can be easily changed)
- all dialogs using inline-dialog.js (currenlty only the linker-plugin i think)
- all dialogs using popups/popup.js __dlg_translate (most are...)
This way should work I think, just search for _lc("....") (and with single quotes too), with <l10n>....</l10n> and _(...) for the inline-dialog html files. For the buttons, we should probably translate them when putting them into the toolbar, eg in htmlarea.js
this.btnList = {
bold: [ HTMLArea._lc("Bold"), ["ed_buttons_main.gif",3,2], false, function(e) {e.execCommand("bold");} ],The popups might be a bit more tricky
PHP and it's ignored trailing commas have much to answer for in the world of Javascript bug hunting ![]()
I think I will add a "boilerplate" file to the examples directory which people can more easily modify to be thier own (currently they have to copy the example body and delete a chunk of stuff from the bottom).
What about if you remove overflow:auto (and what styles are set for #scrolldiv in your CSS)?
The code that determines the window size is simply...
if (self.innerHeight) // all except Explorer
{
x = self.innerWidth;
y = self.innerHeight;
}
else if (document.documentElement && document.documentElement.clientHeight)
// Explorer 6 Strict Mode
{
x = document.documentElement.clientWidth;
y = document.documentElement.clientHeight;
}
else if (document.body) // other Explorers
{
x = document.body.clientWidth;
y = document.body.clientHeight;
}Are you setting _editor_url correctly?
Well, each (text) file should have a comment header with the revision number replacements in it (see the comment header in htmlarea.js). For actual release numbers though we have none really as yet, just stable (which I've tagged 0.1 as I recall) and nightly. When a release is made then the version number replacements can be made when the svn export is done (we don't really want specific version numbers in the repository, outside of tag/branch names).
Generally in this phase of not yet really ready for release you should use and update the nightly every now and then (using subversion, or downloading).
Hey GOGO and all others here.
If you (gogo) or anyone else thinks they would benifit from my contributions on the ASP and ASP.NET side of things let me know by posting here or emailing me cward(at)dynamicbydesign.com If those here see no benifit from my help no big deal I'll keep my work to myself as I find benfit in it basically because we don't run any PHP only ASP and ASP.NET.
Hi Chris, of course any and all contributions of code, in any language are excellent
You should contact yermo on this board, he is working on a new "backend" system for plugins and will probably want some help with the ASP side of things.
Mmm, I guess we could do something like that. Somebody submit a feature request ticket, if anybody cares to make a patch please attach to the feature request.