I would have to agree on the visibility thing.

 

Though not a Mac person myself, I can see how your setup could become
annoying quickly.  Can the Google Chrome "IE Tab" extension be run on a Mac?
Seems like probably not, depending on how they've done it.  Worth a look
though.

 

I'd suggest a Chrome/Firefox compatible version isn't too far away...

 

Richard.

 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Craig Plummer
Sent: Thursday, 19 April 2012 12:26 AM
To: [email protected]
Subject: Re: Red Dot Management Server and IE9 incompatibility

 

Hi Richard,

Thanks for the response, I didn't realise there was ActiveX used as we
disabled those features in our setup.

I think my personal feeling is that OpenText are slow to keep up with the
latest developments in technology, I know they are trying to make things
better now but they have a hell of a lot of catching up to do. As our team
are moving more over towards Macs as our development, as it is a better
platform for us for the non CMS development work we do it is frustrating to
have to boot a VM just to edit some settings in the CMS. Especially when we
work hard to make sure all our custom built applications work across all
platforms.

The poor communication from OpenText about this issue hasn't helped either,
with them saying IE9 support is coming in a particular update and then it
not materialising with no explanation.

Regards,
Craig

On Wednesday, 18 April 2012 14:44:39 UTC+1, Richard Hauer (5 Limes) wrote:

Hi Craig,

 

There are certainly elements of SmartEdit that utilise ActiveX components
including the Word editor integration, inline editing and drag and drop
functions.  Remember that this interface was built when IE6 was the browser
king with over 90% utilisation.  It also delivered a number of JavaScript
enhancements over rival browsers of the day (hence its popularity at the
time) but, as there were few properly established standards, Microsoft took
a number of liberties in attempting to influence the overall direction of
JavaScript; many of these did not stick.

 

SmartTree uses JavaScript that works in IE8 because of its legacy support
for the not very modern JavaScript constructs used heavily by RedDot, but as
Microsoft succumbed to industry pressure to drop support for vendor-specific
'enhancements' in favour of supporting ECMA standards-compliant behaviour in
IE9 much of the UI because a bit broken.

 

I think OT have found it difficult to justify the cost that a ground-up
rebuild of the SmartEdit and SmartTree UI would involve as IE8 is still very
widely adopted and supported, but as time goes on this is less and less the
case.

 

V11 presents a ground-up rebuild of the back-end technology stack for the
'RedDot' products and I think it's reasonable that the front-end will
receive similar treatment in the not too distant future (I have it on good
authority actually).

 

Note that under MS policy, once IE10 is released support for IE7 will be
stopped and IE8 becomes end-of-life, making it inevitable that organisations
upgrade their browsers.  It's impossible that OT don't update their browser
support at that time or they face the likelihood of being impossible to
implement.

 

Rgds,

Richard.

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Craig Plummer
Sent: Wednesday, 18 April 2012 9:11 PM
To: [email protected]
Subject: Re: Red Dot Management Server and IE9 incompatibility

 

I think it was just poorly coded in the first place, I don't think there is
anything that would require IE for it to work. I don't think it makes use of
Active X as I have never been asked to install any components. It just
wasn't written in a standards compliant way, which is likely why it doesn't
work in IE9 unless you turn on compatibility mode.

It gets asked in almost every webinar when it will work with other browsers,
but an excuse is always made. I think the latest was they would rewrite it
to work in all browsers after IE10 is released, but considering that IE9 has
been out a year and was in beta for about 6 months before that and OpenText
still don't fully support it I think it is unlikely it will ever change.

Craig

On Tuesday, 17 April 2012 22:19:47 UTC+1, Tony Chung wrote:

On Tue, Apr 17, 2012 at 1:57 PM, Ibrahim Sawadogo <[email protected]>
wrote:
> The best browser for reddot is ie8.
>

I find it curious that the reddot/OpenText CMS deliberately limits the
compatibility of the administration interface to such antiquated
browsers. I don't see how much of a part ActiveX plays in Smart Tree,
for example, or whether those features would be missed if they were
replaced by something coded in pure JavaScript.

-Tony

-- 
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/reddot-cms-users/-/sqdt7cHTQSEJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/reddot-cms-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/reddot-cms-users/-/n1mYjREbVM8J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/reddot-cms-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en.

Reply via email to