I am an aspiring software engineer and in doing some studying and development work I have found that it would be very convenient to have a Terminal command which would launch chrome in a new window with the first argument being passed as the URL to launch (or a local HTML file). Is there a way to do this on Mac OSX (I'm on Sierra 10.12.4)? I tried searching but the only guide I found was 5 years old and doesn't seem to work.
Bonus:
It would be even better if we could force the new window to open with the Inspection window already opened showing source code and page structure!
Related
When I was using MacOS 12.5.1, I found out that older version(e.g. 11.3) of Xcodes can't be opened. It's icon became a banned image and can be opened neither by double click nor 'open' cmd in terminal.
So I want to know how to verify Xcode in terminal? Use 'open' cmd is an option but if the target app is available, it will be opened which I don't expect to happen.
I found there is a "Minimum system version" in /Applications/Xcode.app/Contents/Info.plist, but no "Max system version". In my case I wanna to know which older verison of xcode is unavailable on new MacOS. Any help will be appreciated!
Use the excellent Go64 application from St. Clair Software. When you load it and scan, you can then see programs that will not work on your system clearly marked with a strike thru circle:
Recently I developed an application in Xcode using Swift that starts up the Terminal like this and:
open -a /Application/Utilities/Terminal.app /project/run_stack.sh
After exporting the Application and trying to run it I get this message if my Terminal is running already or I have previously started the same command from the same app (the command is executed through a menu item).
ru_stack.sh can’t be opened because Sandbox is not allowed to open documents in Terminal.
Anyone know why this happens ? If I run it on my Mac it works fine and each time a new terminal starts on the call but when I tried the application on my friend's Mac we get that error in the described cases.
I was having the same problem. I ended up setting iTerm2 as the "Open With" application for .sh files and that fixed my issue. https://iterm2.com/
I was rooting around for the answer on StackOverflow to the question above, as I had recently updated to Mac Sierra and by doing so Xcode 7 updated to 8 automatically. I couldn't find the answer to what I wanted, so I decided to share my findings.
Of course I'm not quite ready to invest the time just yet in Swift 3.0 so I wanted to know how to keep two instances of Xcode on my machine for the time being.
Therefore below is how I went about doing this...
Login to Apple Developer Downloads and find Xcode 7.3.1 or equivalent version of what you want to maintain on your machine.
Download the file and double click on it to open the installer
DON'T drag it across to Applications just yet
Instead, open a Finder Window and drag it to Desktop/Downloads, to install it there
Control-click on the Xcode file to "Get Info"
Under Name & Extension, in the text field, change this from Xcode.app to Xcode7.app (or equivalent naming convention)
Drag this renamed file into Applications
Restart Mac
Open Xcode7 (or new & renamed application)
Voila! 2 x instances of Xcode on your Mac (Xcode proper & Xcode7)
I gather you should never open both apps at the same time. However here is a solution that really does help you if you are still currently developing in two apps or environments on different versions of Swift. Hope this helps.
I'm experiencing an issue with a Qt app on Mac OS X 10.10.5, whereby a QFileDialog will not close properly when canceled. While this may be a bug in Qt, I only see this bug when running the app as a normal user would, e.g. opening it in the Finder (or via command line open). If I launch the app via Xcode or by calling the binary directly, there is no issue.
Launch the app via calling the binary directly on the command line or within Xcode, e.g. ./MyApp.app/Contents/MacOS/MyApp
Launch the app via the Finder or open, e.g. open ./MyApp.app
What are the differences between these two methods - and how does it impact a running application?
The major difference is the working folder. You don't have any control over what it is, but it will be different between the two invocations.
What directory are you showing the QFileDialog in? You should probably start in a well-defined place, like the user's home.
We have an Adobe AIR app, which was created by a 3rd party contractor, that we have been using successfully on Windows. The application runs full screen automatically and, for the most part, primarily is chrome for displaying some web pages.
On windows, it works perfectly. Only now, 9 months after development, has someone asked to try to run it on a Mac. We figured it would work since AIR is cross platform. It installs just fine (latest AIR SDK on OSX Lion). When we run the app, it launches but only shows the name of the app next to the Apple symbol in the upper left. No window or other chrome appears on the screen. I can Quit the app from the menu, but not much else.
Any thoughts as to why it's behaving this way on the Mac and not Windows? We do not have access to the original developer, and I am not a Flash/Flex person, but I do have the source and a copy of Flash Builder 4, so I could make basic tweaks. Any pointers would be very appreciated.
Have you tried to call maximize() after creation complete? I had the same problem (main window not showing up on Mac OS, everything is fine on Windows). Hope this helps.