Help!
My supervisor asked me to migrate all the (and it’s a big “ALL”) information about Indico, currently in my personal wiki, to the new official Indico Wiki. Great! I love to see things documented, and adding information to the project wiki is a pleasure for me…
However, the Indico Wiki works on the MS Sharepoint platform. And… guess what? In 2007, this Sharepoint cr*p comes with a rich text editor that only works under Internet Explorer.
Yes, son… no IE, no editor… so, if you are persistent and still want to run Firefox (or simply if you use Linux), you are condemned to edit your wiki using… guess what… no wiki markup! Just plain old and crappy HTML! Why do they call it a “wiki”? It’s a damn CMS, people! Plone would do better!
Fortunately, there seems to be a fix for this:
I’ve already asked the guys who maintain Sharepoint to fix this. There should not be any problem with it…
Anyway, this is yet another revelation of what Microsoft thinks about cross-compatibility and standards.
June 12th, 2007 at 10:02 pm
Stop whining.
Telerik has developed a free (as in beer) version of their brilliant RADEditor (rich text editor) in cooperation with MS.
Simply put it enables a scaled down version of their editor to be shown to non-IE clients.
The scaled down version is much limited compared to teleriks normal product , but should still be at least on par with the MS rich editor.
Hope it helps
/soeren
June 13th, 2007 at 7:52 pm
OK, that’s good, but shouldn’t cross-platform usage be one of the main priorities in a web application? At Indico, we test each new feature under Gecko, Trident and WebKit-based browsers, to make sure that accessibility remains high.
It’s not only me who cares about it: the W3C has a document called WCAG - Web Content Accessibility Guidelines, which clearly condemns “browser discrimination”.
July 12th, 2007 at 2:44 pm
And of course you are right
It is more than a little annoying that Microsoft partitions the world into level 1, 2 and 3 browsers.
Level 1 being IE that can handle ActiveX controls (incidentially the rich text field is one of those)
Level 2 being all the rest premier browsers (newer versions of firefox, mozilla, opera, etc.)
Level 3 being everything else.
As long as MS uses activeX within their site they have to disciminate. They should limit the ActiveX crap to the places where it’s absolutely necessary, which they don’t at the moment.
Until W3C updates the standards to support things like multiple file upload and some sort of integration to desktop apps this is not something that is going to change. Ohh and the browsers actually supports it.
However I do note that the support for non-IE is better in this release than the previous one (about the lowest quality criteria there is
), I often use FF on my SharePoint sites - it is completely possible (provided that you’ve designed a decent masterpage/html/css).