While a default value is useful, the ability to have a "one-click"
option to toggle all current values is generally more useful. A few
of the things that this allows the user to do is to fix
existing-but-undesired settings, make a project's settings consistent,
and change a project from one type of locking to another. Just add
an "Update" button after the default value to push the default value
to every entity attribute.
Cayenne supports this for schema, superclass, package, and optimistic locking.
On 4/27/07, Mike Schrag <mschra..dimension.com> wrote:
> > as an aside, and the reason why this bug report was lodged, was
> > especially because I found that the more entities I added to the
> > model the slower Entity Modeler was, with all the notifications and
> > whatever it was doing in the background (I suppose verifying the
> > model with every action). Thus, little things like this became
> > increasingly irritating as it was just another thing that slowed
> > the process down for modelling the entities.
> This is a bigger bug report to me than the locking issue (though I
> can just make a preference pane with a default value).
>
> > e.g., Clicking on the "Add new attribute" button five times in a
> > row would take longer than 5 seconds to populate. Beach-ball city
> > after a while... and clicking each of the attributes locking to
> > untick the ones I wanted unticked, took too long also. Too much
> > mouse clicking.
> I've never gotten a beach ball in EM.
>
> What kind of machine are you on? How big of a model and model group
> are we talking: model count, entities in the active model,
> attributes in the entity?
>
> ms
>
>
This archive was generated by hypermail 2.0.0 : Fri Apr 27 2007 - 11:32:47 EDT