Changes between Version 49 and Version 50 of WikiTicketCalendarMacro


Ignore:
Timestamp:
Aug 11, 2010, 11:00:03 PM (14 years ago)
Author:
Steffen Hoffmann
Comment:

updated information according to latest feature release

Legend:

Unmodified
Added
Removed
Modified

  • WikiTicketCalendarMacro

    v49 v50  
    6060    [[WikiTicketCalendar([year,month,[showbuttons,[wiki_page_format,
    6161                          [show_ticket_open_dates,[wiki_page_template,
    62                           [query_expression,[list_condense]]]]]]])]]
     62                          [query_expression,[list_condense,[cal_width]]]]]]]])]]
    6363
    6464    Arguments
    … …  
    7373    wiki_page_template = wiki template tried to create new page
    7474    list_condense = ticket count limit to switch off ticket summary display
    75 
     75    cal_width = set calendar table 'min-width', and optionally 'width'
     76                for surrounding div triggered by prepending '+' to value
    7677    Advanced Use
    7778    ------------
    7879    [[WikiTicketCalendar([nav=(0|1)],[wiki=<strftime-expression>],
    7980        [cdate=(0|1)],[base=<wiki_page_template>],[query=<TracQuery-expr],
    80         [short=<integer-value>])]]
     81        [short=<integer-value>],[width=[+]<valid-CSS-size>])]]
    8182
    8283     - equivalent keyword-argument available for all but first two arguments
    … …  
    99100    [[WikiTicketCalendar(wiki=Meeting-%Y-%m-%d,query=type=task&owner=wg1)]]
    100101    [[WikiTicketCalendar(wiki=Meeting_%Y/%m/%d,short=6)]]
     102    [[WikiTicketCalendar(*,*,true,Meeting-%Y%m%d,width=+75%;)]]
    101103}}}
    102104
    … …  
    116118short=0           same as 'list_condense', total ticket count per day, that'll have
    117119                  ticket list display condensed to just ticket no., 0 = never condense list
     120width=100%;       same as 'cal_width', check '+' prefixed values, if you need more forceful width definition
    118121}}}
    119122The ''query'' keyword supports any expression supported by TracQuery. This is the single new ticket selection logic that can use custom field values as well as expressions chained by AND (OR since 0.12 only). An invalid expression was chosen on purpose to select and show all tickets by default. Use your own query expression to create per-developer or per-component ticket calendars, or you could choose to display tickets only with high/highest priority, tickets with some special content in a custom field, etc.
    … …  
    124127ticket.due_field.name = due_close
    125128ticket.due_field.format = %y-%m-%d
    126 ticket.due_field.utcoffset = 0
    127129}}}
    128130Again these are the implicit default values to give backwards compatible behaviour.
    … …  
    133135ticket.due_field.name = due-date
    134136ticket.due_field.format = %m/%d/%Y
    135 ticket.due_field.utcoffset = -5
    136137}}}
    137  * account for US east coast time
    138138 * for a custom due date field named 'due-date' that holds
    139139 * US style date with 4-digit year
    … …  
    143143ticket.due_field.name = due_date
    144144ticket.due_field.format = ts
    145 ticket.due_field.utcoffset = 2
    146145}}}
    147  * support European time zone offset
    148146 * for a custom due date field named 'due_date' that holds
    149147 * true POSIX microsecond timestamps (see: [t:wiki:TracDev/Proposals/TracTicketsCustomTimeFields custom time fields proposal])