someish

Activity Graph

Page 1 of 3 | Next »

2019-01-29

[22:35:01] someish: has joined #RubyOnRails
[22:35:19] someish: has left #RubyOnRails: ()

2018-02-08

[06:32:59] someish: has joined #RubyOnRails
[13:16:16] someish: Quit: someish

2018-02-07

[01:23:56] someish: Quit: someish
[01:24:17] someish: has joined #RubyOnRails
[05:13:14] someish: Quit: someish

2018-02-06

[20:11:46] someish: has joined #RubyOnRails

2017-12-04

[19:23:32] someish: has joined #RubyOnRails
[19:41:26] someish: Quit: someish
[19:41:47] someish: Client Quit
[19:41:47] someish: has joined #RubyOnRails
[20:49:16] someish: has joined #RubyOnRails
[21:03:45] someish: Quit: someish

2017-11-20

[00:04:13] someish: has joined #RubyOnRails
[00:38:57] someish: Quit: someish

2017-11-19

[22:44:00] someish: has joined #RubyOnRails
[23:58:12] someish: Quit: someish

2017-11-18

[03:07:34] someish: has joined #RubyOnRails
[04:54:04] someish: Quit: someish

2017-11-17

[07:03:39] someish: has joined #RubyOnRails
[07:03:45] someish: Client Quit
[12:25:23] someish: has joined #RubyOnRails
[13:43:43] someish: Quit: someish
[17:48:33] someish: has joined #RubyOnRails
[17:58:25] someish: Quit: someish

2017-11-16

[00:17:47] someish: Quit: someish
[03:42:35] someish: has joined #RubyOnRails
[03:57:52] someish: Quit: someish
[07:01:53] someish: has joined #RubyOnRails
[07:02:07] someish: Client Quit
[14:13:03] someish: has joined #RubyOnRails
[16:47:38] someish: Quit: someish
[17:39:23] someish: has joined #RubyOnRails
[18:20:47] someish: Quit: someish
[18:30:07] someish: has joined #RubyOnRails
[19:01:54] someish: Quit: someish
[20:17:23] someish: has joined #RubyOnRails
[23:25:14] someish: Quit: someish

2017-11-15

[15:29:52] someish: has joined #RubyOnRails
[18:33:41] someish: Quit: someish
[23:19:50] someish: has joined #RubyOnRails

2017-10-23

[16:38:14] someish: has joined #RubyOnRails
[16:52:51] someish: Quit: someish
[18:59:57] someish: has joined #RubyOnRails
[19:00:49] someish: Client Quit

2017-09-28

[15:17:39] someish: has joined #RubyOnRails
[18:43:53] someish: Quit: someish

2017-07-17

[15:07:55] someish: has joined #RubyOnRails
[15:56:47] someish: Quit: someish
[16:17:09] someish: has joined #RubyOnRails
[18:02:42] someish: Quit: someish

2017-07-12

[01:31:01] someish: Quit: someish
[01:49:16] someish: has joined #RubyOnRails
[01:58:53] someish: Quit: someish
[03:51:40] someish: has joined #RubyOnRails
[04:29:33] someish: Quit: someish

2017-07-11

[18:31:15] someish: has joined #RubyOnRails
[19:52:10] someish: Quit: someish
[22:30:57] someish: has joined #RubyOnRails

2017-06-28

[13:48:15] someish: has joined #RubyOnRails
[16:12:18] someish: Quit: someish
[17:05:39] someish: has joined #RubyOnRails
[20:26:54] someish: Quit: someish

2017-05-30

[11:38:52] someish: has joined #RubyOnRails
[19:07:07] someish: Quit: someish

2017-03-22

[00:18:31] someish: Quit: someish

2017-03-21

[23:16:22] someish: has joined #RubyOnRails

2017-03-09

[01:00:14] someish: has joined #RubyOnRails
[02:18:19] someish: Quit: someish
[09:35:29] someish: has joined #RubyOnRails
[13:13:52] someish: Quit: someish

2016-07-29

[15:33:56] someish: has joined #RubyOnRails
[18:22:42] someish: Quit: someish

2016-07-25

[14:37:41] someish: has joined #RubyOnRails
[22:18:18] someish: Quit: someish

2016-07-12

[13:39:35] someish: has joined #RubyOnRails
[14:12:31] someish: Quit: someish
[14:28:08] someish: has joined #RubyOnRails
[14:29:48] someish: Client Quit

2016-06-28

[01:13:53] someish: has joined #RubyOnRails
[02:19:00] someish: Quit: someish
[11:03:54] someish: has joined #RubyOnRails
[11:11:14] someish: Quit: someish

2016-06-26

[12:36:21] someish: has joined #RubyOnRails
[16:02:11] someish: Quit: someish

2016-06-25

[14:05:10] someish: has joined #RubyOnRails
[14:12:48] someish: I’m attemping to initialize an active resource class; however I’m getting an uninitialized constant error. I’m using rails 4.2 and the 4.0 active resource gem. Yes, I’m typing in the correct class name.
[14:46:01] someish: If anyone cares, the file was not being autoloaded because it was erroneously named. I camel cased it.
[14:56:04] someish: Quit: someish

2016-06-20

[03:06:58] someish: has joined #ruby
[03:06:58] someish: has joined #RubyOnRails
[05:06:51] someish: Quit: someish
[13:15:54] someish: has joined #ruby
[13:15:54] someish: has joined #RubyOnRails
[13:18:29] someish: Client Quit

2016-06-19

[11:28:35] someish: has joined #ruby
[11:28:35] someish: has joined #RubyOnRails
[13:53:08] someish: Quit: someish
[17:45:29] someish: has joined #ruby
[17:45:29] someish: has joined #RubyOnRails
[18:58:16] someish: Quit: someish

2016-06-18

[13:52:58] someish: has joined #RubyOnRails
[17:50:03] someish: has joined #ruby
[17:50:16] someish: What’s a more eloquent way to write this: https://gist.github.com/saturday/ffc89e4fd5ad7afe5a9c7971cc2dd080
[17:57:10] someish: I updated the gist.
[17:57:11] someish: https://gist.github.com/saturday/ffc89e4fd5ad7afe5a9c7971cc2dd080
[17:59:08] someish: base_id is set on the first iteration.
[17:59:54] someish: adam12: Exactly.
[18:00:15] someish: The others have a base_id value that equals the id of the first saved task.
[18:01:00] someish: adam12: Exactly.
[18:02:38] someish: I’m reading the docs on each_cons
[18:08:11] someish: jhass: I think your suggestion will save the first index in the array twice.
[18:10:20] someish: jhass: Ahhh. I like it.
[18:12:12] someish: I really like that actually. And since its the end of the line for the object, I’m not super concerned with modifying it inline.
[18:32:13] someish: adam12: Small world. Fellow Software Niagara member.
[21:53:24] someish: Quit: someish

2016-05-31

[02:08:54] someish: Quit: someish

2016-05-30

[23:57:33] someish: has joined #RubyOnRails

2016-05-22

[03:40:48] someish: Quit: someish
[12:50:12] someish: has joined #RubyOnRails
[14:50:14] someish: Quit: someish
[15:01:22] someish: has joined #RubyOnRails
[17:18:41] someish: Quit: someish
[23:43:31] someish: has joined #RubyOnRails
[23:48:25] someish: Quit: someish

2016-05-21

[12:37:03] someish: Ping timeout: 240 seconds

2016-05-20

[14:41:19] someish: has joined #RubyOnRails
[16:12:36] someish: Quit: someish
[21:39:44] someish: has joined #RubyOnRails

2016-05-18

[04:02:34] someish: Quit: someish
[12:25:16] someish: has joined #RubyOnRails
[15:15:03] someish: Quit: someish

2016-05-17

[00:58:11] someish: has joined #RubyOnRails
[00:58:31] someish: has joined #ruby
[01:00:25] someish: Why do I have to write application_results[“app_name”][0][0] to get the first result for that particular “app_name”? Why doesn’t the code I wrote allow me to access it like this application_results[“app_name”][0] … https://gist.github.com/saturday/64daae33bd3050885b7c45a03fc410b4
[01:11:35] someish: Radar: Thanks. I’ll read up.
[02:59:41] someish: morenoh149: Did you try restarting the terminal?
[04:04:05] someish: Quit: someish
[04:04:33] someish: has joined #ruby
[04:04:33] someish: has joined #RubyOnRails
[04:04:38] someish: Client Quit
[22:40:52] someish: has joined #RubyOnRails
[22:43:51] someish: Hey rails super people. I’ve got the following model that requires all kinds of preprocessing in order to get the data I want, but only for one use case. Most other use cases could use the model as a typical mapping to the db. Right now I’ve set up all of said builder methods as class methods. Is there a better way to do this? It currently returns a hash, but I’m concerned it should return an active record model instance inste
[22:43:52] someish: https://gist.github.com/saturday/1a2eaf45f262a63782de8078c71e32f8
[23:22:24] someish: cnk: They definitely are. I started to break them out into a non-active record model.

2016-05-15

[01:38:59] someish: Quit: someish
[11:41:38] someish: has joined #RubyOnRails
[17:09:27] someish: Quit: someish

2016-05-14

[23:06:50] someish: has joined #RubyOnRails

2016-05-10

[11:04:29] someish: has joined #RubyOnRails
[16:05:51] someish: Quit: someish

2016-05-09

[02:10:53] someish: Quit: someish
[14:17:32] someish: has joined #RubyOnRails
[20:21:21] someish: Quit: someish
[20:35:42] someish: has joined #RubyOnRails
[21:28:58] someish: Quit: someish

2016-05-08

[09:03:26] someish: has joined #RubyOnRails
[09:08:04] someish: Ping timeout: 252 seconds
[10:04:35] someish: has joined #RubyOnRails
[10:09:09] someish: Ping timeout: 250 seconds
[11:05:16] someish: has joined #RubyOnRails
[11:10:07] someish: Ping timeout: 260 seconds
[12:06:00] someish: has joined #RubyOnRails
[12:10:47] someish: Ping timeout: 260 seconds
[13:06:46] someish: has joined #RubyOnRails
[13:11:43] someish: Ping timeout: 252 seconds
[13:54:05] someish: has joined #RubyOnRails
[14:20:22] someish: Does anything exist that will let me utilize rails-like helper methods, specifically image_tag, within an embedded coffeescript file?
[17:55:04] someish: Quit: someish
[21:55:00] someish: has joined #RubyOnRails

2016-05-07

[03:54:59] someish: has joined #RubyOnRails
[05:55:38] someish: Quit: someish
[13:19:18] someish: has joined #RubyOnRails
[17:32:27] someish: Quit: someish
[18:12:34] someish: has joined #RubyOnRails
[19:43:00] someish: Is it possible to include an .eco tag inside an .erb tag? i.e. <%= image_tag(<%%= @name %>) %>
[19:45:54] someish: fryguy: I did. It didn’t work using my method. Is there another method?
[19:47:14] someish: fryguy: swan.jpg
[19:49:00] someish: No. That’s the name of the image.
[19:49:10] someish: The file is called “filename.jst.eco.erb”.
[19:49:51] someish: Ahh, the nested tag needs to compile first right?
[19:53:29] someish: fryguy: I don’t have much of a choice if I want to use eco templates, correct? I guess the only other option would be make sure the rails helpers are available as javascript functions, and call those directly from the eco template? Does anything like that exist?
[21:05:35] someish: Quit: someish

2016-05-06

[14:33:46] someish: has joined #RubyOnRails
[20:11:05] someish: Quit: someish

2016-04-27

[19:13:06] someish: has joined #RubyOnRails
[20:15:47] someish: Quit: someish

2016-04-19

[12:45:45] someish: has joined #ruby
[12:45:45] someish: has joined #RubyOnRails
[13:00:57] someish: Quit: someish
[13:01:15] someish: has joined #ruby
[13:01:15] someish: has joined #RubyOnRails
[18:45:27] someish: Quit: someish
[19:38:45] someish: has joined #ruby
[19:38:45] someish: has joined #RubyOnRails
[19:40:15] someish: Client Quit

2016-04-18

[13:26:08] someish: has joined #ruby
[13:26:08] someish: has joined #RubyOnRails
[22:36:53] someish: Quit: someish

2016-04-17

[03:09:37] someish: Quit: someish
[13:20:19] someish: has joined #ruby
[13:20:19] someish: has joined #RubyOnRails
[17:00:47] someish: *.net *.split
[18:46:58] someish: I’m using devise’s confirmable module, and I’ve set it up so that when a user is created, they receive the confirmation email and are asked to enter a password after clicking the confirmation link. The weird thing is that the devise confirmable mailer is sending the raw token instead of the digested token. Also, I’m definitely using the @token variable in the mailer view as everything I’ve read on google suggests.
[22:07:57] someish: Quit: someish

2016-04-16

[00:36:29] someish: has joined #RubyOnRails
[00:36:42] someish: has joined #ruby
[00:38:21] someish: Does anyone know of a good algorithm for equally distributing the items of a large array to the items of a smaller array? For example, I have a patients array, and a clinicians array. I want to assign patients to clinicians so that each clinician has an equal number of patients, up until the last clinician.
[00:42:29] someish: The in_groups active support method seems to give me a good start.
[00:44:49] someish: smalltalker: That should work as well.
[00:51:21] someish: havenwood: I’m fine with that. That’s what the in_groups method seems to do.
[00:51:48] someish: I like what you did though.
[00:57:47] someish: You guys are super helpful. Thank you.
[02:03:08] someish: I have a users table. Any user can be have a role of patient, or clinician. I ned to associate clinicians to their respective patients. How should that association be set up for rails? Right now I have a clinician_patients table, but I’m having some issues with two columns acting as a foreign key to users.
[02:06:56] someish: Right. The problem is I have a users table and a user_roles table that is used to set up a user as a patient or a clinician, but I need to associate clinicians to their respective patients. You’re suggesting I split this up entirely by removing the user_roles table, right?
[02:07:37] someish: So in essence, I’d have a separate table for each role.
[02:08:06] someish: …and a seperate associative entity for each relationship.
[02:08:22] someish: That doesn’t seem scalable.
[02:08:46] someish: havenwood: ^
[02:11:20] someish: thanks havenwood. cheers.
[02:12:01] someish: pwnd_nsfw: But I would have to create an additional table for each additional role.
[02:13:50] someish: I doesn’t seem ideal in terms of scalability. It could become an issue for a scenario where we have many roles; however I’m not even certain I’ll have that issue.
[02:18:09] someish: Lets say I have 100 roles. I’ll have to add 100 tables, and an additional table for every role-to-role association.
[02:20:54] someish: Can’t I just use the clincian_patients entity, and somehow set the foreign keys at run time depending on whether or now the user belongs to an certain role?
[02:21:15] someish: I guess that would solve my problem.
[02:22:18] someish: A sort of: If the user is a clinician, the foreign key to the clincian_patients table is clinician_id. if it is a patient, the foreign key is patient_id.
[04:19:44] someish: Quit: someish
[12:14:58] someish: has joined #ruby
[12:14:58] someish: has joined #RubyOnRails
[15:15:14] someish: Quit: someish
[16:05:04] someish: has joined #ruby
[16:05:04] someish: has joined #RubyOnRails
[16:49:30] someish: Quit: someish
[20:58:34] someish: has joined #ruby
[20:58:34] someish: has joined #RubyOnRails
[22:43:29] someish: What’s the idiomatic way to do this: https://gist.github.com/anonymous/7214cef8852e9e17ea57f5ec1966a878
[23:00:05] someish: Nawn: I like that.
[23:00:31] someish: I like that a lot.
[23:04:47] someish: Fancy pants.
[23:05:35] someish: I wouldn’t really consider the original question a rails question.
[23:09:55] someish: I see what you’re suggesting.
[23:13:18] someish: It sounds like you want to learn about object orientation in ruby.
[23:14:41] someish: flashpoint9: I had a lot of success with this book: http://ruby-doc.com/docs/ProgrammingRuby/

2016-04-15

[21:09:19] someish: Quit: someish
[21:30:13] someish: has joined #ruby
[21:30:13] someish: has joined #RubyOnRails
[23:28:34] someish: Quit: someish