(10) why didn't anyone tell me to give a dress rehearsal presentation
beforehand? <g>
(9) so /that's/ what my stupid video card insists on doing with the
video out port
(8) oh. I cannot cover three hours of material in forty minutes?
(7) If I want a connection with the audience I might have to shut up some.
(6) "Five minutes?!!"
(5) no, it is /not/ "neat that the simple illustrative example turns out
to touch on a lot of advanced features"
(4) anything introduced with "let's quickly..." should be done quickly
(3) You shoulda seen the slides!
(2) OK, this will be easier: anyone /not/ working on their own version
of Cells, raise your hand.
...and the number one lesson learned by Kenny from his ILC2003 talk....
(1) Make free libraries, not presentations.
Annotations:
(10) I would have, but no one was available in the 20 minutes between
when I finished preparing the presentation and when it began.
(3) On-line and annotated, RSN.
(2) I knew there was a lot of prior art, now I know there is a lot of
parallel art. I call it the Lisp of Paradigms. First used and loved in
1962. Loved and used by a happy few all along. Had a spike of interest
for a few years. "Dead" and busting out all over.
(1) Well, talks are still fun and the ensuing conversations have me all
excited about a Deep Rewrite. But doing Cello, the Universal CL GUI will
get people to Actually Use(tm) Cells, not yakking.
--
http://tilton-technology.com
What?! You are a newbie and you haven't answered my:
http://alu.cliki.net/The%20Road%20to%20Lisp%20Survey
Kenny Tilton <·······@nyc.rr.com> writes:
> (2) OK, this will be easier: anyone /not/ working on their own version
> of Cells, raise your hand.
"I'm not!". I did write the computational substrate for a spreadsheet
app, though, in a very "spreadsheety" manner (including sparse 3D
arrays for the spreadsheet). Never got around to write a GUI for it,
though. And it did handle circular dependencies, in that it made "one
round" of updates automatically and if you wanted more, you need to
call the update routine explicitly.
//Ingvar
--
Warning: Pregnancy can cause birth from females
Ingvar Mattsson wrote:
> Kenny Tilton <·······@nyc.rr.com> writes:
>
>
>>(2) OK, this will be easier: anyone /not/ working on their own version
>>of Cells, raise your hand.
>
>
> "I'm not!". I did write the computational substrate for a spreadsheet
> app, though, in a very "spreadsheety" manner (including sparse 3D
> arrays for the spreadsheet). Never got around to write a GUI for it,
> though. And it did handle circular dependencies, in that it made "one
> round" of updates automatically and if you wanted more, you need to
> call the update routine explicitly.
Did you track dependencies or just sweep across the whole range of cells
on every turn?
kenny (thinking my census is still at zero <g>)
--
http://tilton-technology.com
What?! You are a newbie and you haven't answered my:
http://alu.cliki.net/The%20Road%20to%20Lisp%20Survey
Kenny Tilton <·······@nyc.rr.com> writes:
> Ingvar Mattsson wrote:
> > Kenny Tilton <·······@nyc.rr.com> writes:
> >
> >>(2) OK, this will be easier: anyone /not/ working on their own version
> >>of Cells, raise your hand.
> > "I'm not!". I did write the computational substrate for a spreadsheet
> > app, though, in a very "spreadsheety" manner (including sparse 3D
> > arrays for the spreadsheet). Never got around to write a GUI for it,
> > though. And it did handle circular dependencies, in that it made "one
> > round" of updates automatically and if you wanted more, you need to
> > call the update routine explicitly.
>
> Did you track dependencies or just sweep across the whole range of
> cells on every turn?
Tracking dependencies on change, caching data, forcing propagation to
non-cyclic cells (or cyclic cells untouched) once cached value
changes, if I remember correctly. I can mail you the code if you want
it, it mentions "cells" a lot, but they're (as I said) firmly attached
to a spreadsheety substrate. There's even load/store functionality in
there.
//Ingvar
--
My posts are fair game for anybody who wants to distribute the countless
pearls of wisdom sprinkled in them, as long as I'm attributed.
-- Martin Wisse, in a.f.p
Ingvar Mattsson wrote:
> Kenny Tilton <·······@nyc.rr.com> writes:
>
>
>>Ingvar Mattsson wrote:
>>
>>>Kenny Tilton <·······@nyc.rr.com> writes:
>>>
>>>
>>>>(2) OK, this will be easier: anyone /not/ working on their own version
>>>>of Cells, raise your hand.
>>>
>>>"I'm not!". I did write the computational substrate for a spreadsheet
>>>app, though, in a very "spreadsheety" manner (including sparse 3D
>>>arrays for the spreadsheet). Never got around to write a GUI for it,
>>>though. And it did handle circular dependencies, in that it made "one
>>>round" of updates automatically and if you wanted more, you need to
>>>call the update routine explicitly.
>>
>>Did you track dependencies or just sweep across the whole range of
>>cells on every turn?
>
>
> Tracking dependencies on change, caching data, forcing propagation to
> non-cyclic cells (or cyclic cells untouched) once cached value
> changes, if I remember correctly. I can mail you the code if you want
> it, it mentions "cells" a lot, but they're (as I said) firmly attached
> to a spreadsheety substrate. There's even load/store functionality in
> there.
<g> OK, Ingvar, put your hand down, we are looking for people /not/
working on something like Cells. Both me and Mark Giulano who works on
the very similar COSI system explain our hacks as "spreadsheets for
internal progam state".
Your code would be fun to see. The latest version of mine is in the
RoboCup project at SourceForge.
kenny (still looking for someone /not/ doing Cells)
--
http://tilton-technology.com
What?! You are a newbie and you haven't answered my:
http://alu.cliki.net/The%20Road%20to%20Lisp%20Survey
Kenny Tilton writes:
> <g> OK, Ingvar, put your hand down, we are looking for people /not/
> working on something like Cells. Both me and Mark Giulano who works on
Here I am. Do I win anything?
Paolo
--
Paolo Amoroso <·······@mclink.it>
Kenny Tilton wrote:
>
>
> Ingvar Mattsson wrote:
>
>> Kenny Tilton <·······@nyc.rr.com> writes:
>>
>>
>>> Ingvar Mattsson wrote:
>>>
>>>> Kenny Tilton <·······@nyc.rr.com> writes:
>>>>
>>>>
>>>>> (2) OK, this will be easier: anyone /not/ working on their own version
>>>>> of Cells, raise your hand.
>>>>
>>>>
>>>> "I'm not!". I did write the computational substrate for a spreadsheet
>>>> app, though, in a very "spreadsheety" manner (including sparse 3D
>>>> arrays for the spreadsheet). Never got around to write a GUI for it,
>>>> though. And it did handle circular dependencies, in that it made "one
>>>> round" of updates automatically and if you wanted more, you need to
>>>> call the update routine explicitly.
>>>
>>>
>>> Did you track dependencies or just sweep across the whole range of
>>> cells on every turn?
>>
>>
>>
>> Tracking dependencies on change, caching data, forcing propagation to
>> non-cyclic cells (or cyclic cells untouched) once cached value
>> changes, if I remember correctly. I can mail you the code if you want
>> it, it mentions "cells" a lot, but they're (as I said) firmly attached
>> to a spreadsheety substrate. There's even load/store functionality in
>> there.
>
>
> <g> OK, Ingvar, put your hand down, we are looking for people /not/
> working on something like Cells. Both me and Mark Giulano who works on
> the very similar COSI system explain our hacks as "spreadsheets for
> internal progam state".
>
> Your code would be fun to see. The latest version of mine is in the
> RoboCup project at SourceForge.
>
> kenny (still looking for someone /not/ doing Cells)
I'm not working a Cells-alike(tm) system.
--
Doug Tolton
(format t ···@~a~a.~a" "dtolton" "ya" "hoo" "com")