Mojolicious book?

[tempire]

Between the Mojocasts, the Mojolicious documentation, MojoExample, YAPC presentations, the mailing list, IRC channel logs, various blog entries and github repos, there's plenty of information about Mojolicious for both noobs and seasoned developers.  The biggest frustration I've seen for those new to Mojolicious is that they read the documentation in the wrong order, or worse, read API docs instead of the Guides.

(That's a hint folks - if you're having trouble, the recommended learning order is to watch the Mojocasts, then read through the links on http://mojolicio.us/perldoc in the order they're presented.  You'll save yourself weeks of frustration, quite literally)

Even with all that available, every once in a while, we hear a request for a Mojolicious book.

This raises the question - what would a Mojolicious book include, and is it even necessary?  Even more importantly - would you buy it?

There's no need to reiterate the same information in the docs, and example apps are already available.  Book content would have to provide extra value.

Share your thoughts.  Even if you're just starting; especially so.

[Dave Cottlehuber]

> --
> You received this message because you are subscribed to the Google Groups
> "Mojolicious" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/mojolicious/-/37sOXt4QCkIJ.
> To post to this group, send email to mojol...@googlegroups.com.
> To unsubscribe from this group, send email to
> mojolicious...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mojolicious?hl=en.

I'd buy a book, even just as a way of thanking the devs.

In particular I am interested in linking front end stuff via some sort
of binding through mojo to a DB, in my case always CouchDB, and
applying templates on the way through, like mustache or similar. And
then dealing with authentication both using external APIs
twitter/facebook/github/similar, and providing that internally.

HTH
Dave

[Michel]

Hi Dave

Have a look at this framework that I just discovered:
https://speakerdeck.com/u/norbu09/p/planet-express-ship

I played with it yesterday and I must say it works great! Now I am just stuck as I do not know any way of having access to a CouchDB compatible API on my shared hosting platform... I shall try to install Planet-Express-Ship to Heroku but I am not sure it would work...

[Dave Cottlehuber]

On 3 October 2012 16:12, Michel <machs...@gmail.com> wrote:
> Hi Dave
>
> Have a look at this framework that I just discovered:
> https://speakerdeck.com/u/norbu09/p/planet-express-ship

Yes, I already got a copy of it. Many thanks Lenz if you are reading here!

> I played with it yesterday and I must say it works great! Now I am just
> stuck as I do not know any way of having access to a CouchDB compatible API
> on my shared hosting platform... I shall try to install Planet-Express-Ship
> to Heroku but I am not sure it would work...

CouchDB is accessed only over HTTP, so you can use iriscouch or
cloudant as you like.

Feel free to ping me offline or on list if you want a hand getting
something set up.

A+
Dave

[Wes Cravens]

What I think folks are after is basically what other framework books
turn out to be; a tutorial walking through implementations of several
common features used in WebApps. In my opinion Mojolicious references
go to great effort to be accessible for getting started, but then leave
those new to web development hanging once they get to anything non
trivial. My guess is that lots of great features are lost due to folks
not understanding how they could help solve problems. e.g. I consider
Bridges to be a trivial topic but it seems that they are frequently
misunderstood or overlooked as a solution. Think of the title:
'Building HTTP Applications with Mojolicious'.

In my opinion all of the current Mojo references are terse and it takes
a while to digest without the appropriate experience / examples in which
to provide context for the technologies. This isn't a criticism of the
current resources, far from it. I think that the current docs are great
as reference once you figure out where everything is ( it's often
awkward to remember where a particular technology is described in the
guides). I'm just trying to illustrate the difference between reference
and the tutorials/introductions/definitive guides that I think folks are
seeking.

I also don't think that this effort needs to be authored by a core
developer. The core team would want to review the content as it
develops but it may well be better written by someone less familiar with
the 'guts' and more familiar with the difficulties that are experienced
by someone coming at it fresh. In any case, my bet is that one is
published soon, perhaps even being written already.

$0.02.

Wes

[sri]

I think the ideal Mojolicious book for me would be a basic
introduction to all aspects of web development with Perl. Explained
with fully functional but not too complex Mojolicious example
applications, and that anyone could read right after finishing
"Learning Perl" and "Intermediate Perl", without prior web development
experience. :)

--
sebastian

[Stefan]

Hey, guys! How's this book coming??  :D

The Mojo docs are great for reference.  A good book would build on the reference and simple examples, combining them in creative ways that less experienced people wouldn't think to do.  I like the books that have a general theme and guide the reader thru the process of building a much larger and relatively practical application.  2 or 3 total applications ought to do it.

Joel's new pastebin, for example?  Or vti's SSH or VNC client?  What about even sri's own mojolicio.us?  I imagine that mojolicio.us is rather simple, which would be a great app #1.  Definitely include some websockets.  I've been working on a Ubuntu Landscape kind of project that has a client and a server and communicates via websockets.  That'd be a super interesting project to follow!

To me, more frequently than not, responses to questions on this list (and some questions themselves) are way over my head.  I try to follow.  And I read every message on the list in hopes that I'll learn something by osmosis or something -- I don't know.  Therefore, it seems like many of the topics on this list would be great topics to focus on or have in sidebars.

Go in depth on plugins and dissect some of the more popular ones.

Go in depth on commands and instill in the reader the convenience that this feature brings.

For me personally, some in depth discussion about blocking vs. non-blocking.  I'm still struggling to make a performing webapp using DBIx::Class to MySQL.  DBIC doesn't support non-blocking operations to MySQL and therefore Mojolicious will block.  What to do about it?  Just run 1,000 workers and only 1 concurrent connection each?  Switch to Mango?  Are there any good non-blocking RDBMS solutions?

Get into forms and validation.

Focus on including some Javascript like jQuery and Bootstrap.  I've been working a lot with jqGrid.  Building a plugin to handle that would be neat. 

Anyway, I mostly just wanted to bump up the conversation.  I know that all of my feedback is entirely bias.  :D

[Stefan Adams]

Anyone know anything about Web-Entwicklung mit Perl und Mojolicious: Starthilfe für Anfänger by Michael Mangelsdorf?  Seems like it has a decent table of contents...

--

You received this message because you are subscribed to the Google Groups "Mojolicious" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious...@googlegroups.com.

To post to this group, send email to mojol...@googlegroups.com.

Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/groups/opt_out.

[Tekki]

Am Dienstag, 29. Oktober 2013 05:49:17 UTC+1 schrieb Stefan:

Anyone know anything about Web-Entwicklung mit Perl und Mojolicious: Starthilfe für Anfänger by Michael Mangelsdorf?  Seems like it has a decent table of contents...

This book was published in spring 2012, when Mojolicious was around version 2.50. Today we are at 4.52, which is in my opinion too far away from what you read in the book.