Perl 6 - the future is here, just unevenly distributed

IRC log for #padre, 2015-02-15

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:08 kaare joined #padre
01:15 kaare joined #padre
01:49 asarch joined #padre
01:52 kaare joined #padre
02:25 kaare joined #padre
03:05 kaare ppisar, El_Che, sewi: The website is in https://github.com/PadreIDE​/template.padre.perlide.org
03:07 kaare But of course there is no automatic update from there. I think Gabor has given up for good.
08:17 sewi joined #padre
08:32 Di-ima joined #padre
09:22 toi joined #padre
10:35 El_Che kaare: thx
10:36 El_Che kaare: I have been trying to peek a little in padre lately. I am been busy trying to get Alien::wxWidgets to compile on linux with gtk3 (succes!) and also Wx(.pm) (not working yet, although the compilation failes later than before)
10:37 El_Che I saw some mails on perlporters that the bugshould be fixed with perl 5.20.1 but it's still there
10:37 El_Che warming up perlbrew for the new 5.20.2 :)
11:23 toi joined #padre
11:33 kaare El_Che: So you're not a contributor before?
11:34 kaare To me it seems that Gabor is actively discouraging people to do anything in Padre
11:46 El_Che kaare: I was
11:46 El_Che but I haven't touch the code in a very long time
11:46 El_Che I was using ubuntu's build as it's very upto date now :(
11:47 El_Che I heard there was some build problems for new constributors so I wanted to have a look at that
11:47 El_Che and indeed
11:52 El_Che I'll add the instruction to github once a finish
11:53 El_Che it took me ages to get Alien::wxWidgets built (it take a patch to add support for wxwidgets 3.0.1 as the module only downloads up to 3.0.0)
11:55 El_Che I wonder if it builds ok in windows
12:15 kaare It's me who moved Padre to Github, so I know a bit about that.
12:16 kaare I have no round, or any other form, tuits to do any Padre work though.
12:16 kaare It's a pity. It's bitdecaying rather fast now.
12:16 El_Che I am trying to do a little, like making the build info up to date
12:17 El_Che I even forked it to see what would happen e.g. if I added Moo(se)
12:17 El_Che but before that I need to build it on a recent system :)
12:18 El_Che I had these intructions on my blog, but they are not working anymore due to changes in AlienWidgets and Wx: https://nxadm.wordpress.com/2010/12/10/buil​d-padre-svn-easily-with-perlbrew-and-cpanm/
12:18 El_Che I'll reopen the old wx bug report that is marked as fixed
12:21 kaare El_Che: If you're not part of the https://github.com/PadreIDE you should definitely be so.
12:21 El_Che kaare: I am
12:21 El_Che I have manager rights
12:22 El_Che I don't have a lot of time, but I thought it may help against the stagnation
12:22 El_Che no one will contribute if they don't get it built in the first place
12:22 kaare I think everybody is a manager there :-)
12:23 kaare Sorry I didn't know. It's so rare I'm around, so I forget :-(
12:25 El_Che kaare: you had the biggest tuits doing the migration. No excuses needed/accepted. kaare++
12:28 El_Che the Moo(se) experiment I had in the back of my head would have created a lot of resistance in the past. But with many people not caring, and the possibility of github of creating friendly forks, why not
12:29 kaare I learned a lot about svn to git, Github and trac interfaces. And I had fun.  Couldn't ask for more.
12:29 El_Che the bless keyword does my eyes bleed :)
12:30 kaare Yeah, Moose makes Perl nicer.
12:31 kaare There's a myth it's slow. Perhaps if you do one-time stuff. But for serious work, it tends to speed things up.
12:31 El_Che Most of my perl code, uses Moo (lots of it is cli based)
12:32 El_Che but a thing like padre can use meta programming
12:32 kaare And it does wonders to the layout of your code.
12:32 El_Che I am thinking of plugins and the like
12:33 El_Che I watched rjbs's oscon talks about moose the see if there was something new I should be aware of
12:34 kaare I guess not?
12:36 El_Che nope. A lot of avanced stuff are nice to have but not needed in an early stage
12:36 El_Che coercion and the like
12:36 kaare I could use good plugin ideas w/Moose in another project.
12:37 El_Che having a moose like layout does wonders for readibility
12:38 El_Che a long time ago a implemented a plugin system using moose's mop. It was a build system and the backend was pluggabled. Moose MOP injected a lot of methods automatically so the class to be implemented was minimal
12:39 El_Che of course, a lot of that could be done with roles
12:39 El_Che but that's less l33t :)
12:41 kaare Yeah, but the dificult part is to identify which methods or roles are to be used where and when.
12:42 kaare If you want to have a basic system, where you can add user defined (more or less) roles.
12:46 kaare AFAICS you have to store the names of the roles you want to apply as text, and then apply them upon instantiation.
12:47 kaare Or, as you said, inject methds through the mop. Still, the methods have to be stored somewhere, and injected by name.
12:47 kaare It's a bit fragile. But perhaps the only way.
12:52 El_Che yes, I wrote a radius check client (mostly a wrapper around eapol_test and radclient) that does the text thing
12:53 El_Che # Client run
12:53 El_Che my $client_class = 'RadiusCheck::Client::' . ucfirst($params->{mode});
12:53 El_Che my $client = $client_class->new(
12:53 El_Che ...
12:53 El_Che and so on
12:53 El_Che each class loads a generic role
12:54 El_Che it's the other way around ad you described but it's the same fragile system
13:03 El_Che for a bigger system coercion would be better, or a simple __build_obj method
13:08 kaare Yeah, something like that.
13:43 sewi joined #padre
14:48 dod joined #padre
14:53 dod joined #padre
15:42 dolmen joined #padre
16:56 asarch joined #padre
21:20 dod joined #padre
22:37 dolmen joined #padre

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary