It's funny you say this (albeit in jest), because I've thought to myself many times: "I wonder if Mojolicious will ever be considered 'done'? Not counting the new HTTP/2.0 and other RFC pending changes..." I always think there can't possibly be anything else to add or improve. But then you continue to make excellent subtle documentation or code enhancements, and then you figure out a new feature to add! :D
--
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/d/optout.
--
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/d/optout.
I guess Mojolicious is done. :)
I noticed that subroutines in Mojo source code are ordered alphabetically. Can anyone share how to do that? Is there some magic vim plugin?
1. Digest authentication in Mojo::UserAgent;
2. Full asynchronous API for Minon::Backend (fail_job, finish_job, job_info, list_jobs, remove_job, retry_job);
3. Support UDP in Mojo::IOLoop (may be UNIX sockets too) and asynchronous DNS client;
4. Asynchronous working with files;
5. Likeness AnyEvent::Util::fork_call.
SOCKS 4/5 proxy support for Mojo::UserAgent :)
1) improve documentation- more real live examples instead of "toy size" (foo, bar, Hello World ..) examples
2) improve non-core plugins (not a task of the core Mojolicious project)
Sebastian uses Atom (previously Textmate), not vim, and when I asked he said he does all the documentation manually.
So no magical plugin, just obsessive diligence.
Impossible to do without IO::AIO, which is out of the question for political reasons.
2. Full asynchronous API for Minon::Backend (fail_job, finish_job, job_info, list_jobs, remove_job, retry_job);Not necessary, Mojolicious applications only call ->enqueue, everything else happens in the Minion worker process.
These functions (at least job_info and list_jobs) can be useful for writing administrative web interface to the queue. Of course, for this you can use the synchronous version, but it is not always convenient to do so.
...but we can talk more about this once a web interface actually exists.
Since the complexity would just be too much, very few people would actually be able to write alternative backends.
I noticed that there is no command to generate a command. It could be
great to have
/script/myapp generate command Foo
or something like that which generate the command MyApp::Command::Foo in
the good directory.
Would it be possible to add it ?
SOCKS 4/5 proxy support for Mojo::UserAgent :)This has come up before, i'm not against it, but there needs to be a new abstraction layer first.
Having thought about this some more, i was about to suggest that perhaps something much simpler would work too. Such as a handshake mechanism based on IO::Socket::Socks added to Mojo::IOLoop::Client (much like the TLS code), but as it turns out IO::Socket::Socks currently doesn't even install on OS X. :(
Soooo... it's been over 6 months since our last wishlist thread (https://groups.google.com/forum/#!searchin/mojolicious/wishlist/mojolicious/YK7SrFvEneY/uwr-TZAlGmcJ), a lot has happened since then (5.0 and Mojoconf, yay!), and i believe we are ready for another round.In this thread you can post changes or features you would like to see in Mojolicious, no rules, just blurt away. :)P.S.: Our official roadmap can still be found on GitHub (although it is almost empty now). https://github.com/kraih/mojo/issues?labels=future&state=open
--sebastian
json_like('/foo', qr/bar/, 'match') and also json_unlike would be quite nice to have for testing. Don't know if this has been suggested before.
--
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/d/optout.
It would be great to have some performance and load information available from within the app. For instance, to be able to report from within the app the number of workers, number of requests for each worker, etc.
json_like('/foo', qr/bar/, 'match') and also json_unlike would be quite nice to have for testing. Don't know if this has been suggested before.Please be more specific, what would be the exact semantics? And how is it consistent with json_is, which does an is_deeply comparison?
I would love to see form handling in UserAgent to make filling out forms
easier. I hate having to specify every input in the form when I mostly
want defaults.
Soooo... it's been over 6 months since our last wishlist thread (https://groups.google.com/forum/#!searchin/mojolicious/wishlist/mojolicious/YK7SrFvEneY/uwr-TZAlGmcJ), a lot has happened since then (5.0 and Mojoconf, yay!), and i believe we are ready for another round.
In this thread you can post changes or features you would like to see in Mojolicious, no rules, just blurt away. :)
- Some kind of EventEmitter that allows you to subscribe and emit events from and to any process when using hypnotoad. I think it should support several backends (like Mojo::Plugin::Minion does), ie: File, Mango, Redis
- SSH and Telnet clients on Mojo::IOLoop (meaning non-blocking clients). Probably not very demanded requests, but in my opinion they would help developers to choose mojolicious as a base framework for apps that concentrate several platforms with different interfaces (so you can choose using Mojo::UserAgent or for instance Mojo::SSHClient or Mojo::TelnetClient in a non-blocking way depending on what the target platform supports).
- Some way to overwrite time for testing time related logic. I use an environment variable and read it, something like$mytime = $ENV{MY_MOJO_FAKE_TIME} || time;
Perhaps a wrapper to ->post( form => { ... } )?
my $tx = ...->res->forms( name => 'login' )
->submit({ user => 'me', password => '12345'});
being a shortcut to
my $form = ...->res->dom->at('form name[login]');
my $action = parse_action_from( $form );
my %inputs = parse_inputs_from( $form );
my $tx = $ua->post( $action => form => {
%inputs, user => 'me', password => '12345' } );
my $tx = ...->res->forms( name => 'login' )
->submit({ user => 'me', password => '12345'});
We are currently considering the addition of a Mojo::DOM::val method (like in jQuery, but with support for entire forms) as a first step.
{"authenticity_token" => "FGsjskskdw;dsd;akdw;odkaw;dkaw;2344;ska;sdkad;akdw;doakw==", "source_label" => "Homepage Form"}
We are currently considering the addition of a Mojo::DOM::val method (like in jQuery, but with support for entire forms) as a first step.
SOCKS 4/5 proxy support for Mojo::UserAgent :)
read: Connection reset by peerMojo::Reactor::Poll: Read failed: Mojo::UserAgent: read: Connection reset by peer at /Library/Perl/5.16/Mojo/EventEmitter.pm line 19.Mojo::Reactor::Poll: Read failed: Mojo::UserAgent: read: Connection reset by peer at /Library/Perl/5.16/Mojo/EventEmitter.pm line 19.Mojo::Reactor::Poll: Read failed: Mojo::UserAgent: read: Connection reset by peer at /Library/Perl/5.16/Mojo/EventEmitter.pm line 19.Mojo::Reactor::Poll: Read failed: Mojo::UserAgent: read: Connection reset by peer at /Library/Perl/5.16/Mojo/EventEmitter.pm line 19.
$upload->move_to(
File::Temp->new);
app->validator->error_class('has-error')
Making 'field-with-error' something you can set, e.g.
app->validator->error_class('has-error')
--
You received this message because you are subscribed to a topic in the Google Groups "Mojolicious" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mojolicious/mIRRwNwDLSE/unsubscribe.
To unsubscribe from this group and all its topics, 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/d/optout.
--
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/d/optout.
To unsubscribe from this group and all its topics, send an email to mojolicious+unsubscribe@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/d/optout.
--
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+unsubscribe@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/d/optout.
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/d/optout.
Soooo... it's been over 6 months since our last wishlist thread (https://groups.google.com/forum/#!searchin/mojolicious/wishlist/mojolicious/YK7SrFvEneY/uwr-TZAlGmcJ), a lot has happened since then (5.0 and Mojoconf, yay!), and i believe we are ready for another round.In this thread you can post changes or features you would like to see in Mojolicious, no rules, just blurt away. :)
P.S.: Our official roadmap can still be found on GitHub (although it is almost empty now). https://github.com/kraih/mojo/issues?labels=future&state=open
----sebastian
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.
I'd like to see the Validation thingy working on JSON parameters ($c->req->json)
$validation->required_json('person/address/number')->range(10, 20)
Couldn't this be done without what you described below?