(copied from http://interblah.net/2004/10/22/textmate-web-preview/ )
I have posted some feedback about the Web Preview to the [wiki](http://wiki.macromates.com), along with a [screenshot](http://www.lazyatom.com/media/images/textmate-web- preview.jpg). I'm happy to provide my revised .nib file too.
In summary, and in order of perceived importance, the changes are:
* changed the base font size of the OakWebPreview to 14 - this way it matches at least my setup for Safari and Firefox, and I'm not aware of every having changed the defaults in those apps. Either way, ENSURE that the font sizes are similar, otherwise the preview is pretty much useless. * move, resize, relabel and re-anchor the "Back", "Forward", and "Reload" buttons. The top row of controls is now Back, Forward, URL, Reload. This more closely-matches real browsers. The Reload could be placed to the left of the URL, the important point is that these controls go on top * Remove the window texture - it's unnecessary, and unattractive. This isn't a rant against metal, I like metal, it's just *better* as aqua here. * Resize the "Show Options" checkbox to "small", and place it flush against the bottom of the view. Then Increase the vertical size of the OakWebPreview accordingly.
### Feature Requests
1. Have the web preview always shown, if it has been opened. It should then display whatever is in the selected tab, if the file meets some "web previewable" criteria. If the current tab is showing an html file, or a php file, or a .asp file, change the web preview to it, otherwise, leave it displaying the last file that did match. This will enable a lot of very useful editing, like changing the CSS and having the preview update automagically, as outlined next.
2. Have another option which updates the preview, after whatever delay, if ANY file in the project is changed. This way, I can: * edit an html, open the web preview * check the NEW "update if any file is modified" option on the web preview (a project-persistent option) * switch to the CSS (or JS, whatever) in the project. Note that since CSS/JS aren't "previewable", the web preview window still shows the html file * as changes are made to the file, the web preview is told to update, with whatever delay * now, the consequences of any changes I make to external files are updated automatically in the preview This feature would REALLY kick ass. You know it.
3. Keep the "Base URL" persistent within a single project. Store the base url within that project! This doesn't require a preference, just each time it's manually updated, change the entry in the .tmproj file
None of these features/fixes are very hard, nor can I think of any way that they negatively impair the current workings of TextMate - what are the chances of seeing any of them in 1.0.2?
On 22/10/2004, at 9:55 PM, James Adam wrote:
- changed the base font size of the OakWebPreview to 14 - this way it
matches at least my setup for Safari and Firefox, and I'm not aware of every having changed the defaults in those apps. Either way, ENSURE that the font sizes are similar, otherwise the preview is pretty much useless.
Firefox and Safari and pretty much every other browser ship with 16px -- I'm 99% certain of this. Eventually a preference is planned for you to pick your own I think. When the first betas shipped, it was set to 12, but people complained about it not being like Safari and Firefox, so whatyagonnado?
Can't please everyone until there's a font size preview -- and even if TM were to preview things EXACTLY the way YOU prefer (14px), it's only previewing your Safari/Firefox set-up, not previewing my set-up, or some guy down the road surfing the web on his XBox.
It's a quick and handy HTML preview, not a full-on browser... and isn't that good enough?
Personally, I still use Safari, and don't use TM's web preview at all.
Justin
I do'nt use web preview neither (who still writes static html ??) BUT I would if the web preview could be used as the output of a custom TextMate command. One could the call a script whose output would be well designed html to display a complex error log, for instance.
Dominique PERETTI http://www.lachoseinteractive.net
On 22 oct. 04, at 16:33, Justin French wrote:
On 22/10/2004, at 9:55 PM, James Adam wrote:
- changed the base font size of the OakWebPreview to 14 - this way it
matches at least my setup for Safari and Firefox, and I'm not aware of every having changed the defaults in those apps. Either way, ENSURE that the font sizes are similar, otherwise the preview is pretty much useless.
Firefox and Safari and pretty much every other browser ship with 16px -- I'm 99% certain of this. Eventually a preference is planned for you to pick your own I think. When the first betas shipped, it was set to 12, but people complained about it not being like Safari and Firefox, so whatyagonnado?
Can't please everyone until there's a font size preview -- and even if TM were to preview things EXACTLY the way YOU prefer (14px), it's only previewing your Safari/Firefox set-up, not previewing my set-up, or some guy down the road surfing the web on his XBox.
It's a quick and handy HTML preview, not a full-on browser... and isn't that good enough?
Personally, I still use Safari, and don't use TM's web preview at all.
Justin
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/mailman/listinfo/textmate
On Oct 22, 2004, at 10:13 AM, Dominique Peretti wrote:
I do'nt use web preview neither (who still writes static html ??) BUT I would if the web preview could be used as the output of a custom TextMate command. One could the call a script whose output would be well designed html to display a complex error log, for instance.
Just my opinion but why not let your command do this instead? you could pipe it to safari or end in `open -a Safari /tmp/error_test.html`
While I'm at it .. I would also vote to not put too much development into WebPreview since Safari is only a command-tab + command-R away.... unless there was a feature like SubEthaEdit that did WebPreview in realtime as you type.
k
Dominique PERETTI http://www.lachoseinteractive.net
On 22 oct. 04, at 16:33, Justin French wrote:
On 22/10/2004, at 9:55 PM, James Adam wrote:
- changed the base font size of the OakWebPreview to 14 - this way
it matches at least my setup for Safari and Firefox, and I'm not aware of every having changed the defaults in those apps. Either way, ENSURE that the font sizes are similar, otherwise the preview is pretty much useless.
Firefox and Safari and pretty much every other browser ship with 16px -- I'm 99% certain of this. Eventually a preference is planned for you to pick your own I think. When the first betas shipped, it was set to 12, but people complained about it not being like Safari and Firefox, so whatyagonnado?
Can't please everyone until there's a font size preview -- and even if TM were to preview things EXACTLY the way YOU prefer (14px), it's only previewing your Safari/Firefox set-up, not previewing my set-up, or some guy down the road surfing the web on his XBox.
It's a quick and handy HTML preview, not a full-on browser... and isn't that good enough?
Personally, I still use Safari, and don't use TM's web preview at all.
Justin
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/mailman/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/mailman/listinfo/textmate
I do'nt use web preview neither (who still writes static html ??) BUT I would if the web preview could be used as the output of a custom TextMate command. One could the call a script whose output would be well designed html to display a complex error log, for instance.
Just my opinion but why not let your command do this instead? you could pipe it to safari or end in `open -a Safari /tmp/error_test.html`
I do such a thing currently. I'm just pro the cool factor :-)
While I'm at it .. I would also vote to not put too much development into WebPreview since Safari is only a command-tab + command-R away.... unless there was a feature like SubEthaEdit that did WebPreview in realtime as you type.
But at the same time, I agree with you. There is a lot to be done (the "refresh" bug drives me nuts) right now before the developers should take time for new features (expect maybe the function popup :-) ).
On Oct 22, 2004, at 4:33 AM, Justin French wrote:
On 22/10/2004, at 9:55 PM, James Adam wrote:
- changed the base font size of the OakWebPreview to 14 - this way it
matches at least my setup for Safari and Firefox, and I'm not aware of every having changed the defaults in those apps. Either way, ENSURE that the font sizes are similar, otherwise the preview is pretty much useless.
Firefox and Safari and pretty much every other browser ship with 16px -- I'm 99% certain of this. Eventually a preference is planned for you to pick your own I think. When the first betas shipped, it was set to 12, but people complained about it not being like Safari and Firefox, so whatyagonnado?
While I agree with most of Jame's suggestions for improving web preview (In fact I have a few of my own) I have to side with Justin here. You should leave the Browser default text size alone especially when testing design & accessibility.
-
Dominique Peretti -
Dominique PERETTI -
James Adam -
Justin French -
kumar mcmillan -
Timothy Martens