[Catalyst] Job opening: Software developer, Sanger Institute
Hi, We are looking to hire a couple of good perl developers / informaticians for a 2.5 yr term in the High Throughput Gene Targeting team - http://www.sanger.ac.uk/Teams/Team87 - at the Wellcome Trust Sanger Institute in Hinxton (near Cambridge). The role involves requirements gathering and developing software to support the molecular biology lab. There are also some good informatics projects to do with the data we're gathering. Our lab has about 25 scientists and staff, and currently has a team of five providing software support. We are deep into a couple of large gene- knockout projects (KOMP: http://www.knockoutmouse.org and EUCOMM: http://www.eucomm.org). Some of our software is deployed here: http://www.sanger.ac.uk/htgt The core skills we need are server-side (OO-) perl over relational databases. We use Catalyst, Template Toolkit and Prototype/ Scriptaculous Jquery. If you have equivalent skills and you're interested then you should get in touch. The salary is c. 27k - 37k, and you need to apply using the Sanger's jobs site. The full job details are on the current jobs section of the Sanger site, here - https://jobs.sanger.ac.uk/wd/plsql/wd_portal.show_job? p_web_site_id=1764p_web_page_id=67915 (watch the URL, I notice that it usually gets wrapped and distorted). This project has been fun over the last couple of years (we have a good team). I think it will continue to be that way, plus Sanger is a good place to make contacts with other groups and scientists. If you want to find out more informally then you could also contact me, v...@sanger.ac.uk . Cheers, Vivek -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. ___ 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/
[Catalyst] CatalystX::ListFramework::Builder Error
Hi,
I'm getting this error with LFB 0.41
[error] Caught exception in SomeApp::View::LFB::JSON-process
encountered object 'SomeApp::Model::DB::UsageTerms=HASH(0xdff80f0)',
but neither allow_blessed nor convert_blessed settings are enabled at
/usr/lib/perl5/site_perl/5.8.6/JSON/Any.pm line 423.
Is this a problem with my DBIC model? It refers to a belongs_to in my schema
...
completed_on,
{ data_type = CURRENT_TIMESTAMP, is_nullable = 1, size = undef },
usage_terms,
{ data_type = INTEGER, is_nullable = 0, size = unde
...
__PACKAGE__-belongs_to(usage_terms = 'SomeApp::Schema::UsageTerms');
Thanx,
Dp.
___
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/
[Catalyst] Re: In search of RESTful CRUD holy grail
* Zbigniew Lukasiak zzb...@gmail.com [2009-03-04 21:45]: OK - does that mean that you agree that someone can build a RESTful CRUD with that URI structure? Yes, because one can do with almost *any* URI structure. :-) * Peter Karman pe...@peknet.com [2009-03-04 23:25]: When I hear RESTful URL I interpret that as URI-as-a-noun (or more negatively-defined, URI-with-no-verbs). Perhaps we should use something like REST-friendly URL? [0] e.g., http://www.mail-archive.com/catal...@lists.rawmode.org/msg01712.html Yeah. And URIs-as-nouns is a good goal that should be encouraged, absolutely. URIs should identify resources, not operations, that is true. However, putting too much emphasis on the structure of URIs is at the same time problematic, because while it drives people away from a terrible style, it also pushes them in the direction of another bad style (however a less problematic one, to be sure). They forget to put links into their output documents, instead putting application-specific IDs in there, and then they publish API docs that consist of tables of URI construction rules. Then clients have to be hardwired for the interaction between those IDs and the URI construction rules. Which is exactly the opposite of REST. In REST, URIs are opaque as far as the client code is concerned. Clients only ever know what URIs to follow because they get them as links or build them from forms or URI templates they find in the content of server responses – *at runtime*. Not hardwired in. The documentation of an actually RESTful API explains the format of the server response and where to find links in it, as well as what methods can be used against what type of link, and for what purpose. The server URI structure is totally irrelevant. If it changes tomorrow, and then again the day after, and again next week, you don’t need to care; the response format is the same (or actually, gets extended in compatible ways) so you can still find the links in the right places and the client magically keeps working while the server completely changes its implementation and turns its URI structure upside down. *That* is the point of REST: completely decoupling servers and clients from each other. Good URI design is useful as a usability issue for humans OT1H (bookmarkability, hackability etc are usability concerns), and as a server implementation concern OTOH. But it’s entirely orthogonal to the principles of REST. Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/ ___ 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/
[Catalyst] Catalyst - any good AJAX tutes?
hello there, I would like to use AJAX in my catalyst app. Any good references/tutes to recommend? thanks. K. akimoto ___ 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/
