Hi Jens,
On Sun, 2015-01-18 at 20:16 +0100, Jens Gassmann wrote:
> i'm currently building a catalyst-based CMS - it is fully working, but
> needs some help to make it open source and add some more features.
[...]
> For those who are interested in, i will gave a online presentation.
> Please cont
From:
Octavian said:
Imho a beginner should not start by creating "best practice" apps, but
apps
which help him/her to understand each step as easy as possible. She or he
just need to know that there are better ways that will be learned later.
Your 2012 Catalyst Advent Calendar articles "Ca
Hi,
i'm currently building a catalyst-based CMS - it is fully working, but
needs some help to make it open source and add some more features.
Based on Catalyst, Template Toolkit, DBIx::Class, and some more great
Perl-Modules. Multiple Rights and Roles - combined with a great
Drag-n-Drop-Inte
There is at least one other potential newbie entrance point into Catalyst.
That is where he/she installs a fully functional application (generally a
blog, CMS, forums, etc.), then slowly begins contributing within a plugin
architecture, then full applications, as his/her understanding of how the
pa
Octavian said:
> Imho a beginner should not start by creating "best practice" apps, but
> apps
> which help him/her to understand each step as easy as possible. She or he
> just need to know that there are better ways that will be learned later.
>
Your 2012 Catalyst Advent Calendar articles "Catal
From:
I think that one of the main use of Perl is to create web apps.
And the best way of creating web apps is by using a web framework.
And the most developed web framework for Perl is Catalyst.
But those who prefer other frameworks do it because they consider
Catalyst
too complex and hard t
But that really depends on the system, doesn't it? I can install the
usual parts of Catalyst by installing just a few packages on a Debian
(and Debian-derived) systems. It takes a few minutes (less than ten,
surely), but it's an easy process.
Isn't that the primary purpose of distribution pack
I'm rather concerned with that statement, but will allow time for all of
us to sober up.
On 03/01/15 22:44, Lance A. Brown wrote:
Robert Brown wrote on 1/3/2015 5:36 PM:
Is this something we can resolve, or simply make better as its install
process, that maybe needs explaining better?
I don
My greatest concern is only that we keep this accessible, no strings, no
branches, etc.
how can we best do this?
On 03/01/15 22:44, Lance A. Brown wrote:
Robert Brown wrote on 1/3/2015 5:36 PM:
Is this something we can resolve, or simply make better as its install
process, that maybe needs
> I think that one of the main use of Perl is to create web apps.
> And the best way of creating web apps is by using a web framework.
> And the most developed web framework for Perl is Catalyst.
> But those who prefer other frameworks do it because they consider Catalyst
> too complex and hard to
Installation is basically a one shot (especially if you have a
transportable perl compiled with perlbrew of Perl::Build). A framework is
for life not just for a 5 minute "write a blog engine" demo.
On Sun, Jan 4, 2015 at 9:44 AM, Lance A. Brown wrote:
> Robert Brown wrote on 1/3/2015 5:36 PM:
>
Robert Brown wrote on 1/3/2015 5:36 PM:
> Is this something we can resolve, or simply make better as its install
> process, that maybe needs explaining better?
I don't think it can be resolved unless Catalyst wants to move in the
same direction Mojolicious has taken, which I don't agree with.
I h
Is this something we can resolve, or simply make better as its install
process, that maybe needs explaining better?
On 03/01/15 22:26, Lance A. Brown wrote:
Kieren Diment wrote on 1/3/2015 3:43 PM:
3. Catalyst used to be hard to install (and catalyst had a lot of
influence on improving the
Kieren Diment wrote on 1/3/2015 3:43 PM:
> 3. Catalyst used to be hard to install (and catalyst had a lot of
> influence on improving the cpan toolchain during the relatively early
> days), but this isn't the case any more, but the perception lingers in
> places.
Catalyst isn't nearly as difficul
From: Kieren Diment
The catalyst docs could do with a substantial review, they haven't had much
attention lately. In particular there could do with being a good index.
I think the issue with people thinking catalyst is too big/complex is that
lots and lots of developers are used to a pr
I find that getting involved in a project like Catalyst is much like
releasing your own CPAN module - possibly daunting at first, hence some
reluctance?
From my own experience only, it took years to finally find something I
was comfortable to release, but when I did, it then starts to flow.
umm from something they're *more* familiar with.
On Sun, Jan 4, 2015 at 7:43 AM, Kieren Diment wrote:
> The catalyst docs could do with a substantial review, they haven't had
> much attention lately. In particular there could do with being a good
> index.
>
> I think the issue with people think
The catalyst docs could do with a substantial review, they haven't had much
attention lately. In particular there could do with being a good index.
I think the issue with people thinking catalyst is too big/complex is that
lots and lots of developers are used to a procedural approach to dealing
w
From:
http://www.catalystframework.org/calendar/2014/21
"I've also considered making a request for a grant from the Perl Foundation
in order to work on these docs, and wonder what you all think of that :)"
I think that one of the main use of Perl is to create web apps.
And the best way of cre
19 matches
Mail list logo
