00:00:00 --- log: started forth/08.02.14 00:09:38 --- quit: Quartus () 00:10:05 --- join: ecraven (n=nex@140.78.42.139) joined #forth 00:34:40 --- quit: proteusguy (Read error: 110 (Connection timed out)) 00:35:20 --- join: proteusguy (n=proteusg@ppp-124-121-211-249.revip2.asianet.co.th) joined #forth 00:48:12 --- quit: nighty^ ("Disappears in a puff of smoke") 00:52:15 --- quit: ecraven ("brb") 00:53:20 --- join: ecraven (n=nex@140.78.42.139) joined #forth 01:05:09 --- join: DocPlatypus (n=doc@mousetrap.platypuslabs.org) joined #forth 01:30:42 --- quit: ecraven ("brb") 01:33:58 --- join: ecraven (n=nex@140.78.42.139) joined #forth 01:37:09 --- quit: proteusguy (Read error: 110 (Connection timed out)) 01:55:07 --- quit: DocPlatypus (Read error: 104 (Connection reset by peer)) 02:27:53 --- join: nighty^ (n=nighty@p5221-adsau17honb13-acca.tokyo.ocn.ne.jp) joined #forth 02:51:30 --- quit: sauvin ("Leaving") 02:51:59 --- join: sauvin (n=sauvin@74-136-191-181.dhcp.insightbb.com) joined #forth 03:15:24 --- quit: nighty^ ("Disappears in a puff of smoke") 03:16:03 --- join: nighty^ (n=nighty@p5221-adsau17honb13-acca.tokyo.ocn.ne.jp) joined #forth 03:50:50 --- join: viperhr (n=xiper@chello084114184044.13.15.vie.surfer.at) joined #forth 03:51:26 --- quit: sauvin (Remote closed the connection) 05:42:11 --- join: DocPlatypus (n=doc@mousetrap.platypuslabs.org) joined #forth 05:43:22 --- quit: maht (Read error: 110 (Connection timed out)) 05:43:26 --- join: maht (n=maht@85-189-31-174.proweb.managedbroadband.co.uk) joined #forth 06:17:56 --- join: proteusguy (n=proteusg@ppp-124-121-211-249.revip2.asianet.co.th) joined #forth 07:08:12 --- quit: madwork (Read error: 104 (Connection reset by peer)) 07:20:42 --- quit: ecraven ("bbl") 07:22:01 --- join: madwork (n=foo@204.138.110.15) joined #forth 07:35:00 --- quit: ramkrsna ("Leaving") 07:44:12 --- join: skas (n=skas@72-254-162-45.client.stsn.net) joined #forth 07:55:16 --- quit: skas ("Ex-Chat") 09:12:38 --- join: neceve (n=ncv@unaffiliated/neceve) joined #forth 09:22:03 --- quit: Al2O3 (Read error: 104 (Connection reset by peer)) 09:22:39 --- join: tgunr (n=davec@70-41-216-48.cust.wildblue.net) joined #forth 09:32:41 --- join: Al2O3 (n=Al2O3@c-76-120-54-133.hsd1.co.comcast.net) joined #forth 09:54:43 --- join: arke (n=arke@p57A76AD1.dip.t-dialin.net) joined #forth 09:54:43 --- mode: ChanServ set +o arke 10:07:19 --- quit: Al2O3 () 10:16:56 --- join: Al2O3 (n=Al2O3@c-76-120-54-133.hsd1.co.comcast.net) joined #forth 10:52:58 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 11:14:56 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 11:24:49 --- join: snoopy_1711 (i=snoopy_1@dslb-084-059-202-172.pools.arcor-ip.net) joined #forth 11:32:38 --- join: X-Scale (i=email@89-180-28-194.net.novis.pt) joined #forth 11:32:50 --- join: tgunr (n=davec@70-41-216-48.cust.wildblue.net) joined #forth 11:33:09 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 11:33:32 --- nick: snoopy_1711 -> Snoopy42 11:39:21 --- quit: Quartus__ ("used jmIrc") 11:39:37 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 12:17:45 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 12:30:30 --- join: tgunr (n=davec@70-41-216-48.cust.wildblue.net) joined #forth 12:41:46 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 12:53:40 --- join: tgunr (n=davec@70-41-216-48.cust.wildblue.net) joined #forth 12:58:38 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 12:58:39 --- mode: ChanServ set +o tathi 13:07:58 --- quit: Raystm2 ("Should have paid the bill.") 13:19:47 --- join: Raystm2 (n=Ray@unaffiliated/raystm2) joined #forth 13:46:48 hi ray 13:47:55 Hi Charles. :) Nan says Hi. We missed you. Hope you and yours are well. :) 13:51:29 --- quit: nighty^ ("Disappears in a puff of smoke") 13:55:39 --- join: mark4 (n=mark4@70.102.202.140) joined #forth 13:57:13 hi crc, Raystm2 13:57:14 hi mark4 13:58:20 hi slava 14:01:14 --- join: JasonWoof (n=JasonWoo@unaffiliated/herkamire) joined #forth 14:01:14 --- mode: ChanServ set +o JasonWoof 14:01:14 not ONE single person responded to my huge post of sources... last time they all flamed me constantly for daring to post that much in one blob lol 14:01:24 guess they all got me on ignore and never saw it :P 14:01:55 or maybe werty and friends drove all the real people away 14:02:02 yeah 14:02:23 they should come chat here then. werty would get a ban here he could never get there 14:02:30 all things in moderation 14:02:36 i'm going to be setting up a blog server soon 14:02:39 including moderation! 14:02:43 for forth/factor/random stack language blogs 14:03:01 you guys should blog there ;) 14:03:12 im not one much for blogging 14:03:28 its wjust like a newsgroup post :) 14:05:13 Hi slava, Hi mark4. missed you both. Hope you both are well. 14:05:33 hello there JasonWoof. missed you too. :) 14:06:00 hey raystm2 ltns :) 14:06:03 lately I've just been online when I'm actually at my computer 14:06:07 mostly cuz im not here much lol 14:06:37 ive been developing the 8051 environment but thats about it 14:06:42 neat. 14:06:53 im very happy with that simulation 14:06:56 cool to hear of slava's blog server. 14:07:05 there was a very stupid bug in my assembler tho lol 14:07:08 it might take a while to build the server 14:07:15 we're still writing the database access library, but it's almost done 14:07:17 in the encoding for the ajmp and acall opcodes 14:07:18 it's in good hands. :) 14:07:27 after that i need to write an authentication library that does all the stuff where you sign up and it e-mails you a password, etc 14:07:47 complicated? sounds like it. 14:07:55 also we need to finish the openssl bindings 14:07:57 mark4 what was this about a post? 14:07:59 i mean the 8051 assembler i published in isforth and pasted into CLF a while back, ajmp and acall assembled an incrroect address 14:08:02 once those three components are in place a blog server is easy 14:08:14 raystm2 i publised the soruces to my 8051 simulators opcode execution engine 14:08:26 I see, thanks Mark. 14:09:02 ive not FULLY tested all opcodes but the ones i have tested are working and im somewhat confident about the rest 14:09:14 neat! indeed. 14:09:21 but ill be prooving them eventually lol 14:09:59 i wrote it cuz im writing an 8051 forth (that im target compiling in isforth dos) and i need to debug that sans hardware 14:10:18 got the hardware but getting the forth on it will break it if its not working FIRST lol 14:10:21 brick it 14:10:48 I see. 14:11:06 sounds like a sound project. 14:11:25 well. ive not DONE any coding of my own in probably over 3 years now 14:11:25 all my projects recently are income related so I don't mention them here. :) 14:11:39 a bit disheartened about not having an assembler in isforth 14:11:50 im at work right now lol 14:12:18 * slava is at work also 14:12:43 cool. I may be healthy enough for work soon. I hope. I hate being stuck in. Even tho I took the kids to texas last week, I spent much of the time in the motel room. :( 14:13:21 where in texas 14:13:58 Fort Worth. 14:14:13 about 12 hours from here, gas and food stops included. 14:14:52 Arn't you in Austin or close? 14:15:01 aren't even. 14:15:06 i was in san antonio but i live in phoenix now 14:15:09 well... tempe 14:15:23 OH! cool. well Hot :) 14:15:29 hehe NICE 14:15:34 from hotter to HOTTER. 14:15:36 its not hot right now and i like hot 14:15:44 me too. :) 14:16:56 mark4: just break down and write the assembler :) 14:17:02 :) 14:18:17 crc i tried. numerous times 14:18:29 i get so far and get totally stuck. no idea how to proceed. 14:18:35 Oh hey I do have a bit of a colorforth project that I'm calling "colorForthIBL Graphics". This is a paper about the graphic facilities that come with colorforth. Icons Boxes and Lines. 14:18:38 usually when i get to that point i go away and do something else 14:18:46 and when i come back to it all the code just flows 14:18:48 i have the answers 14:18:53 not with this 14:20:37 its not like i cant write a forth assembler, i have one i wrote for the 8051 but the 8051 opcodes make sense 14:20:44 x86 opcodes make zero sense to me 14:21:11 have you looked at colorforth listing for hints? 14:22:07 no way 14:22:41 :) okay. Your prejudice is noted. hehe. :) 14:26:38 mark4: has isforth's site moved? 14:31:16 mark4: i can give you hosting if you want 14:31:21 as long as you don't start getting mad hits :) 14:45:38 colorforth its gone 14:45:41 er 14:45:51 isforth is gone 14:45:55 the site hosting isforth went away i dont know where 14:46:13 actually im going to have it hosted on forth inc's site lol 14:46:15 well 14:46:22 on a friends machine thats co hosted by forth inc 14:48:16 i was gona say colorforth isnt forth lol i cant read that stuff 14:49:12 you are correct. at a very low level colorforth is assemblerForth. This was the reason I asked if you'd like to see a listing. :0 14:49:30 x86 assemblerForth for that matter. 14:53:35 --- quit: DocPlatypus ("Leaving") 14:54:01 And hence my long interest. I am thrilled to find that out of that mass of shit called the x86 line of chips and opcodes that someone could build such an amazingly powerful forth. 14:56:37 I suppose it's because I see any other programming environment as a compromise, including those authored by them that frequent here. I would always be wanting to remove much of what the author has done to get down to the bottom of why. 14:57:03 Tippically, these creations are to solve some problem the implementor sees. 14:58:15 I never see those problems. They don't make my life easier. They are frameworks that I tippically have a hard time understanding there purpose, usually don't save me time because of all the research required to make sure I don't screw up a future portion of the code or what have you. 14:58:17 i wanna get into the SEAForth thing 14:58:21 that looks interesting 14:58:44 it does indeed. 14:58:48 Raystm2: what kind of applications do you write? 15:00:32 Tippically, the applications I write are to solve a specific problem I have. Normally I do stuff for my finances. 15:00:54 I play with graphics, and I'm starting to play with sound. 15:01:42 Dr Nick Maroudas has graciously provided me with a colorforth suite that can create music and sounds and drive DAC equipment. 15:01:57 I'm currently learning to use it. 15:05:18 Also, I've completed the Chuckbot to well beyond the specs of the original Karel. This will become the training environment for OLPCcolorForth. It is easily converted to drawing programs and editors. 15:06:05 Chuckbot is basically a programmable cursor. 15:07:33 sound and graphics is what is needed to teach children on olpc. The basic tasks are all available and just need to be combined. 15:08:01 When I go to Europe this spring, I'd like to do this in a sprint with my EuroColorforth buddies. 15:09:40 --- join: crest__ (n=crest@p5B107123.dip.t-dialin.net) joined #forth 15:10:30 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 15:11:13 There is at least one xo with-in the colorforth community. I will apply for another and hope to get it before the trip, but failing that, the simsoftware will have to do. 15:11:39 the xo sucks 15:12:47 It will be better on the SeaForth USB. 15:14:27 He he, I get the impression that the people building that system are having to go to a bunch of people with no expereance in computing to get there money. Which is true actually. 15:15:09 So, they have to use all the recent(ancient last 5 years) buzzwords of computing to get the thing produced. 15:15:36 They seem to thing there is some merit in folowing the current trends rather they to go beyound them. 15:17:25 --- quit: crest_ (Read error: 110 (Connection timed out)) 15:18:30 I'm saying I can use their production, just as I use the Pentiums surounding me here. 15:23:08 I think it's safe to say the we here seem to see the beauty of what is currently proposed at intellasys. I don't think anybody thinks that intellasys will even put a dent into what microsoft and IBM are doing for the General Public. 15:23:59 And I suppose I'm not talking about General Public computing either, when I talk about these minimalist systems. I am talking about programmers. 15:24:28 You either write your own framework or use someone elses. 15:24:54 I use a basterized version of an early version of a Chuck Moore framework. 15:25:47 everything else I do with computing came with the computer or is found for free online. 15:25:55 --- join: tgunr (n=davec@70-41-216-48.cust.wildblue.net) joined #forth 15:26:29 I don't try to re-create these things unless they create a particular challenge. Most don't. Much of what is done anymore is just data moving. 15:29:28 I have the luxury of not being important in the world of computing. :) 15:29:42 Factor gets more important everyday. :) 15:30:07 * Raystm2 taking son to work. 15:38:57 --- quit: forther ("Leaving") 16:26:21 --- quit: neceve (Read error: 104 (Connection reset by peer)) 16:30:46 --- quit: JasonWoof ("Leaving.") 16:48:43 --- quit: mark4 ("Leaving") 16:52:17 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 16:55:20 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 16:55:20 --- mode: ChanServ set +o Quartus 16:55:36 Hi. 16:58:30 y0 17:01:46 How goes it? 17:02:02 good 17:02:12 debugging some compiler changes 17:02:20 i implemented a really crappy hack today 17:02:24 its a "disassembler" 17:02:44 it asks factor for the address of a word, then spawnsa gdb instance, sends it some commands, and reads the output from a pipe 17:03:08 "disassmelber" in quotes because too much symbolic info is lost; a real factor disassembler would tell you what word each address pointed to in the output, etc 17:03:17 but still useful, better than attaching gdb by hand all the time 17:03:19 Still. Probably useful. 17:03:23 yup 17:07:46 Perhaps you could also feed a symbol file in. 17:08:10 good point 17:08:17 i assume the format is relatively simple 17:28:14 --- join: nighty^ (n=nighty@210.188.173.246) joined #forth 17:35:23 --- join: edrx (i=edrx@189.25.184.105) joined #forth 18:21:09 --- quit: viperhr (Remote closed the connection) 18:22:49 --- quit: tathi ("leaving") 19:40:05 --- quit: Quartus (Read error: 110 (Connection timed out)) 19:40:15 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 19:40:15 --- mode: ChanServ set +o Quartus 20:32:56 --- join: mark4 (n=mark4@63-229-121-143.phnx.qwest.net) joined #forth 20:33:16 is foxchip jeff fox? 20:40:52 yes 20:42:59 ive not seen him talk in here with that nick 20:50:12 He attends #c4th or #c4th-ot when he has a mind to do so or something interesting he'd like to report to the fandom. 20:50:36 aha :) 20:50:39 no pun intended 20:50:48 lol :) 20:50:53 took me a sec... 20:50:58 got it. lol 20:51:00 lol 20:52:20 In response to something JF once said on his blog, thinking he was talking about me in error, I lambasted him ( sorta) in c.l.f. He many not return now even to c4th. 20:54:02 If he wasn't the only person at Intellasys that actually talks to the outside world... 20:56:55 Heck, that's not absolutely true. I was contacted recently by another there that is also interested in seeing colorforth on something like the OLPC> 20:56:56 . 20:57:57 CLF got a posting off of some guy at intellasys saying they were not ignoring the hobby crowd 20:58:10 Missed that one. :) 20:58:12 they just didnt have enough of the thumb drives available cuz of problems making them 20:59:07 I've offered to support the hobby community by stripping out the proprietary software from colorforth. I never get a response. 21:00:02 Promises to even create the "Non-discloser" docs using my own lawyer or any documentation they use, goes unanswered. 21:01:30 Applying as a non-payed ( or actually paid by the receipt of the finished product -- they have first approval, obviously) has not bared fruit 21:01:31 . 21:07:22 intellasys is a vaporware outfit 21:07:33 :) 21:07:47 Nothing good will come? 21:07:59 well, they keep announcing stuff and making all thes promises... 21:08:10 indeed they do. 21:15:25 If their claims are true, speed, programability, usefulness to the world... It would be a crime if they don't produce. 21:16:25 I suppose there is an entire culture in technology that allows for organizations that pay people to create nothing all day. 21:16:39 This makes sence to me. 21:16:55 This is a good way to keep your competition busy and out of the way. 21:18:04 In a way, this helps to keep things normalized long enough to build on a companies earlier ideas with out always having to keep up with people you don't control. 21:18:28 lol, a conspiracy. :) 21:40:58 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 22:34:50 --- join: sauvin (n=sauvin@74-136-191-181.dhcp.insightbb.com) joined #forth 22:38:51 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 22:39:45 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 22:52:17 --- quit: crest__ (Read error: 110 (Connection timed out)) 23:00:38 --- quit: edrx (Remote closed the connection) 23:32:01 --- join: mark4_ (n=mark4@63-229-121-143.phnx.qwest.net) joined #forth 23:33:09 --- quit: mark4 (Read error: 110 (Connection timed out)) 23:47:29 --- quit: arke (Read error: 110 (Connection timed out)) 23:48:10 --- quit: forther (Read error: 110 (Connection timed out)) 23:51:26 --- quit: madwork (Read error: 104 (Connection reset by peer)) 23:59:59 --- log: ended forth/08.02.14