| What are the licencing conditions for tGedit? |
|
tGedit is distributed under the BSD Licence. We are moving the project to SourceForge for hosting/development. The Licence is as follows:
Copyright (c) 2008, Geomantics
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the Geomantics nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| What are the
system requirements for tGedit? |
| |
User System Requirements
- Windows 95/98/ME/NT/2000/XP/Vista
- Internet Explorer 5.0 or Firefox 2.0 or later
- JavaScript enabled
Server System Requirements
- ColdFusion Server 4.5 or later
- OR PHP5.x
|
| Can I have multiple
instances of tGedit on the same form? |
|
Multiple instances are supported by the Pro version
only. You must set the multipleinstance parameter to true
for the second and subsequent instance and use distinct names for
each instance of the editor. |
| Why
do I get an 'unterminated string' error when tGedit is placed in my
template? |
| |
tGedit is not compatible with the Cold
Fusion <cfform> tag which incorrectly substitutes additional
code into the template when tGedit is included. Change your template
to use the the simple <form> tag instead. |
| Why
can't I get tGedit to work when submitting a form using JavaScript? |
| |
As tGedit uses the onSubmit() event
internally submitting a form using a button and call to the submit()
event will not work. This can easily be fixed by firing the onsubmit
event manually. For example for a Form names 'mf then
< INPUT TYPE="Button" value="Go"
onClick=submit()>
should be replaced by
<INPUT TYPE="Button" value="Go"
onClick="mf.fireEvent('onsubmit'); mf.submit()">
|
| How
do I use the inline editing function (as shown on the Gedit sample
page)? |
| |
tGedit simplifies the use of JavaScript
to dynamically edit a HTML page without any need to submit a form.
This method relies on the use of the innerHTML and innerText properties.
- Set the ID tag of the page area you wish to edit.
for example. <P ID="edittextarea">
- Set up a HTML link that will open up a popup
window containing tGedit inside a form.
- Add the openersource tag to the tGedit call to
tell tGedit where to find it's source. openersource="window.opener.document.all[""edittextarea""].innerHTML"
- Set up an JavaScript call that will close the
popup window onSubmit - for example.
<INPUT TYPE="submit" NAME="submit" VALUE="Save
changes" ONCLICK="window.close()">.
tGedit will now extract the HTML from the area of
the page identified by the ID when it is opened, and update that
area with edited text when closed. This method does not update any
database or source code (you will probably wish to do that it parallel)
but it does immediatly update the page without it having to be reloaded. |
| When
I go to a page containing tGedit it asks me to enter my Office 2000
CD, is this a bug? |
|
Because tGedit uses the DHTML Edit Control some
systems may detect sharing issues with Office 2000. Office 2000
doesn't need to do anything to the files needed for tGedit to run
and the following work-around will solve the problem and stop it
from happening again.
- Click Start > Settings > Control Panel
> Add/Remove Programs
- Highlight Microsoft Office Professional in the
list.
- Click Change (This will pop-up the Office Maintenance
Window)
- Click Add or Remove Features.
- Expand the Office Tools Directory.
- Click the down arrow next to HTML Source Editing.
- Select Run from My Computer.
- Click Update Now.
|
| How
do I set up image paths? |
| |
tGedit allows some latitude over pathing
to images and consequently where tgedit.cfm can be placed. For example
tGedit consider the situation where you have tgedit in an admin
system located in inetpub/admin/ and you wish to use images located
in inetpub/usersite/image/. You have two choices...
a. Use relative pathing. In this
case tGedit will attempt to resolve all image paths to relative
paths when saved. In this case set the parameters
baseURL="http://www.mysite.com/usersite/"
initiallocation="../usersite/"
The baseURL parameter is set to the URL of the user's site, and
the initiallocation parameter to the relative path to this directory
on the server from where tGedit is located. Note that in this case
the image manager will always open in the root directory of the
site.
b. Use absolute pathing. With absolute
pathing tGedit will simply save the full image path. In this case
set the following parameters
baseURL="http://www.mysite.com/usersite/"
initiallocation="../shop/images/"
absimgURL="http://www.mysite.com/usersite/images/"
Please note that both baseURL and absimgURL
parameters require the http:// prefix.
Again, the baseURL parameter is set to the URL of the user's site,
the absimgURL parameter to the URL of the image directory, and the
initiallocation parameter to the relative path to this image directory
from where tGedit is located. Note that in this case the image manager
will open in the image directory of the site.
Generally relative pathing is preferred, but because tGedit has
to parse and manipulate image paths to remove the full path when
saving the HTML code, it is possible to construct site structures
where relative pathing will not work correctly - for example if
the admin system was located in a directory below the usersite directory
(e.g. inetpub/usersite/admin/). In this case use absolute pathing,
which will work in all directory structures.
|
| Can
I improve load times? / I see an error "unexpected call to method
or property access" when tGedit loads. |
| |
When tGedit loads it creates a timed event to
complete initialization actions after loading has finished. This
interval for this event is set to 250 milliseconds and suffices
for all machines we have tested. However on very old (Pentium I
or similar) systems this may not be sufficient. If your users report
this error you should increase the value set in the line:
tgedit_timerID=setInterval("tgedit_init()",250);
Conversely we have generally found that for most
machines (Pentium III or equivalent) a timing of 100 milliseconds
is more than adequate and reducing this value will allow tGedit
to initialize more quickly.
Note added for v2.0: Mozilla based browsers
seem to be more sensitive to this parameter than IE, and you may
need to increase this parameter on slower servers if your users
use Mozilla, even on faster PCs. |