I am currently running 3.0.2 and looking into upgrading to 4.0.3. If we do go forward with the upgrade, will I have to go into all of the html and change the calls i currently have for the icons?
Thanks
You shouldn't have to, but there might only be small changes to continue using font awesome.
There were some pretty significant changes from 3.x to 4.x.
The biggest change is that, instead of being icon-*, everything is now fa fa-*. (2 CSS classes - this is because it makes things easier on the CSS engine, enough to make a noticeable improvement in page rendering times.) However, there were also a number of renames and other small changes.
Full migration guide is available at https://github.com/FortAwesome/Font-Awesome/wiki/Upgrading-from-3.2.1-to-4
Related
I'm trying to target .NET 6 for my WPF app, but because I'm using RX.net, the highest I can go is net5.0-windows10.0.19041. One example is that ObserveOnDispatcher() is not available when I'm targeting net6.0-windows, which my app makes heavy use of.
Does anybody know either A) when a .NET 6 version of RX.NET will be released, or B) any workarounds for ObserveOnDispatcher() or ObserveOn(DispatcherScheduler.Current.Dispatcher) on .NET 6?
Thanks
A relatively painless way I found was to simply add the ReactiveUI.WPF package to my WPF projects. This allowed me to advance to net6.0-windows, and also to use DispatcherScheduler. I am not using anything from ReactiveUI library, so this is technically a hack, but took 5 minutes of my time and added only a few hundred kilobytes added to the shipped binaries, so it was worth it for me to be able to move on from previously being held back on net5.0-windows10.0.19041 because of RX.
If I had more time and skill I would dig into how the ReactiveUI.WPF source code achieved this desired effect, and apply this to my own source code... maybe someone has a more elegant, non-hack solution.
This will be fixed in v5.1
https://github.com/dotnet/reactive/pull/1660
You could try the nightly builds as per the readme.
https://github.com/dotnet/reactive#get-nightly-builds
It is this sad moment to a developer's life that he has to maintain and fix legacy code... In my case I have to deal with a modified (core scripts) tinyMCE 3.2.2 which I have to update to the latest version in order to play in IE9+...
So my question is if there is a way to check which files have been changed since version 3.2.2 and try to update only those cause it is an overkill to check all the code for the modifications...
Thanks in advance
I fear there are so many changes in so many files that most of them have changed since then and in order to work with IE9.
If possible you should never ever modify the core code. Instead use custom plugins if possible.
I am using Firefox with Firebug, and came to a point where I have a more mature version of my page that has more features, but apparently one feature has gone bad, and I have an earlier version in which it works, but is way behind.
I was thinking that I may make use of dumping the DOM of both versions and compare them,
how can I do that ?
Thanks !
I've got Eclipse 3.6 + eclim set up and working for PHP and JavaScript.
As I'm slowly moving away from the Flash IDE for my actionscript projects I've sucessfully installed the — limited but working — axdt plugin for Eclipse but eclim doesn't seem to work for actionscript files.
Neither FDT nor Flash Builder nor asdt/axdt being listed anywhere on eclim's site I think as3 is not supported by eclim. Am I Right?
As of now, vrapper is helping me a lot, but is there a workaround — other than buying Flash Builder/FDT/IntelliJ IDEA Ultimate — to this situation ?
Thanks.
Sounds like you are a Linux user, otherwise you would surely know about FlashDevelop (it's experimental now, but you should be able, to an extent, to run it through Wine, too...).
Other than that, I used this for some time and it was OK for what I needed. It has some problems on top of some problems the original has, some features entirely removed, but it's still better then AXDT.
Here are some other suggestions about AS3 editor on Linux: http://flashdevelop.org/community/viewtopic.php?f=9&t=3973 . Unfortunately, they are not as good as commercial solutions for Win / Mac.
I am currently involve in developing projects on MODx Revolution. I like this system, it fast and great, but what really annoying is manager interface. It works really slow. Every single action require ExtJs panels refreshing. Is there any way to change this behavior or roll back to Evolution interface?
Thank you!
AFAIK you cannot change it (without modifying the core), and Revolution is a complete rewrite so there is no way you can use the old manager with the new core.
It shouldn't be so slow..
Make sure you're not using Firefox with Firebug on, while using the manager. Also, try a different browser.
Revolution's manager does have it's pros and cons, but if you take a quick look at the changelogs until the current RC3, you'll see they are still activly developing the manager interface..