Thursday, March 25

Campaign Review of BoW

In the course of Open Source Management our team members had to write a review of the other team’s campaign.

First of all, I had a lot of trouble installing their campaign which resulted in numerous error dialogs. At first I thought this was because I use a rather “special” OS system – Windows 7 64-bit in Estonian. Also, like in the classroom in TLU, I installed the beta version of BoW to my system. Therefore at first I tried looking into the main configuration file to create some workaround.

Later on my team members all shared in Skype the same problems and offered a solution – to install BoW stable version. As for them, this helped me also.

The campaign was about a some sort of mobster, that terrorized the villages around him (collecting roof-money etc.).

I have to admit that I am bad at non-real-time-strategy games, therefore maybe the level “easy” that the team had made, was still difficult for me.

This was because I tried to kill all the soldiers that attacked me, but later on I understood that I had to kill the nemesis up north. This wasn’t said in the scenario introduction (simply collect the villages). So I had a whole interesting hour trying to get to the second level.

Now, thanks to the help from Ott, I managed to reach to the second level. I have to stress out, that there should be always a re-birth limit for the bad guys. Some reality should be implemented.

The second scenario was again different than described. My old strategy of killing the enemy or quickly escaping towards the goal-point didn’t give me success.

On the third scenario my limited play-skills ended, because I just got constantly killed. So sadly I can’t report anything else.

I’d like to state out that for example when playing my all time favorite Wolfenstein, when you select the level easy, it really is easy, and you could kill your opponents simply by “wearing them out”. Ok that is a little bit of lie.

So at the end, I’d like to say, that although the campaigns were made very creatively (I liked that the units images were imported, not used the inbuilt one’s), I had a somewhat half-made feeling towards the scenarios when playing the campaign.

But great creativity and I only wish, that someone from the community would continue to generate a campaign with more elaborate and storyline’d content.

Sunday, March 21

Javascript

Hacks
Mõned head veebilehitseja häkkimist selgitavad lehed:
http://www.webcredible.co.uk/user-friendly-resources/css/hacks-browser-detection.shtml
http://articles.sitepoint.com/article/browser-specific-css-hacks

Peamised IE probleemid, mida siis häkkidega lahendatakse, on MS teine arusaam CSS poolt kuvatavast disainist (suuruserrorid jne.).

Delfi.ee kasutab näiteks ifIE häkke.

Javascript
Ise olen javaskripte tõmmanud selliselt lehelt: http://www.dynamicdrive.com/

Huvitav javaskript nt: http://www.tmk.edu.ee/~nkaareste/mkeeled/lumi.html

Tuesday, March 9

Finished courses in TLÜ

Spring semester 2011

Autumn semester 2010
Spring semester 2010
Autumn semester 2009

Finished courses in TMK

Kevadsemester II - 2010
Kevadsemester I - 2010
Sügissemester - 2009

Wednesday, March 3

Kodeeringud

HTML kodeering
  • http://www.w3schools.com/TAGS/ref_charactersets.asp
  • HTML kodeeringu eesmärk või olemus on "anda veebilehitsejale info, millist sümbolitejada peaks ta kasutama koodirea visualiseerimisel kasutajale". 
  • kooli koduleht kasutab ISO-8859-4 kodeeringut
  • Postimees, Delfi,  (UTF-8), Neti.ee (ISO-8859-15)
  • Facebook, Orkut, Rate.ee (UTF-8)
  • Uue veebisaidi loomisel kasutaksin mina UTF-8 kodeeringut
  • Kuna nii saan olla kindel, et minu loodu kuvatakse kõigile ühelaadse sisuga 
HTML sümbolid
  • http://www.w3schools.com/TAGS/ref_symbols.asp
  • http://htmlhelp.com/reference/html40/entities/symbols.html
  • HTML sümboleid kasutatakse juhul, kui soovitakse veebilehitsejas kuvada sümboleid, mis kuuluvad tegelikult koodi hulka (vaikimisi neid ei kuvata, vaid need "töödeldakse" veebilehitseja poolt. Et kasutaja saaks neid kasutada (>, ' , jne.), peaks ta need sümbolid kas .jpg'na vms. kuvama lehel või kasutama HTML keelt nende kuvamiseks (parem variant, kuna on kiirem). Suurepärane valik, mida ja kuidas kuvada, on toodud siin:
  • http://www.webdesignerwall.com/tutorials/using-html-symbol-entities/
URL kodeering
  • Kuna veebi loomise ajal oli kasutatavaks kodeeringuks US-ASCII, siis kasutati seda ka veebiaadresside kodeerimisel. Tänaseks on aga keelte rohkus ja veebimaastiku suurus sellise kodeerimisviisi jaoks liialt suur, mistõttu kodeeritakse URL'e, parendamaks veebilehitsemise võimalusi.
  • Levinuim URL kodeerimine on automaatsete veebiaadresside genereerimisel puhul. Näiteks võib mõni foorum genereerida foorumipostituste URL'e, lähtudes aadressi genereerimisel loodava postituse pealkirjast. Juhul kui selles pealkirjas on tühik, või $ märk või õ täht (Nt. "Jo, t$ekkake seda õli!", siis  üks võimalikke URL kodeeringu tulemusi oleks "Jo%2C+t%24ekkake+seda+%F5li%21 "
  • Põhireeglid URL kodeeringu puhul on lihtsad: kodeerida saab ainult US-ASCII kodeeringus. Kodeeringus ei saa olla tühikuid ning kõik mitte-tüüpilised sümbolid (loe: mitte-inglise tähed) konverteeritakse koodi (number on indeksiks). Antud indekseid võib leida siit:
  • http://www.w3schools.com/TAGS/ref_urlencode.asp
CSS raamid

Viide tehtud tööle:
http://www.tmk.edu.ee/~nkaareste/mkeeled/kodeeringud

Loetelud veebilehel

Parimaid lehti listide koostamiseks, kasutades CSS põhimõtteid, on kindlasti
http://css.maxdesign.com.au/listamatic/

Sarnaseid andmebaase on kindlasti veel, kuid antud lehel on toodud küllaldane ülevaade enamikest võimalustest nimekirjastamisel, kasutades CSS'i.

Viide tehtud tööle:
http://www.tmk.edu.ee/~nkaareste/mkeeled/veebiloetelu