Customizing Opera's "View Source" to Use Homesite - now problematic

[tedster]

This is a change that happened several versions back, but I keep hoping for a change.

I use Opera as my workhorse browser - in short I live there by choice. So it's common for me to find a page online and use "View Source" which I've customized to open the source code in Homesite. That customization is something that Opera offers natively and easily and I've always loved it.

Problem is, these days if Homesite is already open, nothing at all happens when I click "View Source" for an online page -- although a local page opens just fine. When Homesite needs to be opened, then I get a Homesite error message that the file is "not a recognized text document". I can respond to that error message by clicking on "open it anyway".

This means that I must first CLOSE Homesite in order to open the source code of an online page - a time wasting inconvenience. Opera now uses a .tmp file for the source, and I've added that filetype to Homesite's settings - but to no avail. And since Adobe no longer supports Homesite, I can only hope for an Opera change.

Either that or, some kind advice from someone who has resolved this issue.

[penders]

It is a bit of a shame that Opera uses a .tmp file for the source (so editors don't immediately recognise this as an HTML file), but this does work OK with Notepad++ on my machine.

Does this affect other editors on your machine as well? ie. There isn't a problem with where Opera saves this .tmp file and user permissions?!

Do you need to supply any command line parameters in Opera settings?

I can't help but feel that may be this is a problem with Homesite? How did Opera behave previously? Was it simply a case of saving a .html file?

[jdMorgan]

If it's possible, set Homesite as a recognized handler for the .tmp filetype. You can do this by editing the registry or in some cases, by right-clicking a .tmp file and selecting "Open with..."

It should not be necessary to set HomeSite as the default handler, though. I'd prefer to keep Notepad or some other "simple, non-Web-enabled text editor" as the default for those files.

Dunno if this will help, but easy and worth a try...

Jim

[tedster]

Thanks Jim. I did take those steps and Homesite still doesn't recognize the file as legitimate.

I can't help but feel that may be this is a problem with Homesite? How did Opera behave previously? Was it simply a case of saving a .html file?

yes, I also believe it's a Homesite problem, however Adobe has abandoned the software ;(

In the past, I just used Opera's native customization for "View Source" and the cache file ([coded number].html) would open seamlessly.

I don't even mind the one extra click to answer the challenge question when Homesite is opening. However, if it's already open, then View Source does nothing at all.

[penders]

May be you could work around the problem by having an intermediary script that copies Opera's .tmp cache file to a .html file and pass that to Homesite instead, since that appears to be OK with .html files?

Get Opera to call a Windows Batch file instead (eg. C:\Tools\ViewSource.bat)

@ECHO OFF 
REM CALL: C:\Tools\ViewSource.bat tmpcachefile 
REM Copy .tmp cache file passed as arg to .html file and open in favourite editor 
SET HTMLFILE=C:\Tools\temp\viewsource%RANDOM%.html 
COPY %1 %HTMLFILE% 
"C:\Program Files\Notepad++\notepad++.exe" %HTMLFILE% 
EXIT

This at least works with Notepad++, and now it recognises it as an HTML file. A %RANDOM% HTML file is created each time. Remove %RANDOM% to overwrite the same file each time, but that could cause problems with some editors if viewing the source of more than 1 page at a time? I did think about renaming the cache file by appending ".html", but thought that it might mess up Opera's cache?!