I’m noticing that none of the CSS stylesheets in interface/themes work very well, other than the default style_sky_blue.css. Also there are still a few colors and such in globals.php that should be moved into the themes.
You fellows MIGHT go ahead and remove those styles, or make an interface to mod the styles. It sure stinks that an admin assistant decided to try to tweak these, then caused an uproar among the powers that be heheheheheh. If I do something with this, who should I submit code to?
This has already been dealt with in the development version (ie. fixed for the future 4.0 release). In the demo, check out Adminsitration->Globals->Appearance->Theme
Also can submit code in the “Code Review” tracker here on sourceforge (just remember to announce it here in the forums so the developers know to look for it)
Checked it out last night. Version 4.0 seems well on it’s way.
I figured style sheet tweaks and graphics (with all the examples already available) would have been something I could have done as minor grunt work, but with it already done it will be a long while before I have any code worth posting in a repository. I am not a web developer, and though php has sparked my interest, it will still be a while before my work will do more than draw stares and laughs ;) I will be there though.
I am glad to see that you guys put a globalvar tweaker right in the admin stuff. That should cut down on a lot of questions.
I’m gonna stick to learning php, and look for any opportunities to submit documentation/tutorials/readme’s to help out the project. As someone with coding experience and technical writing skills, but is totally outside his normal realm of experience, I can probably interpret things in a way the average supern00b will be able to understand. “Real Coders” seem to universally hate documentation, assume too much on the part of the user, and seem to use syntax more suited to their particular language/script. I recently saw a programmer posting measurements for some boat parts in VECTOR3(0,0,0).
and on.
Unless the CSS stuff is already in the bag for 4.0, I am willing to provide graphics of different styles for buttons etc.
I assume it would not be too much of a drag on bandwidth if some single-use buttons were used rather than printing a link text on top of a blank button, yes? And perhaps some on/off or mouse collision code?
I know that the sky_blue background is like a 4x4 gif, and we need to keep installs technologically sleek, but I personally think the interface could use some help in the display department, even at the cost of a tiny bit of bandwidth.
I think a few like "New Patient, View, Currrent, Done, Close, Billing, Encounter, blah-blah-blah would really help. I could make them either blank (assuming that we arn’t using visited link color differences) or pre-text. I could make alpha layer buttons so we only need one set for dark backgrounds and another for light backgrounds, or just give the buttons all backgrounds. We can have blank buttons for different languages or whatever.
If this is anything that might be desired (and indicated by someone in a position to say so), I’d like to make this my first contribution here. If so, I’ll get my GIT on.
Any contributions to standards related to graphics and buttons both style and use are appreciated. Keep in mind that while good progress has been made to move most of the style stuff to the CSS files, some residual hard coded stuff remains that will need cleaning up as we go.
-Tony
Hmmm…you guys probably already have a general idea of everywhere that might be, but otherwise anyone designing a style sheet using graphics would be able to track down inconsistencies pretty quick.
I guess that if everything is controlled by CSS, non-text specific (blank) scalable buttons are the way to go. Otherwise, hard code would need check a flag for what style is in use before a particular button is called unless the graphics resources were assigned in an array/class. I like the of being able to use symbols as well as text, and not just a dead icon like the folder image next to a document link in the imported documents. THAT bit has caused much confusion in the past, as folks try to click the folder image to access the contents of a directory/category of document.