Trippy grid of squares. Click to show wireframe.
This is somewhere to note down some ideas about how to design UI's in qlikviews. It's possible to do lots of things in qlik, but that doens't mean we should just do whatever we feel like. In particular in this document, I want to think about how we implement interactions with the UI in Qlik - I've made mistakes in this regard in the past and ended up with applications that were particularly difficult to maintain (chains of macros, lots of hidden/overlapping objects, a million variables driving show/hide conditions, etc.). Requirements from clients can often make certain ways of interacting with an object seem like a good idea:
It would be cool if I could click on this object and have another view pop up on top with some extra information. Can we use a macro to do that?
But it's a rare occasion that decisions that deviate from native qlik methods for interactions end up being a good idea. Whilst they may (or may not) look pretty, they are usually time consuming to maintain and pr
| # Ignore Data Files: | |
| # Rather than excluding the whole directory structure, lets exclude specific file types. This way we can still store notes or other useful data. | |
| # Qlikview Data Files | |
| *.qvd | |
| *.qvx | |
| # Excel Files: | |
| *.xlsx | |
| *.xls | |
| *.xlsm | |
| # Text Data Files |
| name | value | |
|---|---|---|
| Bushido | 10299 | |
| Beagle | 10275 | |
| Buppy-Sugar | 10266 | |
| Bright-Young-Thing | 10103 | |
| Mrs Cardboard Box | 10048 | |
| Big-Kahuna | 10047 | |
| Bunji | 10042 | |
| Beatle | 10020 | |
| Banks.j | 10018 |
| name | value | |
|---|---|---|
| Locke | 4 | |
| Reyes | 8 | |
| Ford | 8 | |
| Jarrah | 16 | |
| Shepard | 23 | |
| Kwon | 42 |