to points in urls for this:
* /user/id/foo
Public viewing of user stuff (public may mean only a restricted
set of users can view it, but it's not private)
* /account/action
For doing stuff that only you can do to your own account (change
password etc)
--
Oliver Charles / aCiD2
rafl!
--
Oliver Charles / aCiD2
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
extra traits, like
Moose::Role. That would give something like~
use MooseX::Role::Parameterized -traits = [
'MooseX::MethodAttributes::Meta::Role' ]
--
Oliver Charles / aCiD2
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http
ERROR: RETARD AT COMPUTER.
Turns out this is *exactly* possible at the moment:
http://github.com/bobtfish/moosex-methodattributes/blob/master/t/param_role.t
Sigh, I feel a little bit dumb now
--
Oliver Charles / aCiD2
___
List: Catalyst
is presented. Then, when the login is successful, the URI
is restored, and the user is redirect.
However... after seeing Devin's approach, which is essentially the
same but without the session, I may change to that. I believe the two
approaches are essentially the same though.
--
Oliver Charles
make use
of caching in your back end models (which are independent of Catalyst,
right!?) with the Cache:: modules, and if you need some Catalyst
integration, then you could use Catalyst::Plugin::Cache.
--
Oliver Charles / aCiD2
___
List: Catalyst
guess JSON::XS is your best option [2]
- but there are a few JSON related modules on CPAN.
--
Oliver Charles / aCiD2
[1]: http://search.cpan.org/~miyagawa/Catalyst-View-JSON
[2]: http://search.cpan.org/~mlehmann/JSON-XS
___
List: Catalyst
://www.catalystframework.org/calendar/2008/14
--
Oliver Charles / aCiD2
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site
).
--
Oliver Charles / aCiD2
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Data::Pageset or even Data::Pageset::Render
Saddly won't work for me because they same to require knowing
total_entries at the point of creation - I did look at them, but for
reasons I couldn't use them. At least I'm pretty sure that's the
problem I had.
- Ollie
On 23 Jan 2009, at 15:00, Jesse Sheidlower wrote:
I like this quite a bit, more than some of the other solutions
which I tried, and think I'll use this.
Glad you like it :)
One question, from an arithmetically-challenged one: How would
I modify this to allow the user to skip by, say, tens?
I might as well join in with this :) Here's what we use at work:
[% IF pager %]
ul class=paginator
li class=counterPage [% pager.current_page %] of [%
pager.last_page %]/li
lia href=[% c.req.uri_with( page = pager.first_page )
%]laquo;/a/li
[% IF pager.previous_page %]
Can you also provide the CSS classes used by this example?
Sure, here it is - not particularly amazing though, but I'm no designer :) [1]:
.paginator ul {
margin: 0;
}
.paginator .counter {
margin-right: 20pt;
}
.paginator li {
display: inline;
}
.paginator li a {
padding:
Hi,
This has hit me a few times, and I've just encountered it again, so I
thought it would be good to ask those wiser than I :)
There have been a few times where I could do with querying the
database (which I'd normally do through $c-model), but this is not
available. For example, I've added the
I'd be very interested in seeing this, as I use Form::Processor
extensively at $work.
On Mon, Nov 24, 2008 at 5:45 PM, Gerda Shank [EMAIL PROTECTED] wrote:
I've Moosified Form::Processor and will eventually release it as a
development release to CPAN, followed by an official release at some
I was considering Lucene as the basis of an text search engine.
Lucence fans claim it's the industry standard.
http://search.cpan.org/~tbusch/Lucene-0.18/lib/Lucene.pm
Mmm, maybe - we've just moved from it to Xipian at $work - same
results but significantly easier to deploy (no longer
Hi,
Sorry for the shakey subject title, but that's the best way I can
think of to sumarise. Anyway, in my project at the moment I often have
forms where the user is moving something, and needs to first search
for a destination. An example is changing the track artist: first the
user searches for
17 matches
Mail list logo