From david.macfarlane2 at mcgill.ca Tue Jan 13 14:53:31 2015 From: david.macfarlane2 at mcgill.ca (Dave MacFarlane) Date: Tue, 13 Jan 2015 14:53:31 -0500 Subject: [Loris-dev] FW: Loris Developers' Workshops In-Reply-To: References: Message-ID: For any Loris developers who didn't receive this email, please see below. - Dave From: david.macfarlane2 at mcgill.ca To: david.macfarlane2 at mcgill.ca Subject: Loris Developers' Workshops Date: Fri, 9 Jan 2015 16:10:09 -0500 Hi all, As I brought up at the ADM, I'd like to get some feedback on the idea of organizing some Loris Developers' Works Hops, inspired by the BrainBrowser workshops that Tarek organized before leaving. The goal would be to transfer all the knowledge about everything developers need to know about Loris. It would be open to anyone (not just the Loris team) who might be interested in working on Loris or knowing how Loris works, but probably starting internally in the lab. There's two ways this could happen: 1. A full day event. 2. A regular hour long weekly event (until finished.) I'd prefer option 2, but I'm not opposed to 1. The type of topics that I'd cover are: 1. Loris code structure (what are different directories, what do they contain) 2. Third party tools used by Loris (composer, smarty, phpunit, PHP_Codesniffer, HTML_QuickForm...) What are they and how are they used? 3. Loris base classes 4. Loris module structure - what are modules and how do they work? (would explain the structure and design of modules in general, not any module in particular -- there's too many) (probably using the BigBrain Loris modules as an example since the modules are simpler) 5. Loris test coverage and coding style -- what gets tested automatically? What doesn't? Why? 6. How do HTTP requests get handled? (Loris entry point, how the dispatching works) 7. How is configuration handled? 8. How are errors handled? 9. Overriding Loris functionality (project directory) 10. Etc Basically, the goal is to transfer enough knowledge in enough depth that a competent developer would be able to sit down and start hacking on Loris, and it would act as a refresher for people who don't hack on the code every day. Where possible, I'd try and include enough historical background to know why things are done the way they are. What I'd mainly like to know is: 1. Are you interested in following a series of workshops about this? 2. What topics would you like to have covered? (Doesn't have to be from the above, those are just generally the type of topic that I have in mind.) If there's enough interest, I'll see what I can do to get it going... Thanks, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordan.stirling at mail.mcgill.ca Tue Jan 20 11:25:36 2015 From: jordan.stirling at mail.mcgill.ca (Jordan Stirling, Mr) Date: Tue, 20 Jan 2015 16:25:36 +0000 Subject: [Loris-dev] FW: Loris Developers' Workshops In-Reply-To: <31235_1421771069_54BE813D_31235_70_1_BAY168-W10C9C6B15E59CFEFCC1BDAF8400@phx.gbl> References: , <31235_1421771069_54BE813D_31235_70_1_BAY168-W10C9C6B15E59CFEFCC1BDAF8400@phx.gbl> Message-ID: Testing reply Sent from my iPhone On Jan 20, 2015, at 11:24 AM, Dave MacFarlane > wrote: For any Loris developers who didn't receive this email, please see below. - Dave ________________________________ From: david.macfarlane2 at mcgill.ca To: david.macfarlane2 at mcgill.ca Subject: Loris Developers' Workshops Date: Fri, 9 Jan 2015 16:10:09 -0500 Hi all, As I brought up at the ADM, I'd like to get some feedback on the idea of organizing some Loris Developers' Works Hops, inspired by the BrainBrowser workshops that Tarek organized before leaving. The goal would be to transfer all the knowledge about everything developers need to know about Loris. It would be open to anyone (not just the Loris team) who might be interested in working on Loris or knowing how Loris works, but probably starting internally in the lab. There's two ways this could happen: 1. A full day event. 2. A regular hour long weekly event (until finished.) I'd prefer option 2, but I'm not opposed to 1. The type of topics that I'd cover are: 1. Loris code structure (what are different directories, what do they contain) 2. Third party tools used by Loris (composer, smarty, phpunit, PHP_Codesniffer, HTML_QuickForm...) What are they and how are they used? 3. Loris base classes 4. Loris module structure - what are modules and how do they work? (would explain the structure and design of modules in general, not any module in particular -- there's too many) (probably using the BigBrain Loris modules as an example since the modules are simpler) 5. Loris test coverage and coding style -- what gets tested automatically? What doesn't? Why? 6. How do HTTP requests get handled? (Loris entry point, how the dispatching works) 7. How is configuration handled? 8. How are errors handled? 9. Overriding Loris functionality (project directory) 10. Etc Basically, the goal is to transfer enough knowledge in enough depth that a competent developer would be able to sit down and start hacking on Loris, and it would act as a refresher for people who don't hack on the code every day. Where possible, I'd try and include enough historical background to know why things are done the way they are. What I'd mainly like to know is: 1. Are you interested in following a series of workshops about this? 2. What topics would you like to have covered? (Doesn't have to be from the above, those are just generally the type of topic that I have in mind.) If there's enough interest, I'll see what I can do to get it going... Thanks, Dave _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca http://www.bic.mni.mcgill.ca/mailman/listinfo/loris-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From waveflux at gmail.com Tue Jan 20 16:06:03 2015 From: waveflux at gmail.com (Tom Beaudry) Date: Tue, 20 Jan 2015 16:06:03 -0500 Subject: [Loris-dev] FW: Loris Developers' Workshops In-Reply-To: References: Message-ID: Hi, I'd be interested in attending! Have a nice day, Tom On Tue, Jan 13, 2015 at 2:53 PM, Dave MacFarlane < david.macfarlane2 at mcgill.ca> wrote: > For any Loris developers who didn't receive this email, please see below. > > - Dave > > ------------------------------ > From: david.macfarlane2 at mcgill.ca > To: david.macfarlane2 at mcgill.ca > Subject: Loris Developers' Workshops > Date: Fri, 9 Jan 2015 16:10:09 -0500 > > > Hi all, > > As I brought up at the ADM, I'd like to get some feedback on the idea of > organizing some Loris Developers' Works Hops, inspired by the BrainBrowser > workshops that Tarek organized before leaving. The goal would be to > transfer > all the knowledge about everything developers need to know about Loris. It > would be open to anyone (not just the Loris team) who might be interested > in > working on Loris or knowing how Loris works, but probably starting > internally > in the lab. > > There's two ways this could happen: > 1. A full day event. > 2. A regular hour long weekly event (until finished.) > > I'd prefer option 2, but I'm not opposed to 1. > > The type of topics that I'd cover are: > > 1. Loris code structure (what are different directories, what do they > contain) > 2. Third party tools used by Loris (composer, smarty, phpunit, > PHP_Codesniffer, HTML_QuickForm...) > What are they and how are they used? > 3. Loris base classes > 4. Loris module structure - what are modules and how do they work? > (would explain the structure and design of modules in general, not any > module > in particular -- there's too many) > (probably using the BigBrain Loris modules as an example since the > modules are > simpler) > 5. Loris test coverage and coding style -- what gets tested automatically? > What doesn't? Why? > 6. How do HTTP requests get handled? (Loris entry point, how the > dispatching works) > 7. How is configuration handled? > 8. How are errors handled? > 9. Overriding Loris functionality (project directory) > 10. Etc > > Basically, the goal is to transfer enough knowledge in enough depth that a > competent > developer would be able to sit down and start hacking on Loris, and it > would act as a > refresher for people who don't hack on the code every day. Where possible, > I'd try and > include enough historical background to know why things are done the way > they are. > > What I'd mainly like to know is: > > 1. Are you interested in following a series of workshops about this? > 2. What topics would you like to have covered? > (Doesn't have to be from the above, those are just generally the type > of topic that I have in mind.) > > If there's enough interest, I'll see what I can do to get it going... > > Thanks, > Dave > > _______________________________________________ > Loris-dev mailing list > Loris-dev at bic.mni.mcgill.ca > http://www.bic.mni.mcgill.ca/mailman/listinfo/loris-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.desrosiers at criugm.qc.ca Tue Jan 27 09:37:11 2015 From: mathieu.desrosiers at criugm.qc.ca (Mathieu Desrosiers) Date: Tue, 27 Jan 2015 09:37:11 -0500 Subject: [Loris-dev] loris issues Message-ID: Hi Loris team, Updating Cima-q loris installation failed with error message require_once(/srv/loris/cimaq/htdocs/../vendor/autoload.php): failed to open stream: No such file or directory in /srv/loris/cimaq/htdocs/main.php on line 6, referer: http://loris.cima-q.ca/ I cannot find this vendor/autoload.php anywhere. Is someone have any idea???? Thanks ? Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.macfarlane2 at mcgill.ca Tue Jan 27 10:16:50 2015 From: david.macfarlane2 at mcgill.ca (Dave MacFarlane) Date: Tue, 27 Jan 2015 10:16:50 -0500 Subject: [Loris-dev] loris issues In-Reply-To: References: Message-ID: The vendor/autoload.php is generated by PHP composer, which replaces PEAR for package management. You can install it following the instructions from https://getcomposer.org/, and then in the Loris directory run "composer install" (or "composer install --no-dev" on a production environment to not install the development dependencies), which should generate the autoload.php file (and the entire vendor directory, which contains Loris dependencies) - Dave From: mathieu.desrosiers at criugm.qc.ca Date: Tue, 27 Jan 2015 09:37:11 -0500 To: samirdas99 at gmail.com; zia.mohades at gmail.com; cecile.madjar at gmail.com; loris-dev at bic.mni.mcgill.ca CC: pierre-emmanuel.morin at criugm.qc.ca Subject: [Loris-dev] loris issues Hi Loris team, Updating Cima-q loris installation failed with error message require_once(/srv/loris/cimaq/htdocs/../vendor/autoload.php): failed to open stream: No such file or directory in /srv/loris/cimaq/htdocs/main.php on line 6, referer: http://loris.cima-q.ca/ I cannot find this vendor/autoload.php anywhere. Is someone have any idea???? Thanks ?Mathieu _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca http://www.bic.mni.mcgill.ca/mailman/listinfo/loris-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From waveflux at gmail.com Wed Jan 28 11:53:28 2015 From: waveflux at gmail.com (Tom Beaudry) Date: Wed, 28 Jan 2015 11:53:28 -0500 Subject: [Loris-dev] dicom-toolkit on CentOS 6.6 Message-ID: Hi Everyone, I was wondering if anyone has been able to install dicom-toolkit (dcmtk) on CentOS. There are a lot of missing libraries that are hard to track down to get it to work. Thanks, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.macfarlane2 at mcgill.ca Wed Jan 28 12:43:37 2015 From: david.macfarlane2 at mcgill.ca (Dave MacFarlane) Date: Wed, 28 Jan 2015 12:43:37 -0500 Subject: [Loris-dev] Loris Developers' Workshop, Part 1 Message-ID: Hello interested parties, It's been decided that the first Loris Developers' workshop will be on Friday February 6th at 3:30pm in the Bell room at the BIC. This first workshop will go over some basics of Loris that need to be covered before getting into more advanced topics at future workshops, and then leave some time for feedback on the workshop itself (scheduling of further workshops, prioritizing what content to cover, etc). Everyone is invited, so feel free to forward this to anyone who might be interested. - Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcbrien.work at gmail.com Wed Jan 28 13:21:34 2015 From: dcbrien.work at gmail.com (Don Brien) Date: Wed, 28 Jan 2015 13:21:34 -0500 Subject: [Loris-dev] dicom-toolkit on CentOS 6.6 In-Reply-To: References: Message-ID: Hi Tom, I installed this on 6.5 from source without much issue. I installed directly from source using dcmtk-3.6.0.tar.gz . Don On Wed, Jan 28, 2015 at 11:53 AM, Tom Beaudry wrote: > Hi Everyone, > > I was wondering if anyone has been able to install dicom-toolkit (dcmtk) > on CentOS. There are a lot of missing libraries that are hard to track > down to get it to work. > > Thanks, > Tom > > _______________________________________________ > Loris-dev mailing list > Loris-dev at bic.mni.mcgill.ca > http://www.bic.mni.mcgill.ca/mailman/listinfo/loris-dev > > -- Donald Brien MRI Research Associate CENTRE FOR NEUROSCIENCE STUDIES Rm 238 Botterell Hall. Queen?s University Kingston, Ontario, Canada K7L 3N6 Phone: x32811 / 75031 Cell: 613-583-5680 Fax: 613-533-6840 -------------- next part -------------- An HTML attachment was scrubbed... URL: