@ Wayne
Wayne wrote:
DiskDoctor wrote:
You mean down for mobile? Or you just simple feel kindda bored?
I mean, -- with all intended respect -- it's getting kinda old to hear every other post on the subject of redoing Amiga.org to be:
"mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile, mobile.".
Yes. We know. You want a mobile site. I get it. Enough already.
PLEASE -- Let's see what we can do about saving the site itself before we concentrate solely on a feature that all of 5 people might, or might not use please?
Wayne
You misunderstood.
This topic is about web system's transition. Nothing more. By mentioning the m-word, I entirely meant mobile rendering for classic, not mobile rendering for mobile. Just as means to achieve classic compliance.
As I posted in
Any webpage on ANY amiga browser thread already, I think mobile rendering is a possible out-of-the-box workaround to guarantee classic support after your planned transition.
Maybe I wrote somewhere I wished there was mobile.aorg site, but hey, I'm reading/posting on mobile sometimes and it feels great already! I want NO change thereafter (since a guy helped me out on it with my HTC phone) I do not state mobile aorg version is needed anymore. Especially on this very thread.
All I wanted to quote in my previous posts is that mobile CMS infrastructure provides a way to isolate and serve classic browsers properly.
My personal opinion is that new aorg site should indeed, support classics, for sake of preservation. But as I said, no one wants your time wasted on it.
Whatever way it is, mobile rendering, smoothing proxy or any other (including classic abandonment), it is you who decides here. You wanted opinion, you got my opinion, that's all.