> > We, Camptocamp, have been using MapFish/Pylons with repoze.who|what. > So far we're very pleased with repoze: it works great, it's well > documented and its main developer has been very helpful on the mailing > lists.
Access control on cartographic resources/data is one thing that I'm sure repoze.* does well. However, I was wondering how you cope with UI generation. If both users A and B have read access to resource X, but only user B has write access to it, how does the final MapFish UI render the "map" to the user ? That is, for user B there would be an editing widget available but not for user A. Cheers, Yves _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
