Xinha Discussion Forum

ooooo pretty   would you like these included in the Xinha distribution or you prefer not?  Submit a ticket if you would like them in

Hmmm.  Strange.  What version IE?

I like the proposals   Lets say we have a vote and choose just before releasing Version 1.0.  So entries welcome up until then!

I'll haev to find some voting thing for punbb or something

Xinha should resize on-the-fly no problem if you are using relative sizes.  Eg if your textarea is style="width:100%;height:100%" it should work.

You can however call the sizeEditor() method on the editor explicitly if you wish

myEditor.sizeEditor(width, height)

Trunk is because thats where we are working, on the trunk, when V1 is done and released it will become a branch and tickets specific to V1 and not V2 would be assigned to the V1 branch, while tickets specific to V2 development are assigned to trunk.

The tickets are shown ordered by priority, the severity is a different thing.  Severity should be set by the ticket submitted (so if they think something is very serious they select serious) it is an indicator of how bad the problem is, Priority on the other hand should be set by the Xinha developers after looking at the ticket, it is an indicator of how quickly we should look at the problem in relation to other problems.  But really the ordering doesn't matter, just pick something you can do and do it

No, I was thinking of turning the current toolbar array into a toolbar object

this.toolbar =
  {
     'character' : ['color', 'font', 'size'],
     'control'     : ['htmlmode', 'infopopup']
  }

etc.  Then plugins can do toolbar.control.push(my_new_control_button_here)

But shouldn't it be that you just extend Linker into your own plugin which caters for all your needs, or make a Meta-plugin that combines features from other plugins etc etc.  I can't really imagine a situation where you would be benefited by being able to "unregister" a plugin and then register another plugin in it's place, without reloading the page.

Once version 1 is done, the toolbars system is due for a rethink and rewrite, I want to clean that whole thing up and am thinking about having "named" groups in toolbars so that a plugin can insert a button into a certain group of buttons (eg insert a button into the "character" group, or into the "lists" group or the "control" group etc....) rather than just smushing them onto the start or end of the bar without any care.

At the same time we will take a look at allowing for expanding and contracting the groups in the toolbar with a handle on the edge of each group and perhaps even rearranging them via drag-drop and saving the positions in a cookie, now that would be cool.

We may take a look at implementing progressive loading of plugins also, however I'm still not convinced that it's worth the extra trouble to save a few seconds of loading time.

If it's not used, then it's a candidate for removal

aldoh: as niko says, you need to give more information.  What character sets are involved?  The recommended is utf-8 all the way, but iso-8859-1 should be OK too.

Nope, never had a book on JS or DHTML or anything, google is my best friend

Don't forget the reason for EP (and dom_checkInsertP) in the first place isn't just to get Moz and IE to produce the same code, it's to get Moz to produce code that's usefully manipulable with CSS

Patches welcome niko

I'll have to plead ignorance on how threading happens in javascript.  It may be that events (and timeouts etc) won't fire until tbere are no instructions to be executed, that is, they wouldn't fire until generate has done.  Essentially that the event "threads" are synchronised into a single thread.