Between different Macs plugin works and doesn't work

[slbaumgartner]

@mwm5053 said:

I double checked the terminal and retyped and restated SU still no right click web inspector?

Missed it again! You typed com.google.sketchup8pro, it should be com.google.sketchuppro8

Steve

[mwm5053]

[mwm5053]

I don't understand why right click won't bring up Inspect Element?

---

[slbaumgartner]

@mwm5053 said:

I don't understand why right click won't bring up Inspect Element?

Still typing the command wrong!

defaults write com.google.sketchuppro8 WebKitDeveloperExtras -bool true
^ ^
t space between Extras and -bool

[edit] Ack, that didn't format right! You left the t out of Extras and attached the - to its end instead of to the front of -bool.

[mwm5053]

Ya not a very good typist sorry is this right

---

[slbaumgartner]

@mwm5053 said:

Ya not a very good typist sorry is this right

That appears to be right. Did it work?

I'm turning in for the night in a minute. Will check back tomorrow.

Steve

[mwm5053]

still no inspect element on right click

[mwm5053]

Ok this AM I had Safari open with Inspect Element open on a web page just to see what it did and opened SU and clicked on Web Dialog Test and right clicked on Connect to Website and Web Inspector popped up with this. Now what? I'll be here for a while then off to work for the day will check back.

Walt

---

[slbaumgartner]

@mwm5053 said:

Ok this AM I had Safari open with Inspect Element open on a web page just to see what it did and opened SU and clicked on Web Dialog Test and right clicked on Connect to Website and Web Inspector popped up with this. Now what? I'll be here for a while then off to work for the day will check back.

Walt

That's more like it! I wonder what was wrong before...

Anyway, click on the console button and show me what it displays then. In particular, if there are any warning or error messages. The little red symbol at the bottom makes me think there was a error reported.

Steve

[mwm5053]

Evidently Inspect needs to open in Safari eo get Web Inp. to popup but here it is.

---

[slbaumgartner]

@mwm5053 said:

Evidently Inspect needs to open in Safari eo get Web Inp. to popup but here it is.

OK! My cross-domain security theory confirmed!

What's happening is that when the html is loaded directly, the document's domain is empty (null). The XMLHttpRequest security won't allow load from some other domain. I can verify that the domain is also empty on my Mavericks box, so this implies that they added a special case for null domain in the security rules after the WebKit version that comes with Lion (or perhaps modified the domain to be an empty string instead of null).

Steve

[edit] The typeof document.domain on my Mavericks box is a string, "". They fixed it so that a locally loaded html gets an empty string domain instead of null.

[slbaumgartner]

Garry,

To fix this you will either need to load the html from your site instead of from Ruby (so the document's domain is your domain) or try the xml content technique described in the reference I posted previously (which requires some server settings as well). Your code can make the domain less specific (e.g. strip www off http://www.cabmaker32.com), but it cannot make it more specific (e.g. change the null to anything else).

Steve

[Garry K]

Steve,

I'm not sure where to go next. I really don't want to have to load the html page from the server. But then I don't currently know how to do that.

The hosting company that I use doesn't provide SSL unless I double my yearly payments. It is a WordPress site.

My StairMaker_service.php is pretty simple. I do use JSON format. Currently I use the following to read the http POST coming from web dialog

$raw = file_get_contents( "php://input" );
$json = json_decode( $raw, true );

// Then I do a bunch of validation, cleaning, testing etc.

I use echo to send the information back to the web dialog.

[slbaumgartner]

@Garry - You don't need SSL to address this. If you read the link I sent, there are ways to do it via javascript and server-side php. But if you don't want to do that, perhaps it would be enough just to trap the error and inform people that you don't support pre-10.8 versions of Mac OS X.

@Walt, could you try the attached version and see if it pops up an alert about the error? I just added an error handler to the javascript, but since I don't get the error I don't know whether it works Thanks

Steve

---

dialog_test.rb

[jeff hammond]

@garry k said:

I'm not sure where to go next.

next is telling walt to get rid of that 1,1 macpro*.. save up for a new mac pro.. they're super sweet.. and they run mavericks

(just kidding @walt)
*(I'm guessing as to why he's on lion but this is the reason i have lion on one of my computers)

[Garry K]

Jeff,

I've been reading that Mavericks 10.9 is a free upgrade to Lion 10.8.
If this is indeed true what is stopping you from upgrading?

[jeff hammond]

@garry k said:

Jeff,

I've been reading that Mavericks 10.9 is a free upgrade to Lion 10.8.
If this is indeed true what is stopping you from upgrading?

the early mac pros (2006) aren't supported by mavericks (or 10.8 mountain lion).. they top out at lion 10.7.5..

apple is less likely to support older hardware.. once they make a decision to move forward, they'll do so.. in general, you're looking at approx 5 years before your mac won't be able to upgrade to a new OS.. so roughly 8 year max life span if you want to keep your applications up to date.

@unknownuser said:

There are two things that prevent 10.8 from installing on a MacPro 1,1. The first is the lack of EFI64. Mountain Lion as has no support for 32bit kernel and extensions so it will not boot. This is true of many early Intel macs… The other thing is that checks are made by the installer; against a supported machines list. If your mac isn’t on the list, it refuses to install.

[mwm5053]

@slbaumgartner a couple screen shots

@ Jeff don't I wish I drool every time I go to Apple .com

---

---

[slbaumgartner]

So the Alert shows that it caught the error, but evidently I don't know how to read out the message. BTW, I added that "Hello!" just because a blank dialog leaves me wondering if anything happened.

Steve