Everything you wanted to see in the LightSpeed designer but ran out of screen space for

(with apologies to Woody Allen)

There’s a lot of information in the LightSpeed designer — data types, code generation settings, aggregates, et cetera et cetera — and we’ve had a few people ask if we can make some of this information a bit more visible on the design surface. I’m pleased to announce that the latest LightSpeed nightly builds provide some optional display settings to do exactly this.

You can access these options through a new LightSpeed page in the Tools > Options dialog:

The current options are as follows:

  • Display the data type of each property before its name, e.g. Int32 Age
  • Display which named aggregates each property is a member of after its name, e.g. VideoData (@WithVideo;WithAll)
  • Display a lazy-load indicator on the property icon if, given the current view filter, the property would be lazy loaded (that is, the property is part of a named aggregate and that aggregate isn’t the current filter)

Here’s how an entity might look with the data type and aggregate name options:

Of course, you probably won’t want to run like this all the time but it can be handy when you’re trying to get an overview of your model.

We’ve also added an icon to distinguish properties that aren’t code-generated, as a visual reminder that you’ll need to apply attributes and things to them by hand. You don’t need to turn this on — it happens automatically.

Want to try it out? Download the free Express edition, or if you’re a customer then get the latest update from the store. (LightSpeed 3.11 only; it will be in the 4.0 beta shortly.)

Any other view options you’d find useful? Leave a comment or post a feature request in the forums!

Tagged as LightSpeed

5 Responses to “Everything you wanted to see in the LightSpeed designer but ran out of screen space for”

  • Can you separate the DataType with a delimiter instead of a space?

  • That looks promising!

    I would prefer that the property names starts at the same horizontal position (a more table like layout) or use a bold font for the property names. So that the type and property is more distinguishable.

  • Johan: We could do this, obviously at the expense of ‘option clutter.’ What presentation are you thinking of?

    Sornt: Yes, we would have liked to do something like this, but we believe it would have required major work, far more than we could justify for a feature like this. Sorry!

  • Ivan my initial though was just a colon. I’m sure other users would like to other types but the colon worked well for another DSL that I used.


  • Just want to say thank you for the dispay options!
    Is is now much more simpler/convenient to spot the
    essentials of the model – well done :-)


  • Leave a Reply


Join our mailer

You should join our newsletter! Sent monthly:

Back to Top