I haven't done exactly what you're referring to, but years ago I wrote my
own set of minifiers (in AppleScript/BBEdit frankencode) for HTML, CSS, and
JS, so I've thought about the logistics of using it. Right now I have to
trigger the minimizer scripts manually, either on files one at a time that
are open in BBEdit (from its Scripts menu, with a Save As...) or else in
Finder by dropping whole folders on the batch-application versions that I
also created. I end up with two of each file locally, which sounds like
your goal, but I dislike that. Alternatively I run the compressions
remotely by opening files one at a time off the online/live server directly
into BBEdit, triggering my script, then re-saving up to the server. Still
clumsy.

It seems to me that the best thing would be *not* to save separate
minimized versions locally, which gets cluttered really fast, and not to
trigger the minimization manually at all, but rather to minimize the files
*automatically*, *on-the-fly* when uploading from the local-dev server to
the online-live server. If that were possible, you'd always have just one
devel (full) version locally, and one live (minimized) version on the live
server.

Some programs, I've read, are "attachable" -- I think that means they can
run an AppleScript automatically by piggy-backing it onto another standard
menu command (like "Upload to Server" or whatever). However, I doubt that I
could set that up in Yummy FTP (I'm not sure), and I don't know how to
attach an AppleScript to be triggered by a regular menu command in BBEdit
either.

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to