Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Matt Brailsford 3642 posts 19322 karma points MVP 9x c-trib
    Oct 31, 2012 @ 16:50
    Matt Brailsford
    0

    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

    <tab title="something">
        <field ... />
        <field ... />
    </tab>

    It can be annoying if you want to change the tab name, and you have to do it like 20 times.

    Cheers

    Matt

  • Sune Bøegh 64 posts 374 karma points
    Nov 01, 2012 @ 13:09
    Sune Bøegh
    0

    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

  • Matt Brailsford 3642 posts 19322 karma points MVP 9x c-trib
    Nov 01, 2012 @ 13:12
    Matt Brailsford
    0

    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

  • Sune Bøegh 64 posts 374 karma points
    Nov 01, 2012 @ 13:34
    Sune Bøegh
    0

    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

  • Matt Brailsford 3642 posts 19322 karma points MVP 9x c-trib
    Nov 01, 2012 @ 13:37
    Matt Brailsford
    0

    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

  • Sune Bøegh 64 posts 374 karma points
    Nov 01, 2012 @ 16:27
    Sune Bøegh
    1

    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

  • Matt Brailsford 3642 posts 19322 karma points MVP 9x c-trib
    Nov 01, 2012 @ 16:30
    Matt Brailsford
    0

    Sweet :)

Please Sign in or register to post replies

Write your reply to:

Draft