Webdev/SeatingChart: Difference between revisions
< Webdev
Jump to navigation
Jump to search
(Created page with '''Doing some preliminary research for the upcoming seating chart app.'' Just looking for feedback, comments Sorry if many/all of this has been covered prior to my arrival. Just t…') |
No edit summary |
||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
''Doing some preliminary research for the upcoming seating chart app. | = Some General Questions = | ||
''Doing some preliminary research for the upcoming seating chart app. Just looking for feedback, comments.'' ''Sorry if many/all of this has been covered prior to my arrival. Just trying to get up to speed on this one before I start work on it.'' | |||
Goal is to evolve this page into a sort of requirements doc for this. | Goal is to evolve this page into a sort of requirements doc for this. | ||
= | === Proposal === | ||
==== Component I : Floorplan editor ==== | |||
*Display an image of the floor plan in a Web interface. | |||
*User can assign landmarks (seats/desks) on the image by simply clicking on a point | |||
Questions? | |||
*do we even need to define 'seats' Is it okay to just have emp icons on the image of a floor plan | |||
*where do we persist this info | |||
==== Component II : Assign Emp to Seat (landmark) ==== | |||
*In wed interface display the image with 'landmarks' layer | |||
*user can click a seat and 'assign' an emp to the seat | |||
**could also remove an emp (and place them elsewhere) | |||
Questions? | |||
* | *where do we persist this info | ||
<br> | |||
==== Component III : Confluence of The above with the Moz phonebook ==== | |||
*Seating chart location becomes an ldap field displayed on a phonebook record | |||
*clicking the link takes you to the floorplan image with emp's seat in focus | |||
*in on the "view the seating chart, we enable URI like this | |||
.../seating/skeen@mozilla.com <br> we would not need to add any fields to Ldap | |||
Latest revision as of 23:04, 25 March 2010
Some General Questions
Doing some preliminary research for the upcoming seating chart app. Just looking for feedback, comments. Sorry if many/all of this has been covered prior to my arrival. Just trying to get up to speed on this one before I start work on it.
Goal is to evolve this page into a sort of requirements doc for this.
Proposal
Component I : Floorplan editor
- Display an image of the floor plan in a Web interface.
- User can assign landmarks (seats/desks) on the image by simply clicking on a point
Questions?
- do we even need to define 'seats' Is it okay to just have emp icons on the image of a floor plan
- where do we persist this info
Component II : Assign Emp to Seat (landmark)
- In wed interface display the image with 'landmarks' layer
- user can click a seat and 'assign' an emp to the seat
- could also remove an emp (and place them elsewhere)
Questions?
- where do we persist this info
Component III : Confluence of The above with the Moz phonebook
- Seating chart location becomes an ldap field displayed on a phonebook record
- clicking the link takes you to the floorplan image with emp's seat in focus
- in on the "view the seating chart, we enable URI like this
.../seating/skeen@mozilla.com
we would not need to add any fields to Ldap