Ticket #22 (closed enhancement: fixed)

Opened 7 years ago

Last modified 6 years ago

parametrized dashboards

Reported by: dozzie Owned by: dozzie
Priority: normal Milestone: release 1.0
Component: - Keywords:
Cc: Parent ID:

Description (last modified by dozzie) (diff)

In the long run, for DashWiki to react on fully dynamic data (without pre-defining dashboards for each and every server), some kind of page parametrization will be necessary.

For example, there is a dashboard Servers, which has a parameter %ServerName. This way there's just one place where dashboards for onyx.atled.pl, basalt.atled.pl and jarowit.net are defined, without need for creating pages for each server separately.

Child Tickets

Change History

comment:1 Changed 7 years ago by dozzie

  • Milestone set to pomysły

comment:2 Changed 6 years ago by dozzie

  • Milestone changed from ideas to release 1.0

comment:3 Changed 6 years ago by dozzie

  • Component set to -

comment:4 Changed 6 years ago by dozzie

  • Type changed from idea to enhancement

comment:5 Changed 6 years ago by dozzie

  • Description modified (diff)

comment:6 Changed 6 years ago by dozzie

  • Owner set to dozzie
  • Status changed from new to accepted

I've included a hack that defines artificial macro @__param__() for this.

But since it's a hack, it's not a pretty way of working with parameters. To be replaced with real code infrastructure for such things.

comment:7 Changed 6 years ago by dozzie

comment:8 Changed 6 years ago by dozzie

  • Status changed from accepted to suspended
  • Summary changed from parametryzowane dashboardy to parametrized dashboards

comment:9 Changed 6 years ago by dozzie

  • Status changed from suspended to closed
  • Resolution set to fixed

I replaced the hack with something dedicated. Now page parameter may be accessed with pre-defined macro value $page_param.

Note: See TracTickets for help on using tickets.