Overview
The Groundswell Calendar Display, powered by ToastUI, gives designers the ability to quickly have a modern calendar display in their sites and dashboards with the simplicity of a single component. The dense, versatile display supports different calendar views with styling matching your site’s accent color. Example interfaces and utility rules are attached, which demonstrate usage and features of the component.
Key Features & Functionality
sergiob0004 I prefer adding full localization support vs adding parameters. I don't speak those languages, so if your team has the capability to provide translations, I'd be happy to include them in the product roadmap.
Here is the en-US template:
'en-US' : { month0: 'January',month1: 'February', month2: 'March',month3: 'April', month4: 'May',month5: 'June', month6: 'July', month7: 'August', month8: 'September', month9: 'October', month10: 'November', month11: 'December', day0: 'Sun', day1: 'Mon', day2: 'Tues', day3: 'Wed', day4: 'Thurs', day5: 'Fri', day6: 'Sat', allDay:'All Day', milestone:'Milestone', task:'Task', detailAttendees: 'Attendees: ', detailLocation: 'Location: ', detailRecurrence: 'Recurrence: ', validationView:'Invalid View Selected. Valid views are "DAY","WEEK","MONTH"', validationWeekend:'Invalid Weekend View Selected. Valid views are "FULL","NARROW","NONE"', validationVisibleWeeks:'Visible weeks must be greater than 0'}
Hi, will it be considered the suggestion I made of adding two more parameters to provide custom translations for months and days? If not, could be added the translation for Polish and Portuguese in a future update? Thanks!
As Arabic is currently an unsupported language, and it is a large effort to ensure effective RTL support, the immediate update I can provide is ensuring it loads properly with a default locale of en-US. The result will look like the following:
This will be submitted to Appian in the coming days.
The same issue appears (NAN) for Arabic Interfaces,
Can you please fix it?
@carlosobiols new version is published that should correct this
Thanks for catching this. Will get this corrected and submitted this week
Known issue, but no impact to performance to our knowledge given our testing
Hello,
I have a problem in the Spanish version.
Thank you,
Justin Watts
Hi, the component displays OK in our environment, but if we check the chrome developer console we can that the following error is thrown several times. How can we solved it? Could it impact the performance? It happens in versions 21.4 and 22.4