Home/ Questions/Q 8768767
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T17:09:01+00:00

I am trying to use a p:schedule , but the column headers are showing

  • 0

I am trying to use a p:schedule, but the column headers are showing the format like: EEE MM/dd and I really need to switch to EEE dd/MM.

researching the primefaces forums and google project, i ran into this (and several other threads): http://code.google.com/p/primefaces/issues/detail?id=2546

that seems to address the issue, but I am clueless as to how to use it to solve the issue.

I am unsure as to wheter this question is a duplicate (as the issue has been lingering around for a couple years now) but searching the SO did not come with any hits.

So, how can I change the format of the column headers?

I imported the showcase example into my project, so far the config of my schedule event is:

<p:schedule value="#{scheduleController.eventModel}"
widgetVar="myschedule" view="agendaWeek"     allDaySlot="false"
slotMinutes="15" firstHour="7" showWeekends="FALSE"
leftHeaderTemplate="prev,next" rightHeaderTemplate=""
minTime="7am" maxTime="21pm" timeFormat="dd/MM hh:mm"
axisFormat="HH">

using primefaces 3.3.1

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A very crude solution, I fixed these headers by hijacking the output of the schedule page, changing the javascript code for the schedule call in order to put the format in it:

    I used the classes written by Jeremy Stein (click to go to question) (yeah, regex on HTML output, bash on) and placed a filter listening on the output of the specific page with the schedule.

    I used the following Pattern and Replace String:

    Pattern. compile("timeFormat:(.*?), behaviors");

replaceString= "timeFormat: $1, columnFormat : { month : 'ddd' , week : 'ddd d/M' , day : 'dddd d/M' }, behaviors"

    by inserting the columnFormat property in the output, it started rendering the headers right.

    I would love to see another way to get around Primefaces reluctance in implementing this feature.

    • 0