Re: [Catalyst] Catalyst::Manual::Tutorial::01_Intro
On 13/09/2011 16:45, Chris Stinemetz wrote: If you type netstat -tupan | grep 22 in the VM console, do you get anything? (That should show if there is an SSH daemon on port 22.) tcp 0 0 0.0.0.0:22 0.0.0.0:*LISTEN 1153/sshd tcp6 0 0 :::22 :::*LISTEN 1153/sshd Do you have a DHCP server on your network ? That output suggests to me that no IP address has been assigned to eth0. The VM uses DHCP to assign an IP address. In NAT'd mode the VM host software, such as VMPlayer or VirtualBox, will use it's own internal DHCP server but in bridged mode you will need one available on the local network. Simon. ___ 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/
Re: [Catalyst] The Netiquette thread (OT)
On 28/4/09 09:59, Ian Wells wrote: Top posting is bad. Bottom posting is bad. Actually, it's mostly the inconsistency that's bad. I'm on several lists that work just fine with top posting. These are the basics of old-fashioned usenet netiquette, of which there are more comprehensive guides elsewhere. But if you take in these two points, all our current problems will end. People coming to open source and email lists from a corporate environment will not be familiar with this, we ought to take more time to educate people on the whys of using the usenet style. It really isn't at all obvious to people used to corporate email. If you want to be helped, you'll get more sympathy from the people with the knowledge you need if you follow these guidelines. Agreed ! If you are offering help, I assume you want to aid the community, and driving people away from the mailing list with petty annoyances is not going to achieve that. Most certainly true. Be liberal in what you accept and strict in what you send. Or as my dear old mother used to say if you can't think of anything nice to say, don't say anything at all :-) S. ___ 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/
Re: [Catalyst] The Netiquette thread (OT)
On 28/4/09 11:13, J. Shirley wrote: Addendum: Don't drive away prolific responders by responding to single lines uttered as an aside, because you have your own gripes. You mean me, obviously. In response all I'll say is that I picked you up when you had repeatedly complained about top posting. It wasn't in response to a single line but your repeated complaint and in particular you automatically complaining about top posting when the OP hadn't done any such thing in the case to which I responded. But I'm sorry if I caused you any offence, I realise that I was in danger of trolling which wasn't my intention at all. That's why I didn't continue the discussion. You are more helpful on the list that I am, as you know more about Catalyst that I do, so I don't really have a good position from which to criticise. I did consider sending this as a private email but I'll send it back to the list to acknowledge that meta-complaints just don't help. I'll endeavour not to repeat the mistake ! Rgds, Simon. ___ 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/
Re: [Catalyst] Can't seem to use forward or detach. Any special requirements?
On 27/4/09 13:35, J. Shirley wrote: STOP. TOP. POSTING. He didn't. It was a whole message without any previous content. Arguably this might have been a new thread but it seems to continue the thread so I think it was OK. Since you're whining about posting etiquette, can I ask you to trim your posts properly, including just the relevant context to your reply. Bottom posting without trimming is just as bloody annoying as top posting. Thx. S. ___ 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/
Re: [Catalyst] how to reuse Catalyst Schema for non-web purposes?
On 23/4/09 03:59, kakim...@tpg.com.au wrote: From the Catalyst tutes, I seem to get the impression that pretty much a lot of the business logic is done in the controller. Yes, because it's a Catalyst tutorial not a tutorial for whatever model provider you choose to use. You *can* put your logic in the controller and if all you will ever build is a single web app that doesn't need to talk to anything else then that's fine. The general experience is that, in the long term, making the web app a simple layer over a standalone model is more flexible, easier to extend and easier to test. But it's up to you, I suggest reading more widely around the concepts behind MVC and do whatever works best for you. As Kieren says, you'll learn by experience :-) Best of luck. Simon. ___ 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/
Re: [Catalyst] how to reuse Catalyst Schema for non-web purposes?
On 22/4/09 14:52, Matt S Trout wrote: On Wed, Apr 22, 2009 at 02:41:34PM +1000, kakim...@tpg.com.au wrote: I just looked at my app and found that I need to reuse the Schema files found in my 'Schema' directory. Your DBIC classes aren't connected to the Catalyst app at all. Unless you've fallen into the trap of putting business logic in your Controller classes. See this as a good opportunity to refactor the logic back into the Schema classes where it belongs (or to a set of business objects if that suits your application better). Your code will be better for it :-) S. ___ 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/
Re: [Catalyst] how to reuse Catalyst Schema for non-web purposes?
On 22/4/09 23:03, kakim...@tpg.com.au wrote: IMO the best place for your business logic is the controller. Then you're wrong, at least in the eyes of many people. http://en.wikipedia.org/wiki/Model-view-controller The Controller is just a layer that converts the input to something that can be passed to the Model and then sends the output back to the user via a View. You *can* put all your logic in the controller but typically you will end up with two problems: 1. Your app is tightly bound to a web framework and adding some other sort of user interaction, or extending the application code elsewhere becomes difficult, which is what started this thread isn't it ? 2. It becomes hard to test as you need to have the web framework running to run the tests. You should be able to test all of the use cases business interactions outside of the web framework. If you can't, then that's a code smell and an indicator that you have too much going on in your Controller classes. The Catalyst Model classes should really be a very thin shim over the top of your DBIx::Class Schema objects which is where all the 'heavy lifting' of the business process takes place. Hope that makes sense, Simon. ___ 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/
Re: [Catalyst] about catalyst authentication
On 18/4/09 09:00, Malloy wrote: I think something is wrong. Please check: Read the docs. http://search.cpan.org/~robm/Cache-FastMmap-1.28/FastMmap.pm If the share_file exists when the process starts it won't be deleted on exit. If it doesn't exist the default is to delete it when the process exits. If you want to be sure of it existing pass undelete_on_exit = 0 to the constructor. S. ___ 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/
Re: [Catalyst] how to confirm before deleteing
Dave Howorth wrote: Paul Falbe wrote: That works thank you very much. Don't know how many google searchs I did trying to find that out! Rodrigo-51 wrote: Paul, how about a javascript confirm() box? ... and if the user has Javascript disabled? Or if you have some like Google's ill-fated prefetch running, caching all the links it finds on a page ? GETing a link should really only be used when the action is idempotent. If it changes stuff then you ought to use a POST via a form button. S. ___ 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/
Re: [Catalyst] ANNOUNCE: SimpleDB - Auth configuration made easy
Matt S Trout wrote: On Mon, Oct 27, 2008 at 03:51:49PM -0700, Darren Duncan wrote: Zbigniew Lukasiak wrote: * Your passwords are stored in the 'password' field in your users table and are not encrypted. This is always a bad idea. If someone ever gets direct database access, they now know each user's mindset as to how they choose passwords This is the catalyst list, not the stating the fucking obvious list. If the purpose of SimpleDB is to make things simple for people with less clue why offer clear text as an option at all ? Since the best practice is to use hashed passwords why not be opinionated about it and not offer anything else ? Surely being opinionated is something we're good at around here ;-) S. ___ 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/
Re: [Catalyst] Re: Catalyst site design drafts feedback thread
Jonathan Rockway wrote: Let's spend our collective efforts doing something other than arguing about colors. Exactly. Leave the design of the site as it is and concentrate on making the the content easier to understand and use. Sprawling inconsistent self-contradictory content is still that no matter what colour you paint it. Make the content easy to find and use and it almost doesn't matter what the design looks like. Information architects hate this design-down approach as much as you core Catalyst developers hate poor APIs. Both desires, easy to use web sites and well thought out adaptable APIs require similar approaches and deep thinking in understanding how the site/code may be used and abused. But I guess I am bikeshedding, I don't have the time to be actively involved in the process so what I say is less important. FWIW, I vote that Matt picks what he likes and goes with it as someone is always going to be unhappy with the end result. S. ___ 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/
Re: [Catalyst] Re: Catalyst site design drafts feedback thread
Matt S Trout wrote: I was thinking about yours but can I get away with asking for all of the above? Given myself and kieren both find most of the other sites objectionable it'd be nice to see why you prefer them. I think you're not the target audience that those sites are trying to reach. As someone else pointed out, those sites are designed to appeal to the bosses who sign off on the decisions as much, if not not more so, than the developers who work with the framework. You, or this list, needs to decide who the audience for the catalyst site is. If it's trying to persuade developers and management to switch to Catalyst then it needs to appeal to those people. By your very position you are in neither of those two groups so perhaps not in a good position to decide what would appeal to them :-) obias's design is good if somewhat shamelessly derivative. That's a complement really as he's trying to speak the visual language that many people will expect to see. BTW - I heartily recommend Web ReDesign: Workflow that Works (http://www.amazon.co.uk/Web-Redesign-Workflow-Voices-Matter/dp/0735714339/) Form follows function, almost always :-) S. ___ 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/
Re: [Catalyst] two Catalyst flaws
Fayland Lam wrote: the first is to load all modules at beginning. I want to ask why? for $c-forward()? I think $c-model() can load when called. why I hate this is because it eats too many memory. one of my App has 80+ pm then it takes 150+M. I can't afford that! You don't mention how you are running the catalyst application, I presume you're using fastcgi or mod_perl or some other long running persistent process ? In which case you want to load everything first, particularly in mod_perl so it can be shared between processes. In any event, the answer is to throw more ram at it, ram is cheap and it's not really worth trying to optimise for low ram conditions. the second one is hard to use model in cron pl. I know we can do something like my $c = MyApp-prepare(); or Catalyst::Model::Adaptor (trust me, that's not so easy or fast) why I can't get a simple $c without function forward, without req, without res. just get $c-model and $c-cache like? I don't want this $c to load any Controller modules or View modules. Catalyst is a web application framework. You have two choices: 1. Use a simple LWP type script in cron to call the necessary web URI and let the server do the heavy lifting; or 2. Make sure you encapsulate the business logic in the model and not in the controller, then you can just load the necessary schema classes and ignore catalyst entirely. In the latter case there's still some work to do if you want to have a shared config file but that's not too hard to figure out. Simon. ___ 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/
