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.
> 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.
> --
> 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 mojolicious@googlegroups.com.
> To unsubscribe from this group, send email to
> mojolicious+unsubscribe@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.
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...
On Tuesday, October 2, 2012 6:24:46 PM UTC-3, dch wrote:
> On 2 October 2012 20:50, tempire <gl...@empireenterprises.com<javascript:>> > wrote: > > 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.
> > -- > > 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<javascript:>.
> > To unsubscribe from this group, send email to > > mojolicious...@googlegroups.com <javascript:>. > > 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.
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.
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.
> 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.
> -- > 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 mojolicious@googlegroups.com.
> To unsubscribe from this group, send email to
> mojolicious+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mojolicious?hl=en.
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. :)
