Hi Matthew, thanks for you comments
On Oct 20, 2005, at 10:02 AM, Matthew Bevan wrote:
First, I specify title attributes on my SQLObject properties, yet
CatWalk ignores them. I think it would be a good idea to display the
"title"s in headings, and with a : appended to them on forms. This
would provide an easy method to make CatWalk a little more end-user
friendly.
I need help here, I must admit I don't know what you are talking about.
Where do you define a title? (A model example will be nice)
Having the relational data available from within the preview is bloody
brilliant. Kudos! However, being able to add new "child" records
from
this same interface (add another button per linking table next to
Cancel and Edit called "Add <ObjectName>") would make it perfect.
You are right on spot, that feature was suppose to be in this release,
but I wanted to make it part of my standard grid control, instead of
doing something
specific for relatedJoins. And as the grid control need a general
overhaul i decided to wait.
Being able to set the default view in a configurable way, and even
hide
the Structure, for example, or even whole objects, would again make it
a bit more user-friendly. Combined with custom "title"s for the
objects and the relational system already there, this would allow a
developer like me to create a quick, and very elegant administration
interface for my clients.
Nice point. I'm planning to add more state into it, so when you
choose and object
and select the 'browse' view (I'm not shure about this lable, will
'list', 'objects' or 'rows' be better?), that label become active,
and if you choose another class from your model the main content
will load the 'browse' view, instead of the default structure.
The same goes for 'cancel', it shoul take you back to the view you
where before.
Right now if you choose preview on an object listed in a relatedJoin
and then hit cancel you are trown back to the related object's browse
view
and not to the original context.
I'll be investigating thus further, and I will attempt to see how much
I can get done by myself. First, I think I'll tackle the titles bit -
now to learn enough Python to detect the presence of an optional
attribute...
While you are at it let me tell you CW doesn't (yet) handle default
values =(
With all this user-friendliness, I'm thinking
Cheers
Ronald
