New Surface – Eastwood in Vienna

Oh my x!
We got a new surface, looks absolutely prol!
What do you think?
I just wanted to write about the Clint Eastwood-film Firefow from the year 1981, & now i open the vienna metroblog – & RÖÖÖÖÖÖÖCHL!!!
But I want to come back to the subject:
Do you know the mentioned movie Firefox? Parts of it play in Moscow but these scenes are filmed in good old Vienna. Coooll: you shold imagine Moscow & you recognize Vienna :-) & I tell you: It all looked the same at the beginning of the 80ies here in Vienna, the Donaukanal, the underground, even the small orange cars cleaning the trottoire. The only thing that changed are the signs, it seems they were at this time in cyrillic. Funny. & fun to watch, because I like it to guess where Clint Eastwood & his team shot this or that scene.
Of course it is not really a good film, but I like the soundeffects & the trashy fx & I tell you: You never saw a si stupido first secretary of the USSR. A film right out of the cold war!
& not to forget: You also find the austrian actor Klaus Loewitsch (whom I hated when I was young for his tv-series Peter Strohm. But now I liked to see him, it was like greetings from my youth ;-)) as Vladimirov. Reallyreally funny!

10 Comments so far

  1. nex (unregistered) on February 20th, 2006 @ 11:37 pm

    at first i was positively surprised. i was looking forward to going through the loooong list of things wrong with the technical implementation of the site and discovering that at least some of the issues are resolved. but it doesn’t seem likely. it’s still based on MT. i still see no measures guarding against comment spam. there are new issues. for example, some features rely on javascript now and there’s no fallback for user-agents that don’t support it. and even if you have it turned on, they don’t work at all. you can’t even navigate to another city, or have a look at the archives. i’m using the most recent firefox, mind you. the wonderful picture gallery is gone. the code is totally fucked … there are typos … not in the text, mind you, but in the markup, where every browser barfs if even a single bit is wrong. typos and even sillier grave mistakes, even illegal characters. OH PUKE!

    to the designer, whoever it is: the UI isn’t too bad, that can be fixed. visually it looks quite neat. but please, don’t you ever attempt to write HTML or JS again. i mean, look, you’re probably a really nice person and it’s nothing personal, but if you make a site with lots of links that do exactly nothing when clicked upon, my first thought is that you might be a complete twit.

  2. melancolia (unregistered) on February 20th, 2006 @ 11:46 pm

    so far, i like the look. well, am not a programmer, am just an ordinary average looker. but so far, my only complaint is that, yeah, navigating to other cities is impossible. i was thinking that by clicking the map and pointing anywhere will bring me to other cities.

  3. nex (unregistered) on February 20th, 2006 @ 11:56 pm

    that’s the point, melancolia. of coure i know how to get around the bugs. (btw., in safari some features work, but the layout is pretty much broken.) but an average websurfer will just become hopelessly lost, and (a) surf away and not come back for quite a while or (b) try to report the problem, click on ‘contact’, see nothing at all happen, become frustrated, surf away and not come back for quite a while.

    your idea with the map is awesome, melancolia. this should definitely be implemented … just show other cities as little dots and put in an image map thingie. creative and neat.

  4. Boris Anthony (unregistered) on February 21st, 2006 @ 1:27 am

    Servas “Nex”

    Instead of railing off falsities, can you please for the developpers and designers’ sakes, pin point exactly what you see as broken? Everythign works perfectly well in every browser I have checked it with myself. I am sure they would appreciate that more than silly hand waving and excusing oneself for insulting their intelligence…

    Agreed the map thing would be quite cool. ;)

  5. sami (unregistered) on February 21st, 2006 @ 2:04 am

    i hate changes.

  6. Christian (unregistered) on February 21st, 2006 @ 11:50 am

    sogar für meinen wirklich wirklich grossen apple bildschirm … ist es mir schlicht zu breit. (ich surf am apple halt gerne in 850pxbreiten fenstern; und seh dann die recht nette movtype-werbung gar nie nicht; am pc wird mich das nicht so stören.)

    allein die textspalte ist auch zu breit. zum lesen.

    man gewöhnt sich aber eh an alles.

    nett die aufklappbaren menus da rechts. nicht nett, mich noch immer nicht auf der rolle zu haben. was solls? vielleicht die rechte auszeichnung fuer mich. ;)

    weitermachen. danke. gausg

  7. nex (unregistered) on February 21st, 2006 @ 12:31 pm

    boris, everything i said is true, there are no falsities. the most severe issue is already described pretty exactly: none of the javascript works in the most recent firefox. i just forgot to say i’m using mac OS X. (the observant reader will have gleaned that from my mention of using safari though. *g*) the menu items in the sidebar, for example, use the toggle function, which is not defined. (from the POV of Fx and if they have trouble reproducing the bug they can always contact me and i’ll see what i can do to help. is this still not accurate enough? should i break out the debugger and fix the code for them?

    but boris, i don’t think trying it in a couple of browsers and declaring everything is alright is enough. there are typos and other errors in the code and the w3 validator doesn’t even begin to check it because it says it’s not utf-8 as it should be (thus my report of illegal characters), so you can never know which of the many user agents out there will be tripped up. it’s also not false that there is no fallback for user agents without js. i’m not talking about funky extra features like adding a story to your, mind you, but about vital navigtation links.

  8. Michael (unregistered) on February 21st, 2006 @ 2:25 pm

    May I also note, blind readers with screenreaders will have their problems accessing some of the content here. Javascript in the href attribute is far from “best practice” – I guess most AJAX (*cough* *cough*) devs will tell you to use a listener in the JS file. Also, lists aren’t marked up as such, among other problems, that I won’t go into detail here.

  9. nex (unregistered) on February 21st, 2006 @ 4:57 pm

    dear coder, it’s working now; thank you! *smooooch* the encoding and code are still wonky, and i also find what michael said very important. scratch that, it is important, no doubt. better semantic mark-up (actually declaring headlines as headings etc.) and techniques that degrade more gracefully when not or poorly supported would be helpful; not just for the blind, but for everyone. but i also found a few small things that are slowly moving in the right direction now, so i’m cautiously optimistic.

  10. scott (unregistered) on February 21st, 2006 @ 10:35 pm

    “You must think in Russian”!

Terms of use | Privacy Policy | Content: Creative Commons | Site and Design © 2009 | Metroblogging ® and Metblogs ® are registered trademarks of Bode Media, Inc.