kiranrajendran wrote on Wednesday, December 12, 2012:
New iframe/Jquery based layout……
kiranrajendran wrote on Wednesday, December 12, 2012:
Could anyone give me a suggestion regarding the possibilities of the layout change. Currently we are using the original frame based layout , but we are looking for a new layout which is based on iframes and jquery. As a developer i am bothered about the difficulty in the layout change because of the old frameset structure and its related functions. So i want to know how feasible this layout change, does it take more time for the modifications?
Please give me an idea asap….
yehster wrote on Wednesday, December 12, 2012:
You can take a look at what is involved in updating the interface here:
https://github.com/yehster/openemr/tree/tabs-master-12-12-12
kevmccor wrote on Wednesday, December 12, 2012:
Do you plan to move interface/main/main_screen_tab.js to the library/js/ directory? Also, what about documentation or comments? Perhaps this is all preliminary/experimental work, but “main_screen_tab.js” does look promising, even though I don’t know too much about javascript. It looks like the idea is tabs with related iframes to replace the top and bottom frame concept. I imagine that could create a really good interface which is relatively easy to script if it is easy to relate and populate the iframes. You have been busy.
Thanks
yehster wrote on Wednesday, December 12, 2012:
Do you plan to move interface/main/main_screen_tab.js to the library/js/ directory?
No. I believe that “highly related” files should reside in the same directory. It shouldn’t go into library/js just because it is javascript.
No documentation or comments. This code is presented “as-is/use at your own risk.” The good news is that if you are using it and run into a problem clicking “Home” will bring back the old interface.
kiranrajendran wrote on Thursday, December 13, 2012:
Thanks Yehster nice job. So you are saying that there would be the probability for errors in this particular version? if so ,then what would be the issues ,in interface level or functional level?
yehster wrote on Thursday, December 13, 2012:
there would be the probability for errors in this particular version
Even the most rigorous of scientific experiments has non-zero probability of errors.
I’m not aware of anything major, but since this code interacts with nearly every function in the system it’s a big task to evaluate it thoroughly. My testing has also been almost exclusively with Firefox, and given the heavy use of javascript, there may be problems with other browsers.
The one really minor glitch I do know about is that some pages don’t have a “title tag” which the tabs can use as a name to display, so when you navigate to certain pages, the text displayed on the tab doesn’t get update properly. The dynamic patient finder, administration>practice and administration>service page are examples of this.
The kinds of problems that one would be most likely to find are links that target other frames might not open properly.
One of the issues that I have had to deal with is that besides the main title,left_nav,RTop and RBot frames, some of the pages like the calendar and the “load form” mechanisms introduce additional frames.
If you want to see what the interface looks like, checkout the demo video in my campaign for funds for Fee Sheet Enhancements.