Oops.. should have previewed the post...
Better to use multiple nbsp or < pre > tag?
Not trying to line up the columns, just not have the output all mashed up.
I don't wanna dig you guys for code-lernin', I have peeps for that, but I really need to get on the bandwagon and help fix stuff. It may be rough at first.
Last edit: Art Eaton 2014-12-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I meant a table within the td that you are currently writing those 2 lines into. What you are doing is OK (I think, didn't test), just depends on what effect you are going for. I personally wouldn't try to space them out like that... if you want to distinguish patient data from labels, then it seems better to use color, size or bolding to distinguish, but then it becomes a bigger project to make it consistent everywhere.
Rod
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know you are right when you say to add these as TD's, and I am sure we will redress the print view of a lot of stuff in upcoming months.
The issue was that the ID and DOB were running together in an illegible manner (at least with FF). Label-space-value-break-label-space-value worked better visually than label-break-value-break-label-value. Color changes are nice, but they don't do much when printing B/W. Whitespace was the MD reviewed preference, and Reception agreed...so I minded my betters. Bold tags for the labels are probably a good idea everywhere though.
For the moment, I am satisfied, 'cause going any further should equate to a general spiffing up of the whole thing, but it works pretty damn good right now.
The next version (with a FAR wider net thrown) should allow configuration at the "codes" level for opting in/out of codes on the fee sheet printout vs. the fee sheet drop downs. The other element on our wish list is to bridge the options available between the two lists (Fee_Sheet and Service_Categories?) that determine the content of the fee sheet drop downs. We ship OpenEMR with the Fee_Sheet list, support the Service_Categories, and don't document the differences. We need the Fee_Sheet multi-code selection feature in the new system, and we need to expand it to more fully support adding modifiers, units, notes, diagnosis/justification, and all that. Thus the short term kludge approach. Gets a branch onto the Hack Shack repo as a reminder if nothing else.
-Rod, Kevin, Brady, thank you so much as usual.
Last edit: Art Eaton 2014-12-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added some comments on github. Thanks.
Rod
54228c9b08a07e69edde3ec102a9aca4cf1647ca
Followed your instructions (I think) and popped another commit.
Added a couple more suggestions. Otherwise, if it works, looks good to me.
Rod
a32989f032d555542a449544dae58585baa46a3b
Try #3.
Is it better to use multiple for a tab, or use the
If you really want the columns to line up, I'd suggest putting them in a table.
Rod
They are in a table!
Instead of padding with nbsp, the width could also be explicitly set.
Oops.. should have previewed the post...
Better to use multiple nbsp or < pre > tag?
Not trying to line up the columns, just not have the output all mashed up.
I don't wanna dig you guys for code-lernin', I have peeps for that, but I really need to get on the bandwagon and help fix stuff. It may be rough at first.
Last edit: Art Eaton 2014-12-10
I meant a table within the td that you are currently writing those 2 lines into. What you are doing is OK (I think, didn't test), just depends on what effect you are going for. I personally wouldn't try to space them out like that... if you want to distinguish patient data from labels, then it seems better to use color, size or bolding to distinguish, but then it becomes a bigger project to make it consistent everywhere.
Rod
I know you are right when you say to add these as TD's, and I am sure we will redress the print view of a lot of stuff in upcoming months.
The issue was that the ID and DOB were running together in an illegible manner (at least with FF). Label-space-value-break-label-space-value worked better visually than label-break-value-break-label-value. Color changes are nice, but they don't do much when printing B/W. Whitespace was the MD reviewed preference, and Reception agreed...so I minded my betters. Bold tags for the labels are probably a good idea everywhere though.
For the moment, I am satisfied, 'cause going any further should equate to a general spiffing up of the whole thing, but it works pretty damn good right now.
The next version (with a FAR wider net thrown) should allow configuration at the "codes" level for opting in/out of codes on the fee sheet printout vs. the fee sheet drop downs. The other element on our wish list is to bridge the options available between the two lists (Fee_Sheet and Service_Categories?) that determine the content of the fee sheet drop downs. We ship OpenEMR with the Fee_Sheet list, support the Service_Categories, and don't document the differences. We need the Fee_Sheet multi-code selection feature in the new system, and we need to expand it to more fully support adding modifiers, units, notes, diagnosis/justification, and all that. Thus the short term kludge approach. Gets a branch onto the Hack Shack repo as a reminder if nothing else.
-Rod, Kevin, Brady, thank you so much as usual.
Last edit: Art Eaton 2014-12-11