OpenLayers Integration with existing site/code

Take an OpenLayers template(map stack with Google, Yahoo, Bing, and OSM base maps) and integrate it with existing website/code. Overlay layers atop the aforementioned base maps will include point, polyline, and polygon vectorial geometries from a GeoServer, and these layers are originating from a PostgreSQL/
PostGIS source. These vectorial overlay layers need to be editable. Here is a starting point example showing all the base layers mentioned above, and vectorial editing tools: http://openlayers.org/dev/examples/spherical-mercator.html

The existing website that this OpenLayers map-stack needs to be integrated with, has a database of 100,000+- clave numbers and corresponding polygon geometries that represent physical properties(as in real estate). Although most clave numbers have a corresponding polygon geometry, about 8% of these do not, in which case they will typically have point geometries(aka POIs or place marks). When a clave number is queried, the corresponding vector geometry from GeoServer(ala a PostgreSQL/PostGIS source) needs to be displayed atop the map stack(base map(s)) zoomed to an appropriate zoom level. About 2% of the clave numbers in the database do not have either polygon or point geometries, in which case the map simply displays the respective region/bounds, and the user can create a new polygon or point geometry for said clave number record.

In all cases, the polygon or point geometries need to be editable, and should display handles for resizing, rotating, and dragging. When a polygon or point is moused-over/rolled-over, it should change states. Here are some examples:
moving polygons/points:
http://openlayers.org/dev/examples/rotate-features.html

change state when rolled-over:
http://openlayers.org/dev/examples/sld.html

fill & stroke example:
http://openlayers.org/dev/examples/symbolizers-fill-stroke-graphic.html

bounding box for resize & rotate:
http://openlayers.org/dev/examples/transform-feature.html

drawing holes in polygons:
http://openlayers.org/dev/examples/donut.html

In the case of polygons, snapping and splitting needs to be implemented. Here are some examples:
snapping & splitting vertices:
http://openlayers.org/dev/examples/snap-split.html

snapping example:
http://openlayers.org/dev/examples/snapping.html

splitting example:
http://openlayers.org/dev/examples/split-feature.html

When a polygon or point is clicked on, a pop-up needs to display pertinent information from the PostgreSQL database. Here are some examples:
pop-up window example:
http://openlayers.org/dev/examples/sundials-spherical-mercator.html

overlay and popup example:
http://openlayers.org/dev/examples/wmts-getfeatureinfo.html

Each time an existing polygon or point geometry is edited/changed, each version of said geometry must be saved/stored in the database so these different states may be viewed and compared. This means a single clave number may have multiple geometries that represent the most current/recent state of said property, as well as historical states of said property. Using a simply forward and backward arrow/icon will suffice, and time/date stamps should be displayed for each respective state/version of said geometries. Here is loose example showing numerical input of time/date information to query and display various geometry states:
WMS time example:
http://openlayers.org/dev/examples/wmst.html

This map-stack is to be displayed on the individual clave number/record page(dmp.php), and on this page only one geometry is shown ata time on the map-stack/base maps.

The map-stack also needs to be displayed on the claves.php page, wherein unlike the above mentioned dmp.php page, the claves.php page can display multiple geometries atop the base maps at any given time, as are selected by the user via the list of clave numbers as are found in the clave number groupings. As few as one single geometry, or as many as 100,000+- polygon and point geometries may be displayed on this map-stack on this claves.php page.

OpenLayers needs to reside on the server, and not called remote via http://www.openlayers.org/api/OpenLayers.js .

Need to use Google Maps V3 API which requires no API key, as is the case for their previous V2 API(more info here: http://openlayers.org/blog/ ).

Include the loading panel/image:
http://trac.osgeo.org/openlayers/wiki/Addins/LoadingPanel
http://dev.openlayers.org/addins/loadingPanel/trunk/examples/loadingpanel.html

Include the bookmark feature:
http://trac.osgeo.org/openlayers/wiki/Addins/Bookmark
http://dev.openlayers.org/addins/bookmark/trunk/examples/bookmark.html

When the project is completed, the user should be able to query a clave number/view clave page, wherein the map-stack loads/displays the corresponding vectorial polygon or point. The polygon/point changes state when moused-over, displays informational pop-up when clicked, is edited when editing tool is selected, shows bounding box when editing for resize, rotate, etc., can create holes in polygons(multipolygons), can add bookmarks, properly saves geometries to PostgreSQL/PostGIS database, maintains each edited version of time/date stamped geometry, can browse back to older versions of geometries, older versions of geometries are not editable(for historical purposes).

Please ask questions if you need any clarification.

Thank you,

Eric Jarvies