upon successful connection, what do we do ?

[mfrasca]

currently, the server states and does this:

// Upon a successful connection, we send the complete list of plants for
// which we have the geographic coordinates, and register three handlers that
// will be used as receivers of client changes. The client will emit
// messages of type 'move', 'insert', 'delete'.

we have now a different approach:

• Upon a successful connection, we display gardens.

• the user selects one garden, (client tells the server about the choice),

• server replies passing the client plants for that garden.

• user leaves garden - client tells server it's not any more looking at specific garden and deletes from memory list of plants.

we only want very special clients to be allowed to edit plant location information. I suppose I will implement this with some sort of tokens.

[mfrasca]

I also think we should not differentiate among gardens, plants, photos, or information panes. all are localized objects, all have an icon (like our ugly compact target icons), possibly an awesome marker (meaning a colour and again an icon), and a brief html text that will be shown in the popup when the marker is clicked on.

I don't know how to realize the 'click here and send a request to the server', but we will see... why I'm saying this: imagine you look at the pop-up for a garden, one action has to be please zoom into the garden; imagine you look a tthe pop-up for a plant, one action has to be please highlight all similar plants; what else... ?

[mfrasca]

there's cleaning up to do, but that's a different issue