> So, do I hear you say: ETP out puts a stripped down
> TW/tiddler in an actual HTML format (which is the ONLY
> format TW content is ever exported to)?
umm... no. That's not quite right...
The purpose of the ExportTiddlersPlugin (and the"export file" format)
is to make it easier to *store*, *share* or *transport* a set of
tiddlers from one TW document to another, and does not provide
functionality for *converting* your tiddler content into some other
format for use outside of TW.
Although TW files are usually named with an ".html" extension, a
regular TW document (or an "export file") is actually a simple "plain
text" file containing a combination of HTML, CSS, and JavaScript.
The content that you view as rendered tiddlers when you've loaded the
document into the browser is NOT stored in the file in "HTML
format"... it is stored as unparsed wiki-syntax *source* text,
(contained in "hidden DIVs" in the file), which are only read-in and
rendered as viewable content once the TW javascript "engine" is loaded
and running in your browser.
Note: it IS possible to convert and save selected tiddler content to a
file as "pure HTML" by using the "snapshot" feature from
http://www.TiddlyTools.com/#NewDocumentPlugin
> If within a tiddler, I had code the message area to be
> a certain hexi-decimal color, and maybe even gradient,
> will the ETP export carry that formatting?
If it's in a tiddler, then ExportTiddlersPlugin exports that tiddler's
*source* definition. Again, it's all saved as plain text... there is
no *conversion* to any special file format, which is a big help when/
if you manage to "paint yourself into a corner" where your latest
change to the document breaks things so badly that you can't edit
those changes to fix them.
Fortunately, because the TW file stored on disk is plain text, you can
always open it in a text editor (*not* a word processor), then scroll/
search for the "broken" content, and edit/save the file to correct the
problem, so that it can once again be successfully loaded by your
browser.
HTH,