I'm uncomfortable using zipserve because of its performance
characteristics.  Niceedit looks like a good option as well ...
perhaps a bit smaller than TinyMCE minimal in bytes ... since it
offers customized js packages.

On Jun 28, 8:20 pm, johntray <john.tur...@gmail.com> wrote:
> To anyone using TinyMCE, I would recommend using zipserve to serve the
> editor from the distribution .zip file (so that it only counts as 1
> file). zipserve is not well documented, but see the source file in the
> GAE distribution (google\appengine\ext\zipserve\__init__.py), also 
> athttp://code.google.com/p/googleappengine/source/browse/trunk/python/g....
> There is also a zipserve example 
> athttp://code.google.com/p/google-app-engine-samples/.
>
> On Jun 28, 12:14 pm, Tim Hoffman <zutes...@gmail.com> wrote:
>
>
>
> > I am using nicedit  http://nicedit.com/itjust decorates textareas
> > so
> > very little is required to make it work unless you want custom image
> > uploading within in it.
> > It also externally hosted so it doesn't have to add to your static
> > file count.
>
> > T
>
> > On Jun 28, 11:26 pm, Stephen Mayer <stephen.ma...@gmail.com> wrote:
>
> > > So I was looking for a good way to impliment a rich text editor on a
> > > site I'm building.  There are two obvious possible options: FckEdit
> > > and TinyMCE.  TinyMCE is smaller and has a simpler design so I decided
> > > to work with it instead.
>
> > > Starting Point: 241 files, 101 folders, 1.41mb
>
> > > But since I only need the simple version of tinyMCE listed 
> > > here:http://tinymce.moxiecode.com/examples/simple.php
>
> > > So I used firebug's net tab to watch which files tinyMCE actually
> > > loaded after adding it to my page.  I created a list of these files,
> > > and then moved them into a tiny_mce_min folder.  Then I switched to
> > > using my minimal installation directory ... eliminating most of the
> > > unnecessary code quickly and easily:
>
> > > Ending Point: 6 files, 7 folders, 182kb
>
> > > The process
> > > 1) Add the full TinyMCE to your dev enviornment, update app.yaml
> > > 2) Add TinyMCE to your script ... set any options you need to get the
> > > version you want
> > > 3) View TinyMCE in FireFox with Firebug powered up and the Net tab
> > > open
> > > 4) Create a version of your TinyMCE install that includes only the
> > > files from TinyMCE that are listed in the net tab
> > > 5) Use the minimal install in your deployment rather than the full
> > > install
>
> > > Now I think we could go one step further and eliminate a few file
> > > loads (like the lang files) if we hacked tinyMCE js code ... and get
> > > it down to one file (or three if you count the css + images).  But
> > > right now I don't have time to do that.
>
> > > I realize that the file limit is now bigger than it used to be (now
> > > 3000 files) ... but think that it's very constructive to go through
> > > this process.  Ultimately I don't want to use 241 of my file count
> > > limit towards something that could be loaded in one js file.  Much of
> > > the time we have grown used to slapping in a library but using only a
> > > very small percentage of it.  I'm hoping that library developers soon
> > > begin offering "custom versions" of their code that are highly
> > > optimized for a specific task.
>
> > > Hope this post might be helpful for someone else who confronts the
> > > same problem/issue.  Another suggestion to Google: perhaps they could
> > > host some of these commonly requested libraries by default.  I don't
> > > think that any of the rich text editors (fckedit or tinymce) are
> > > available on a CDN anywhere right now.
>
> > > - Stephen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to