Controller and take as much business logic as possible
out of your view.
Best,
Ian
--
Dr Ian Sillitoe
Orengo Group, Structural and Molecular Biology
University College London
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi
...@dryft.net wrote:
On 22 October 2010 05:43, Ian Sillitoe i...@sillit.com wrote:
I have a Catalyst model that runs a system command as part of a search
facility. The system call only takes a fraction of a second so is
processed
inline and this all works fine when tested outside of Catalyst
I have a Catalyst model that runs a system command as part of a search
facility. The system call only takes a fraction of a second so is processed
inline and this all works fine when tested outside of Catalyst and when
called under the Catalyst standalone server. However, when I deploy it to my
Just to rule out the obvious - you try this after uncommenting those lines
from the config options?
from ...
#START_TAG = '?',
#END_TAG = '?',
);
to ...
START_TAG = '?',
END_TAG = '?',
);
(or perhaps):
TAG_STYLE = 'php',
);
Just to rule out the obvious - you try this after uncommenting those lines
from the config options?
Sorry, ignore that bit.
Use TAG_STYLE = 'php' or quote those tag strings as suggested in docs:
START_TAG = quotemeta( '?' )
Hi Anne,
try this:
$c-stash-{result} = $result = $result-page($page)
I figured Michael's answer would sort it actually - that looked exactly the
sort of thing that would could cause the problem you noticed (my bad for not
reading the DBIC::RS-page() docs thorough).
Probably got to a point
Thanks for advice, not always too keen to offload total problems for
free code input, but in this instance after lots of hours spent ...
Quickest way to get the problem fixed.
I haven't got time to test the following just now, but my guess is that it
is how you are assigning the result:
-
Could be wrong, but I think the former is causing the resultset to be
evaluated as an array and is therefore returning all the entries
before the pager is being applied.
Apologies - I was talking rubbish about the usage of stash being the cause
(although I do think the resultset is being
Hi Anne,
I don't have my copy of the book in front of me right now. However, either
way your best bet is to cut and paste your actual code so people on the list
can actually see what the problem is (e.g. the complete code of the method
in your controller and the relevant bit of your TT template
|
'+---'
t/controller_API-SOAP-DataServicesok
t/model_TestDBok
All tests successful.
Files=5, Tests=13, 7 wallclock secs ( 0.07 usr 0.02 sys + 6.32 cusr
0.61
csys = 7.02 CPU)
Result: PASS
--
Ian Sillitoe
CATH Team
/Relationship.pm#belongs_to
Also maybe take a closer look at the usage examples in my last post - that
should really explain the same as above.
Cheers,
--
Ian Sillitoe
CATH Team -- http://cathdb.info
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http
I've tried in vain to figure out where/how/why INSTALL_BASE is set, but
alas I have failed.
Perhaps I'm missing something - are you talking about this:
CPAN::Shell-o('conf', 'mbuildpl_arg', --install_base
$APP_DIR/locallib);
?
--
Ian Sillitoe
CATH Team -- http://cathdb.info
header (not the RPCLiteral style dispatch).
--
Ian Sillitoe
CATH Team -- http://cathdb.info
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com
patches.
--
Ian Sillitoe
CATH Team -- http://cathdb.info
___
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
be crazy not to.
I guess there's:
http://dev.catalystframework.org/wiki/recommended_plugins
or something like:
http://search.cpan.org/~perigrin/Task-Kensho-0.0.4/lib/Task/Kensho.pm
Cheers,
Ian
--
Ian Sillitoe
CATH Team -- http://cathdb.info
/;
Cheers,
Ian
--
Ian Sillitoe
CATH Team -- http://cathdb.info
___
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
: http://dev.catalyst.perl.org/
--
Dr Ian Sillitoe
CATH Team -- http://cathdb.info
___
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
otherwise I'll probably just have to downgrade X::C and postpone the
problem for a rainy day.
Hmmm... it appears that versions of XML::Compile older than 0.93 have been
cleared off CPAN. I was able to find older versions of X::C and X::C::SOAP
by Googling around but it does make it more of an
only 6 days at home during the whole month of
April.)
Andy
- Original Message -
From: Ian Sillitoe [EMAIL PROTECTED]
To: Andy Oram [EMAIL PROTECTED]
Sent: Thursday, April 17, 2008 4:28:34 AM (GMT-0500) America/New_York
Subject: Re: Catalyst Cookbook/Best Practices
Andy,
Thanks for getting
This is a great tutorial - many thanks.
It also introduces Moose as a Object/Class framework which for some reason I
hadn't come across before - at least until I stumbled across a recent
conversation on the IRC channel. While I'm sure I would have seen this soon
enough, I'm very glad I saw this
I'm just getting started on implementing SOAP services in my Catalyst
app so I figured I would try and make sure I'm using the best tools
before I start coding.
Catalyst::Controller::SOAP looks perfect as I'm not doing anything too
complicated yet, really just exposing data via SOAP. However, I
.
Ian
On Wed, Mar 19, 2008 at 11:05 AM, Matt Lawrence
[EMAIL PROTECTED] wrote:
Ian Sillitoe wrote:
This may be more of a DBIx::Class issue - if so, apologies - however I
think it come down to my lack of understanding of exactly what
Catalyst is doing when it loads DBIx::Class modules hence
Thanks for the reply.
No, it's got to do with the fact that you seem to be confused about
what ResultSets and ResultSources are, they're very different things.
So, yes take it to the DBIC mailing list.
Yup, I'm aware of this, but my post was obviously confusing, sorry. My
method was
I'm curious about catalyst best practices regarding exceptions. FWIW I found
the following links outline a neat way of handling Exceptions (i.e. tying
additional functionality to typical HTTP headers) and I'm currently using
this model (not Model) in my application.
as objects, while neat in
concept, isn't necessarily adding a huge amount of new functionality. And it
is more typing :P
Cheers,
Ian
On Fri, Mar 14, 2008 at 3:22 PM, Ashley [EMAIL PROTECTED] wrote:
On Mar 14, 2008, at 5:09 AM, Ian Sillitoe wrote:
I'm curious about catalyst best practices regarding
Ali - I take your point, but I disagree that authors shouldn't write text
books. I like reading good books offline and I appreciate that really good
books take a great deal of time and effort to write. I think it's completely
fair enough that authors of good text books should receive some
at 8:24 PM, Zbigniew Lukasiak [EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 8:35 PM, Ian Sillitoe [EMAIL PROTECTED] wrote:
Hopefully there is a quick and obvious answer to the following - if so,
apologies for the length of this email. Apologies in advance also if
this is
considered off-topic
yup, I'm using reusable TT2 widgets via [% PROCESS widget.tt2 %] to render
given objects (e.g. row of a given table) so I can call them from several
other TT2 pages (and on their own in AJAX calls).
root/src/foo/list.tt2
[% FOREACH foo = list_of_foos %]
[% PROCESS foo/brief_summary.tt2
, Ian Sillitoe [EMAIL PROTECTED] wrote:
Controller/TableA.pm:
$c-{stash}-{row_a} = $c-model('MyDBIC::TableA')-find('id');
$c-{stash}-{template} = 'view_a.tt2';
$c-forward('Catalyst::View::TT');
/root/src/view_a.tt2:
[% rows_b = row_a.get_related_rows( optional = param
Hopefully there is a quick and obvious answer to the following - if so,
apologies for the length of this email. Apologies in advance also if this is
considered off-topic and/or covered in previous threads - I have trawled
around for a while (and recently got Jonathan's book !) but all my solutions
30 matches
Mail list logo