PLEASE VOTE NOW!

[combatking0]

Calling all forum members!

Please don't forget to cast your vote for the JavaScript Pi/Pie competition!

Please visit
http://dbfinteractive.com/index.php?topic=2352.0
for full details on the entries, and to leave your comments.

[Shockwave]

I voted 

[0x4e71]

Good stuff. I liked'em

[slippy]

Uhh wait - just saw your nick 0x4e71 ... isn't that the opcode for NOP in 68k ASM, is it ?!

[0x4e71]

Uhh wait - just saw your nick 0x4e71 ... isn't that the opcode for NOP in 68k ASM, is it ?!

Bingo 

Favorite instruction of my (still) favorite CPU ;-)

[combatking0]

I was always a fan of 0x5f82.

But I don't know what I'm talking about.

[Clyde]

My votes in the bag CK0 dude.

[combatking0]

Cheers everyone. The more votes the better!

@anyone who has yet to vote:

Please download and examine the entries from the link in the first post on this thread, and cast your votes - all views and comments are welcome - apart from destructive criticism. If you have a criticism, please make it a constructive one.

[Shockwave]

Even though there are only a few entries the Ã,£30 prize will still be awarded at the end of it

[p01]

I voted a couple of days ago.

My feelings are mixed.

To me, the highlight of the contest was to see an entry from a complete JS newbie. Although the points raised in this entry's thread have not been addressed, the overall code itself was actually nice.

However I hoped to see better code. I don't know how familiar people are with JavaScript, and I realize it is tongue in cheek of me to complain since my only contributions to the contest were feedback and the cross-browser framework, but I must say the code and coding practices I saw looked obsolote.  I guess I should elaborate on each entry later. Meanwhile people can check the framework I provided to get an idea of the type of code I expected.

DISCLAIMER: Bare in mind that I'm a JavaScript developer in the Web Applications team of a browser company with a strong commitment to web standards and accessibility.


0x4e71: Not sure what's my favorite operation, if I have any on 68000. On 68030 it was probably move.l ([a0],d0),(a1)+ or whatever the syntax of a move in indirect addressing mode was.

[Shockwave]

I don't think that you should feel bad about posting your opinion on this just because you didn't enter it, you did your best to make it a success by posting your framework and I appreciate it, I know other people here do too.

Let's face it, most comps we have here have had a lot more entries than this, but it was an interesting one.. I would say that nearly all the people here are Javascript novices, they have no J$ knowledge at all, of the few that have I guess that they'd never used the J$ to make a demo.

Most comps we have are open ended and on average get at least 12 entries, maybe next time you'll see a bit more variety, the lack of entries to this were really down to the low j$ userbase here I guess.

When the language is open ended we get a lot more.

[benny!]

@p01:
Definately. What shockwave said. No need to feel bad. I think the framework you posted is
really advanced and the framework really upvalue the contest. In my eyes you are definately
a person from which I hope to learn something in this forum concerning javascript ... so
thanks again for providing your framework, p01!

[0x4e71]

j$/DOM is, in many ways, horribly limited (edit: in the context of demo coding, before I get flamed). So, extra kudos to those who DID submit entries!

@p01: hehe yeah motorola changed their mind about the syntax a couple of times at least. Other than the do nothing" op, another good favorite of mine are all movem operations, e.g.

  
    movem.l  $04(a0,d0.w),d1-d4  

these can also be used as "push" and "pop" but do not implcitly reference a specific register (unlike the x86) which makes them highly flexible. The fact that move instructions update the flags is also a + for me, the fact you could move and branch e.g.:

   move.b   mt_arplist(pc,d0.w),d0
   beq.s   mt_arp0