Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

Forums » Features / Usability » Tiki Functionality in Open Source environments
 
Thread actions
Print this page
  • Print all pages

    • Tiki Functionality in Open Source environments

    Posted by NAVman posts: 9 United States

    Recently, I've noticed that as Tiki works perfectly in IE, it seems to read the layout deficiently in Mozilla/FireFox, and I have been unable to find an answer or the source of the problem.

    I've looked through documentation, and haven't found anything. Is it a file setting? Server setting? Just me at 12:00 at night?

    Any help would be appreciated, and I can post a shot if needed. Thanks.

    Reads: 1132
    Posted by Damian Parker posts: 2881 United Kingdom

    Actually its more the other way round, we lack Windows developers with IE, we are all mainly Linux geeks running Mozilla and Firefox. 😊

    Change your style, or tweak your style to something else and the browser behaviour will be completely different.

    Its down to the CSS thats in use, at least thats my experience, and Ive done Tiki themes, and a whole load of tiki coding 😊

    Damian


    Posted by drmagu posts: 29 United States

    Hey NAVman!

    I am deploying TW as part of an intranet. We do, however, have a multitude of systems in use, i.e. Windows with M$IE, Mac OS-X (Safari) and *some* linux with Mozilla. Unfortunately, most themes work in some browser, but none work in all. As part of my deployment, I am putting a page together wich discusses CrossBrowserCompatability. I wouldn't mind seeing such a page on this site. Actually, the matrix is three dimensional (theme)(browser)(feature), as it also appears that the 'breakage' of a certain theme is feature specific.
    Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should

    • (a) indicate which browser(s) a theme has been tested (certified?) with
    • (b) ensure that a theme x browser combination works on all features


    Just my two cents.
    Cheers,
    Dr Magu

    Posted by Damian Parker posts: 2881 United Kingdom

    > Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should
    > *(a) indicate which browser(s) a theme has been tested (certified?) with
    > *(b) ensure that a theme x browser combination works on all features
    >

    Good idea except many Tiki developers dont have access to Windows machines to fix those themes.
    Forget IE, install Mozilla and help prevent the adware crap in the world!

    Such a table is good, if you have the resources to keep it maintained and also update all the themes to behave correctly in all browser combo's

    There was work started on mods.tikiwiki.org to organise the themes and show which browsers are supported by it. But resources are lacking in the documentation area. Much more fun to code and make new Mozilla ones 😀

    Damian
    TikiWiki anti M$ IE team 😉

    Posted by NAVman posts: 9 United States

    > Damian:
    >
    > Good idea except many Tiki developers dont have access to Windows machines to fix those themes.
    > Forget IE, install Mozilla and help prevent the adware crap in the world!
    >
    > Such a table is good, if you have the resources to keep it maintained and also update all the themes to behave correctly in all browser combo's
    >
    > There was work started on mods.tikiwiki.org to organise the themes and show which browsers are supported by it. But resources are lacking in the documentation area. Much more fun to code and make new Mozilla ones 😀
    >
    > Damian
    > TikiWiki anti M$ IE team 😉

    Aiyahh, it must be something about open source groups sticking together! 😉

    I suppose a structural environmental test would be interesting, also: does (x) template read differently on (Y) server, or (Z) server?

    I wouldn't mind writing documentation on the templates I've tested (Netscape, Safari, Mozilla, FireFox, IE, Opera), it's just a matter of having a free weekend

    If I can get IRC to run correctly, maybe I'll visit there later to talk more about it.

    Posted by Damian Parker posts: 2881 United Kingdom

    >
    > I suppose a structural environmental test would be interesting, also: does (x) template read differently on (Y) server, or (Z) server?

    I dont the server will render templates any differently. Its still the same smarty doing the work.

    > I wouldn't mind writing documentation on the templates I've tested (Netscape, Safari, Mozilla, FireFox, IE, Opera), it's just a matter of having a free weekend

    hehe 😊 Your in the same boat as everyone else. Not enough time to do everything 😀

    > If I can get IRC to run correctly, maybe I'll visit there later to talk more about it.

    Yeah, come and meet us all. its a growing room.

    Damian

    Posted by NAVman posts: 9 United States

    > drmagu:
    > Hey NAVman!
    >
    > I am deploying TW as part of an intranet. We do, however, have a multitude of systems in use, i.e. Windows with M$IE, Mac OS-X (Safari) and *some* linux with Mozilla. Unfortunately, most themes work in some browser, but none work in all. As part of my deployment, I am putting a page together wich discusses CrossBrowserCompatability. I wouldn't mind seeing such a page on this site. Actually, the matrix is three dimensional (theme)(browser)(feature), as it also appears that the 'breakage' of a certain theme is feature specific.
    > Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should
    > *(a) indicate which browser(s) a theme has been tested (certified?) with
    > *(b) ensure that a theme x browser combination works on all features
    >
    > Just my two cents.
    > Cheers,
    > Dr Magu

    I was chatting with Damian in the channel for a bit today (before I got so tired I fell asleep at the node I was working in), and he said that the reason TikiWiki.org runs across all browsers is because "it runs off of Smarty template engine, not the caching side". Can you elaborate on this further?

    Right now, I can think of a few others who would be delighted to see documentation on different browser themes, or to possibly contribute their current notes to a compilation.

    I'll send off an e-mail to you sometime tommarow morning, and it will be interesting discussions indeed...

    • seaches C:/ for whatever documentation I have handy*


    Cheers to a good night's sleep,
    NAV man

    EDIT- Actually, I don't have your e-mail! 😁 (Just realized that!). My temporary address is hmx1wolf at yahoo.com, or just tell me other contacts to talk to you.

    EDIT2- Found some sparse documentation I had written based on experiences with IE/FireFox theme compatability on an older version (1.4), so I'll review to see if it still holds true.


    Posted by drmagu posts: 29 United States

    Hey NAVman!

    I am deploying TW as part of an intranet. We do, however, have a multitude of systems in use, i.e. Windows with M$IE, Mac OS-X (Safari) and *some* linux with Mozilla. Unfortunately, most themes work in some browser, but none work in all. As part of my deployment, I am putting a page together wich discusses CrossBrowserCompatability. I wouldn't mind seeing such a page on this site. Actually, the matrix is three dimensional (theme)(browser)(feature), as it also appears that the 'breakage' of a certain theme is feature specific.
    Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should

    • (a) indicate which browser(s) a theme has been tested (certified?) with
    • (b) ensure that a theme x browser combination works on all features


    Just my two cents.
    Cheers,
    Dr Magu

    Posted by Damian Parker posts: 2881 United Kingdom

    > Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should
    > *(a) indicate which browser(s) a theme has been tested (certified?) with
    > *(b) ensure that a theme x browser combination works on all features
    >

    Good idea except many Tiki developers dont have access to Windows machines to fix those themes.
    Forget IE, install Mozilla and help prevent the adware crap in the world!

    Such a table is good, if you have the resources to keep it maintained and also update all the themes to behave correctly in all browser combo's

    There was work started on mods.tikiwiki.org to organise the themes and show which browsers are supported by it. But resources are lacking in the documentation area. Much more fun to code and make new Mozilla ones 😀

    Damian
    TikiWiki anti M$ IE team 😉

    Posted by NAVman posts: 9 United States

    > Damian:
    >
    > Good idea except many Tiki developers dont have access to Windows machines to fix those themes.
    > Forget IE, install Mozilla and help prevent the adware crap in the world!
    >
    > Such a table is good, if you have the resources to keep it maintained and also update all the themes to behave correctly in all browser combo's
    >
    > There was work started on mods.tikiwiki.org to organise the themes and show which browsers are supported by it. But resources are lacking in the documentation area. Much more fun to code and make new Mozilla ones 😀
    >
    > Damian
    > TikiWiki anti M$ IE team 😉

    Aiyahh, it must be something about open source groups sticking together! 😉

    I suppose a structural environmental test would be interesting, also: does (x) template read differently on (Y) server, or (Z) server?

    I wouldn't mind writing documentation on the templates I've tested (Netscape, Safari, Mozilla, FireFox, IE, Opera), it's just a matter of having a free weekend

    If I can get IRC to run correctly, maybe I'll visit there later to talk more about it.

    Posted by Damian Parker posts: 2881 United Kingdom

    >
    > I suppose a structural environmental test would be interesting, also: does (x) template read differently on (Y) server, or (Z) server?

    I dont the server will render templates any differently. Its still the same smarty doing the work.

    > I wouldn't mind writing documentation on the templates I've tested (Netscape, Safari, Mozilla, FireFox, IE, Opera), it's just a matter of having a free weekend

    hehe 😊 Your in the same boat as everyone else. Not enough time to do everything 😀

    > If I can get IRC to run correctly, maybe I'll visit there later to talk more about it.

    Yeah, come and meet us all. its a growing room.

    Damian

    Posted by NAVman posts: 9 United States

    > drmagu:
    > Hey NAVman!
    >
    > I am deploying TW as part of an intranet. We do, however, have a multitude of systems in use, i.e. Windows with M$IE, Mac OS-X (Safari) and *some* linux with Mozilla. Unfortunately, most themes work in some browser, but none work in all. As part of my deployment, I am putting a page together wich discusses CrossBrowserCompatability. I wouldn't mind seeing such a page on this site. Actually, the matrix is three dimensional (theme)(browser)(feature), as it also appears that the 'breakage' of a certain theme is feature specific.
    > Now, how to fix it, I don't know. Maybe some themes, really cool, will be restricted to, e.g. mozilla. And that maybe fine. If there's a warning or guidelines with the themes it would definitely improve the usability. What would not be acceptable is that features break a (theme)(browser) combination. So, the release testing of TikiWiki should
    > *(a) indicate which browser(s) a theme has been tested (certified?) with
    > *(b) ensure that a theme x browser combination works on all features
    >
    > Just my two cents.
    > Cheers,
    > Dr Magu

    I was chatting with Damian in the channel for a bit today (before I got so tired I fell asleep at the node I was working in), and he said that the reason TikiWiki.org runs across all browsers is because "it runs off of Smarty template engine, not the caching side". Can you elaborate on this further?

    Right now, I can think of a few others who would be delighted to see documentation on different browser themes, or to possibly contribute their current notes to a compilation.

    I'll send off an e-mail to you sometime tommarow morning, and it will be interesting discussions indeed...

    • seaches C:/ for whatever documentation I have handy*


    Cheers to a good night's sleep,
    NAV man

    EDIT- Actually, I don't have your e-mail! 😁 (Just realized that!). My temporary address is hmx1wolf at yahoo.com, or just tell me other contacts to talk to you.

    EDIT2- Found some sparse documentation I had written based on experiences with IE/FireFox theme compatability on an older version (1.4), so I'll review to see if it still holds true.