I'm just testing Aware IM out, it's interesting to say the least. I can see a lot of efficiencies to the approach taken. We're software devs, quite used to having coding and SQL so we're trying to see if we have to trade away too much.
One question I have is about unique values for attributes. The Library example application has a rule that keeps RegularUsers LoginName unique
If EXISTS SystemUser WHERE (SystemUser.LoginName=ThisRegularUser.LoginName AND SystemUser.ID<>ThisRegularUser.ID) Then
REPORT ERROR 'User with this login name already exists. Please choose a different name'
In most modern 'regular' databases, configuring a table column so that it only allows unique values would be a checkbox setting. Aware IM seems to require 'coding' for the same thing...but of course it's not really quite the same thing, as Aware IM is handling the entire stack including user interface. Still I wonder that why it takes a rule, and it's a checkbox in Aware IM like the 'required' setting?
Second question, and this might become obvious as I read more in the docs, but can one create a page that combines views and forms, ie has multiple outputs on it? In the example apps so far the interface is usually a single form for a single purpose. Just curious as to how versatile it can be.