21:45 <CM-Punk> Hi there. So if I have a plugin_name set in every plugin, and then within another plugin I want to call on an array of all the plugin_names how would I go about doing that?

21:47 <leftylink> hmm, I have a line in my code that reads commands = m.bot.config.plugins.plugins.map { |p| defined?(p::COMMANDS) ? p::COMMANDS : [] }

21:47 <leftylink> possibly relevant, butI dunno, you may have to adapt

21:50 <onewheelskyward> yeah it's not pretty.

21:50 <dominikh> on an unrelated note, anyone want to take Cinch, fix its various API flaws and design Cinch 3.0 under my supervision? :P

21:51 <onewheelskyward> I'm using bot.plugins[].

21:51 <onewheelskyward> dominikh That's tempting. What kind of api flaws are you speaking of?

21:52 <dominikh> if you can't see em, you're not the right man for the job :P – on a more serious note, there's too much coupling. messages take part in the dispatching of messages, the parser is useless without the actual connection, etc

21:52 <onewheelskyward> haha

21:52 <dominikh> and plugins internally just build on the "on" primitive and lots of workarounds that make some things hard

21:53 <dominikh> Cinch is an untestable mess (unit test wise). trying to write those tests reveals many of the internal flaws

21:53 <onewheelskyward> It's funny how that works. I've been through that myself a few times.

21:53 <dominikh> not to mention there are too many ways of using a method ("oh, we'll guess what you meant, just pass any of these 5 types")

21:53 <onewheelskyward> Honestly, I wouldn't have the time to take it on anyhow. But I wouldn't mind contributing.

21:53 <dominikh> personally I don't work on Cinch anymore besides very light maintenance

21:54 <dominikh> most people don't seem to see the many flaws, anyway, so there's no incentive for me to fix them, anyway. and I don't really do ruby anymore, either

21:55 <dominikh> problem is, it would require a rewrite from the ground up. would be easier than fixing it incrementally

21:56 <onewheelskyward> I imagine a re-envisioning of the plugin system would be one of the bigger elements to take on.

21:56 <onewheelskyward> Still loving Go?

21:56 <dominikh> oh I don't mind the plugin system itself (just some of the naming choices. c.plugins.plugins still annoys me)

21:56 <dominikh> yes, still loving Go

21:56 <dominikh> not its community, but the language's nice :P

21:57 <onewheelskyward> It's young yet.

21:57 <dominikh> oh, the community was fine two years ago

21:57 <dominikh> it's not so fine anymore with everyone jumping on it and complaining that it doesn't look like $language_we_already_have :)

21:59 <onewheelskyward> Ah, roger

22:00 <dominikh> I liked the initial community because it was actually invested in the language, understood where it came from and generally had a good understanding of systems programming, unix, etc

22:00 <dominikh> now it's nodejs folks thinking Go is the next thing that'll earn them money

22:02 <CM-Punk> Yeah, I'm still having an issue with this onewheelskyward, I have set :plugin_name in each of my plugins on my bot. I need to use another plugin, help.rb to call on an array of each entry

22:03 <onewheelskyward> You really need to embrace the underpinnings to understand and be successful with a language. Otherwise you're just wasting your time.

22:03 <onewheelskyward> CM-Punk isn't there a built-in help helper already?

22:03 <dominikh> c.plugins.plugins.map {|p| p.plugin_name}

22:05 <dominikh> onewheelskyward: none that will give you an overview of all plugins

22:05 <onewheelskyward> Ah, not exactly built-in: https://github.com/Quintus/cinch-plugins/blob/master/plugins/help.rb

22:06 <dominikh> (there *is* a built-in !help <plugin_name>)

22:06 <dominikh> one of those choices I regret, btw

22:06 <dominikh> should not have been there

22:06 <onewheelskyward> Too implementation-detail?

22:08 <leftylink> it was not sufficient for me; had to do my own. that's actually what my line of code was for

22:08 <dominikh> onewheelskyward: 1) it's half-arsed. most people implemented their own 2) Cinch is an IRC library/framework, not a full-fledged bot framework. "help" being there is weird, we don't have anything else of that kind

22:11 <CM-Punk> @bot.plugins.map {|p| p.class.plugin_name}

22:11 <CM-Punk> That worked

22:14 <dominikh> are you sure? it should be @bot.plugins.plugins, shouldn't it