Matt Todd wrote:
> [Lots of stuff]
General comment: It's much easier to comprehend posts in mail lists or
reading through the archives if you quote something of what you're
responding to.
> Now, to the requirements talk: how important is the availability of
> revision history in this bare-b
Conrad Schneiker skribis 2006-06-10 15:37 (-0700):
> target spec. (2) Would Juerd be willing to serve as the judge of who
> sufficiently fulfilled the specs?
I would, but perhaps my personal opinions would matter too much to be an
objective judge.
Regards,
Juerd
--
http://convolution.nl/maak_j
> From: Michael Mathews [mailto:[EMAIL PROTECTED]
> Having just been away on yet /another/ training course in Agile
> methodology, I'd say this is a classic disconnect of concerns.
> Sounds
> like Conrad just want something that works, and can be available
> quickly -- a rather traditional customer
I'll be honest and say that I'm not too concerned with the
prize/grant, so that may be the reason I want to go beyond that
minimal ideal. I'm specifically concerned with a poorly designed (or
at least slightly clumsy to upgrade) wiki, all in for the sake of
speed, minimal functionality, and money.
On 11/06/06, Matt Todd <[EMAIL PROTECTED]> wrote:
2) I agree that it is both important and pertinent to get the general
requirements down for the project, but I do see a need and a benefit
to having the architecture forming in the meanwhile. I see how these
things can be connected, obviously, bu
1) Understood. I've been disconnected from Perl for a while, and this
is really the first time I've been participating in the Perl
community. Thanks for the heads-up. :)
2) I agree that it is both important and pertinent to get the general
requirements down for the project, but I do see a need an
Matt Todd wrote:
> On the architecture note, I've written up a quick article about a
> possible implementation of the MVC pattern for the wiki. Indeed,
it's
> a very flexible implementation and really resembles a framework. (To
> be honest, it's from my work on my PHP framework.)
>
> Please take a
Hello,
> From: Michael Mathews [mailto:[EMAIL PROTECTED]
[...]
> On 08/06/06, Matt Todd <[EMAIL PROTECTED]> wrote:
> > Maybe this would be a good time to (semi-)formalize some form of
> > recommendations for the project?
>
> Agreed. (We're talking about the minimal requirements to get the
> thous
[Sorry Michael, I didn't mean to send it you twice. :) ]
I like the RFC idea. I will read up on them and see, if it is a
particular format, how to simplify it. But, most definitely, the
community must have dialog about the requests. For each request
really.
On the architecture note, I've written
On 08/06/06, Matt Todd <[EMAIL PROTECTED]> wrote:
Honestly, I'm not familiar with the Perl way of doing things, but I'm
open to learn especially because I see the Perl community going
through a (much-needed) reform. Thusly, I'm not familiar with the RFCs
(Request For Change?) but I do see the mer
Honestly, I'm not familiar with the Perl way of doing things, but I'm
open to learn especially because I see the Perl community going
through a (much-needed) reform. Thusly, I'm not familiar with the RFCs
(Request For Change?) but I do see the merit for something similar.
However, as far as the j
On 08/06/06, Matt Todd <[EMAIL PROTECTED]> wrote:
Maybe this would be a good time to (semi-)formalize some form of
recommendations for the project?
Agreed. (We're talking about the minimal requirements to get the
thousand for a pswiki, right?) Will this work like the Perl 6
RFC-Roundup, where t
[...]
Also, what is the best place to begin learning the Perl6 syntax? A
tutorial would be great, as a dry technical specification of the
language doesn't teach very well.
IMHO examples teach the best. A table with "Perl5 version" versus "Perl6
version" examples - even one-liners - would be
I was just reading the AES referenced above and I can say now that I'm
really happy about some changes to Regexes, and that a grammar may
well be what we're looking for. However, even with this great tool, we
still have to handle the implementation. Though I can see the benefit
of using the gramma
To bring this back around to the implementation portion in an effort
to get back on topic..
There are also sample grammars (for those who like samples in
addition to docs) available in the parrot source tree, e.g.:
http://svn.perl.org/parrot/trunk/compilers/tge/TGE/Parser.pg
http://svn.perl
I would recommend using a templating system as opposed to having calls
to include files in numerous pages. Even though it's minimal, it's
still duplication, and it can get rather messy.
I know that some people don't know about or don't like it, but I would
recommend setting things up in a Model-V
* Michael Mathews <[EMAIL PROTECTED]> [2006-06-08 13:15]:
> This is the smartest suggestion I've yet seen on the subject,
> but, not being all *that* familiar with Perl6 Grammars (aren't
> they something like contextually-smart regexes?), can anyone
> give an example of Perl 6 code that uses gramma
Michael Mathews wrote:
> This is the smartest suggestion I've yet seen on the subject, but, not
> being all *that* familiar with Perl6 Grammars (aren't they something
> like contextually-smart regexes?), can anyone give an example of Perl
> 6 code that uses grammars and can express some wiki-forma
On 07/06/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
Let's use Perl 6 Grammars to define syntaxes. We are just about
to get this mindblowingly awesome tool for parsing; why insist on
tieing our feet together and having to hop around like that?
This is the smartest suggestion I've yet seen on th
* Thomas Wittek <[EMAIL PROTECTED]> [2006-06-07 15:05]:
> I guess that the architecture/design for such a flexible piece
> of software will be relatively complex.
All I can think of is “YAGNI”.
Defining a syntax in a configuration file doesn’t strike me as a
particularly smart move. You will eith
20 matches
Mail list logo
