I have Netbeans 6.9.1 and I want to change the default browser to Chrome. I have seen a thread that says for Netbeans 6.5, it can be configured from Tools > Options > General but the problem is I can't find Options in my Tools tab because I am not using that version. Anyone know how to do this with Netbeans 6.9.1?
In the file C:\Program Files\NetBeans 6.8\etc\netbeans.conf, add the following line to the netbeans_default_options properties:
-J-Dorg.netbeans.modules.extbrowser.UseDesktopBrowse=true
Then set Chrome as the default browser.
Alternative method (tried this with Netbeans 7.1):
Open Tools > Options and you should see this:
Click the edit button. Then click on the add button. A new browser named "External Browser" will be shown. You can rename it to Chrome, then change the "Process" field to a path like this:
C:\Users\{User}\AppData\Local\Google\Chrome\Application\chrome.exe (on
my Windows 7)
In your case, you can right click on the Chrome icon and select the properties option (windows) and see where is the target path.
In case someone came across the same problem for Netbeans 8.2:
it is under
Run> Set Project Browser > Chrome
(You can choose other browsers of course!)
Related
When starting Chrome with Selenium, it opens up a new version of the browser.
No history, no bookmarks and default settings as if it just got installed.
Is there a way to open a new version of Chrome like Selenium does, without using Selenium?
I already know about incognito mode or profiles. I searched online but can't anything.
Thanks for your help
The easiest way,
On the top right corner beside the kebab menu click on the profile pic. Then click on Guest option in the bottom of the drop down menu. It will open a fresh profile for you to use.
You can open chrome with different profile using command line switch. But you have to specify the directory and if you use the same directory it will use the same profile. Change the directory from the following to your liking.
start chrome --user-data-dir=C:\tempdir\
Reproduce the problem:
Create an any html file and launch it in Google Chrome. The URL will be like "file:///C:/test.htm" in the address bar.
Right click on the page --> Choose "Inspect"
Try to click the "Add new style rule" icon for any elements, it won't work. The newly added style rule will disappear on the panel when trying to edit it.
If using the URL of "http://localhost/test.htm" to open the webpage in Chrome, "Add new style rule" works perfectly. The issue has started exist since upgrading to Chrome 64. It used to work very well for this feature.
Tested in many other computers, all got the same problem.
the only solution (for now) for fixing this issue is to install the previews version 63 of chrome and stop the chrome from auto update on windows 10
download chrome older version from here:
https://www.slimjet.com/chrome/google-chrome-old-version.php
and a guide to stop chrome from auto update in windows 10:
https://www.technobezz.com/disable-google-chrome-auto-update-in-windows-10/
also report this issue in the google chrome "about section" in settings.
waiting to the the next version to check if the issue is fixed...
As you probably know, Chrome Dev Tools has the same icon as browser itself. In order, to increase productivity I would like to change it's icon, so it will be easier to find it in the taskbar.
Thanks in advance.
Give this a try:
Open up Chrome and then open up developer tools in another window so that you have two Chrome icons on your taskbar. Right click the devtools one and Pin to taskbar.
Right click on the newly pinned icon, right click on Google Chrome (2) and properties.
Under Shortcut->Change Icon, pick something else. Then 'OK' out.
You'll need to restart explorer.exe, so open Windows Task manager, kill explorer.exe and restart it.
You'll now see two different icons.
Do this: Start regular Chrome. Then CTRL+Shift+i and it should open devtools as the new icon.
Unfortunately, clicking the devtools icon initially will not open devtools on startup. Supposedly you can change the properties to start using chrome.exe --args --auto-open-devtools-for-tabs but I was unable to make that work.
YMMV with your operating system but this works with Windows 7. Hope that helps.
Note: If you're using Windows 10, you won't see explorer in the task manager by default, you have to click "More details" on the bottom and switch to the "Details" tab.
Alternatively, open PowerShell and type:
Get-Process explorer -ErrorAction SilentlyContinue | Stop-Process
This will kill explorer, and windows will automatically restart it
This answer may be a nice work around for non-Windows users who are debugging from Visual Studio Code. It uses Chrome's Canary build for debugging. It has a different icon so telling it apart from regular Chrome should be easy.
This answer talks about setting the executable to Canary which is easily distinguishable from regular Chrome. You will need to download the Canary version of Chrome first.
settings.json:
"runtimeExecutable": "canary"
How to configure Visual Studio Code debugger to use Chrome Canary?
I have successfully installed both netbeans and the chrome extension for doing html/css/js work. It appears to work for the most part but I've seen some questionable activity that is... "limiting".
Netbeans > Chrome seems like a fragile interaction. In netbeans, I select run file, and the page opens in chrome always in a new window (is that right?). Part of the marketing here is that you're supposed to be able to edit the css without having to constantly go to the browser and reload. But in netbeans, when I go to the tab of the css file (in the same project), the chrome page bombs with the Dead Folder icon and the text "Something went wrong while displaying this webpage".
What's supposed to be the process here? It seems to work in principle, but not in practice.
[update]
I had also had the addon problem that if I did Run Main Project while looking at the css file, it would show the css file as if it were the main html file. After setting chrome as the default browser, this action shows the actual main html file. At that point, making any change to the css file, any typing at all, will bomb the chrome page.
Take a look at this tutorial.
Once you run a page/project in Chrome with NetBeans integration, in NetBeans there is a window CSS Styles and slightly different Navigator (in 7.3). Now in browser you can start Inspect mode (for instance right click on NetBeans logo in omnibar and check "Inspect in NetBeans mode") and then you can for instance click on elements in browser and if you do that, the CSS Styles window in IDE shows all css properties and rules applied to selected element. You can edit CSS from either CSS Styles or by plain old editing of CSS file in NetBeans. In both cases, changes are visible in Chrome without any reload (without even saving the css file). And you can also use JavaScript debugger in NetBeans.
I don't know what do you mean by "chrome page bombs", but page cannot be debugged by 2 "debuggers" at the same time in Chrome - so you can either use NetBeans or Chrome Developer tools.
There are many new features in the upcoming NetBeans 7.4 (you can download 7.4 Beta from netbeans.org). You can try it as well.
Is there a way for me to get Google Chrome to launch in Aptana?
I tried adding it under Web Browsers but when launching the webpage, from Aptana, it launches it in Firefox instead.
Selecting Default system browser doesn't work either.
How I would do it is where the green > button is, at the top (next to debug), go into run configuration and add a new entry for google chrome.
The path for chromes exe is at (Win7)
C:\Users\USERNAME\AppData\Local\Google\Chrome\Application\chrome.exe
WinXP
C:\Documents and Settings\<username>\Local Settings\Application\chrome.exe
Then you can run that straight from the drop down menu. This is the way I do it, however it may not be applicable for your situation.
I added Chrome to the Run Configurations ...
I deleted Firefox from the General > Web Browser settings.
I restarted Aptana Studio 3 and now, when I click on the green arrow run button, Chrome is the browser.
Say hello to F12 and debugging HTML and JavaScript with ease.
I have Windows 7 and followed the advice listed above for the 'green button'. For Chrome, my file path was "C:\Users\user name\AppData\Local\Google\Chrome\Application\chrome.exe". It was very simple and worked beautifully. Thank you.
rickyduck's answer applies but the path to Chrome may have changed in newer versions to :
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
That's the path I had to use.
rickyduck's answer is exactly what I have been looking for! Thanks Ricky!
To get the exact path to chrome on your machine, just go to your start menu, type in chrome and when it comes up, right click on it and select the Shortcut tab to copy the target path and paste right into Aptana.
Another way to directly launch chrome upon pressing green button is to delete other browsers from run -> run configuration -> web browser . . . and leave chrome alone . . if you want other browsers you can add later on . .
You can add as many browsers as you want. Click on Run -> Run Configurations then right-click on Web Browser in the left nav pane, then select New. Use the Browse button to get the application path then at the top of the dialog, type in a descriptive name. Click Apply and Close. You now have more than one browser to choose from for testing.
I added Chrome to run configurations, and deleted Firefox and IE, also changed likewise under General Web Browsers. The Chrome tab doesn't show up on Green dropdown. If I exit program and restart, the Firefox and IE are back again, but still now Chrome.
Click the tiny black arrow thats looks at the bottom and is located at the top, next to the green Run button:
Choose Run Configurations and then you should see a Browser executable field, under the Web Browser tab:
where you want to click Browse, navigate to the Google Chrome executable (at my Max OS X at El capitan: Applications -> Google Chrome) and double click on it.
Then, click Apply (in the Run Configurations window). Then Run.
That's it! :)
Tested with Aptana Studio 3, installed like this on Mac.