15:00:51 #startmeeting Robot Happy Hour 15:00:51 Meeting started Wed Apr 1 15:00:51 2015 UTC. The chair is catohornet. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:51 The meeting name has been set to 'robot_happy_hour' 15:03:18 #info Mac users: According to core team Ride updates are infrequent. Robot updates are more frequent because core team focus. 15:04:08 #info Any Robot or Ride questions? 15:04:27 how about this: are there any other robot IDEs that people like? 15:04:47 hello catohornet :) 15:04:49 PhilShea: great question 15:05:00 I've been using PyCharm with the intellibot plugin. 15:05:00 hello plaurin :) 15:05:21 and I'm having fair but not great results. 15:05:43 Is anyone using others IDEs? 15:06:11 PhilShea: no but I would like to hear about other IDEs too 15:06:13 Or does anyone want to compare experiences with intellibot. 15:06:48 I've found two plugins for pycharm/intellij. 15:07:04 https://wiki.opendaylight.org/view/TSC:Main#Agenda 15:07:21 give me a minute, I'm bringing up my cheatsheet of the differences... 15:07:33 I've not used this plugin but am intrigued by the idea. 15:08:35 I like that I can run both python scripts and robot scripts from the same window. 15:09:26 The problem I was having with RIDE is that if you make changes too fast, it sometimes gets confused. And it won't link to python definitions. 15:09:47 PhilShea: Me too! 15:10:39 Yeah, I tend to make a lot of typing mistakes and doing a lot of ctrl-z. 15:10:59 RIDE sometimes doesn't like me to do that. 15:11:26 There's an eclipse plug-in too. 15:11:49 but I wasn't able to get "go to definition" to work with that. 15:12:43 I have an IDE comparison table that I made. I wonder if there's an easy way to share that. 15:13:39 PhilShea: I tend to have that problem when using RIDE exported from a remote system. 15:14:03 PhilShea: google docs? 15:14:28 Oh sure, I can do that. 15:15:27 Thank you for creating a comparison table! 15:16:06 * plaurin looking at pycharm/intellij plugin 15:16:34 It would be good if others could try it too. I've had intermittent luck with some of the features - I've I'm doing something wrong, maybe someone could teach me the trick to doing it right. 15:17:57 I should have this table ready to share in a couple minutes. 15:18:07 I have just spent few (tens of) minutes looking at various IDEs to use for Robot, but so far I am not impressed (various shallow reasons). I think that for near future I will continue to use an ordinary text editor (mcedit), doing all the stuff manually. 15:18:52 PhilShea: Thanks 15:21:07 https://docs.google.com/document/d/1_Ynrylj8mJXib81AIQGPVfPM4tAtm7J34ajNPfUX8Tg/edit?usp=sharing 15:26:59 So, is there a requirement/recommendation on Robot file formatting (aligned column in Settings table, but exactly 4 spaces everywhere else)? 15:28:19 vrpolak: I would go with how RIDE formats .txt files. 15:30:37 catohornet: Ok, will do. 15:32:56 Next questions: Should Robot file contain a licence header? If yes, is there an example file (to copy and paste from)? 15:33:49 I was wondering about that too. 15:35:17 I've never seen a requirement for using a license header. 15:37:39 http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#copyright-and-license 15:38:17 I vaguely recall Thanh was submitting patches to add license headers to Java, Python and Bash files, so maybe we should ask him about his opinion. 15:41:18 I think no Robot file is included in ODL release (the .zip file) so perhaps licences are not strictly needed. 15:44:04 vrpolak: True, we don't release test cases or the testing framework. 15:48:05 PhilShea: Would you like us to add to your comparison chart? 15:48:19 vrpolak: how does RIDE handle the pipe format of your robot suites? is it ok? I know when I opened it in intellij, it was not working. 15:49:01 catohornet: sure, were you able to read it? I can open it for edit too, if you like. 15:49:33 now open for edit: https://docs.google.com/document/d/1_Ynrylj8mJXib81AIQGPVfPM4tAtm7J34ajNPfUX8Tg/edit?usp=sharing 15:49:52 PhilShea: No problems reading it. 15:49:55 jamoluhrsen: When I opened a file with pipes, it showed me space-only view. I have not tried saving yet, wait a sec. 15:54:45 jamoluhrsen: It saves with space-only separation. Settings and Variables have second column aligned to 18 chars (may depend on file). Everywhere else it uses 4 spaces exactly, including lines in Settings and Variables with more than 14 characters in first column. 15:56:33 Everywhere else includes lines with comments. 15:57:49 jamoluhrsen: Have you seen my second reply (the one after "wait a sec") before you got disconnected? 15:59:17 I missed it vrpolak. 15:59:20 bad wifi. 15:59:46 jamoluhrsen: It saves with space-only separation. Settings and Variables have second column aligned to 18 chars (may depend on file). Everywhere else it uses 4 spaces exactly, including lines in Settings and Variables with more than 14 characters in first column. 16:01:13 Ok. 16:01:55 BTW, there is some "vim" tweaks you can use to get it to paint the editor with syntax coloring if you are interested. since you said you are just using a text editor for now. 16:02:30 jamoluhrsen: vim tweaks are welcome :) 16:04:35 let me see what I have. one sec. 16:07:19 vrpolak: this is what I have: https://github.com/mfukar/robotframework-vim 16:07:49 works ok for me, but I rarely use vim for editing. maybe 5% or less. the other 95% is in intellij with the robot plugin from jivesoft 16:08:06 jamoluhrsen: I am using mcedit. Few months ago I have searched for Robot syntax highlighting definition file for mcedit. It exists, but not in Debian stable repository, so I have decided I do not need it that much. :) 16:13:49 I have to end the meeting now but please continue your discussion. 16:14:22 #endmeeting