Difference between revisions of "User talk:Jack"

From Organic Design wiki
(Too nackered catchya next time ;-))
(Hardware news: ballistic nanotransistors)
Line 1: Line 1:
Gidday, Aran's actually headed out til about 9:30 or thereabouts.--[[User:Milan|Milan]] 19:58, 17 Aug 2006 (NZST)
+
Ballistic nanotransistors - [[User:Jack|Jack]] 09:46, 18 Aug 2006 (NZST)
:Yo - yeah I'll be fairly late, and probly just wanna hit the sack after this - but say gidday to justin for me ;-)
+
 
----
+
http://www.primidi.com/2006/08/17.html#a1599
If you haven't left yet, would you be able to grab some more of those injun meals on the way if not too inconvenient? --[[User:Nad|Nad]] 14:53, 31 Jul 2006 (NZST)
 
 
----
 
----
 
Link to whitepaper by MRAM manufacturers Freescale -- [[User:Jack|Jack]] 23:00, 18 Jul 2006 (NZST)
 
Link to whitepaper by MRAM manufacturers Freescale -- [[User:Jack|Jack]] 23:00, 18 Jul 2006 (NZST)

Revision as of 21:46, 17 August 2006

Ballistic nanotransistors - Jack 09:46, 18 Aug 2006 (NZST)

http://www.primidi.com/2006/08/17.html#a1599


Link to whitepaper by MRAM manufacturers Freescale -- Jack 23:00, 18 Jul 2006 (NZST)

http://www.freescale.com/files/memory/doc/white_paper/MRAMWP.pdf


New quantum tunnelling memory chips, one page version -- Jack22:51, 18 Jul 2006 NZST)

http://www.theregister.co.uk/2006/07/17/freescale_rfid/print.html


Aran, How are you compiling your C code? Are you doing it on a Linux box? Jack 11:21, 6 Jul 2006 (NZST)

Yes, the od server is a linux box with gcc (the GNU Compiler Collection (http://gcc.gnu.org/)) running on it --Rob 11:27, 6 Jul 2006 (NZST)
It's done with c.php, you can test C code in sandbox.c and see compiled results in sandbox.c/compile. --Nad 11:29, 6 Jul 2006 (NZST)
OK I'll get a Debian install CD off one of you guys sometime, its about time I set up a Linux box anyway Jack 11:36, 6 Jul 2006 (NZST)
You don't need linux to run a c compiler, gcc works fine on windows. Also husk.c and its includes are designed to work on windows, osx and ux. --Nad 12:17, 6 Jul 2006 (NZST)

Yo, here's that Java hello world example:

test.java/compile compiles test.java

Thanks for those quantum-computation links. That first one is a much simpler way of understanding the core QM issue than the double-slit I reckon. And the intro to quantum-computation referred to in it is damn good - I hadn't realised how tied in with quantum computation the nodal core was. --Nad 18:12, 5 May 2006 (MST)


Thanks for pointing that out - there was a strange glitch in the dynamic-dns service where it suddenly switched back to an ip from 9 days ago?! so I just changed them to 0.0.0.0 and back again which always seems to fix these dynamic-dns issues. --Nad 16:59, 30 Mar 2006 (NZST)


Gooday - you might want to set hide-minor-edits by default in your prefs page, so that huge lists of minor corrections don't show up :-) Nad 16:43, 15 Mar 2006 (NZDT)

http://www.jack.co.nz/calc.jpg


Okidoki, there you go, I've made an Actionscript sandbox for you with the bouncing ball in it that you can modify etc. There's three articles involved:


Nodal code fragment example

Here's a nodal function called resolve which is used by get/set to allow a path to be specified which is relative to the current this. The nodes are created along the way if they didn't already exist. The code is taken from the currently developing peer-nodal.as.

[[+node.resolve.as|]]
Notes
  • The path parameter is an array of node-refs to be treated as relative path from this
  • The shift method applied to it in the loop means to pull the first item out of the array reducing its length by one.
  • We need to introduce internal id's for nodes and use key.id rather than just key because key is a node-ref and isn't allowed as an associative-array-key (ie. ECMA fails the key-as-ref test).
  • The difficult looking line is using the ?: operator
A = cond ? B : C is equiv to if (cond) A = B else A = C
  • In ECMA, the prototype property of a constructor defines all the methods and properties that will be available to instances (in this case instances of node)