@all Many things that need more browser specific work were decided to get fixed after the new site is online, because we should get rid of the temp website as soon as possible. We tried to make all the necessary work to make it run fine as it is created by the Xoops team, with the old data in it.
The second thing that we had in mind was to not change a single line of code, because whenever we will have to make an update, then the changes will be overwritten. Whatever we did with the theme was done in a way to keep the xoops cms intact.
From now on we are going to make additions to the website and make it full compatible with the most of the amiga browsers. We didn't want to lose time for fixing those issues first.
@Chris Be sure that really soon my beloved NetSurf is going to be supported totally... I just need some time. :D
As a web developer I personally do not agree on avoiding javascript or css. Come on, they were introduced in mid-nineties! I do not want my Amiga to be stuck in the past, I've choosed to use a Sam460, not an Amiga 1200...
All well and good if it improves the site witrhout breaking it. It is unreadbale in IB so I will not be visiting as often as I used to, no fun trying to follow the diabolical layout.
Why make more complex sites with less compaitibilty when the previous site worked so well, that is what I do not understand.
It is certainly not worth the effort of firing up that slow diabolical monstrosity OWB which brings my 1260MHz A1 down to a crawl.
Breaking a site just to be able to use modern gimmicks that are not a neccessity is not progress. It is bad web design to create sites that do not work on all browsers, or to allow alternatives when things like CSS and flas are unavailable.
I will not be buying a ruddy PC to be able browse Amiga sites.
All well and good if it improves the site witrhout breaking it. It is unreadbale in IB so I will not be visiting as often as I used to, no fun trying to follow the diabolical layout.
Really? It's perfectly legible in AWeb just a bit "grey", ie background colours and images aren't showing. (I don't expect them too, even though it would be nice).
Quote:
Why make more complex sites with less compaitibilty when the previous site worked so well, that is what I do not understand.
The previous site was hacked (due to security flaws in the xoops code I presume) any browsers failures are the side effect of installing more recent "fixed" code, which wasn't writen with non CSS browsers in mind, giving that fact I'd say it's working very well.
Quote:
It is certainly not worth the effort of firing up that slow diabolical monstrosity OWB which brings my 1260MHz A1 down to a crawl.
Really? OWB runs quite fast on all but a few sites which really do over do the javascript on my SAM 733Mhz, how recent a version are you using? I do sympaphise as I use AWeb for browsing sites where I no it works, but I fire up OWB just as often.
Anyway I'm posting this with AWeb and it'as working fine, so if you want to stick with a 'traditional' Amiga browser there's always that option, if Ibrowse doesn't cut it.
It is certainly not worth the effort of firing up that slow diabolical monstrosity OWB which brings my 1260MHz A1 down to a crawl.
Something are wrong for you in terms of setup looks like .. For me OWB runs almost the same by speed as IB (i think on 1 second slower). And exit faster (just because no cache-cleanup). Dunno why you stack in the past and what sites you visit with IB.. for me all the sites which i visit in last days, works only in OWB, and be in hope that they will works on something which very old and unsupported (IB) .. dunno.
Maybe its just some fetish , like "i want to visit amiga sites from ibrowse, and does not care about any other solutions" ?:)
@kas1e If BillE uses dial-up, then that might explain it. Our current OWB *may* be much slower on dial-up, due to waiting for responses from more stuff (less network "multitasking") before able to render the page.