in reply to What does Mojolicious do exactly and is it right for me?

One can read "a framework" as "a set of libraries". As you can see, there are libraries for many kinds of things a developer may stumble upon in web development (for example: cookies, JSON API, templating, web server). CGI module can handle GET/POST parameters, file uploads, HTTP headers, cookies, and build HTML for itself, too, and also allows you to build complex programs, being a part of a bigger system (HTTP Server + CGI script + Templating engine + Data Storage), while Mojo already incorporates "everything" (including signed cookies for session storage, templating engine, a web server...), which makes building both simple and complex applications easier.

Right now I'm writing a CMS for the site of a local progressive rock fan club (it's a strange thing that there are no good CMS's written in such a good web framework, or did I miss something?). A lot of things are already done for me by Mojo, signed cookies help a lot, the most hard part was the database (which I have to implement myself since Mojo is database agnostic). My suggestion is to start writing your web UI in Mojolicious::Lite and see how it goes.

  • Comment on Re: What does Mojolicious do exactly and is it right for me?

Replies are listed 'Best First'.
Re^2: What does Mojolicious do exactly and is it right for me?
by Anonymous Monk on Apr 30, 2013 at 11:55 UTC
    Joel Berger's Galileo might work for you. https://github.com/jberger/Galileo
[reply]

      Well, Galileo is almost what I need, but I'm a little biased against JavaScript, and my browser happened not to support WebSockets (I was surprised because I thought that it was modern enough to support it). More serious issue is requirement to register users manually via admin interface instead of giving users the ability to register themselves.

      I should have probably updated my browser and added the required functionality to Galileo, but I succumbed to NIH syndrome and started everything from scratch. Shame on me.

[reply]
Re^2: What does Mojolicious do exactly and is it right for me? (and CMS?)
by Anonymous Monk on Apr 30, 2013 at 12:10 UTC
    Honestly I never really understood the term CMS, whats the difference to a framework like Mojo?

    Multiple users with different rights to publish or ...?

[reply]

      Usually, with a CMS, there come some predefined user groups and workflows.

      You have different edit pages, and not everybody is allowed to edit all kinds of items. This usually means permission groups on the actions and items.

      Usually, you have rules for publication approval of items, and maybe you can't publish your own items but have to have somebody else from a similar group approve that item.

      Also, asset management like pictures of people, and a structure that keeps things that are used together available together, like a slideshow that accompanies are something I'd expect to find in a CMS.

[reply]
        You have different edit pages, and not everybody is allowed to edit all kinds of items. This usually means permission groups on the actions and items.

        Usually, you have rules for publication approval of items, and maybe you can't publish your own items but have to have somebody else from a similar group approve that item.

        So perlmonks is a special kind of CMS?

        Or are wikis?

[reply]

In Section Seekers of Perl Wisdom