the_trove/slack-data/C04DFUV41.md at master · echopen/the_trove

2015-04-14 19:48:46> @U04DFTZ7D: <@U04DFTZ7D> has joined the channel
2015-04-14 21:41:20> @U04CV54A4: <@U04CV54A4> has joined the channel
2015-07-20 10:09:25> @U07SNUM7F: <@U07SNUM7F> has joined the channel
2015-09-15 23:32:59> @U0AAL4W13: <@U0AAL4W13> has joined the channel
2015-12-03 14:28:25> @U0FN1B8KD: <@U0FN1B8KD> has joined the channel
2015-12-03 14:28:50> @U0AAL4W13: <@U0FN1B8KD>: si tu veux lister du contenu pour la page scan conversion, tu as un peu de détails sur la page http://echopen.org/index.php?title=Scan_Conversion
2015-12-03 14:56:07> @U0FN1B8KD: ça marche, la newsletter vous convient? et la page capDev? ou je détaille plus?
2015-12-03 15:00:38> @U0AAL4W13: Oops là on est sur le canal app
2016-02-15 14:32:36> @U0AAL4W13: Un article cool sur la detection de features : http://www.mdpi.com/2313-433X/1/1/193/htm
2016-06-02 13:49:08> @U04DFTZ7D: <@U04DFTZ7D> has renamed the channel from "app" to "1_2_mobile_app"
2016-06-02 13:49:46> @U04DFTZ7D: <@U04DFTZ7D> has renamed the channel from "1_2_mobile_app" to "mobile_app"
2016-06-13 09:56:39> @U1G9AEN7L: <@U1G9AEN7L> has joined the channel
2016-08-20 16:22:38> @U0B47KC3S: <@U0B47KC3S> has joined the channel
2016-08-21 23:16:00> @U23D8HAC9: <@U23D8HAC9> has joined the channel
2016-08-22 08:55:32> @U0B47KC3S: hi <@U23D8HAC9> I am currently testing the GitHub's milestone functionality. So you’ll find it here : https://github.com/echopen/android-app/milestones. If you want we can even schedule a dev plan for this milestones. What do you think ?
2016-08-22 08:57:30> @U0B47KC3S: also could you give me your GitHub username so that I can invite you on echOpen’s github organization
2016-08-22 10:56:39> @U23D8HAC9: Yeah its great, let's get started. My github username is 'nameispriyank'
2016-08-22 11:48:27> @U0B47KC3S: you’re in our github team 😉 btw, for the images ressources, we can fake them for the moment with some available pictos. We’ll make the design in a few weeks with a dedicated designer !
2016-08-24 08:48:37> @U0B47KC3S: hi Pryiank, the Image Processing team is going to use http://www.zube.io, you know about this tool ?
2016-10-05 10:07:08> @U0GMX7QUB: <@U0GMX7QUB> has joined the channel
2016-10-10 09:16:16> @U04DFTZ7D: <@U04DFTZ7D> has renamed the channel from "mobile_app" to "prj_medtec_app"
2016-10-17 17:07:33> @U0B47KC3S: <@U2Q4137LL> voici le README sur lequel tu trouveras qqs mockups
2016-10-17 17:07:34> @U0B47KC3S: https://github.com/benchoufi/android-app
2016-10-17 17:07:45> @U2Q4137LL: <@U2Q4137LL> has joined the channel
2016-10-17 17:08:29> @U2Q4137LL: Ok merci
2016-11-01 12:58:58> @U0B47KC3S: hello <@U2Q4137LL> : en regardant les templates psd, je constate que la gesture n’est pas intégrée directement sur le screen. Or,il se trouve qu’il y a une solution qui semble être saluée comme un breakthrough par les designers et qui est intégrée à Invision v5. Je te laisse checker : http://blog.invisionapp.com/mobile-prototyping-for-ios-and-android-is-now-instant-offline-and-awesome/ Peux-tu me faire un retour dès que tu peux ? dans la vue du workshop de jeudi à Africa4Tech
2016-11-01 13:34:50> @U2Q4137LL: Dans les vues invision j'ai déjà intégré les mouvements sur certains boutons quand c'était possible. Quand il n'y pas d'animation c'est que les mouvements proposés sans passer par la version payante ne correspondaient pas. C'est pour ça que dans le zip il y a toutes les vues avec un texte explicatif sur la gesture à côté. Au fait la version psd avec tous les éléments séparés n'est pas encore uploader, on hésiter hier entre github ou le drive, du coup je la met ou?
2016-11-01 13:57:36> @U0B47KC3S: peux-tu me dire les possibilités supplémentaires qu’offre la version payante, dans notre contexte ? par ailleurs <@U04DFTZ7D> pour le choix drive vs github - j’ai un penchant pour drive;)
2016-11-01 14:24:08> @U2Q4137LL: Sur le site ils ne précisent pas, ils disent juste qu'il y a plus de prototype et options. Mais dans notre cas je ne vois trop d'intérêt, on a très peu d'écrans et animations différentes donc rien qui ne soit compréhensible rapidement par le texte explicatif ou à l'oral
2016-11-01 19:24:13> @U0B47KC3S: ok on fait comme ça
2016-11-01 19:29:38> @U0AAL4W13: Niveau stockage de document on a eu cette discussion encore récemment à une réunion du lundi, c'est pas mal de laisser les fichiers accessible au public sur un repo git
2016-11-01 19:29:40> @U0AAL4W13: D'autant plus que ça permet de garder le versioning même des fichiers design
2016-11-01 19:31:11> @U0AAL4W13: Sachant que l'accès au drive est moins ouvert
2016-11-01 19:31:46> @U0AAL4W13: Et que pour un camp c'est facile de partager un repo et collecter les contributions de manière visible
2016-11-03 20:29:13> @U0B47KC3S: en cours sur un repo qu’on va publier incessamment
2016-11-04 14:17:29> @U2Y7FPEUB: <@U2Y7FPEUB> has joined the channel
2016-11-07 19:22:12> @U0B47KC3S: <@U0B47KC3S> set the channel topic: dedicated to the Android App development : UX, UI, back-end
2016-11-12 20:40:21> @U32FZ0QLX: <@U32FZ0QLX> has joined the channel
2016-11-13 19:01:37> @U3210MXC5: <@U3210MXC5> has joined the channel
2016-11-13 19:01:37> @U31UCUFPW: <@U31UCUFPW> has joined the channel
2016-11-15 02:07:05> @U1NTT0ZPH: <@U1NTT0ZPH> has joined the channel
2016-11-15 02:07:05> @U1NM17NHF: <@U1NM17NHF> has joined the channel
2016-11-15 02:07:05> @U1NLWV4BZ: <@U1NLWV4BZ> has joined the channel
2016-11-15 20:33:21> @U2Y7FPEUB: Présent 🙂 (reactions: @U0B47KC3S)
2016-11-16 09:38:35> @U32AR6TED: <@U32AR6TED> has joined the channel
2016-11-16 12:51:07> @U0B47KC3S: <@U2X7189QR> <@U2Y7FPEUB> <@U2XLJS5L0> 1) Badr will help us select and recruit the Android developers for our first global hackathon, 16.12.16-19.12.16 2) We will schedule other hackathons as and when we need it 3) We isolated 3 fields of xHub-echOpen collaboration on which xHub experts can intervene : - interface Hardware-Software, - Performance in rough and in detail - Data architecture + Machine Learning the idea is for an expert would come for a full residency month in Paris, Hôtel-Dieu 😉 So happy working with you guys, moroccan nascent team !!
2016-11-16 14:50:08> @U0B47KC3S: <@U04DFTZ7D> <@U0GMX7QUB> I have just pushed on my forked repo of the app, a suggestion of documentation architecture and first examples of what could be the modules and interfaces markdown. What do you think ?
2016-11-16 14:50:09> @U0B47KC3S: https://github.com/benchoufi/android-app/tree/master/app/src/main/assets
2016-11-16 14:52:28> @U0B47KC3S: [FYI] for all, to explain the precedent post, we are testing a documentation format and for that purpose we attach to some folder of the app, some markdowns files. The idea is that these files will be processed by some script in order to deploy auto-magically the app documentation, at a higher and more intelligible level than a doxygen like doc
2016-11-16 15:23:07> @U04DFTZ7D: <@U0B47KC3S> looks great and clear !! Just, i don't know why the markdown format don't show up properly when i try to read the MDL-user_interface. I let <@U0GMX7QUB> telling you about the structure for the automatic website.
2016-11-16 15:24:48> @U0B47KC3S: what do you mean by they don’t show up properly ?
2016-11-16 15:31:29> @U04DFTZ7D: Github manage preview of mardown files without showing up the structure of the document. I attached examples
2016-11-16 15:31:54> @U04DFTZ7D: <@U04DFTZ7D>
2016-11-16 15:31:59> @U04DFTZ7D: <@U04DFTZ7D>
2016-11-16 15:55:26> @U32UWGGN9: <@U32UWGGN9> has joined the channel
2016-11-16 16:11:55> @U34231VFH: <@U34231VFH> has joined the channel
2016-11-16 18:47:41> @U0AAL4W13: <@U04DFTZ7D> it's not clear in your screenshot if the files have a dot md extension. Files without MD extension may be interpreted as raw text files by github parser.
2016-11-16 18:50:41> @U0B47KC3S: I had an issue with my IDE which was supposed to create .md file. Do I fixed and pushed
2016-11-16 19:13:42> @U04DFTZ7D: Great so it's fixed
2016-11-18 22:22:43> @U34N7NQNR: <@U34N7NQNR> has joined the channel
2016-11-19 09:37:03> @U33817K25: <@U33817K25> has joined the channel
2016-11-21 18:18:35> @U04DFTZ7D: <@U04DFTZ7D> has renamed the channel from "prj_medtec_app" to "prj_medtec_androidapp"
2016-11-23 17:50:09> @U35LGETA4: <@U35LGETA4> has joined the channel
2016-11-24 21:45:12> @U36QEPF51: <@U36QEPF51> has joined the channel
2016-11-24 22:08:54> @U37GZRZU6: <@U37GZRZU6> has joined the channel
2016-11-28 23:13:22> @U38HVMZ6K: <@U38HVMZ6K> has joined the channel
2016-11-30 09:53:13> @U38JDLY2E: <@U38JDLY2E> has joined the channel
2016-12-02 10:34:37> @U0KLG7CP8: <@U0KLG7CP8> has joined the channel
2016-12-02 10:53:52> @U0B47KC3S: <@U0B47KC3S>
2016-12-02 10:54:12> @U0B47KC3S: this is a file shared by @murat For the record @murat is an engeneer and master student in image processing in mobile device. He developed USB drivers for android device. Murat is interested in low complexity Scan Conversion algorithms.
2016-12-02 10:54:23> @U0B47KC3S: We are going to work with @murat on a Vulcan implementation
2016-12-02 10:54:41> @U0B47KC3S: For the record, I developed seperately a GPU implementation with OpenCL, which was thunder fast but which is no longer supported for android, and an OpenGL frames refreshing. What make Vulcan great is that it packs together GPU calculous parallelisation and OpenGL api
2016-12-07 04:08:32> @U3ARRLDQ8: <@U3ARRLDQ8> has joined the channel
2016-12-07 19:08:06> @U1PKXQVDW: <@U1PKXQVDW> has joined the channel
2016-12-08 22:03:08> @U3CDR25JP: <@U3CDR25JP> has joined the channel
2016-12-09 17:30:51> @U3CV9P9NH: <@U3CV9P9NH> has joined the channel
2016-12-13 09:30:02> @U3D9HA0N4: <@U3D9HA0N4> has joined the channel
2016-12-16 17:25:59> @U04DFTZ7D: <!channel> echOpen CAPDev start in 40 minutes 😉 Get ready here to follow all discussion using this channel and the call tools included 😉
2016-12-16 18:56:04> @U0B47KC3S: Started a https://echopen.slack.com/call/R3FVD5AJ1.
2016-12-16 18:56:34> @U0B47KC3S: <@U2X7189QR> hi, we’re there
2016-12-16 18:57:09> @U0B47KC3S: Started a https://echopen.slack.com/call/R3FVDPS1K.
2016-12-16 18:57:48> @U04DFTZ7D: To join the call click on join call ⬆️
2016-12-16 18:58:24> @U38HVMZ6K: 👍:skin-tone-2: enjoy and have fun!
2016-12-16 18:58:48> @U04DFTZ7D: Thanks <@U38HVMZ6K> you don't wanna join us for the kick off ?
2016-12-17 02:03:12> @U0B47KC3S: 4 those working on Vulkan for Android, you should
2016-12-17 02:03:16> @U0B47KC3S: 1) use last version of gradle compiler
2016-12-17 02:03:19> @U0B47KC3S: 2) Upgrade to last version of Android Studio
2016-12-17 02:03:34> @U0B47KC3S: 3) If you’re stick with older version such as 1.2.1, then Android Studio will complain to find cmake despite you install latest SDK Tools or SDK build tools. However, there is a quick fix referenced here <https://github.com/Commit451/android-cmake-installer>
2016-12-17 02:03:39> @U0B47KC3S: Remark It is a known issue of google’s android studio team, which was fixed in latest version
2016-12-17 07:00:08> @U38HVMZ6K: <@U04DFTZ7D> I would have loved to join but was busy with "family life tasks" 😉
2016-12-17 09:07:59> @U0B47KC3S: hi hi guys, Hackathon #Day 2 is starting, have fun !
2016-12-17 13:47:24> @U3FCS2UP3: <@U3FCS2UP3> has joined the channel
2016-12-17 15:19:00> @U3GQS8JTZ: <@U3GQS8JTZ> has joined the channel
2016-12-17 21:06:07> @U0B47KC3S: [:mega::zap::rocket:] the @phaino team have pushed for the first time :wink: Android App is shaping progressively :flag-ma: <@U2X7189QR> <@U2YN8FREG> <@U2Y7FPEUB> <@U2XLJS5L0> Stay tuned ! (reactions: @U04DFTZ7D,@U37GZRZU6)
2016-12-17 21:15:20> @U0B47KC3S: <@U37GZRZU6> <@U1PKXQVDW> after 2 checks, no working Nexus are available on my side :thinking_face:
2016-12-18 00:09:15> @U37GZRZU6: <@U0B47KC3S> on my side neither... 😞
2016-12-18 00:21:59> @U0B47KC3S: hey <@U37GZRZU6> there is something in between CPU and GPU usages which is RenderScript. It allows parallel processing. The only thing is we can’t force the code to use either one or another, it is low level OS choice who allocates ressources accordingly to the availibilties. But it seems to be broadly supported from Jelly Bean API 16 😉 And there is a bunch of publications documenting the power of this framework in parallel processing contexts 😉 I am currently jumping in the doc
2016-12-18 00:28:38> @U37GZRZU6: <@U0B47KC3S> that's great if you found an alternative 🙂 actually I was just thinking, if Vulkan forces people to update to the last Android device / OS then it's not suited for echOpen anyway... right ? The most important criterion to chose the right API is whether it can be widespread or not...
2016-12-18 00:39:03> @U0B47KC3S: exact <@U37GZRZU6>
2016-12-18 00:39:08> @U0B47KC3S: 1) the thing is that Google claimed that it is strategic for them to develop an equivalent of IOS’s metal, which is widely supported on IOS devices. So for 2 years, it is announced to be a core evolution of android and supposed to be as widely supported as IOS metal, so that it can meet echOpen’s criterion. Those kind of announces can lead to fast move and quick uptake for the android devices park. But, today’s experience can lead us sure to have a close look on these evolutions but not to rely on this and move forward to another way of hacking around the thing. In between, OpenCL set aside and Vulkan promise, there could be a good alternative in RenderScript (reactions: @U37GZRZU6)
2016-12-18 00:39:10> @U0B47KC3S: 2) Btw, guess what, I installed thsi google samples, and this time it work like a charm https://github.com/googlesamples/android-BasicRenderScript So that we can begin working on it !
2016-12-18 00:54:49> @U37GZRZU6: <@U0B47KC3S> thanks a lot !! seems to run on my side as well... can't wait tomorrow to play with it 🙂
2016-12-18 02:10:08> @U0B47KC3S: <@U2PFHNN3C> <@U37GZRZU6> <#C1G7T0PNX> look at this
2016-12-18 02:10:12> @U0B47KC3S: 1) this is called CNNdroid
2016-12-18 02:10:16> @U0B47KC3S: 2) It is "GPU-Accelerated Execution of Trained Deep Convolutional Neural Networks on Android”
2016-12-18 02:10:20> @U0B47KC3S: 3) and it uses RenderScript!
2016-12-18 02:10:22> @U0B47KC3S: Published 2 months ago, and Open Source t https://github.com/ENCP/CNNdroid
2016-12-18 16:39:24> @U3FCS2UP3: For me the renderscript examples work as well! So what exactly are the computations that need to be ported to the App?
2016-12-19 01:49:47> @U0B47KC3S: <@U37GZRZU6> <@U3FCS2UP3> I have just pushed the last version and here is the current state :
2016-12-19 01:49:52> @U0B47KC3S: 1) It’s working 😉
2016-12-19 01:49:57> @U0B47KC3S: 2) We have a pretty good performance of 1,4µs per frame which can let us hope of 70 frames per second for simple images !!
2016-12-19 01:50:01> @U0B47KC3S: But
2016-12-19 01:50:08> @U0B47KC3S: 3) The image is slightly noisy, I don’t understand why. You have an idea ?
2016-12-19 01:50:19> @U0B47KC3S: 4) The code can be still optimized : in fact, I didn’t use the rs_allocation because I can’t get the index of the rs_allocation being parsed (the index not the counter). So how to do that ? RenderScript is still poorly documented
2016-12-19 01:50:23> @U0B47KC3S: btw <@U3FCS2UP3> what I understand is that the loop of the kernel methods which are taken in charge by RenderScript's internals are not the natural increasing order, but rather randomly, which I think explain the images that we got earlier
2016-12-19 01:50:40> @U0B47KC3S: 5) Btw, when the RenderScript algo will be optimized, I ll make some clean up code to throw out all the allocation in a more static context so that it doesn’t have to be parsed at each loop
2016-12-19 10:20:31> @U37GZRZU6: you rock <@U0B47KC3S> 😉 I'll have look at the last version, hopefully this evening. BTW, I just told our lead dev about Renderscript, first time of my life I teach him something about Androïd 😎 (reactions: @U0B47KC3S,@U0AAL4W13)
2016-12-19 13:51:26> @U3GHS132Q: <@U3GHS132Q> has joined the channel
2016-12-19 22:02:44> @U37GZRZU6: <@U0B47KC3S> well, on my side the app crashes 😕 what device/OS are you using in your emulator ?
2016-12-20 00:15:53> @U0B47KC3S: <@U37GZRZU6> yes I use an emulator with API 25, it should not depend on the device, however I use Galaxy Nexus. Could you tell us what you in the logs ? especially the ones marked in red with a thrown exception
2016-12-20 12:07:41> @U2PFHNN3C: <@U2PFHNN3C> has joined the channel
2016-12-21 15:09:51> @U3HH0CEAW: <@U3HH0CEAW> has joined the channel
2016-12-22 15:07:53> @U3J40RUDT: <@U3J40RUDT> has joined the channel
2016-12-22 15:16:59> @U2PTWF6SX: <@U2PTWF6SX> has joined the channel
2016-12-22 15:16:59> @U1N5Q9334: <@U1N5Q9334> has joined the channel
2016-12-22 15:16:59> @U2M9XDS5N: <@U2M9XDS5N> has joined the channel
2016-12-22 15:16:59> @U07SS18MT: <@U07SS18MT> has joined the channel
2016-12-22 15:17:01> @U1DGN6S80: <@U1DGN6S80> has joined the channel
2016-12-22 15:17:01> @U33KM85FA: <@U33KM85FA> has joined the channel
2016-12-22 15:17:01> @U0LPTV0Q4: <@U0LPTV0Q4> has joined the channel
2016-12-22 15:17:01> @U33389FRA: <@U33389FRA> has joined the channel
2016-12-22 15:17:02> @U0HF2S3QX: <@U0HF2S3QX> has joined the channel
2016-12-22 15:17:02> @U2NAWHM9N: <@U2NAWHM9N> has joined the channel
2016-12-22 15:17:02> @U0GN7EB32: <@U0GN7EB32> has joined the channel
2016-12-22 15:17:02> @U2404BG5N: <@U2404BG5N> has joined the channel
2016-12-22 15:17:02> @U1PAGSKGU: <@U1PAGSKGU> has joined the channel
2016-12-22 15:17:02> @U3BFTB7M4: <@U3BFTB7M4> has joined the channel
2016-12-22 15:17:03> @U3BAH0X62: <@U3BAH0X62> has joined the channel
2016-12-22 15:17:03> @U38TWKY9Y: <@U38TWKY9Y> has joined the channel
2016-12-22 15:17:03> @U2V03QR8E: <@U2V03QR8E> has joined the channel
2016-12-22 15:17:03> @U394HRZ1B: <@U394HRZ1B> has joined the channel
2016-12-22 15:17:03> @U336DPZV4: <@U336DPZV4> has joined the channel
2016-12-22 15:17:03> @U352MKG4V: <@U352MKG4V> has joined the channel
2016-12-22 15:17:03> @U2X7189QR: <@U2X7189QR> has joined the channel
2016-12-22 15:17:04> @U32V2JWFJ: <@U32V2JWFJ> has joined the channel
2016-12-22 15:17:04> @U2YN8FREG: <@U2YN8FREG> has joined the channel
2016-12-22 15:17:04> @U2X419KJS: <@U2X419KJS> has joined the channel
2016-12-22 15:17:04> @U2XLJS5L0: <@U2XLJS5L0> has joined the channel
2016-12-22 15:17:04> @U2MF267L2: <@U2MF267L2> has joined the channel
2016-12-22 15:17:04> @U20C8CKTL: <@U20C8CKTL> has joined the channel
2016-12-22 15:17:05> @U0JFW4XTQ: <@U0JFW4XTQ> has joined the channel
2017-01-05 15:56:25> @U3ML4L01Z: <@U3ML4L01Z> has joined the channel
2017-01-05 23:07:55> @U3N1SENJY: <@U3N1SENJY> has joined the channel
2017-01-09 11:53:12> @U3NT8G2BC: <@U3NT8G2BC> has joined the channel
2017-01-12 00:18:33> @U3PLYAJPJ: <@U3PLYAJPJ> has joined the channel
2017-01-12 12:50:14> @U3QGT3Q74: <@U3QGT3Q74> has joined the channel
2017-01-17 15:42:15> @U0B47KC3S: <@U0B47KC3S> and commented: some report with nice links about Software metrics, published by codacy #sweet
2017-01-17 15:45:10> @U3T7KBEMV: <@U3T7KBEMV> has joined the channel
2017-01-18 08:41:13> @U3QGT3Q74: Hi <@U0B47KC3S>, is there an online meeting to participate to signal processing weekly review this afternoon ?
2017-01-18 10:04:41> @U0B47KC3S: hi <@U3QGT3Q74> sure there is also an online meeting ! we meet on skype at 6.30 pm, and generally at about 6.45/50 pm. Could you provide your skype id ?
2017-01-18 11:23:44> @U3QGT3Q74: Skype id - clement.lecouedic I will do my best to join at Hotel-Dieu otherwise I will join online.
2017-01-18 12:06:08> @U0B47KC3S: great dude !
2017-01-19 20:17:51> @U3TUWV3SQ: <@U3TUWV3SQ> has joined the channel
2017-01-19 21:57:11> @U0B47KC3S: hi #channel : just to let you know that we have some jam coding session this saturday afternoon, playing around GPU and renderscript with some echTopians -> <@U37GZRZU6> and <@U3QGT3Q74>
2017-01-19 21:57:12> @U0B47KC3S: On remote, or irl don’t hesitate to join 😉 (reactions: @U37GZRZU6)
2017-01-19 22:13:28> @U3TUWV3SQ: Ok, if I have some free time, I will come. Thanks for the invitation
2017-01-19 22:41:52> @U3QGT3Q74: Hi all, I will be available on Saturday in early afternoon. I gave a look a renderscript and it looks very promising in term of performances. I also want to mention ITK an other famous open source C++ framework specialized in medical imaging that could be compilated ans used in the Android NDK. It will probably not be as good as renderscript for perfs but it will provide many filters and renderers. Also it would be portable on both iOS and Android
2017-01-19 22:48:04> @U0B47KC3S: that’s interesting ! do you think we can implement renderscript + ITK, jus to get filters and renderers if these are necessary, and try to implement them progressively in GPU if there are paralellizable
2017-01-21 12:24:40> @U3QGT3Q74: I think it's compatible yes. ITK provides automatic parallelization for most of the filters and I know some are also implemented with GPU (reactions: @U37GZRZU6)
2017-01-21 12:25:14> @U3QGT3Q74: I will investigate a bit more
2017-01-21 12:32:22> @U0B47KC3S: great 😉
2017-01-21 12:36:30> @U38HVMZ6K: For the reference... https://itk.org/ I also had a quick look at it and seems really good. Well documented and maintained with regular releases. (reactions: @U0B47KC3S)
2017-01-21 18:31:43> @U0B47KC3S: thanks <@U38HVMZ6K> we were just talking about it. Btw, we arben trying now to document a robust rendering pipeline
2017-01-21 18:34:32> @U0B47KC3S: besides, we are working with <@U37GZRZU6> on refactoring the code for the RenderScript implementation and we get for the only ScanConversion algo 6ms 😉
2017-01-25 00:14:29> @U3QGT3Q74: <@U0B47KC3S> <@U37GZRZU6> Following our discussions from last saturday on the rendering pipeline I investigate on the communication part between the device and the mobile phone * UDP protocol does not seems to be compatible with medical device as it allows packet loss during data transfert, we should focus on TCP/IP * standard encoding for medical images is Lossless JPEG that ensure no image degradation with a compression factor between 6:1 to 12:1 (reactions: @U20C8CKTL,@U37GZRZU6)
2017-01-25 00:17:48> @U0B47KC3S: indeed <@U3QGT3Q74>, there is a legacy UDP implementation related to first POCtotype, we used this protocol for opportunity reason. Currently, we have a TCP implementation running fine
2017-01-25 00:18:33> @U0B47KC3S: perfect for the JPEG implementation
2017-01-25 00:27:49> @U20C8CKTL: Last year i saw something at fosdem on picotcp. Some kind of resized tcp/ip stack
2017-01-25 00:28:33> @U20C8CKTL: Maybe it could be interesting to look at this stuff further.
2017-01-25 10:17:53> @U0AAL4W13: BTW, were there minutes from Saturday?
2017-01-25 10:18:26> @U37GZRZU6: <@U0AAL4W13> no... 😓
2017-01-26 16:37:29> @U0B47KC3S: ☝️ <@U37GZRZU6> <@U3QGT3Q74> <@U2X7189QR> <@U3FCS2UP3> <@U2XLJS5L0> I have just PR with a new branch GPUrway
2017-01-26 16:37:32> @U0B47KC3S: You’ll find the app with RenderScript all together with OpenGL display machinery 😉 it is morning work so there is still some screen parameters to find tune in order to get a bigger picture, but it is speed and works like a charm 😉
2017-01-26 16:37:34> @U0B47KC3S: Morever you’ll find OpenGL test android app, a standalone one, in order to play with it without embrassing with the heavy echOpen’s app (reactions: @U37GZRZU6)
2017-01-26 16:49:14> @U3QGT3Q74: <@U0B47KC3S> I'm currently setting up the mobile-app repository of the project. I will also give a look at GPUrway branch 😉
2017-01-26 17:11:33> @U0B47KC3S: <@U3QGT3Q74> great 😉 we agree that I am not an expert and so not quality code compliant 😉 pleasing myself with some code, that’s it
2017-01-26 17:16:30> @U3WRNP30B: <@U3WRNP30B> has joined the channel
2017-01-26 17:16:54> @U0B47KC3S: <@U3QGT3Q74>, btw I am thinking to add some lock because some part of code could be exposed to concurrency. We’ll discuss that matter
2017-01-28 12:27:41> @U3QGT3Q74: <@U0B47KC3S> don't worry ;D the app is running that is the most important! we will improve some parts if needed
2017-01-30 11:53:48> @U3Y2FPGBV: <@U3Y2FPGBV> has joined the channel
2017-01-30 16:49:01> @U3XHSAQHE: <@U3XHSAQHE> has joined the channel
2017-02-04 13:49:44> @U41049CQ2: <@U41049CQ2> has joined the channel
2017-02-07 15:53:42> @U42P4AT7Z: <@U42P4AT7Z> has joined the channel
2017-02-16 10:16:47> @U3QGT3Q74: Hi <@U0B47KC3S>, I send the pull request to commit the image manipulation quick prototype on the mobile app. (reactions: @U37GZRZU6,@U0B47KC3S)
2017-02-16 11:06:55> @U0B47KC3S: <@U3QGT3Q74> thank you. I am going to review that !
2017-02-21 11:35:59> @U0B47KC3S: [JAVA 👯] hey tonight we having some coding party with <@U3QGT3Q74> <@U07UEJC2H> <@U37GZRZU6> The goal is to upgrade the app with <@U07UEJC2H> brand new implementation. As usual door is open 😉 (reactions: @U37GZRZU6)
2017-02-24 11:22:52> @U492PCSE9: <@U492PCSE9> has joined the channel
2017-02-25 11:47:43> @U0B47KC3S: for guys in the neighborhood, today coding session with <@U3GHS132Q> at echOpen #HDinstance
2017-03-03 00:57:53> @U4CAG5ZFW: <@U4CAG5ZFW> has joined the channel
2017-03-03 00:57:53> @U4DFR8RN3: <@U4DFR8RN3> has joined the channel
2017-03-04 15:43:43> @U0B47KC3S: on air with <@U3GHS132Q> and <@U37GZRZU6> for a saturday snack coding. For people hanging around HD, you’re welcome !
2017-03-04 16:31:11> @U0AAL4W13: till when do you stay there?
2017-03-04 17:00:56> @U0B47KC3S: till 7pm I think
2017-03-11 18:35:53> @U0B47KC3S: oups forgot to say, as a saturday, coding session @ hôtel dieu, with @francis, <@U07UEJC2H> - for those in the area, welcome 😉
2017-03-16 02:46:08> @U0B47KC3S: <@U0B47KC3S>
2017-03-16 08:26:37> @U0AAL4W13: Is that the SigProc or the android app log?
2017-03-16 09:24:31> @U0B47KC3S: sorry guys you’re right
2017-03-18 16:28:58> @U0B47KC3S: yet an other saturday coding session @HD - renderscript is plugged on the main app version - working fine (reactions: @U20C8CKTL,@U37GZRZU6)
2017-03-19 15:37:49> @U0B47KC3S: (no sun)day coding session with <@U3QGT3Q74> <@U3GHS132Q> and <@U0AAL4W13> ! (reactions: @U37GZRZU6)
2017-03-20 11:02:15> @U3QGT3Q74: Hi everybody, I gave a look at the high level Android app architecture. Google recommendations are MVP or MVVM design and you can find from simple to more complex examples on this github: https://github.com/googlesamples/android-architecture. (reactions: @U20C8CKTL,@U3GHS132Q,@U0B47KC3S)
2017-03-20 11:05:55> @U3QGT3Q74: To my point of view, a good balance between code verbosity and quality would be to use MVP design pattern with dependencies injection using Dagger 2 frameworks
2017-03-20 11:51:34> @U0B47KC3S: perfect !! I think I have already some Dagger things running in some branch 😉
2017-03-20 11:51:52> @U3GHS132Q: I am slowly currently trying to branch the new UI (phaino branch on github) to the current backend. It seems to be a big project so I think that we all have to discuss about it. I discuss it a few with <@U3QGT3Q74> , is it possible to plan a meetup to discuss off it more clearly ?
2017-03-21 11:35:38> @U0B47KC3S: <@U3GHS132Q> let’s discuss about it tomorrow evening !
2017-03-21 11:36:18> @U3GHS132Q: <@U0B47KC3S> Understand 🙂
2017-03-21 11:39:49> @U37GZRZU6: <@U0B47KC3S> you mean during your clandestine app meetings which take place every week under cover of a sigproc meeting? 🙃 (reactions: @U3QGT3Q74)
2017-03-27 12:51:28> @U3GQS8JTZ: <@U3GQS8JTZ> has left the channel
2017-04-03 18:50:24> @U38HVMZ6K: (reactions: @U3QGT3Q74,@U37GZRZU6,@U0B47KC3S,@U3GHS132Q,@U0AAL4W13)
2017-04-08 11:37:52> @U37GZRZU6: Who's in for a sunny working session this afternoon? <@U0B47KC3S> <@U3QGT3Q74> <@U3GHS132Q> ? What do you think about relocating echOpen on a terrace? ☀️ ☕ 💻 🙂 (reactions: @U0AAL4W13,@U0B47KC3S,@U3GHS132Q)
2017-04-08 11:42:39> @U3QGT3Q74: 👍 for terrace ! I'm in for this afternoon, I will be available around 2:00
2017-04-08 11:47:07> @U37GZRZU6: Same here, 2pm is ok! anyway I'll have to pass by Hôtel Dieu, but let's brainstorm for a nice place nearby? Waiting for confirmation from <@U0B47KC3S> <@U3GHS132Q> ;) ( <@U0AAL4W13> you're not available today right?)
2017-04-08 11:56:15> @U0AAL4W13: I'm geeking on this Chinese probe sdk release from the sunny district " les Ardennes", coding from my sunny and flowery and bbq-y garden there ;) (reactions: @U38HVMZ6K,@U37GZRZU6,@U3GHS132Q)
2017-04-08 12:28:02> @U0B47KC3S: sure I am in !!
2017-04-08 12:28:35> @U0B47KC3S: around 2pm is nice 😉
2017-04-08 12:29:16> @U0B47KC3S: <@U3GHS132Q> will perhaps be there before 2pm
2017-04-08 12:30:11> @U0B47KC3S: we can go to le café Rostand at luxembourg
2017-04-08 12:36:50> @U3GHS132Q: I do not agree with terrace ! It is a manipulation, <@U37GZRZU6> will profit that the sun hits our heads to manipulate us ! I think that it is a better idea to relocate echOpen in catacombs !
2017-04-08 12:38:14> @U3GHS132Q: More seriously I am ok with terrace if it is not expensive and if I can see my screen (my machine has not an IPS screen) (reactions: @U0AAL4W13)
2017-04-08 12:40:15> @U3GHS132Q: I have an idea for where to go but I do not think that it will be comfy to code, moreover we will not have fairy electricity :s
2017-04-08 12:49:04> @U37GZRZU6: Let's go for cafe Rostand?
2017-04-08 12:53:18> @U3GHS132Q: Is it possible to charge machines at this cafe ???
2017-04-08 13:08:28> @U37GZRZU6: Let's go for it and change if it's not possible?
2017-04-08 13:17:05> @U3GHS132Q: It is a good idea ! So 14 at https://www.openstreetmap.org/node/726896940 !
2017-04-08 13:44:33> @U0B47KC3S: ok perfect - i think I will be 15mn late 😉
2017-04-08 14:15:10> @U37GZRZU6: I'm late as well 😅
2017-04-08 14:33:10> @U3QGT3Q74: I just arrived someone already here ?
2017-04-08 14:39:52> @U0B47KC3S: we are there !
2017-04-09 19:03:31> @U37GZRZU6: <@U0B47KC3S> <@U3QGT3Q74> just noticed your github project board : "v4.0.0 #drums" looove iiiiit 😃 👏 👍 😍 (reactions: @U0B47KC3S,@U3QGT3Q74)
2017-04-14 02:41:45> @U4YF0KAJU: <@U4YF0KAJU> has joined the channel
2017-04-14 09:30:07> @U3QGT3Q74: Hi all, let's join on Saturday afternoon at Hotel Dieu to finish the #cello-cachalot (release 3.0.0 - name is not decided yet) mobile app and start new developments on #drum-dolphin (release 4.0.0 name is not fixed either). Also I start a Doodle to collect proper release name suggestion for mobile app release. Themes are music / animals emitting ultrasounds (reactions: @U0AAL4W13,@U0B47KC3S,@U37GZRZU6,@U0B47KC3S)
2017-04-14 09:53:25> @U0B47KC3S: <@U3QGT3Q74> amazing job dude ! 😉
2017-04-14 10:03:45> @U3QGT3Q74: Actually you can send release name suggestions directly on Slack, we will use Doodle only for final poll (poll members can not add poll choice ;( ) (reactions: @U37GZRZU6)
2017-04-14 10:05:20> @U38HVMZ6K: Or a slack poll with Polly? https://slack.com/apps/A04E6JX41-polly
2017-04-14 10:05:25> @U37GZRZU6: <@U3QGT3Q74> should we make an announcement in <#C04DFTZ7X> ? the name will concern the whole release actually (reactions: @U0AAL4W13,@U3QGT3Q74,@U3GHS132Q)
2017-04-14 10:05:43> @U37GZRZU6: <@U38HVMZ6K> with Polly you are limited to 10 suggestions 😞
2017-04-14 10:11:27> @U38HVMZ6K: Sad... Didn't know about this limitation. It would have been nice to have it at our central place 😕
2017-04-14 10:13:24> @U37GZRZU6: well, that was the case several months ago when I tried to use it (also to choose a release name 😉 ) but maybe they did some improvements since then ?
2017-04-14 10:34:33> @U3GHS132Q: Or we can use a libre service like https://framadate.org/ which permits to create classic polls with many choices 🙂 (reactions: @U0GMX7QUB,@U3QGT3Q74,@U37GZRZU6)
2017-04-15 11:19:48> @U3QGT3Q74: Hi, I will be at Hotel Dieu around 2pm (reactions: @U37GZRZU6,@U0B47KC3S)
2017-04-15 13:27:47> @U0B47KC3S: Hi folks, I will be there in about 10mn 🎉 Besides, <@U3GHS132Q> will be there and I think <@U1PKXQVDW>
2017-04-15 13:28:28> @U0B47KC3S: However supreme chief <@U37GZRZU6> is out of party today ! ☝️ (reactions: @U37GZRZU6,@U3GHS132Q)
2017-04-15 15:22:05> @U0B47KC3S: #InvestigationInProgess we were begining to work with <@U3GHS132Q> <@U07UEJC2H> <@U3QGT3Q74> then <@U3QGT3Q74> is telling us dauntlessly that tuesday an other physicist is begining to work @ echOpen. Heavily suspecting <@U37GZRZU6> is behind this (reactions: @U37GZRZU6,@U37GZRZU6)
2017-04-15 15:34:47> @U3GHS132Q: Physicists ! There are only physicists here ! Go to hell physicists 😈 ! (reactions: @U0AAL4W13,@U3GHS132Q,@U1PAGSKGU)
2017-04-16 11:15:34> @U37GZRZU6: <@U0B47KC3S> I can bring one more physicist as well 😀 what's happening on Tuesday? (reactions: @U0B47KC3S)
2017-04-16 11:48:11> @U0B47KC3S: scared of what’s happening - beyond my control (reactions: @U37GZRZU6)
2017-04-16 14:35:35> @U3GHS132Q: Do not forget, <@U0B47KC3S> some people here want more power ! And they will walk on you if they access this power !
2017-04-16 23:22:12> @U4YCKBDR8: <@U4YCKBDR8> has joined the channel
2017-04-16 23:24:41> @U4YCKBDR8: It seems you are only targeting android phones, why not tablets?
2017-04-17 01:16:53> @U3GHS132Q: <@U4YCKBDR8> Welcome 🙂
2017-04-17 01:17:50> @U3GHS132Q: If I do not say somethibg wrong an app for tablet and smartphone are the same
2017-04-17 01:18:22> @U3GHS132Q: If therr is any difference it is in term of UI so it will no take long time to develop for tablet
2017-04-17 07:44:11> @U38HVMZ6K: > an app for tablet and smartphone are the same > If therr is any difference it is in term of UI so it will no take long time to develop for tablet An Android app is most often the same for tablet and smartphone (same APK) but.. 1) with no special consideration, a smartphone app often looks ugly on a tablet (reduced size of widgets, bad usability,...) 2) UX considerations are a bit different between smartphones and tablets. e.g. smartphones are mostly used with one hand in portrait orientation while tablets are often used wit two hands in landscape mode
2017-04-17 07:45:40> @U38HVMZ6K: The 2 devices are fundamentally difference in terms of UX. While we can well imagine the use with a smartphone (probe in one hand, smartphone in the other for visualization and control e.g. gain) the use of a tablet would be different.
2017-04-17 07:46:50> @U38HVMZ6K: The big advantage of the tablet is the screen size which would radically improve the comfort for visulaization. On the other side, holding the tablet in one and the probe in the other is quite difficult.
2017-04-17 07:52:40> @U38HVMZ6K: We can imagine 2 use cases: 1) Use the tablet "static" on a table as display and implement vocal commands for gain, frequency,... control 2) Use a tablet grip with "free thumb" and put all controls on the margin (reachable with the thumb only): http://lazy-hands.com/wp-content/uploads/2017/02/Tablet-gripx1-black21-800x800.png (reactions: @U0AAL4W13)
2017-04-17 07:57:05> @U38HVMZ6K: For detailed information, see official Android documentation: https://developer.android.com/guide/practices/tablets-and-handsets.html In short, it is possible to support both but this needs consideration right from the beginning.
2017-04-17 13:28:37> @U3GHS132Q: > Use the tablet "static" on a table as display and implement vocal commands for gain, frequency,... control You search complicated. Take the Ultramark, replace the screen by a detachable tablet and the probe by a wireless probe. With this setup the practitioner has a free hand (the one which does not hold the probe). I even think that this setup will be more comfy than smartphone/probe (seriously handle a big phone with the non writing hand is a pain). But it can not be used anywhere. > put all controls on the margin The design of the phaino branch in git has controls on margin.
2017-04-17 13:51:22> @U3GHS132Q: And I am just thinking that it could be possible to other people to develop app for our devices because the communication will be documented. So if people have a very specific UX, for example using the probe while doing headstand, they will develop their own app to use the probe in this manner.
2017-04-17 13:58:26> @U38HVMZ6K: > it could be possible to other people to develop app for our devices because the communication will be documented > they will develop their own app to use the probe in this manner Not for a medical device... For hackers and open source/open hardware community yes, it would be possible but if you think about a real medical application, you won't ever have an app developed by individuals or a community. That's just impossible to pass through certification (MDR/CE in Europe, 510(k) in US and other regulations in other parts of the world).
2017-04-17 13:59:48> @U3GHS132Q: People do what they want. Our app has to be certified but if a private clinic or a small group of maker want to develop their own app : let them do it
2017-04-17 14:05:23> @U38HVMZ6K: Well, that's not as easy as that... Having a public and documented API which can be used by anyone may be problematic, even more if it is on a wireless link. We should at least guarantee that it is our own certified application which is controlling the probe and not an app developed by Mr Lambda in his spare time with poor programming skills. The fact of having an open and accessible API will be very very difficult to argue to regulations authorities. How do you prevent unauthorized access to your device ? How do you mitigate cybersecurity risks, privacy and health information security ?
2017-04-17 14:06:20> @U3GHS132Q: > How do you mitigate cybersecurity risks, privacy and health information security ? By encrypting data ?
2017-04-17 14:07:00> @U3GHS132Q: > The fact of having an open and accessible API will be very very difficult to argue to regulations authorities If we are not certified because our app and device are open source they can for sure go fuck themselves with their certification 🙂
2017-04-17 14:12:02> @U38HVMZ6K: > they can for sure go fuck themselves with their certification Unfortunately, they decide and not you... And they don't care at all if you get their certification or not. At the end of the day, you are the butt of the joke because you cannot market your device...
2017-04-17 14:14:06> @U38HVMZ6K: But if you are convinced that you can make them change their mind and have an open device with an open API usable by anyone, I cannot prevent you of doing so but in my opinion it's just a run straight into the wall.
2017-04-17 14:18:16> @U3GHS132Q: > market your device The objective for me is not to market something it is to save life with open source and low cost probe. > run straight into the wall If you run into a wall with enough speed you can break it
2017-04-17 14:20:36> @U3GHS132Q: But before speaking of that we will develop our app and try to make it certified. But I will never write proprietary code to please some certification group which are possibly corrupted by lobbying of some big companies.
2017-04-17 14:52:00> @U38HVMZ6K: > The objective for me is not to market something it is to save life with open source and low cost probe. If you don't agree with the term "market" just replace it with "legally use for free" and you get > At the end of the day, you are the butt of the joke because you cannot legally use for free your device...
2017-04-17 14:53:09> @U38HVMZ6K: > to please some certification group which are possibly corrupted by lobbying of some big companies. What do you propose then ? Create an open source regulation community recognized by governments for legalizing use of medical devices ?
2017-04-17 14:59:23> @U3GHS132Q: > legally use for free Without certification we can also save lives > Create an open source regulation community recognized by governments for legalizing use of medical devices This is an excellent idea !
2017-04-17 15:10:12> @U38HVMZ6K: Good luck!
2017-04-17 15:12:59> @U3GHS132Q: I will not try to do this because I have not the time do this nor the competences. But open source regulation consortium are always better than closed one
2017-04-17 19:13:57> @U4YCKBDR8: Musicians use tablet holders like this: https://produkte.k-m.de/media/images/product/19742-300-55_Detail_5.jpg , it makes the tablet controllable by one hand, while holding the probe in the other. I think the bigger screen is really beneficial for this application, but indeed UI design will need to be completely different.
2017-04-17 19:22:48> @U4YCKBDR8: As for certification; having experience in a medical devices company, I can assure you this will not be easy. FDA for example (if you can get FDA approval, the rest will follow) needs you to have a really large body of documentation not only about the design, but also for example about all processes involved in quality assurance, bug handling, design process, introducing new features, handling complaints by customers,... I am very curious about what projects like this one are going to do when they really want to go to a market, but I can hardly see any other way than some company investing a lot of money to do all the "paperwork" and then start selling. (reactions: @U38HVMZ6K,@U0AAL4W13)
2017-04-17 19:41:09> @U38HVMZ6K: <@U4YCKBDR8> I am currently working as an R&D Software Engineer in a medical device company and, luckily or not, know well what you are describing. We already have a huge amount of documentation following strict processes under design controls. We are currently in our final development phase and already preparing ourselves for V&V which is planned to start end of this year to finally submit a 510(k) to the FDA. I try to bring insights into medical device development and processes as far as I can and propose methodologies and processes which could allow an easier design transfer to a company eventually taking over the certification process. I see it exactly as you do... Without a company investing much time, money and effort, the chances to see a device in the field are tight.
2017-04-17 19:46:46> @U38HVMZ6K: BTW, did you already successfully passed through the whole FDA process? Personally and for my whole team it will be a first shot... We are (I think) well prepared and have a full software lifecycle process, quality system and assurance procedures,... But as long as we don't submit, we are a bit in the dark on what FDA expectations are and to which extent we fullfil them.
2017-04-17 19:53:36> @U38HVMZ6K: > (if you can get FDA approval, the rest will follow) I think this was true until recently but Europe with its new regulations (MDR: medical device regulation) is now as harsh as FDA even worse in some domains.
2017-04-17 20:09:08> @U4YCKBDR8: I worked as an R&D Engineer on image processing technology for radiology images (http://global.agfahealthcare.com/main/digital-radiography/) and yes, Agfa has FDA approved radiology systems up and running in the field for a long time. I witnessed closely (although not directly involved) how an FDA auditor came to our offices for a week and the panic and fear this caused by many of my colleagues, especially the ones who created all the documentation and processes. For us, R&D engineers, it was a matter of documenting every little piece of change you make and making sure everything was traceable according to the processes, but if you have to setup the whole 510(k) from scratch, I understand you feel a bit in the dark! (reactions: @U38HVMZ6K,@U0AAL4W13,@U0B47KC3S)
2017-04-17 20:12:18> @U38HVMZ6K: thanks for sharing your experience (even if it worries me even more about FDA inspectors audits 😉)
2017-04-17 20:14:13> @U4YCKBDR8: Don't worry, things will work out ;-); what are you working on?
2017-04-17 20:14:21> @U38HVMZ6K: > Digital Radiography: DR & CR powered by MUSICA Very nice devices and technology !
2017-04-17 20:14:44> @U38HVMZ6K: A peritoneal dialysis machine for home use
2017-04-17 20:16:18> @U38HVMZ6K: https://www.debiotech.com/page/index.php?page=product_01&id=1&id_prod=52
2017-04-17 20:16:29> @U4YCKBDR8: Sounds like fun!
2017-04-17 20:18:58> @U38HVMZ6K: yep, fun and challenging... all constraints of a medical device development + constraints of a product to be used by patients at home (= not healthcare professionals, not a clean environment as in clinics,...)
2017-04-17 20:19:25> @U4YCKBDR8: You're in Switzerland, home of all things made with high quality! Great 🙂
2017-04-17 20:38:40> @U38HVMZ6K: 😅 we try to at least
2017-04-26 17:01:48> @U0B47KC3S: 📣🎊🚀🤓 the last PR on the android_app repo is the final cut of the version , currently git-tagged as classic. Big Up to <@U3QGT3Q74> . The app handles the data coming in from the redpitaya, the envelope detection and the scanconversion. We are now jumping to the next version, mainly merge the current backend into the UI developed by the phaino team 😉 (reactions: @U0AAL4W13,@U37GZRZU6,@U20C8CKTL)
2017-04-26 17:49:12> @U3GHS132Q: G G !
2017-04-28 09:14:10> @U0B47KC3S: 🚀 Hi there ! the HETIC developer shool is organizing a complete week dev session the 3rd of july. Around 50 students will work intensively in 3 thematics : 1) Design 2) UI integration 3) Web marketting/comm 👌
2017-04-28 09:14:18> @U0B47KC3S: 20 students had a week session on design in the month of december, we got 11 templates ☄️ Precisely, these will be the starting point of the dev week to unify them into 1 template and then to integrate it
2017-04-28 09:14:24> @U0B47KC3S: We’ll have in june a meeting with <@U3QGT3Q74> and them 🤓 (reactions: @U37GZRZU6)
2017-05-01 15:23:20> @U0B47KC3S: 4 people hanging around the center of paris - currently at HD with <@U3QGT3Q74> and <@U20C8CKTL> working on the python #sigproc platform challenge
2017-05-01 15:42:12> @U0AAL4W13: :)
2017-05-02 14:40:33> @U37GZRZU6: Hey guys, I just created a shared document in our gitbook to gather ideas about what should be of top priority for our next iteration https://echopen.gitbooks.io/echopen_prototyping/content/inprogress/requirements/preparing-captech.html don't hesitate to complete it, it will be useful for next CapTech 😉 (reactions: @U3QGT3Q74)
2017-05-03 13:41:35> @U3GHS132Q: I do not know if someone on this channel already hear about it but I think it can be interessting https://medium.com/gahfy-android/tests-automatiques-dinterfaces-utilisateur-simples-sous-android-f2adcde2497a
2017-05-03 13:48:48> @U38HVMZ6K: I didn't knew about Hamcrest. Seems interesting.
2017-05-03 13:51:25> @U38HVMZ6K: In the other project running in my company they develop an Android app and they mostly use the testing tools provided by the Android SDK itself. Espresso and UI Automator for UI testing (https://developer.android.com/studio/test/index.html) and monkeyrunner for stress testing (https://developer.android.com/studio/test/monkeyrunner/index.html)
2017-05-03 13:52:37> @U38HVMZ6K: I'm not involved at all in these activities but from what I hear from them, the tools are quite confortable to use.
2017-05-03 13:53:28> @U38HVMZ6K: what they particularly like is the good integration within Android Studio
2017-05-09 18:56:06> @U3GHS132Q: http://www.numerama.com/tech/256382-google-sapprete-a-sortir-une-beta-publique-dandroid-o.html Go go (power rangers) you have 6 months to port the app on Android O (and use the PIP mode) 😜
2017-05-09 19:32:51> @U0B47KC3S: yep, there are indeed a few nice features

Navigation Menu

Uh oh!

Uh oh!

FilesExpand file tree

C04DFUV41.md

Latest commit

History

C04DFUV41.md

File metadata and controls