djlurch wrote:
Borg:
Thanks for the new release. I tried unsuccessfully to install it. I got it to almost run, but not quite.
There are a few problems:
The installation notes are incomplete
1) non Dim'ing of variables strFormName and strTextarea
2) path to RTE folders...I obviously don't want to put my files all in
the RTE folder, therefore a relative path assignment to the RTE folder
is required
3) poor usage of include file. I have pages that post back to
themselves. Having multiple <!-- include
file="rte_editor_inc.asp> files is impossible without extreme
funkiness. i want to use that include file once in an asp
page...then use a variable if some code needs to be displayed for the
JS includes and other enabling code.
4) the graphics (B/I/U) are not standard windows. i prefer the traditional buttons, not the white/black buttons
5) too much intermingling of includes to be easily customizable.
Overall though...nice migration to textarea. This is a much more elegant (IMHO) approach than the IFrames.
Troy
|
1. I shall look into that
2. You can place the RTE files into the folder you place the RTE area
into. I tried for 3 days to make it so you can just put in the path to
the RTE files so they could be in their own directory, but this wouldn't
work due to path problems to things like files, images, etc. when the
form is submitted would be incorrect.
3. I think you are implementing it in the wrong way
4. This is just personal taste and you can easily switch the images used for these buttons to something you prefer
5. There are very few includes, most buttons launch pop-up windows, other
includes are used to modulise the code as much as possible for simpler
customisation
An Iframe is still used for the textraea to get the RTE features to
work, it's just less visible now as a Javascript file is now used to
hide the original textarea, then create an Iframe and pass the data
from the textarea to the IFrame.
This like the buttons are more difficult to customise and are created
now with JavaScript, the reason for this is so that if a user doesn't
have javascript enabled they see the normal textarea with no buttons, if
an include was used for this like in the old version, those without JS
would still see the buttons, but wouldn't be able to use them.
I've spent around 100 hours working on version 3.0 from version 2.0,
but allot of things you have to comprimise between what will work and
what is simple to implement. It's a very fine balance and in the process
some things have to be sacrificed, like being able to have the RTE
files in their own folder.