Re: [Schecoon] flow control layer

2002-03-04 Thread Stefano Mazzocchi
Antti Koivunen wrote: > > Thanks for your comments! > > Glad to be of help :) > > BTW, I know it's not our first priority, but one idea for the name could > be 'FlowScript'. It doesn't seem to be in wide use and has a nice sense > of 'flow of script' (although the file suffix might be FS ;). A

Re: [Schecoon] flow control layer

2002-03-04 Thread Antti Koivunen
It seems that the syntax is pretty much agreed upon, I look forward to seeing it in action. When you have worked out the details, you could perhaps post a brief summary of the key syntax elements. Ovidiu Predescu wrote: > > ... I was actually thinking of jWeave, which expresses the > interweav

Re: [Schecoon] flow control layer

2002-03-02 Thread Ovidiu Predescu
On Sat, 02 Mar 2002 12:57:20 +0200, Antti Koivunen <[EMAIL PROTECTED]> wrote: > >> function f1( a, b, *args ) > >> { > >> for (var i = 0; i < args.length; i++) { > >> a[i](a, b); > >> } > >> } > >> > > > > Where did I see this syntax? I like this one, so let's stick

Re: [Schecoon] flow control layer

2002-03-02 Thread Antti Koivunen
>> function f1( a, b, *args ) >> { >> for (var i = 0; i < args.length; i++) { >> a[i](a, b); >> } >> } >> > > Where did I see this syntax? I like this one, so let's stick with > it. I eliminates the need to assign ... to a variable, and it avoid > implicit, hidden vari

Re: [Schecoon] flow control layer

2002-03-01 Thread Ovidiu Predescu
On Fri, 01 Mar 2002 19:03:07 +0200, Antti Koivunen <[EMAIL PROTECTED]> wrote: > >>I agree, but would point out that it's possible (to some extent) to > >>have variable number of arguments using an implicit argument array > >>(and a function that's aware of it), e.g. in JavaScript it's common > >

Re: [Schecoon] flow control layer

2002-03-01 Thread Stefano Mazzocchi
Ovidiu Predescu wrote: > > > > On Thu, 28 Feb 2002 16:12:14 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > > No, you didn't get my point: I totally agree that reduced verbosity is a > > good thing for people that are used to a language, but I believe that > > implicit behavior (means 'n

Re: [Schecoon] flow control layer

2002-03-01 Thread Ovidiu Predescu
On Fri, 01 Mar 2002 10:17:39 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > Ovidiu Predescu wrote: > > > > On Thu, 28 Feb 2002 16:12:14 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > > > Ovidiu Predescu wrote: > > > > > > > Blocks of code are declared with curly braces ('{' an

Re: [Schecoon] flow control layer

2002-03-01 Thread Ovidiu Predescu
On Fri, 01 Mar 2002 19:19:37 +0200, Antti Koivunen <[EMAIL PROTECTED]> wrote: > Stefano Mazzocchi wrote: > > Ovidiu Predescu wrote: > > Built-in datatypes are numbers, arrays, dictionaries and function > objects. There is a special type 'void', that has a single possible > value nam

Re: [Schecoon] flow control layer

2002-03-01 Thread Antti Koivunen
Stefano Mazzocchi wrote: > Ovidiu Predescu wrote: Built-in datatypes are numbers, arrays, dictionaries and function objects. There is a special type 'void', that has a single possible value named 'void'. >>>What about 'strings', 'dates' and the like? >>> >>Oh, yes, those too ;-)

Re: [Schecoon] flow control layer

2002-03-01 Thread Antti Koivunen
Ovidiu Predescu wrote: > On Thu, 28 Feb 2002 14:15:32 +0200, Antti Koivunen <[EMAIL PROTECTED]> >wrote: > > >>See the comments below. I'll try to look at things like an average >>web programmer would, so the results might look more like JavaScript >>than Scheme (but JavaScript is a well known l

Re: [Schecoon] flow control layer

2002-03-01 Thread Piroumian, Konstantin
> "Piroumian, Konstantin" wrote: > > > > Good day! > > > > > > > > > > Built-in datatypes are numbers, arrays, dictionaries and function > > > > > > objects. There is a special type 'void', that has a single possible > > > > > > value named 'void'. > > > > > > > > > > What about 'strings', 'dates

Re: [Schecoon] flow control layer

2002-03-01 Thread Stefano Mazzocchi
"Piroumian, Konstantin" wrote: > > Good day! > > > > > > > Built-in datatypes are numbers, arrays, dictionaries and function > > > > > objects. There is a special type 'void', that has a single possible > > > > > value named 'void'. > > > > > > > > What about 'strings', 'dates' and the like? >

Re: [Schecoon] flow control layer

2002-03-01 Thread Piroumian, Konstantin
Good day! > > > > Built-in datatypes are numbers, arrays, dictionaries and function > > > > objects. There is a special type 'void', that has a single possible > > > > value named 'void'. > > > > > > What about 'strings', 'dates' and the like? > > > > Oh, yes, those too ;-) I forgot about them.

Re: [Schecoon] flow control layer

2002-03-01 Thread Stefano Mazzocchi
Ovidiu Predescu wrote: > > On Thu, 28 Feb 2002 16:12:14 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > Ovidiu Predescu wrote: > > > > > Blocks of code are declared with curly braces ('{' and '}'). A block > > > is really an sequential list of expressions. The value returned by the > >

Re: [Schecoon] flow control layer

2002-02-28 Thread Ovidiu Predescu
On Thu, 28 Feb 2002 16:12:14 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > Ovidiu Predescu wrote: > > > Blocks of code are declared with curly braces ('{' and '}'). A block > > is really an sequential list of expressions. The value returned by the > > block is the last expression in the

Re: [Schecoon] flow control layer

2002-02-28 Thread Ovidiu Predescu
On Thu, 28 Feb 2002 14:15:32 +0200, Antti Koivunen <[EMAIL PROTECTED]> wrote: > See the comments below. I'll try to look at things like an average > web programmer would, so the results might look more like JavaScript > than Scheme (but JavaScript is a well known language and does share > some o

Re: [Schecoon] flow control layer

2002-02-28 Thread Stefano Mazzocchi
Ovidiu Predescu wrote: > > Trust the power of open development and trust the open-mindness of the > > cocoon community. > > I do trust the model, but sometime is hard to formulate what you want > to accomplish. True :) > What I've been thinking about is a syntax which emulates the semantic > o

Re: [Schecoon] flow control layer

2002-02-28 Thread Antti Koivunen
Piroumian, Konstantin wrote: >>Hi Ovidiu, >> >> >>>Hi Maciek, >>> >>>... >>> >>>Yes, that's right. Using inner classes you can implement >>>closures. Once you have closures, you can implement continuation >>>passing style (CPS) very easy. Furthermore, any program written in a >>>language with dire

Re: [Schecoon] flow control layer

2002-02-28 Thread Antti Koivunen
See the comments below. I'll try to look at things like an average web programmer would, so the results might look more like JavaScript than Scheme (but JavaScript is a well known language and does share some of the features of real functional languages). Ovidiu Predescu wrote: > On Wed, 27 Fe

Re: [Schecoon] flow control layer

2002-02-28 Thread Piroumian, Konstantin
> Hi Ovidiu, > > > Hi Maciek, > > > > ... > > > > Yes, that's right. Using inner classes you can implement > > closures. Once you have closures, you can implement continuation > > passing style (CPS) very easy. Furthermore, any program written in a > > language with direct continuations can be tra

Re: [Schecoon] flow control layer

2002-02-27 Thread Ovidiu Predescu
On Wed, 27 Feb 2002 11:21:28 +0300, "Piroumian, Konstantin" <[EMAIL PROTECTED]> wrote: > Thanks for a wonderful lecture. Now I understand why Scheme language > is used and why people love/will love it. But all that is possible > with other means too, although it will require implementing > somet

Re: [Schecoon] flow control layer

2002-02-27 Thread Maciek Kaminski
On 27 Feb 2002 at 9:45, Ovidiu Predescu wrote: Hi Ovidiu, > Hi Maciek, > > ... > > Yes, that's right. Using inner classes you can implement > closures. Once you have closures, you can implement continuation > passing style (CPS) very easy. Furthermore, any program written in a > language with d

Re: [Schecoon] flow control layer

2002-02-27 Thread Ovidiu Predescu
On Wed, 27 Feb 2002 12:25:30 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > why isn't simple and friendly positional syntax good enough? (remember: > > > I'm going to ask you to remove half of the things, and then half again, > > > until everything that's there *has* to be there, I'll

Re: [Schecoon] flow control layer

2002-02-27 Thread Ovidiu Predescu
Hi Maciek, On Wed, 27 Feb 2002 12:06:39 +0100, "Maciek Kaminski" <[EMAIL PROTECTED]> wrote: > On 26 Feb 2002 at 19:46, Ovidiu Predescu wrote: > > > On Tue, 26 Feb 2002 19:07:20 +0300, "Piroumian, Konstantin" > > > ... > > > Yes, that's true. We've been using actions to interact with the > > > f

Re: [Schecoon] flow control layer

2002-02-27 Thread Stefano Mazzocchi
Ovidiu Predescu wrote: > > Sorry I'm so late with my response, I was busy with an approaching > deadline... > > On Sat, 23 Feb 2002 13:27:34 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > > - how the sitemap invokes a top level flow function: > > > > > > > > > > > >

Re: [Schecoon] flow control layer

2002-02-27 Thread Maciek Kaminski
On 26 Feb 2002 at 19:46, Ovidiu Predescu wrote: > On Tue, 26 Feb 2002 19:07:20 +0300, "Piroumian, Konstantin" > > ... > > Yes, that's true. We've been using actions to interact with the flow > > controller. So, why do we need another language to describe the flow? Why not > > Java? > > Because J

Re: [Schecoon] flow control layer

2002-02-27 Thread Piroumian, Konstantin
> On Tue, 26 Feb 2002 19:07:20 +0300, "Piroumian, Konstantin" <[EMAIL PROTECTED]> wrote: > > > > As to using a "Component" to do the work, we already have the proper > > > granularity. I.e. Schecoon. Currently we have Actions to help control > > > flow, and we have Matchers and Selectors. > > >

RE: [Schecoon] flow control layer

2002-02-26 Thread Matthew Langham
>> On Sat, 23 Feb 2002 13:27:34 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > Moreover, we must understand that as soon as books start to come out, we > *must* support technologies for longer cycles, even if this sacrifices > elegance and architectural beauty. > > I'm sure Carsten and M

Re: [Schecoon] flow control layer

2002-02-26 Thread Ovidiu Predescu
On Tue, 26 Feb 2002 19:07:20 +0300, "Piroumian, Konstantin" <[EMAIL PROTECTED]> wrote: > > As to using a "Component" to do the work, we already have the proper > > granularity. I.e. Schecoon. Currently we have Actions to help control > > flow, and we have Matchers and Selectors. > > Yes, that

Re: [Schecoon] flow control layer

2002-02-26 Thread Ovidiu Predescu
Sorry I'm so late with my response, I was busy with an approaching deadline... On Sat, 23 Feb 2002 13:27:34 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > - how the sitemap invokes a top level flow function: > > > > > > > > > > > > > >

Re: [Schecoon] flow control layer

2002-02-26 Thread Piroumian, Konstantin
> Piroumian, Konstantin wrote: > > > > >>I'd be more happy if I can describe the flow in a "normal" programming > >>language, where I can express complex flow by writing a program. This > >>is what I'm trying to do in the Schecoon sub-project. Using the Scheme > >>language, and the fact that cont

Re: [Schecoon] flow control layer

2002-02-26 Thread Berin Loritsch
Piroumian, Konstantin wrote: >>I'd be more happy if I can describe the flow in a "normal" programming >>language, where I can express complex flow by writing a program. This >>is what I'm trying to do in the Schecoon sub-project. Using the Scheme >>language, and the fact that continuations are

Re: [Schecoon] flow control layer

2002-02-26 Thread Piroumian, Konstantin
> I think the finite state machine approach is difficult to extend to > complex sites. It is very difficult, and rather limiting, at least for > me as a programmer, to think the application as a finite state machine > only. Any time I need to introduce a new state in my application, I > have to r

Re: [Schecoon] flow control layer

2002-02-23 Thread Stefano Mazzocchi
Ovidiu Predescu wrote: > The way I intend to hook-up the flow control layer into the system is > by having the sitemap invoke flow functions or continuations. Ok. > If you look in the sitemap of Schecoon right now, you'll see the > following things: > > - how flow scripts are made available to

Re: [Schecoon] flow control layer

2002-02-23 Thread Stefano Mazzocchi
Antti Koivunen wrote: > > Ovidiu Predescu wrote: > > > > > I'd be more happy if I can describe the flow in a "normal" programming > > language, where I can express complex flow by writing a program. This > > is what I'm trying to do in the Schecoon sub-project. Using the Scheme > > language, and

Re: [Schecoon] flow control layer

2002-02-22 Thread Antti Koivunen
Ovidiu Predescu wrote: > > I'd be more happy if I can describe the flow in a "normal" programming > language, where I can express complex flow by writing a program. This > is what I'm trying to do in the Schecoon sub-project. Using the Scheme > language, and the fact that continuations are first

Re: [Schecoon] flow control layer

2002-02-22 Thread Ovidiu Predescu
Hi Kevin, On Fri, 22 Feb 2002 15:27:10 -0600, [EMAIL PROTECTED] wrote: > Ovidiu and Stefano, > > First, I'm new to cocoon, but not the methodology. Welcome! One more head to think about problems and come up with a way to solve them ;-) > I'm in the process of prototyping a conversion from a h

Re: [Schecoon] flow control layer

2002-02-22 Thread Kevin . Ross
<[EMAIL PROTECTED] cc: [EMAIL PROTECTED] .com> Subject: [Schecoon] flow control layer (WAS Re: [RT] Sources and Drai

[Schecoon] flow control layer (WAS Re: [RT] Sources and Drains (long response))

2002-02-22 Thread Ovidiu Predescu
On Fri, 22 Feb 2002 17:05:13 +0100, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > I think that the addition of Actions can attest to that. Lets take > > Cocoon and instead of a web application platform lets place it in the > > light of a web services platform (all XML all the time). > > [sni