Generic XHTML Panel Enabled When Outside Model

Follow

Peter Kristensen

• August 10, 2018 16:54

As as Solution Builder

I want to place Generic XHTML panels outside models

So that I

• can keep them better organised
• put them in a place where they are more visible
• put them in a place where they do not interfere with visible panels
• put them in the same place where I put other panels that should not be visible on the model, such Session Variable, Model Variable, Info Panel

The benefits are the be easier to work with Custom XHTML panels and MooD BA will become more consistent to work with

Acceptance criteria is that Generic XHTML panels can be placed outside models and still work

Priority is medium (going towards high as we start to use them more or more)

1

• 

  Peter Kristensen

  • August 11, 2018 10:23

  I have just discovered when I hide Generic XHTML panels under a textbox on the model, the textbox becomes a foreground symbol. This is another reason why being able to place Generic XHTML panels outside the model is a good idea.

  0

  Comment actions Permalink
• 

  Giles Middleton

  • November 19, 2018 08:36

  Hey Peter,

  One thing I noticed when dealing with Soren's issues with a repository the other day, is that it had a model master with about 6 off screen XHTML panels. Maybe as a 'palette' of possible XHTML options.

  If we enable off screen XHTML panels, all of these would suddenly come alive.

  We'd rather not add yet another option (I think I've just defined an acronym AYAO). 

   

  What's your thoughts on that?

  0

  Comment actions Permalink
• 

  Soren Staun

  • November 19, 2018 09:21

  I think Kev has a case he's following on how to better support these extensions in JS for MooD 16, and it may be interesting to consider further things in there like if there was a cleverer way of adding these boxes in a kind of component style.

  Could imagine you could enable/disable them, perhaps use MooD to do so given queries? That could be potentially really powerful. I have a few idea, but I'm saving them for Kev's roundtable around this topic.

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • November 19, 2018 09:31

  I think it makes no sense that XHTML panels are "disabled" when off screen, because they are invisible when on screen. Also, when other panel types are placed off screen, they are still "enabled", so XHTML panels behave inconsistently. If this was a new behaviour, I would have categorised it as a bug.

  I think, if you include the changed behaviour in the release notes, it won't be a problem.

  0

  Comment actions Permalink

Please sign in to leave a comment.