This content has been marked as final. Show 3 replies
So long as you make no changes in the toolbar in between, you can do as you suggest for this project only.1 person found this helpful
If you have another project with a slightly different toolbar, you need to make a different substitute file.
For example, if you're putting the Search form in the toolbar and change the width of the text entry box, the output file will be different.
My preference is to alter the newest output file after publishing. If you're not publshing, but copying the !SSL! package directly, you would change the output whtbar.js file in that directory.
If you can't edit files after publishing, you can publish to another location on your hard drive, make your changes and send the new package to its destination. If you have a convenient way to compare the new output package with the old one,
you would send only the changed files.
Here's another chance for me to plug Beyond Compare, a very useful tool in which I have absolutely no financial interest or organizational connection, other than as a user.
It's easy to find on the Web.
Or, one could use ReplaceEm to customize the output files after each regeneration.1 person found this helpful
Thanks for the help. I think I've figured it out. I'll download ReplacEm.