kayloos

Activity Graph

Page 1 of 1

2015-11-03

[01:54:53] kayloos: has joined #RubyOnRails
[01:54:53] kayloos: has joined #ruby
[03:06:10] kayloos: Remote host closed the connection

2015-10-19

[00:58:20] kayloos: has joined #RubyOnRails
[00:58:20] kayloos: has joined #ruby
[02:41:14] kayloos: Remote host closed the connection

2015-10-18

[00:59:22] kayloos: has joined #RubyOnRails
[00:59:22] kayloos: has joined #ruby
[02:45:58] kayloos: Remote host closed the connection

2015-10-15

[22:06:34] kayloos: has joined #RubyOnRails
[22:06:34] kayloos: has joined #ruby
[22:14:23] kayloos: Ping timeout: 256 seconds

2015-10-14

[00:26:56] kayloos: has joined #RubyOnRails
[00:26:56] kayloos: has joined #ruby
[01:59:18] kayloos: Remote host closed the connection

2015-10-12

[00:29:15] kayloos: has joined #RubyOnRails
[00:29:15] kayloos: has joined #ruby
[01:59:52] kayloos: Remote host closed the connection

2015-10-11

[00:33:40] kayloos: Ping timeout: 250 seconds

2015-10-10

[21:41:14] kayloos: has joined #RubyOnRails
[21:41:14] kayloos: has joined #ruby

2015-09-28

[00:42:25] kayloos: Remote host closed the connection

2015-09-27

[00:47:40] kayloos: has joined #RubyOnRails
[00:47:40] kayloos: has joined #ruby
[01:25:19] kayloos: Remote host closed the connection
[16:42:30] kayloos: has joined #ruby
[16:42:31] kayloos: has joined #RubyOnRails

2015-06-18

[09:48:26] kayloos: has joined #RubyOnRails
[09:48:26] kayloos: has joined #ruby
[09:49:31] kayloos: Read error: Connection reset by peer
[09:49:39] kayloos: has joined #RubyOnRails
[09:49:39] kayloos: has joined #ruby
[09:50:44] kayloos: Read error: Connection reset by peer
[09:50:54] kayloos: has joined #RubyOnRails
[09:50:54] kayloos: has joined #ruby

2015-05-31

[00:45:10] kayloos: has joined #RubyOnRails
[00:45:10] kayloos: has joined #ruby

2015-05-30

[00:36:38] kayloos: Remote host closed the connection

2015-05-29

[23:08:30] kayloos: has joined #RubyOnRails
[23:08:30] kayloos: has joined #ruby

2015-05-25

[18:09:37] kayloos: has joined #RubyOnRails
[18:09:37] kayloos: has joined #ruby

2014-03-07

[14:22:30] kayloos: ecualombian: HTML should stay in the .html.erb file, only the data should come from any helpers/controllers
[14:24:24] kayloos: ecualombian: try to explain what you want to do more precisely
[14:37:49] kayloos: ecualombian: I can either help you do things the standard way, or help you dive into the rabbit hole with this recursive function. What do you want?
[14:39:35] kayloos: ecualombian: Ok, so it's not normal to have a recursive function within your views. Instead you should do @comments.each do |comment| etc.
[14:40:31] kayloos: If you have the same view logic all over the place, the way to organize it is to put it into a partial, or a view with a filename that starts with '_', and then render that each place you want it
[14:44:12] kayloos: ecualombian: So which is rendered first? Is it Parent > Child > Grandchild or Granchild > Child > Parent
[14:48:38] kayloos: ecualombian: So call .each first on all the parents, and then call it on each set of children. IE: @parents.each {|p| p.children.each {|c| puts c.title } }
[14:50:39] kayloos: ecualombian: do you want infinite nesting?
[14:55:38] kayloos: ecualombian: Yes, that relationship is called a has-many relationship, since multiple children can have the same parent.
[14:56:02] kayloos: ecualombian: Yes, exactly
[15:03:02] kayloos: ecualombian: hold on for a min
[15:10:25] kayloos: ecualombian: Take a look at the answer in this question: http://stackoverflow.com/questions/4308787/using-rails-polymorphism-for-nested-comments
[15:11:06] kayloos: ecualombian: Pulling out your looping logic that is contaminated with html/erb into a ruby file is a bad idea. You should use partials, like certainty suggested
[15:11:46] kayloos: ecualombian: Plus even if you did pull it out, you would have to find some way of rendering it properly, which is kinda troublesome
[15:13:20] kayloos: ecualombian: The infinitely nested comment problem is quite common, so there will be a lot of resources on the net
[15:14:48] kayloos: ecualombian: no problem. I think coming up with your own approach is awesome, but in terms of using a framework it can often be quite painful.

2013-01-07

[00:19:41] kayloos: greengriminal, there is no html element #create_booking in your html code. That's the problem, assuming you are able to spring a response when clicking on a table cell
[00:21:55] kayloos: greengriminal, and you use the same id on different div's, which is a bad id (see what i did there?)
[01:26:25] kayloos: purpose of gems are for sharing. If you have application specific libraries that you don't want to share, it goes in lib, if you wanna share it, gems are fantastic
[01:27:47] kayloos: why bother package code that are app-specific anyway? that's what i don't get. It's just ruby files anyway
[01:37:24] kayloos: lovin the passive aggressive smileys... really gives a good show
[01:46:49] kayloos: Spaceghost|cloud, so if you're having a dispute with a colleague on how to organize code you won't discuss it, but rather just "refactor"? Seems like a huge doucher to have on a team
[01:48:47] kayloos: You're having a discussion about code organization with strangers on the internet and you're saying "I don't give a shit what you think, my way or the highway". Why have this attitude on an IRC channel but not in the code review?
[01:49:50] kayloos: myself, i discuss things to become smarter, not to force my opinion on others
[01:54:08] kayloos: I agree that lib/ can become that. But I also think that gems can become nuggets of shit. Isn't it about keeping the code clean, and not so much whether it's a module in lib/ or packaged as a gem?
[01:54:50] kayloos: sorry i just inferred an abnormal amount of resentment in the discussion, my mistake
[01:58:23] kayloos: Spaceghost|cloud, also if that code is app-specific? If you're not going to use it in any other project, or it never will be usable in another project?
[02:03:12] kayloos: yfeldblum, ah, ok.
[02:07:21] kayloos: yfeldblum, Spaceghost|cloud assume the preposition that your routes.rb got too big, over 150 lines say, and you want to refactor it by splitting routes into methods by extending ActionDispatch::Routing. Where do you put that code?
[02:09:16] kayloos: Spaceghost|cloud, at some point for LAAAAAAAAARGE projects your routes.rb might get very big, and if you're OCD like me your might want to do something about it
[02:10:11] kayloos: Spaceghost|cloud, did you have a large routes.rb file?? what did you do to refactor?
[02:10:16] kayloos: im genuinely interested
[02:10:28] kayloos: yfeldblum, that's a good idea
[02:18:11] kayloos: yeah whats up with concerns???
[02:19:44] kayloos: concerning me deeply. I really don't like that choice of name
[02:21:34] kayloos: yfeldblum, something else. Trait, badge, stripe
[02:21:51] kayloos: there's a reason im not maintaining rails though
[02:23:07] kayloos: Spaceghost|cloud, Good to know! I consider myself a human being though

2013-01-06

[18:44:02] kayloos: fuck, marry, kill: SQLite, Mongo, MySQL
[18:44:27] kayloos: i would marry mysql, fuck sqlite and kill mongo
[18:47:11] kayloos: ddd do you have a use case for when a postgresql feature that mysql doesn't have has saved you/made development easier?