Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Q1: Hierarchical UI element hiding - Optimizing your GPM to avoid hiding elements that are already hidden via a parent is not going to have much of a performance boost in my opinion. My reasons:</p> <ol> <li>You load permissions once when a user logs in, not all the time.</li> <li>Depending on how it is coded, additional processing will be needed to determine the hierarchy anyways.</li> <li>With adequate planning you could avoid registering dozens and dozens of components and stick to overarching containers.</li> </ol> <p>If you really want to keep track of hierarchical information you can always use the 'contains' method that all container components provide for checking if a DisplayObject is contained anywhere in its child list (including down the chain). This could be called up each time a component is registered to check if it already has a registered parent. </p> <p>A flag could then be set in a dictionary to ignore hiding on that component. This flag could get checked first while iterating over the list of registered components to determine what should be hidden. The dictionary could use keys that correspond to the registered component's UID. Furthermore this flag could be used to ignore the component when it comes time to ignore other GPM functions, like form disabling (as the form would never be seen anyways).</p> <p>Q2. Off the top of my head you could disable/enable components, implement state changes, or intercept events, and all alerts. This is really too broad of a question as anything could be done - really up to the designer.</p> <p>Q3. You could:</p> <ol> <li>Provide parameters when registering your components, such as to indicate what type they are (container for hiding, form for setting to read only, etc.)</li> <li>Check each component as it is registered to determine what is going to be done with it.</li> </ol> <p>You would essentially be establishing a contract with various components where the GPM is aware of their interfaces and interacts with them accordingly.</p> <p>Q4. You can always set a form to be disabled (enabled = false). This prevents any user interaction. Some skins will change to indicate that the components are disabled so you may want to modify their skins to prevent some of this display behavior. On that line, you could also change their skins to hide certain elements such as the TextInput box's border so as to make it look more like a 'view' than a disabled input.</p> <p>It would be possible to create a 'transformer' that changes TextInputs with RichText components and such. This would take a decent amount of work and should probably be built into an extended Form class instead of the GPM. I think different skins states for each component type may be a better solution, so as to avoid creation and destruction of components just to change how the form appears.</p>
    singulars
    1. This table or related slice is empty.
    1. POBest way to hide/disable GUI elements based on user's privilege?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKevin Gallahan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest way to hide/disable GUI elements based on user's privilege?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAgreed. I also asked the same question on ExtJS forum and people there suggested I implement the GPM as a plugin and attach the plugin to any component that needs access control, which looks to me the right way to go with Ext. Another suggestion was that each UI component that needs access control be assigned a ResourceId and the mapping between resource ids and spring security roles be done in GPM, which is a even more centralized design and minimizes access control code pollution to the UI code.
      singulars
      1. PO
      1. USTong Wang
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload