i am using Netbeans PHP + Firefox 4 on Windows for my web development.
I've used a common firebug extension called Xrefresh. It was automaticlly refreshing my opened firefox tab everytime change in my projects directory occured, so pressing ctrl+s in netbeans was triggering auto-refresh in the browser. Very comfort way to work with css, almost live preview.
But now since new Firefox and Firebug versions Xrefresh doesn't work anymore and the question is - are therey any good alternatives, or does someone know how to configure Xrefresh now?
Without live preview my development is somehow slower.
https://github.com/NV/auto_update_stylesheets
This could help you. It refreshes the page via ajax on css save.
There's an automatic refresh-on-change tool for IE. It's called ReloadIt, and is available at http://reloadit.codeplex.com . Free.
Not an add-on to IE, but more of an "adjunct". It does not change the IE install, does not install a BHO or anything like that. So very low-impact installation.
You choose a URL that you'd like to auto-reload, and specify one or more directory paths to monitor for changes. Press F12 to start monitoring.
After you set it, minimize it. Then edit your content files. When you save, the page gets reloaded. like this:
I've managed to keep using xrefresh up until Firefox 9 however I'm not having any luck with version 10.
I've now switched to livereload, they've had a decent Mac version out for a while and a very experimental Windows version has recently been released.
Related
As the title says,
I see it is possible to debug a Meteor application in Webstorm but I can't figure out how to do the debug directly on Chrome DevTools
You can debug the client code using Chrome DevTools by just opening Chrome DevTools while viewing localhost:3000.
I'm not aware of a way to use Chrome DevTools for server-side debugging, but you can debug from Chrome via Node Inspector. For details, type meteor help debug and follow the directions.
To get into CDT, mash F12 in the browser window.
Then, you can select the "Sources" tab, followed by the .js file you want to inspect, and at a breakpoint by clicking on the line of code you're currently interested in. e.g., this screamshot shows a breakpoint in a template's "events" section:
As you can see, there are many other tools CDT allows you; poke around, experiment, research, and you will find a wealth of valuable insight.
Besides Chrome, Firefox also has good debugging tools, and probably most other browsers, too, including Microsoft's new Edge browser. AFAIK, they are all invoked via F12.
Ok, so here is the issue we are having. We have a website that uses a DevExpress callback panel. We have gotten calls from users using IE10 that the page is blank.
I setup a machine with IE10 - to try and replicate the problem. When logging into the production website, I saw the same thing – the page is blank, except that you can see an empty SpitterControl up in the top left corner (indicating a control with nothing in it). I checked the f12 developer tools, all of the markup is there. Also, when going to quirks mode, or IE9 mode, page renders fine.
So good so far. The next step is to replicate the issue in my local environment so I can throw in some breakpoints and try to find the cause. Here is where I am stumped. Local dev environment no issue at all; Page renders fine in IE10. I am running IIS7 on my machine with the same .NET framework.
So, on to the next step. We have a machine where we stage code for beta testing – its configuration basically mirrors the production configuration. Same result, all IE10 pages rendered just fine.
I have kind of run out of ideas. I have of course researched the doctype, and forcing the IE9 mode. All things that I could try, but I just puzzled by the fact that all of my testing environments I could not get it to break.
Any thoughts?
Try setting up an offsite dev setup. It could be that within your domain. I know that in one case we had problems with devexpress controls loading out of order.
Figured it out - well work around anyways. Setting the worked. It just wasn't so simple to just make a change like that to the production database - but I finally got it in there to try it. Jeez.. what a pain!
The NuGet package option from this link worked for me so I assume that installing the hotfix on the server would also work:
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
SUMMARY:
Make sure you have NuGet installed
Right click on project then click on Manage NuGet packages
Search Online for "App_BrowsersUpdate"
I installed the one for .net 4
Republish
I was running my application from Flash Builder 4.5.1 without any issues. (It is a Flex application that connects to .Net Web Services). However, something has changed recently in my configuration or project, because when I try to run the app with the play or debug button, I just get a grey screen. I can't even stop on any breakpoints.
Eventually (maybe 30 seconds), a message pops up like so: 'The Flash Builer failed to connect to the running application. Please make sure that you are running the debug version of Flash Player...'
I definitely have latest version of Flash Debug Player installed (11.1.102.55). I have tried uninstalling it and re-installing it.
I have tried cleaning and rebuilding my project.
I have tried switching to a different workspace and back again.
I have tried restarting the PC.
I am using the latest version of IE for testing.
I'm really stumped - has anybody got any ideas on how to solve this?
Thanks
Have you tried deleting the html-template folder? This has caused issues for me in the past.
After it's deleted, when you try to build you will have a compiler error/warning about the missing folder. Right click and 'rebuild'.
There are some issues with compatability between 64 bit IE9, the 64-bit flash player, and 32-bit debugger. It seems like flash builder gets confused on which to use. I haven't seen any decent resolution yet in the Adobe forums for this particular issue other than use a different browser for testing.
To switch browsers, go to Window > Preferences... > General > Web Browser in Flash Builder. Select Firefox or Chrome.
In order to use Firefox, you need the Flash Debugger for Netscape compatable browsers installed. You can get that from Adobe here.
To use Chrome, you need to replace the built in flash player that is installed with Chrome with the debug player. Instructions from Adobe are here.
How to save firebug changes using Eclipse (Windows)?
I found here that it's possible to save firebug changes if we use Eclipse and FireEclipse
Is anyone using this combination successfully? Can anyone explain the step of Installing?
I'm on Windows7 64 bit
And if FireEclipse works with Eclipse then Will it also work with Aptana port of Eclipse?
First, whether it will work on Aptana? Yes, it should.
Now to the main question: The Fireclipse site claims contrary to what the answer you have linked to cites: the FE site claims that it mainly helps in debugging javascript through Firebug and Eclipse consoles (nothing about exporting/saving CSS changes).
Also, I wouldn't really recommend going with this plugin 'coz it hasn't been updated in a while. According to SourceForge (where the source of this project is hosted), Fireclipse was last updated 2008-10-22. Unless, you are still using Firefox 2 and Eclipse 3.2, you should avoid this plugin.
Try some of the other tools listed in that thread, for example, FireDiff sounds promising.
This is how i save my firebug changes.
https://addons.mozilla.org/en-US/firefox/addon/firediff/
Hope this helps.
im using Qwebkit and every time im loading youtube , its asking me to download the latest
flash player plugin , even so i already installed the plugin and i can see youtube videos
in firefox and explorer very well
what is the deal with Qwebkit and Flash plagin ?
There is a way of doing it. Qt in windows doesn't use by default the flash plugin even if you have installed it for firefox. The solution is to manually copy the plugin dll into your compiled application directory (I mean in the same directory than the executable is installed).
I did it more than a year ago so I'm not totally sure if it has to be directly in the directory or under a folder called plugins. Try both and one of them should work.
The flash plugin dll should be in your firefox directory, if not do a search in google and there are several pages in which you can download it.
You also need to activate plug-ins support for QWebView. I think that was done in the pro file, but I have been doing some research and it maybe done changing the web settings:
websettings.setAttribute(QtWebKit.QWebSettings.PluginsEnabled,True)
Go to adobe.com and download the plugin for Other Browsers (Firefox, Safari, Opera), and re-install...
Just to report on my experience of enabling flash in QWebKit, do the following:
download firefox and install flash player for firefox,
enable plug-ins in QWebKit (QWebSettings::globalSettings()->setAttribute(QWebSettings::PluginsEnabled, true);)
then recompile your Qt Application.
Now flash should work fine.
Your problem is very simple to solve. Just add the following lines to your code:
QWebSettings *defaultSettings = QWebSettings::globalSettings();
defaultSettings->setAttribute(QWebSettings::JavascriptEnabled, true);
defaultSettings->setAttribute(QWebSettings::PluginsEnabled, true);