Currently, in SAP UI5 Fiori Planning Calendar there is no option to scroll the days. It only allows switching days by Clicking or tapping the arrows to navigate to the next or previous interval.
Is there any way to add a scrollbar to switch between days.
I've searched but couldn't find a solution.
Unfortunately, this is not possible.
The Planning Calendar header is fixed and does not allow such customizations.
Also, the content grid below does not support such scrolling.
You might want to use different views, e.g. change the default view to “1 Month”, in order to move quickly forward.
As time is unlimited, you would also need an “indefinite” scrollbar.
Related
I've seen that in earlier versions of AEM, when we schedule a page to get activated at a later time, a small calendar icon is showing up under the status column. When we hover over this icon, it displays the scheduled date and time.
But, I can't see that scheduled activation calendar icon anymore. I can only see the workflow icon under the status column.
Is there a way how I can display the scheduled activation status icon in AEM 6.5?
Many thanks in advance for all your help.
This should still be visible by default in AEM 6.5 so you may not need any custom implementation. If it isn't working, maybe there's a bug or there's an existing customization that's preventing those icons from working.
In the list view
In the column that displays the publication status, there's a faint calendar icon. It's quite low-contrast though. Hovering over it will reveal the scheduled publication date.
In the card view
You should be able to see the time of scheduled activation in the page preview on the right hand side.
How you could change or add icons
If you still want to add an icon, you should be able to achieve this via overlaying parts of the sites console. You'd have to find the right scripts under /libs and create an overlay under /apps
This is also where you'd look if any icons available OOTB are missing.
More on the subject:
Using the Sling Resource Merger
Customizing the consoles
I am trying to figure out how to design a calender scheduler in adobe flex.
I have seen the flexlibswc, but it is not structured properly to use.
My idea is to get time in vertical as list and scheduler at right all in one panel.
Can anybody suggest what components I need use to design this custom component.
Please see the protoype screen below
I'll use core graphic components/spark to design this screen. The whole calender background will be a relative layout component like a group/canvas surrounded by the scroller. Each of the slot(blue color) will be extending a spark/uicomponent fills color with Graphics(circle rectangle etc,) so they'll be light weight. I've tried these, they work, but, it is a hectic process to get all things right, it may take 2 months - 3 months to get things done. If you find a open source project try digging the code.
I'm using a website that runs on Plone. On the homepage, the carousel has several images that you have to click the next number to see the next image. What I want though, is to get these images to rotate automatically after a certain number of seconds. How do I do this? Thanks.
It would be very helpful if you could mention current setting for the portlet you're using.
However most probably it is because you forgot to set a reasonable value for Timer field. Check the settings for the carousel portlet and set the Timer to for example 5 and see what happens.
Pattern for pagination is currently on a after 1.0 roadmap for Meteor. Are there any examples or suggestions how to do it now? So how to nicely do an infinite scroll by subscribing to new and new elements as user is scrolling to the bottom?
I recommend that you try my package, Pages: https://github.com/alethes/meteor-pages
It's extremely easy to use (you can set it up with just one line of JavaScript), yet very customizable. It features: incremental subscriptions, local cache, neighbor prefetching, request throttling, easy integration, multiple paginations per page, bootstrap 2/3 styling, failure resistance, built-in iron-router support and a lot of settings that can be modified on the fly, without reloading the page.
There is a package on atmosphere.meteor.com for pagination that should get you started
https://github.com/egtann/meteor-pagination (Pagination)
https://github.com/tmeasday/meteor-paginated-subscription (Pagination with publish)
The second one actually sends down one page of data at a go instead of all the data at once so if you have loads of data it might help with that. With the infinite scroll you would have to attach a manual scroll listener and put in the new data by increasing the size of a page as you scroll down (not specifically moving to page 2).
I'm a bit unsure on what pattern to use specifically because using page size might be a bit troublesome unless you're able to get it to work right with reactivity which should be possible if you're able to seperate your {{#each}} block helpers so that its for each scroll down, perhaps using Meteor.render so that the entire set of data already available isn't re-rendered.
It might also work if you put the data in div block containing a scroll overflow instead of the above so that it does re-render but their position in the scroll remains the same, in effect making the re-render unnoticable.
I'm having problems making FullCalendar fully accessible. I'm using the default month view and can't access the next, previous, and today buttons on the top right without using a mouse. If I run a screen reader, I can access those buttons but not without running the screen reader.
And on another note, I currently am using tool tips that pop up when you mouse over an event title to display more information. If anyone has any tips on how to make those accessible to a screen reader or accessible without a mouse, I'd greatly appreciate it!
Regarding the buttons, I would advice that you write new buttons if accessibility is important. These buttons you could then hook up to your own javascript functions that moves to previous and next.
Check out this documentation example
Regarding the second problem, I think that's the same problem not just for physically impaired but also for things like mobile browsers. My tip would be to avoid onmouseover if the information that appears is really important.