Graham Quince

https://www.youtube.com/user/frogtrade/videos

Less used - if you prefer

What about if you haven't moved through site pages, you've only opened a site? Do you care if the back button only works for site pages?

A widget preference to select another widget would be really useful. If you post it on the ideas portal, I'll get interest going in the office. @Chris.Smith - Is a widget preference like this is possible?

As far as I'm aware, this is the first step in adding better browser integration. Frog is a Single-page-application type of site, with the ability to open multiple sites and apps. Quite how we / you / would want the back button to behave is still being worked out. For instance, should the back button return you to the previous page or previous site? Do we need to record your movements across the platform and build these into a history, even though this could slow down load times? Genuine questions, how would you want the back button to behave?

Kris on the design team has said that during quiet periods, especially in the summer, they'll will work through the less popular themes and update them

In Austen, we added a new feature to pop up a warning message if you click the back button, home button, shortcuts, bookmarks, then you'll get a pop-up asking if you're sure. Hopefully this will save you countless minor irritations. However, this feature has to be enabled via the service desk. Our developers were worried about annoying you with the pop up. If you'd like this activated (and trust me, i think you would) then contact the service desk team and they will happily set it for you. Service desk: 01422 395939 https://www.frogcommunity.com/austen/learn

shhhh! eep-kay iet-quay about-way e-thay image-way arousel-cay There is a phase 2 planned for the image carousel

Thanks to the massive generosity of Simon Clough and Simon Foster at the Radclyffe school, their galelry widget which uses a shared folder is now available to download from the Community site: https://www.frogcommunity.com/frogcode

Hi Funnily enough i put some code together a little while ago just for this, then started building it into a widget. This code in an HTML widget should get you started though: <style style="text/css"> .scroll-body { height: 36px; overflow: hidden; position: relative; background:#a52a2a; border-top: 5px solid #ffac00; } .heading-text { margin:0px 10px 5px 10px; width:150px; font-family: OpenSans-Regular, Helvetica, Arial, "Gill Sans", "Gill Sans MT", sans-serif, "DejaVu Sans Condensed", "Myriad Pro"; font-weight:normal; font-size:18px; line-height:36px; text-align:left; color:#ffac00; float:left; } .scrollCont { width:calc(100% - 150px); height: 36px; overflow:hidden; float:left; position: absolute; left:150px; } .scroll-text { border:0px solid #000000; position: absolute; padding: 0px 0px 0px 150px; width:100%; height: 100%; margin:0px 5px 5px 150px; font-family: OpenSans-Regular, Helvetica, Arial, "Gill Sans", "Gill Sans MT", sans-serif, "DejaVu Sans Condensed", "Myriad Pro"; line-height: 36px; font-size: 18px; color:#ffffff; text-align: center; /* Starting position */ -moz-transform:translateX(100%); -webkit-transform:translateX(100%); transform:translateX(100%); /* Apply animation to this element */ -moz-animation: scroll-left 22s linear infinite; -webkit-animation: scroll-left 22s linear infinite; animation: scroll-left 22s linear infinite; } /* Move it (define the animation) */ @-moz-keyframes scroll-left { 0% { -moz-transform: translateX(100%); } 100% { -moz-transform: translateX(-100%); } } @-webkit-keyframes scroll-left { 0% { -webkit-transform: translateX(100%); } 100% { -webkit-transform: translateX(-100%); } } @keyframes scroll-left { 0% { -moz-transform: translateX(100%); /* Browser bug fix */ -webkit-transform: translateX(100%); /* Browser bug fix */ transform: translateX(100%); } 100% { -moz-transform: translateX(-100%); /* Browser bug fix */ -webkit-transform: translateX(-100%); /* Browser bug fix */ transform: translateX(-100%); } } @media only screen and (max-width: 800px) { .scroll-body { border-left: 5px solid #ffac00; border-top: 0px } } </style> <div class="scroll-body"> <div class="heading-text">Announcements:</div> <div class="scrollCont"> <div class="scroll-text">CSS scrolling text... &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -Some More text, where will it go - nobody knows!!! -</div> </div> </div> I'll get the widget finished one day

which one is the IT one?

We posted at the same time. Unfortunately, you can only assign quizzes from Progression Charts to get the evidence back automatically. Assigning a site isn't linked to the chart in the same way

Sounds like a great idea and if someone wants to beat us to it, then I'll be very happy. Alternatively, the Ideas Portal could capture your idea and get others to vote for it. https://www.frogcommunity.com/ideas-portal

I've put in a request for a theme for this, but the guys are quite busy at the moment, so it might take a couple of weeks. In the meantime, Basic Theme - Navigation Only is a pretty empty theme. The primary class is .ui-theme-basicnavigation So, if you download the example theme and run a find-and-replace on the theme class, then paste the CSS elements into an HTML widget on a site with this theme, you should be able to see changes live. This theme isn't ideal as it doesn't have the title and description, but this is just for proof of concept.

Just been talking to the design guys here. I'm wondering if a better option for creating themes would be to use a blank theme on a site with the HTML widget. We could provide the boilerplate code and you'd be able to edit the CSS to get the theme looking the way you want it, then using something like Notepad++, you could do a find-and-replace on the class name and zip the theme up with any images and contact the service desk. In theory, this would give you a better editing experience. I'll try it out when i'm free and let you know.

I see what you mean. However the theme itself is mobile responsive when it's uploaded to FrogLearn. I think what we're seeing here is a clash between the old theme builder and more up-to-date scripts for mobile responsiveness. I'm starting to think what we need is a method for running a theme .ejs script inside Frog. @Chris.Smith - if i upload the contents of a theme to a FrogCode app, would I be able to preview it? i feel like it would still be missing elements.

Hi Simon The Themes tutorial was updated with a responsive theme: https://frog.frogcommunity.com/themebuilding Graham

Hi @Corinne I'm on a train at the moment, but I think the div for a site's title is tagged site-title and for the description, it's site-desc if you use visibility:hidden is CSS rather than display:none, then the site won't get renamed and should do what you want it to. Graham

Nope, it shows all the work assigned to that student, whether individually or in a class. It's a really useful tool for pastoral staff

Hi @clangstaff, You can export all data from Assignment Monitor as a CSV. Gareth Gay at Glenthorne does this as did Graham Thorpe when designed the Interactive homework prototype before it was built into Austen. ( https://frog.frogcommunity.com/assignments-prototype ) I know others can search for individual students, so I'm glad you reported this issue. Hopefully we can get this corrected ASAP.

Have you seen this site: https://www.frogcommunity.com/learning-frog

#Gobsmacked.

The original Dashboards sites are a bit of a weird legacy and have several quirks. If Paul did change the permissions for students to view and has a forum, file drop, poll or wall on the dashboard then I believe the students would not be able to interact with these widgets. The original noticeboards require Edit and Manage rights to be able to post a notice, which isn't ideal.# In the API, sites.getInfo A dashboard is listed under "type" as "dashboard", whereas a site is listed as "site"

Ah, I see a potential problem here. If a school has a forum on the dashboard site, then students will need contribute access in order to post. With your notice board only requiring Contribute and not edit and manage, there is a little bit of a conflict. Personally, i think we need an additional layer of permissions between contribute and edit & manage and there have been some discussions internally about this. Could I make a suggestion? How about a preference in the widget to turn off the create notice button for contribute level access or just for students (and one for parents)

Hi @clangstaff, Well, that's frustrating. I've been playing around with: <style> .form-header p:before { content:"Lorem Ipsum \A new line"; white-space:pre; } </style> Unfortunately, that's adding the content twice, once to the description and once to the hint text.