User talk:Jack

From Organic Design wiki
Revision as of 09:19, 20 November 2006 by Nad (talk | contribs) (two birds with one stone)

I just thought of a good idea for your SWF e-book project - you could use the full version acrobat to export as html (or copy/paste from acrobat-reader into notepad and add html markup for images/headings etc). Anyway if you stick to very simple html and keep it xhtml compatable, then you can use the same content for the html-only and the swf version because swf textFields have an htmlText property from version 6 onwards (that's 90% of users though).

Oops sorry - I didn't realise I'd deleted the section you'd just made - but that was really just covering the same stuff that's covered in node and node space etc. The nodal model doc needs to be far more general only skimming the surface of nodes and reduction... --Nad 10:45, 15 Nov 2006 (NZDT)

Saved it already - I need to write some good analogies as executive summaries for general consumption - Jack 10:52, 15 Nov 2006 (NZDT)
Yeah that nodal model doc is probably the best start point for general consumption because its the one that introduces and ties together all the other docs which gettin quite solid like node, nodal reduction, node space etc It's also one of the most sparse brain-sumpie ones too probly cos it needs more english than technical :-/ --Nad 10:56, 15 Nov 2006 (NZDT)

Yo, did Nodal diagrams notes on spectrum stuff, not sure how to do identity/s&d more clearly tho as they already have the necessary concepts in them but just not in a very clear way yet... also I've redone list space which was old and not specific enough. --Nad 17:34, 30 Oct 2006 (NZDT)

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)
Retrieved from "https://organicdesign.nz/wiki/index.php?title=User_talk:Jack&oldid=40880"