Ah, yes, I had forgotten about nests and birds. IIRC, they're more like
channels than promises, but channels can serve a similar purpose. So again,
the idea seems to be to leave a token indicating where something should go,
and a token indicating where it should be picked up?
Aside: I haven't expl
On Wed, Sep 11, 2013 at 12:24 AM, David Barbour wrote:
> One PL concept you didn't mention is promises/futures. How might those be
> realized in a UI?
There's precedent: ToonTalk represents promises and resolvers in its
UI as nests and birds. (Some reasons this may miss the mark: It's been
many
Yes, sum (x + y) vs. product (x * y) corresponds to 'or vs. and' or 'union
vs. struct'.
For many purposes, they are very similar: associative, commutative,
identity elements, ability to focus attention and operations on just x or
just y. We can model zippers and lenses for each, which is kind of c
If your sum/product is or/and, I tend to agree there is difficulty. We
chose to use a normalized representation: the same number of factors for
each term, "true" used liberally as a factor. In many cases, there were
only two branches to take. I spent a great deal of time coming up with a
table
This is a good list of concept components.
I think branching should be open - I.e. modeled as a collection where only
one item is 'active' at a time. There is a clear duality between sums and
products, and interestingly a lot of the same UIs apply (i.e.
prisms/lenses, zippers for sum types). (But
Does Minecraft have a way to compile a world (particularly redstone) to
machine code? Is it still a challenge to go from a 3D representation to a
machine language or machine representation? We have at several levels with
Minecraft: the machine, the JVM, Minecraft byte code, Minecraft source
code,
To unify PL and UI:
values: Date Calculator, String Calculator, Numeric Calculator,
Zipper/Document Visualizer
behavior, code: Recorder (the container), Script,
Branch/Table/Conditional/Recursion/Procedure/Function/Method (Unified
Control Structure)
Also, Exceptions (has anyone seen
It may be helpful to view everything as an editor. Something like SUIT
(the Simple User Interface Toolkit):
http://research.microsoft.com/en-us/um/people/rdeline/publications/uist-91.pdf
I'm thinking the web is finally getting to a point where everything is
editable again.
On Tue, Sep 10, 2013 a
On Tue, Sep 10, 2013 at 10:25 AM, David Barbour wrote:
>
> And any "looking under the hood" must be formally represented as
> reflection or introspection, just as it would be in a PL.
>
>
Ideally, as it would be in a secure PL. Cf. Gilad Bracha's Newspeak and the
'Mirrors' concept.
__
I think we cannot rely on 'inspection' - ability to view source and so on -
except in a very shallow way - e.g. to find capabilities directly
underlying a form. Relying on deep inspection seems to have several
problems:
1) First it would take a lot more study and knowledge to figure out the
intent
Thanks for this ref. It looks interesting.
On Mon, Sep 9, 2013 at 7:33 PM, K. K. Subramaniam wrote:
> On Tuesday 10 September 2013 06:24 AM, Alan Kay wrote:
>
>> Check out "Smallstar" by Dan Halbert at Xerox PARC (written up in a PARC
>> "bluebook")
>>
>
> Available online at
> http://danhalber
rlson
>> *To:* Fundamentals of New Computing
>> *Sent:* Monday, September 9, 2013 3:47 PM
>> *Subject:* Re: [fonc] Software Crisis (was Re: Final STEP progress
>> report abandoned?)
>>
>> One thing you can do is create a bunch of named widgets that work
>> to
> --
> *From:* John Carlson
> *To:* Fundamentals of New Computing
> *Sent:* Monday, September 9, 2013 3:47 PM
> *Subject:* Re: [fonc] Software Crisis (was Re: Final STEP progress report
> abandoned?)
>
> One thing you can do is create a bunch
On Tuesday 10 September 2013 06:24 AM, Alan Kay wrote:
Check out "Smallstar" by Dan Halbert at Xerox PARC (written up in a PARC
"bluebook")
Available online at http://danhalbert.org/pbe-html.htm
BTW, Dan Halbert is the author of the "more" command in Unix.
Regards .. Subbu
___
Check out "Smallstar" by Dan Halbert at Xerox PARC (written up in a PARC
"bluebook")
Cheers,
Alan
From: John Carlson
To: Fundamentals of New Computing
Sent: Monday, September 9, 2013 3:47 PM
Subject: Re: [fonc] Software Crisis (was Re:
The trick here is to make the zippers at the meta or schema level.
John
On Sep 9, 2013 6:03 PM, "John Carlson" wrote:
> Also, you could have an input zipper, a flippable conversion area, an
> output zipper, and a history of conversion stack.
> On Sep 9, 2013 5:11 PM, "David Barbour" wrote:
>
>>
Also, you could have an input zipper, a flippable conversion area, an
output zipper, and a history of conversion stack.
On Sep 9, 2013 5:11 PM, "David Barbour" wrote:
> I like Paul's idea here - form a "pit of success" even for people who tend
> to copy-paste.
>
> I'm very interested in unifying
I'd recommend looking into quartz composer on mac os x.
On Sep 9, 2013 5:11 PM, "David Barbour" wrote:
> I like Paul's idea here - form a "pit of success" even for people who tend
> to copy-paste.
>
> I'm very interested in unifying PL with HCI/UI such that actions like
> copy-paste actually have
One thing you can do is create a bunch of named widgets that work together
with copy and paste. As long as you can do type safety, and can
appropriately deal with variable explosion/collapsing. You'll probably
want to create very small functions, which can also be stored in widgets
(lambdas). Wi
I like Paul's idea here - form a "pit of success" even for people who tend
to copy-paste.
I'm very interested in unifying PL with HCI/UI such that actions like
copy-paste actually have formal meaning. If you copy a time-varying field
from a UI form, maybe you can paste it as a signal into a softwa
Good point, Casey - it's not just software. I see shabby service and
workmanship all around, an Industrial Crisis brought on by a preoccupation
with short-term gain... although that in itself is amplified by modern
software/communication technology. Hopefully that will all balance out and
correct
I don't think cut and paste has been the source of the problems with the
systems I've worked on (could be a symptom of one or more of the problems.)
What I see is long-term systems built around short-term, usually
competitive goals, by people who are competing both with one another (for
jobs, promo
22 matches
Mail list logo
