It's cool how simple it is to assign a field to a tab by setting the tabTitle attribute, but I think it would be better if tabs could be defined as parent elements to fields so that you only have to set it once.
Yep, I thought about doing that way, when I made it originally. The primary motivation behind making it an attribute, was to avoid too much clutter in the XML and only introduce elements when they had a fairly important grouping purpose or functionality attached to them. But point taken about many fields, I'll see if it would be possible to introduce some sort of grouping like you described.
Related a little bit to this: I've been thinking about making it possible to do configuration programmatically (fluid-style). Would this be something you would use instead of the xml if it was available?
Agreed, recompiling is annoying :) And I was only thinking it as an optional alternative to the XML or when the developer wanted to for an example make the tree dynamic based on grouping of content or automatically "discovering" tables in a database.
It could definitely be cool. Maybe I'm just still getting my head around all the features right now, so haven't really thought that far.
I've been starting to wonder if there is anything that could be done similar to peta poco though, ie define a model with attributes and dewd can auto administer it, how cool would that be :)
Yea, you can fairly easily edit some model/repository by writing your own Editor inherited from Eksponent.Dewd.Repositories.Object.ObjectEditor (or just the abstract Editor-class). You only need to override 3 methods, there's an example on CodePlex.
But it would be way cool to extract field information etc. from attributes on the model itself as you suggest. I've thought about this and it sort of ties into the notion of being able to configure dewd programatically, so when that's possible, editing some arbitary model decorated for dewd-use should be quite easy.
Feature Request: Make tabTitle an element, rather than an attribute
Hi,
It's cool how simple it is to assign a field to a tab by setting the tabTitle attribute, but I think it would be better if tabs could be defined as parent elements to fields so that you only have to set it once.
ie
It can be annoying if you want to change the tab name, and you have to do it like 20 times.
Cheers
Matt
Hi Matt,
Yep, I thought about doing that way, when I made it originally. The primary motivation behind making it an attribute, was to avoid too much clutter in the XML and only introduce elements when they had a fairly important grouping purpose or functionality attached to them. But point taken about many fields, I'll see if it would be possible to introduce some sort of grouping like you described.
Related a little bit to this: I've been thinking about making it possible to do configuration programmatically (fluid-style). Would this be something you would use instead of the xml if it was available?
- Sune
Hey Sune,
It would definitely be cool, but I do like the fact you can change it without having to recompile. Whether the purists will agree, I don't know :)
Matt
Agreed, recompiling is annoying :) And I was only thinking it as an optional alternative to the XML or when the developer wanted to for an example make the tree dynamic based on grouping of content or automatically "discovering" tables in a database.
Thanks for the input.
- Sune
It could definitely be cool. Maybe I'm just still getting my head around all the features right now, so haven't really thought that far.
I've been starting to wonder if there is anything that could be done similar to peta poco though, ie define a model with attributes and dewd can auto administer it, how cool would that be :)
Matt
Yea, you can fairly easily edit some model/repository by writing your own Editor inherited from Eksponent.Dewd.Repositories.Object.ObjectEditor (or just the abstract Editor-class). You only need to override 3 methods, there's an example on CodePlex.
But it would be way cool to extract field information etc. from attributes on the model itself as you suggest. I've thought about this and it sort of ties into the notion of being able to configure dewd programatically, so when that's possible, editing some arbitary model decorated for dewd-use should be quite easy.
- Sune
Sweet :)
is working on a reply...