While taking the code into my own CVS repository (slightly modified to match our Bugzilla customization) I found the plug in code for the spell checker. What do I need to do to activate that (aside from downloading the perl text::aspell which I have not found on ppm yet)
Thanks in advance for your help and apologies for being so bothersome.
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I got it all installed but am totally stuck trying to add the functionality to the display. Do I have to add additional code to the tr_htmlarea.pl file?
Again, my aplogies (I am barely a Perl hacker, and javascript is pretty much greek to me) And, yes, I know: I am way in over my head.
Thanks so much for your support! I promise, I'll make it up with testing.
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I exchanged some mails with the developer of the perl module, Bill Mosely. He was very kind and responsive but basically told me that I'd have to compile it myself:
"Well, you need a functioning build environment. I'm not sure what that means on Windows, but I think every other platform that's standard. So you don't have MSVC++ available? I assume you can install the cygwin tools and build with gcc, but that's beyond my scope of knowledge."
Since I'm not set up for that, this might be the end of trying to implement this (at least for me). Any other ideas? I'l love to get this to work and document it for everybody.
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
list it as failed for most or all platforms and the winipeg link gets you version 0.0.3 whatever you do. That version is incompatible with ActivePerl 5.8.
That's as far as my digging got me. I do not have the setup or the expertise to compile the thing myself to work with Active Perl 5.8.
If anybody has any ideas of how I could get my hands on a versions of Text-Aspell-0.0.4 please let me know.
Thanks,
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm considering replacing the HTMLArea editor with the FCKEditor(http://www.fckeditor.net). FCKEditor is quite active, there seems to be a great deal of documentation&support, looks good, it does everything that HTMLArea does and it comes with a spell checker.
Would you (or anyone who might be reading this thread) be interested in implementing the FCKEditor in Test Runner, including the spell checker...? I will assist you in this task should you need help.
Kind regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just took a quick look at it--looks really nice, Ed! Sorry for being so inactive, lately. I have been totally buried with hiring and training a couple of new testers.
I would be very interested into doing a pilot with the new editor. There are a few considerations that I need to clarify first.
During the summer months, I don't have any time to work on this outside of company time due responsibilities on my little "ranch" at home. So, I need to see if I can get approval to work on that during work hours:
1. My budget for working on Bugzilla has been cut to bare maintenance right now and about half of my users are using Macs (OS 9 and X). Do you know how the editor behaves when a user runs Safari? I have seen their plea for help for Safari support? If it doesn't work at all right now (e.g., crashes or makes the window unusable), I have a rather weak business case to ask for budget to work on this.
2. The rest of my users on PC are all over the place with regards to browsers. A lot use firefox or mozilla or whatever. The spell checker is for IE only. Again--I need to make my business case to the "Boss".
3. And last but really not least: remember, I am pretty limited to changing code to tweak it to my needs--writing new one, especially JavaScript, is mostly beyond my current capabilities.
I'll test the water with the boss of the company this week. Any more detailed information you have on the editor and above issues would be appreciated.
My apologies for being so non-committal at this point.
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your help. No need for apologies. I learned few days ago about the fckeditor and I remembered that you tried to make the spell checker work on Test Runner. That's why I mentioned it to you. I don't want to give you any trouble.
Maybe you can conduct a quick test of the fckeditor demo page from Safari and see how it goes?? I don't have any Macs around.
Now that you mention it, I have some doubts myself about Test Runner working alright on Safari. I use some advanced javascript on some pages on version 0.6.1. For instance this page: http://testrunner.citat.se/tr_showcaselog.cgi?run_id=236
I'm not sure if changing status or adding notes or attaching bugs from this page works on Safari.
Sometimes I am such an idiot--I whine about not knowing if fckeditor works on the Mac but the thought of running the demo page myself on Mac didn't occur to me! Talk about tunnel vision... I need a vacation.
I have upgrade my test and production sites to 0.6.2 and will try this afternoon to give if a quick spin on the little Mac with OS X that I have on my desk as test machine. If it works on OS X, it'll work on an apple cart (pun intended).
So far, my users with Macs are not using BRT just yet (they are on a different customized instance of Bugzilla), so I didn't spend any time on that part of testing yet. And to be honest, it never really occured to me that it might give us trouble. You have been doing such a great job in making BTR look like a natural part of Bugzilla that that thought didn't cross my mind either ;-) I'll let you know what I come up with.
With regards to the spell checker in fckeditor--I didn't check the fckeditor documenation. I just followed the link to iespell that popped up when I clicked on the spell checker icon in the demo. I'll take a closer look the the Speller Pages you mention.
Thanks again for all your help!
-- Karin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While taking the code into my own CVS repository (slightly modified to match our Bugzilla customization) I found the plug in code for the spell checker. What do I need to do to activate that (aside from downloading the perl text::aspell which I have not found on ppm yet)
Thanks in advance for your help and apologies for being so bothersome.
-- Karin
No problem,
try:
perl -MCPAN -e 'install "Text::Aspell"'
According to the documentation, you must have installed GNU Aspell version 0.50.1 or higher on your system: http://aspell.net
Report back how it goes,
Well, I got it all installed but am totally stuck trying to add the functionality to the display. Do I have to add additional code to the tr_htmlarea.pl file?
Again, my aplogies (I am barely a Perl hacker, and javascript is pretty much greek to me) And, yes, I know: I am way in over my head.
Thanks so much for your support! I promise, I'll make it up with testing.
-- Karin
I exchanged some mails with the developer of the perl module, Bill Mosely. He was very kind and responsive but basically told me that I'd have to compile it myself:
"Well, you need a functioning build environment. I'm not sure what that means on Windows, but I think every other platform that's standard. So you don't have MSVC++ available? I assume you can install the cygwin tools and build with gcc, but that's beyond my scope of knowledge."
Since I'm not set up for that, this might be the end of trying to implement this (at least for me). Any other ideas? I'l love to get this to work and document it for everybody.
-- Karin
Thank you for your interest,
yes, tr_htmlarea.pl needs modifications.
the file tr_testrunner/htmlarea30b/example-spell-checker.html contains the code you need to make it work.
After you succeed, if you could come up with a detailed procedure and share it on this forum, it would be appreciated.
Thanks,
Ed,
I seem to have hit a complete wall on this. The Text-Aspell module I need to run with Active Perl 5.8 is version 0.0.4 which does not seem to be available anywhere. The sites http://ppm.activestate.com/BuildStatus/5.8-T.html
and
http://testers.cpan.org/show/Text-Aspell.html#Text-Aspell-0.04
list it as failed for most or all platforms and the winipeg link gets you version 0.0.3 whatever you do. That version is incompatible with ActivePerl 5.8.
That's as far as my digging got me. I do not have the setup or the expertise to compile the thing myself to work with Active Perl 5.8.
If anybody has any ideas of how I could get my hands on a versions of Text-Aspell-0.0.4 please let me know.
Thanks,
-- Karin
Karin,
I'm considering replacing the HTMLArea editor with the FCKEditor(http://www.fckeditor.net). FCKEditor is quite active, there seems to be a great deal of documentation&support, looks good, it does everything that HTMLArea does and it comes with a spell checker.
Would you (or anyone who might be reading this thread) be interested in implementing the FCKEditor in Test Runner, including the spell checker...? I will assist you in this task should you need help.
Kind regards
I just took a quick look at it--looks really nice, Ed! Sorry for being so inactive, lately. I have been totally buried with hiring and training a couple of new testers.
I would be very interested into doing a pilot with the new editor. There are a few considerations that I need to clarify first.
During the summer months, I don't have any time to work on this outside of company time due responsibilities on my little "ranch" at home. So, I need to see if I can get approval to work on that during work hours:
1. My budget for working on Bugzilla has been cut to bare maintenance right now and about half of my users are using Macs (OS 9 and X). Do you know how the editor behaves when a user runs Safari? I have seen their plea for help for Safari support? If it doesn't work at all right now (e.g., crashes or makes the window unusable), I have a rather weak business case to ask for budget to work on this.
2. The rest of my users on PC are all over the place with regards to browsers. A lot use firefox or mozilla or whatever. The spell checker is for IE only. Again--I need to make my business case to the "Boss".
3. And last but really not least: remember, I am pretty limited to changing code to tweak it to my needs--writing new one, especially JavaScript, is mostly beyond my current capabilities.
I'll test the water with the boss of the company this week. Any more detailed information you have on the editor and above issues would be appreciated.
My apologies for being so non-committal at this point.
-- Karin
Thank you for your help. No need for apologies. I learned few days ago about the fckeditor and I remembered that you tried to make the spell checker work on Test Runner. That's why I mentioned it to you. I don't want to give you any trouble.
Maybe you can conduct a quick test of the fckeditor demo page from Safari and see how it goes?? I don't have any Macs around.
Now that you mention it, I have some doubts myself about Test Runner working alright on Safari. I use some advanced javascript on some pages on version 0.6.1. For instance this page:
http://testrunner.citat.se/tr_showcaselog.cgi?run_id=236
I'm not sure if changing status or adding notes or attaching bugs from this page works on Safari.
According to http://fckeditor.wikiwikiweb.de/Developer%27s_Guide/Configuration/Spell_Checker
the fckeditor can use "Speller Pages" which should run on any browser.
Thanks again for all your support to the project.
Ed,
Sometimes I am such an idiot--I whine about not knowing if fckeditor works on the Mac but the thought of running the demo page myself on Mac didn't occur to me! Talk about tunnel vision... I need a vacation.
I have upgrade my test and production sites to 0.6.2 and will try this afternoon to give if a quick spin on the little Mac with OS X that I have on my desk as test machine. If it works on OS X, it'll work on an apple cart (pun intended).
So far, my users with Macs are not using BRT just yet (they are on a different customized instance of Bugzilla), so I didn't spend any time on that part of testing yet. And to be honest, it never really occured to me that it might give us trouble. You have been doing such a great job in making BTR look like a natural part of Bugzilla that that thought didn't cross my mind either ;-) I'll let you know what I come up with.
With regards to the spell checker in fckeditor--I didn't check the fckeditor documenation. I just followed the link to iespell that popped up when I clicked on the spell checker icon in the demo. I'll take a closer look the the Speller Pages you mention.
Thanks again for all your help!
-- Karin
When I said "I use some advanced javascript on some pages on version 0.6.1"... I meant version 0.6.2.
Version 0.6.1 should be fine on Safari.