eric_h - Thursday, May 5, 2011 4:46 PM:
I think I read some chatter about people integrating with Firefox (well, tying IE into a FF tab) via the IE Tab extension. It looks like the current development is happening on IE Tab 2:
To make it work, I need to access the login via the direct URL, which in my case was something like this (it didn't seem to want to resolve from just */InnovatorServer):
- http://[SERVER]/InnovatorServer/Client/scripts/Innovator.aspx
Also, you can configure IE Tab 2 for what URLs to automatically open in IE inside a FF tab. I have just gotten this to work, and noticed a few funny things, but am trying different settings to see what works best. I like how it opens new windows in a new tab (e.g. opening a part or change object, or structure browser in a tab).
I wanted to put this out there for anyone that might find it useful, but since I also know others have done stuff like this, are there any tips or gotchas to be aware of? Are there better solutions to be had?
Thanks,
Eric
[email protected] - Thursday, August 4, 2011 7:44 AM:
I had used this extension and opted for IE9 setting
working fine for me
One question :- Do we require to configure sdns.exe on clients or not.
regards,
Diinesh
Ronan - Thursday, August 4, 2011 10:06 AM:
Hello Dinesh,
Yes, running sdns is still necessary in this case. IETab is just a wrapper that puts an IE frame inside Firefox's UI, so the rendering engine is still IE, and you still have to to the usual IE housekeeping :)
?
Ronan Jouchet - PLM Consultant, Processia Solutions
eric_h - Thursday, August 18, 2011 11:16 AM:
Hi Dinesh,
It is probably not necessary for me to reply here but maybe I can add some info. What Ronan said is correct. You are really just running IE wrapped inside a Firefox tab. I have actually stepped back away from this practice and have been running direct in IE just like our users are/will be doing. I found occasionally some stability issues with using the IE Tab 2 solution, though nothing too major. I just figured it would be best to use IE native and customize for that case.
Some of the stuff I did was increase the default tear-off window size since we all have large monitors. I also changed the body background color to create some contrast, changed the label font, altered some other fonts via body css and changed some other css properties. Basically I have been trying to improve user experience through subtle changes working within the framework. I suppose one could debate what is the best way to present the data, but the main thing is to keep the focus on the data because that is where the value is. So I suppose this is all a value judgment, but for now I like what I have better than the current out-of-box styling. There are a few things that I cannot yet seem to change (mostly related to the .NET controls), but maybe in time if it is possible. My current iteration looks like this if you are curious:
Anyway, there is a lot you can tweak to make things more to your liking. I think the main reason I posted was to add that I have changed course myself since my original post and am running Aras in IE native now for reasons explained. Even if you run in an FF tab, IE must be locally installed.
Eric
