Re: CForms: HTMLArea Documentation
Jeroen Reijn wrote: I'll see if I can find some time this weekend to create a patch and add it to JIRA. I've never used the HTMLArea widget, but I will be glad to commit the patch if you provide it. :-) Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
I'll see if I can find some time this weekend to create a patch and add it to JIRA. Reijn Derek Hohls wrote: Reijn Yes, I think there are many Cocoon users who would support it; we need a developer to "commit" to work to do it, though. In the meantime, I guess we just take the manual approach. Derek [EMAIL PROTECTED] 2006/03/16 12:51 PM >>> I offered the switch to Xinha a while ago and some people agreed, but no actions was taken. The Xinha documentation is fine and there is a forum as well. Just putting it in should work. We're using it in HippoCMS now and it's much better then HTMLArea. So I'm all for making it default in Cocoon. Regards, Reijn Stewart, Gary wrote: A Switch to Xinha is one of those things that really should happen. Best way to "raise" it is to fix Cocoon to use Xinha instead, and submit a patch. That way it is likely to happen. I'm sure at least one of the correspondents on this thread is up to the task. As it uses all the same (htmlarea.js) references I just gave it a go ripping the htmlarea directory out of cocoon-forms-block.jar and sticking the Xinha nightly one in. Looks like it is working just fine though I haven't tested the multiple language configs or anything. I'm assuming it would work just fine from a build as well though I haven't tested that yet. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Met vriendelijke groet, Kind regards, Jeroen Reijn Hippo Oosteinde 11 1017WT Amsterdam The Netherlands Tel +31 (0)20 5224466 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
Reijn Yes, I think there are many Cocoon users who would support it; we need a developer to "commit" to work to do it, though. In the meantime, I guess we just take the manual approach. Derek >>> [EMAIL PROTECTED] 2006/03/16 12:51 PM >>> I offered the switch to Xinha a while ago and some people agreed, but no actions was taken. The Xinha documentation is fine and there is a forum as well. Just putting it in should work. We're using it in HippoCMS now and it's much better then HTMLArea. So I'm all for making it default in Cocoon. Regards, Reijn Stewart, Gary wrote: >> A Switch to Xinha is one of those things that really should happen. >> >> Best way to "raise" it is to fix Cocoon to use Xinha instead, >> and submit >> a patch. That way it is likely to happen. I'm sure at least >> one of the >> correspondents on this thread is up to the task. > > > As it uses all the same (htmlarea.js) references I just gave it a go ripping > the htmlarea directory out of cocoon-forms-block.jar and sticking the Xinha > nightly one in. Looks like it is working just fine though I haven't tested > the multiple language configs or anything. I'm assuming it would work just > fine from a build as well though I haven't tested that yet. > > Gary > > * > The information contained in this message may be confidential or > legally privileged and is intended for the addressee only, If you > have received this message in error or there are any problems, > please notify the originator immediately. The unauthorised use, > disclosure, copying or alteration of this message is > strictly forbidden. > * > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
I offered the switch to Xinha a while ago and some people agreed, but no actions was taken. The Xinha documentation is fine and there is a forum as well. Just putting it in should work. We're using it in HippoCMS now and it's much better then HTMLArea. So I'm all for making it default in Cocoon. Regards, Reijn Stewart, Gary wrote: A Switch to Xinha is one of those things that really should happen. Best way to "raise" it is to fix Cocoon to use Xinha instead, and submit a patch. That way it is likely to happen. I'm sure at least one of the correspondents on this thread is up to the task. As it uses all the same (htmlarea.js) references I just gave it a go ripping the htmlarea directory out of cocoon-forms-block.jar and sticking the Xinha nightly one in. Looks like it is working just fine though I haven't tested the multiple language configs or anything. I'm assuming it would work just fine from a build as well though I haven't tested that yet. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CForms: HTMLArea Documentation
> A Switch to Xinha is one of those things that really should happen. > > Best way to "raise" it is to fix Cocoon to use Xinha instead, > and submit > a patch. That way it is likely to happen. I'm sure at least > one of the > correspondents on this thread is up to the task. As it uses all the same (htmlarea.js) references I just gave it a go ripping the htmlarea directory out of cocoon-forms-block.jar and sticking the Xinha nightly one in. Looks like it is working just fine though I haven't tested the multiple language configs or anything. I'm assuming it would work just fine from a build as well though I haven't tested that yet. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
Derek Hohls wrote: Gary Well, I think the issue does need to get raised... maybe someone has thought about it before, but just not gotten aroud to dealing with it. And version 2.1.9 is about to be released A Switch to Xinha is one of those things that really should happen. Best way to "raise" it is to fix Cocoon to use Xinha instead, and submit a patch. That way it is likely to happen. I'm sure at least one of the correspondents on this thread is up to the task. Go for it, I say. (I'll try to watch this thread, if I seem to miss something, ping me privately. My PC died, I'm using another computer, and got off a long haul flight to receive 1700 mails, with no mail filtering set up :-( ) Regards, Upayavira Derek [EMAIL PROTECTED] 2006/02/21 05:19 PM >>> Is this something that needs to be taken up on the dev list? Not sure. If you think it would I can forward it up there (though I'd have to join the dev list). I am sure that htmlArea was the best choice at the time that the CForms package was first put together, but some technology just does not last [unlike Cocoon, of course!] and continued reliance on (or seeming support for) a module that is no longer actively maintained is not to Cocoon's advantage... I agree that using an unsupported and undeveloped unit for Cocoon wouldn't be in the best interest of the users. Presumably as Xinha was based on htmlArea3 then the port would be pretty simple. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CForms: HTMLArea Documentation
Gary Well, I think the issue does need to get raised... maybe someone has thought about it before, but just not gotten aroud to dealing with it. And version 2.1.9 is about to be released Derek >>> [EMAIL PROTECTED] 2006/02/21 05:19 PM >>> > Is this something that needs to be taken up on the dev list? Not sure. If you think it would I can forward it up there (though I'd have to join the dev list). > I am sure that htmlArea was the best choice at the time > that the CForms package was first put together, but some > technology just does not last [unlike Cocoon, of course!] > and continued reliance on (or seeming support for) a module > that is no longer actively maintained is not to Cocoon's > advantage... I agree that using an unsupported and undeveloped unit for Cocoon wouldn't be in the best interest of the users. Presumably as Xinha was based on htmlArea3 then the port would be pretty simple. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CForms: HTMLArea Documentation
> Is this something that needs to be taken up on the dev list? Not sure. If you think it would I can forward it up there (though I'd have to join the dev list). > I am sure that htmlArea was the best choice at the time > that the CForms package was first put together, but some > technology just does not last [unlike Cocoon, of course!] > and continued reliance on (or seeming support for) a module > that is no longer actively maintained is not to Cocoon's > advantage... I agree that using an unsupported and undeveloped unit for Cocoon wouldn't be in the best interest of the users. Presumably as Xinha was based on htmlArea3 then the port would be pretty simple. Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
Is this something that needs to be taken up on the dev list? I am sure that htmlArea was the best choice at the time that the CForms package was first put together, but some technology just does not last [unlike Cocoon, of course!] and continued reliance on (or seeming support for) a module that is no longer actively maintained is not to Cocoon's advantage... Can we ask to have Xinha as the "new" editor; or at least modify the samples so as to show how either can be used; thereby giving users a choice of "plug-and-play" functionality? (see also: http://xinha.python-hosting.com/wiki/Compatability ) Xinha does not appear to have extensive documentation (but, hey, as members of the Cocoon project we can't shout that loudly ;-) Xinha functions: http://xinha.gogo.co.nz/punbb/viewtopic.php?id=137 (seem to reference HTMLarea functions... maybe will help?) >>> [EMAIL PROTECTED] 2006/02/20 09:09:52 PM >>> Stewart, Gary wrote: > Hi there, > > Does anyone know where to get the documentation for the HTML Area? I'm trying > to add some of the toolbar menus to the config but my guesses have been > wrong. The htmlarea example states it can be found at > http://www.htmlarea.com/htmlarea_2/documentation.html but that site doesn't > appear to house the documentation anymore. I tried Google's Cache but that > has been replaced as well. Does anyone have the documents? Have a look at http://xinha.python-hosting.com/ Xinha virtually offers the same functionality AND is being maintained. I have not tried to add or remove toolbar menues, but I suppose the information on how to do this is available. > > Thanks, > > Gary > > * > The information contained in this message may be confidential or > legally privileged and is intended for the addressee only, If you > have received this message in error or there are any problems, > please notify the originator immediately. The unauthorised use, > disclosure, copying or alteration of this message is > strictly forbidden. > * > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andre H. Juffer | Phone: +358-8-553 1161 The Biocenter and | Fax: +358-8-553-1141 the Dep. of Biochemistry | Email: [EMAIL PROTECTED] University of Oulu, Finland | WWW: www.biochem.oulu.fi/Biocomputing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CForms: HTMLArea Documentation
Stewart, Gary wrote: Hi there, Does anyone know where to get the documentation for the HTML Area? I'm trying to add some of the toolbar menus to the config but my guesses have been wrong. The htmlarea example states it can be found at http://www.htmlarea.com/htmlarea_2/documentation.html but that site doesn't appear to house the documentation anymore. I tried Google's Cache but that has been replaced as well. Does anyone have the documents? Have a look at http://xinha.python-hosting.com/ Xinha virtually offers the same functionality AND is being maintained. I have not tried to add or remove toolbar menues, but I suppose the information on how to do this is available. Thanks, Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andre H. Juffer | Phone: +358-8-553 1161 The Biocenter and| Fax: +358-8-553-1141 the Dep. of Biochemistry | Email: [EMAIL PROTECTED] University of Oulu, Finland | WWW: www.biochem.oulu.fi/Biocomputing/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CForms: HTMLArea Documentation
Hi there, Does anyone know where to get the documentation for the HTML Area? I'm trying to add some of the toolbar menus to the config but my guesses have been wrong. The htmlarea example states it can be found at http://www.htmlarea.com/htmlarea_2/documentation.html but that site doesn't appear to house the documentation anymore. I tried Google's Cache but that has been replaced as well. Does anyone have the documents? Thanks, Gary * The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems, please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
