61–70 of 154 posts
Is this itself entirely a webapp? As an aside, I'm amazed the way Mozilla have co-opted the term "Web" to mean whatever they want it to. The way they've branded all sorts of non-standard APIs in FFOS "Web" APIs to confuse people into thinking these are somehow more open than anything else is impressive.
Actually, yes: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...
Is this itself entirely a webapp? As an aside, I'm amazed the way Mozilla have co-opted the term "Web" to mean whatever they want it to. The way they've branded all sorts of non-standard APIs in FFOS "Web" APIs to confuse people into thinking these are somehow more open than anything else is impressive.
> Is this itself entirely a webapp? Actually, yes: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...
That's my point. It's not.
EDIT: ici: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...
Earlier quoted context omitted.
The sad answer is that your co' is what is incorrect. If you have "executives" plural you have the budget in your organization to buy a dev mac and a dev device.
I agree that they're being foolish (though hey, they're the ones paying me to waste my time), but I'm just as peeved at Apple for removing a perfectly-workable self-contained solution in favor of yet more platform lock-in.
Peeved, but not surprised, given their track record.
I've always wondered why developer tools are bundled with browsers. Shouldn't they be available as separate downloads as: 1. Most people use browsers compared to working with them for development, and 2. The additional tools just add to the package size and possibly increased resource usage (if they are running with the rest of the browser)? Thanks in advance for the replies.
Cautionary tale: They were bundled separately for Internet Explorer, and everyone assumed they didn't exist. Even now you can see people complaining that say, "developing for IE 6 was hard because it didn't have developer tools".
> We’re working on a protocol adapter that will allow > clients using the Firefox Remote Debugging Protocol – > including the Developer Tools and WebIDE – talk to all > mobile browsers, regardless of rendering engine or > runtime. Our first targets are Chrome for Android and > Safari on iOS. My company expects all of our internal web applications to function on the executives' iPads, but they refuse to purchase Macs…
Earlier quoted context omitted.
> If Mozilla truly reverse-engineers Apple's remote debugging protocol it would be a godsend for us. Google did this a while ago: https://github.com/google/ios-webkit-debug-proxy It works well for connecting Chrome DevTools to Safari, automating Mobile Safari through ChromeDriver, or hooking up your iOS device to a private instance of WebPageTest.
Thanks, I've never heard of this before and it sounds very useful. ...Or rather, it would be very useful were it not for the fact that it only appears to run on Linux and OS X, whereas my employer-granted computer is running—drumroll, please—Windows XP! And like I said, these are all internal applications, and I don't have the authority to VPN in on any computer that I please. Ah well. Enterprise bureaucracy strikes…
Everything that drives the UI are just functions that could just as easily be invoked from the scratch pad. If you know a bit of javascript you can write a few of your own functions to automate some common browsing tasks. And if you need even more functionality you can dig deeper and write your own libraries that seamlessly integrate into the kernel without a hitch and can be invoked from your own menus.
No plugin tom-foolery or artificial walls around the garden.
Looking forward to seeing how this develops!
Earlier quoted context omitted.
> Is this itself entirely a webapp? Actually, yes: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...
XUL is a web technology now? That's my point. It's not. EDIT: ici: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...
It's neat and all, but please Mozilla, don't include this with Firefox. At the very least, have a separate lean-version that doesn't have this "fluff" included. And a developer/power-user version that includes it. I understand that web-app development is big, and it's the "new-desktop", but that doesn't mean that this awesome browser should include everything and the kitchen sink.