Progress!!!

Two very awesome achievements have happened today. First of all, the sliding divs now work thanks to some hacking by Josh. Secondly, I removed "less significant" information that is displayed when a partial search is done (the age and birthday) in addition to shortening the name "Identifier" to "ID" and "Middle" to "M" to remove a sideways scroll bar because of the excess tabular data.

Currently we are trying to remove the error that displays in IE and Firefox. Here is what the page currently looks like:

Trial and Many Errors

This past week, Josh figured out how to make our divisions expand to accommodate the patient search. When the user types in a partial name or information about a patient they are searching for, the div now expands with the information. We have unfortunately one issue with the expansion.

After a partial search is done and the information is in the div, when the user collapses and re-opens the div, there is a scrollbar.. We still don't know why, but that is an issue we are still trying to fix we just haven't invented the correct google search keyword yet.. :)

Another error that we discovered only reveals itself in IE and Firefox. With IE.. I mean we kind of expected something to mess up, but with Firefox showing the same error, its definitely a concern. It is some type of javascript error. The crazy thing is, we didn't write any of it and when we delete it/comment it, nothing changes.

We suspect that the error lives in another document that we haven't found yet. We found the line that it claimed was causing the issue, but like I mentioned above, changes to that line do not change the error. Below is a screen capture of the error on the page and a close up of the error.

Almost forgot to post..

Me and my lab partner have been so preoccupied with tweaking the jsp in openMRS that I forgot to blog about it. Here is what we have:

The changes include the small logo at the top, the upper right hand help/logout area, the gutter bar, the gutter menu, and spacing issues with the content. Most of the difficulties we are experiencing have to do with finding where everything lives inside the vast depths of openMRS. We've made a lot of progress these past few weeks and I hope to continue along that trend. We should have this page finished by the end of the week.

No Rest for the Weary..

Despite the semi-pessimistic title, I have a lot of good news to post!! We have FINALLY finished the design for the find/create patient page. Thanks to Dr. Matocha giving us a little slice of mathcs.obu.edu, Tyler letting us borrow his iPhone for comparisons with my Blackberry, Google, and most importantly caffeine, we have a fully (mostly..) functional page!! :D

We're still working tonight so updates will probably come again tomorrow..

Moving Forward

We have started working on the find/create patient page because it has a high priority. We've condensed, cropped, and created until we have a mostly functional and aesthetically appealing web page. There is still much to do to even complete the page that we are working on but it is looking nice. However, this is only half of the job.

We still have to learn how to use JSP to generate html for the mobile site. The second part is definitely going to be more difficult than the html design..

One Page at a Time

We have opted to neither redesign the entire site, or hack the CSS to the best of our ability. We had some correspondence with bwolfe and we have agreed to design one page at a time (starting with the most needed for the site) for the mobile interface. Once we have designed it in html, we will find out how to create the JSP that will generate our desired html. And of course we will be editing the CSS. Tonight we have started and so far, so good. It shouldn't take us very long to complete our design in html. JSP on the other hand.. but that's another post.. ;)

JSP-losion..

Okay, so I haven't blogged in a little bit and in that empty span several things have happened. What was once a simple edit has turned into a possible rewrite. As me and my partner dug deeper into OpenMRS, we have discovered that the site is completely generated through JPS.

To successfully complete our ticket, we have two options: 1. Throw in bits of code to compensate for the mobile version of the site and sort of patch it together or 2. Create a new mobile version of the site. Either way, things are gonna get messy. I believe we will pick #2 and write our own version which will take forever.

The theory is that even if we don't finish it, if we do things correctly and make our code "pretty" so to speak, someone can pick up where we leave off to complete the project. We do have high hopes that we can finish it or a significant portion of it. The most difficult task will be learning JPS..