Project: Web Components for FHIR Resources

gsoc2018-project
gsoc2018
toolkit

(Judy Gichoya) #26

Anyone here attempted a components so far ?


(Parvati Ravindranathan Naliyatthaliyazchayil) #27

Not yet!! However , I have made few mock-ups of the components that I will be working on


(Saptarshi Purkayastha) #28

I think we are talking across each other and not getting the point. @namratanehete @SuKSW @parumenon1 @Zatoner_Dev - can we have a call to discuss the next steps. As a community, we don’t like to have synchronous calls because of timezone and accessibility issues, but I think this situation calls for it.

Please let us know your availability here - https://doodle.com/poll/e5vs5ypny46r9xqk


(Saptarshi Purkayastha) #29

Can you please post the mockups in your blog, as a blogpost. Maybe you should also add some resources that you have been using to learn about Polymer 3. or any other prep that will bring you and @SuKSW and other students who will build webcomponents in GSoC this summer.


(Namratanehete) #30

Yes that is a good idea. I have marked my availability in doodle.


(Judy Gichoya) #31

adding @lehone and @tenas97 too here


(Subhashinie) #32

Initially I had trouble with running polymer 3 components. Finally realized that “npm install -g polymer-cli@next” had not installed polymer 3 (checked using “polymer --version”). Using the same command again solved the problem.

As @sunbiz suggested @parumenon1 for those who are starting with polymer just like me, since “polymer init” have not yet been implemented for polymer 3 (https://github.com/Polymer/polymer-cli/issues/865) you can start with,

(They will display "Could not render the custom element. Check that JavaScript is enabled." which is written in between the custom element tags, or nothing at all if the cli has not been updated to support 3.0).

Was able to find https://medium.com/@jecelynyeen/polymer-3-0-preview-building-a-mini-card-game-ce8948265fd6 where an app was built successfully with polymer 3 preview 12. Rather than keeping the html templates within the js file she has kept them separately. It looked neat.

I’ll post the link as soon as a component is ready.


(Saptarshi Purkayastha) #33

Based on the doodle poll, besides a couple of hrs back today, the next best time is on May 12th 10am - 11:30 am EST. We will meet over Zoom - https://iu.zoom.us/j/343689707 . The meeting will be recorded and posted for anyone to follow who cant make it at the time.


(Parvati Ravindranathan Naliyatthaliyazchayil) #34

Yes i did post what you suggested on my blog post at


(Parvati Ravindranathan Naliyatthaliyazchayil) #35

Is anyone joining the meeting now?


(Saptarshi Purkayastha) #36

Recording of the call - https://iu.mediaspace.kaltura.com/media/Webcomponents+for+FHIR/1_bp3ey6hu


(Subhashinie) #37

This is the blog post regarding the resources I am currently working on.

Also for those who are working on Polymer 3.0, a stable version has been released four days ago. So Polymer 3.0 templates are now available via 'polymer init`.


(Subhashinie) #38

@sunbiz @judywawira Will it be alright if we use https://github.com/FHIR/fhir.js to request data from the HAPI-FHIR server?


(Subhashinie) #39

Also is it necessary to use material web components for textfields as well? With material it is something like image 1 and we could get a similar thing with only css like image 2. Can’t we use pure css at least for the text fields? We can maintain uniformity by using a single css file. (Although we can get image 2 with material, won’t it then import unnecessary amount of styles we do not need?)

Image 1: textfield

Image 2: inputcss


(Saptarshi Purkayastha) #40

I think it is necessary to use the material components. We will have a common style for all the elements and will be easy to integrate them in the EHR that @parumenon1 needs to start working on after the mid-term.

If all fields on the page use the same styles, it won’t be a problem of loading in the browser, since browsers are intelligent to download this once.


(Subhashinie) #41

Okay… I’ll continue with the material components.


(Namratanehete) #42

I also agree to use material components.


(Subhashinie) #43

I temporarily created a github repository to store what I have done upto now. It currently contains a few partially complete components for the schedule resource and a basic demo. Below is the demo using those components. Did not add the FHIR functionality yet. I guess the documentation of “dom-repeat” have not yet been updated for polymer 3.0. Until I figure that out, I’ll be working on schedule-add component and the components for Appointment this week, while improving the components shown below.


(Parvati Ravindranathan Naliyatthaliyazchayil) #44

Hello @sunbiz, @namratanehete, @judywawira I have made the blog post of this week where I have written about the components I worked on the past week and its functionalities. Would like to request you to give suggestions if something doesn’t seem correct.


(Art Eaton) #45

I am not going to sign up for Medium, but pretend a whole lot of clapping was added. In the meantime, add a really cool rock riff as background music.

  "I was working just yesterday", "But I just bought it.", "My cousin said that can't be the problem."  Yeah.  No shortcuts, and sometimes you have to backtrack to get your eyeglasses and lunch-box.

  -Excellent patience for the patients.  One component at a time.  Now, you can just script the implementation of one, run a quick compile and just have all the rest done in a few minutes..

…or just keep plugging away…

  Two weeks in, and you have something that WORKS.  That is awesome!