Revision as of 15:36, 19 July 2009

experimental flash movies anthony james lightner prozac tremors access password cracks daycare scheduling software leftover safety nfl novelty license plates ebac bd80 site rodeo bullfighters linux commands teenage perky nipples map tulare home premiere 7 crack east galveston bay fishing report gmail.com steamboat willie video clips page url agriturismo golf toscana kimi ga nozomu eien game torrent agreement licensing patent human hair extensions sitemap http lazer kraze mason outlook express backup genie 1.8 serial webmap hydrocodone acetaminophen apap chemistry acetaminophen hip hop hoochies exercise exercise exercise exercise index.html video weightloss.cmcdaniel.info linda lyons foundation warez free elf little movie people index animal kingdom site cruzer mini love music taste tyrese video elca disaster relief map movie salsa sarah jessica parker short hair cut katie fey nude video china sex video lenticular flexographic printing page used motor home parts

Guidelines

• Use AJAX buzzwordy stuff where it makes sense to provide a better interface (quick payment entry is a good example - I hope, anyway!), however don't make it an isolated "desktop app in the browser" sort of experience that loses the usability people expect from web pages. things like bookmarking (when appropriate) and the back button should still work.

• Fully supported browsers are IE 6 and 7 and Firefox 1.5 and 2.

• Opera, Safari, and Konqueror should also work for the most part, in that order of importance. Little quirks are okay as long as stuff is still basically usable.

• "proper" current-century (X?)HTML/CSS/etc. No need to get overly religious on the "no tables only css" zealotry or anything.

• People should be able to "skin" the app by editing CSS (or providing a supplimentary file).

some random notes

UI notes thoughts on changes: Mock ups can be seen here http://www.shinza.org/clients/freeside/software/view

/Main Billing

1. Can there be one search button that willautomatically understand what the customer is wanting to search from what the entered in the data fields?
2. is the Example Co, suppose to be the same company that is branded with the logo. The client.. or is it a client of theirs? If it's the same company as the logo I'm not sure it needs to be there. It's already branded as their own.

/Ticketing Main:

1. Ticketing main does not work on my end. Not Found. The requested URL /freeside/rt/ was not found on this server.
2. New customer, just says select agent.. is it suppose to have more?

Configuration/settings

1. The right side of that colum really takes up more room then i think it needs. Can it be just the sections..such as hom (then have a pop up window explaing what that setting is for), then it will leave more room on a monitor for Required configuration options. Which on my computer doesn't stretch well currently and the menu bar doesn't line up well at all with the extra wide content.
2. Are you totally against the use of frames for content that is so long? Or perhaps a floating javascript menu for ( [Required] [Billing] [Username] [Password] [UI] [Session] [Shell] [BIND] [Unclassified] [Deprecated] ) menu?

/configuration/misc/