Graham Quince

So, we're internal testing today. I've just got the new app installed on my phone:

The student photo was indeed in the app and may return, but it was pointed out that we don't have photos in the platform that prompted both the service desk tool and the redesign. The prototypes change on a regular basis. I update the links on the community site when they do. This is down to how Adobe's prototyping system works - sorry

Student photos will be uploadable via the Service Desk from Da Vinci. FrogSeats is installed for you now. Don't get shouty if it doesn't work with your Frog3/FrogLearn setup

You were there at the conference! "Paul is happy to share FrogSeats with the wider Frog community, but as a deputy head, he is concerned about finding time to support his code. Paul's code relies heavily on Frog's internal APIs which are subject to change by our developers. When we update FrogLearn's code, the seating app may stop working. I do not think any changes we are making in the Da Vinci release (October) will have an impact, but cannot guarantee that is the case. If you're still happy to proceed, I can install FrogSeats for you and talk you through how to get started."

?

I've never published that widget, so @johnmorris01 won't be able to try it. I can reassure you that in the October Da Vinci release, a true Office365 embed widget is coming out, together with FrogDrive integration and SSO. John - I'll jump onto your platform and add the code and drop you a line. Then you can decide if you wish to deploy it from Package Manager.

Thought I'd offer a preview of a new FrogCode widget I've been working on with Caroline Worboys-Mcardle of Hendon School. We worked on this widget together at the FrogCode workshop at the Judd School. In a nutshell, the widget offers simple re-styling of a Frog form: https://drive.google.com/file/d/0B5bTXEl9mgAhQ3JTb3ZBRk0xaVE/view I'll get this released as soon as I can.

Hey @ADT, How was your school trip? Is there any screenshots of the site you can share?

D'oh! It's been one of those months So - firebase only offers 100 live connections, but could you code in connection / disconnections into the saving or alternatively, could you store in the save details in browser and run a save every minutes instead?

Hi Paul, What about connecting to Firebase and storing the information that way? It would solve the problem for you and then we could figure out a way of solving the problem for others later. Graham

I started (but didn't get round to finishing) a widget that could be placed on a common dashboard. My idea was it would run each time the user logged in, but changes could be set in the widget. Ideally it would only run once per user. The internal API for notification preferences is really simple. ?method=notifications.setChannels There's also an idea on the Ideas Portal to cover this https://ideas.frogcommunity.com/ideas/FRG-I-883

- amazing

Hi Matt, That's not something we've considered. The eportfolios might well be multiple pages, so that would be a limited case. We are looking at a widget that would list all the eportfolios you have access to, so at least you wouldn't have to make the links.

Hi @THaines Are you in this week? Let's get someone to call you and see if we can help.

Yes, exactly. This is one of the cleverest features of the site list widget

Hi Paul, I've just learnt that @Chris.Smith is poorly at the moment. It might be next week before he can reply. And I'm fairly certain I don't have an answer myself. sorry

Hi Paul, I've just learnt that @Chris.Smith is poorly at the moment. It might be next week before he can reply. And I'm fairly certain I don't have an answer myself. sorry

Hi @THaines, The SIMS Linked documents can be configured to do this. The service desk can talk you through how to set it up. Graham

Hi @Sue Busher, Paul is happy to share FrogSeats with the wider Frog community, but as a deputy head, he is concerned about finding time to support his code. Paul's code relies heavily on Frog's internal APIs which are subject to change by our developers. When we update FrogLearn's code, the seating app may stop working. I do not think any changes we are making in the Da Vinci release (October) will have an impact, but cannot guarantee that is the case. If you're still happy to proceed, I can install FrogSeats for you and talk you through how to get started.

Hi Tom, In the next release (mid-late October), we are launching ePortfolio Maker, which will create a site per user in a group. Can you hang on for this?

Hi, It's identifying the UUIDs that's the tricky bit and the reason I've not turned this into a tutorial. The 'easiest' method is to run the site in Safe Mode. Right-click on each nested page and choose Inspect Element. This should highlight the correct UUID in the developer console. Ignore the function in a loop thing. That's Frog's HTML widget being picky about best practice. That's not causing a problem with the malformed javascript. If you email me the details of where the site is, I'll jump on and see if i can fix it.

Hi Chris, I think the text widget can get you the buttons and squares quite easily. The gallery is the image carousel and the HTML widget can sort out the twitter and maps bit. Other than a custom theme or re-styling an existing one using the HTML widget and CSS, I'm not seeing anything too challenging. We'll drop you a line and talk you through it.

Hi @THaines, Why create groups for individuals? If you need specific pages hidden except for a couple of individuals, why not create a group for a page, then as the individual is granted access, you just add them to that page's group. For instance, if you have a SENCO page, create a group called SENCO, set the rule to only show to page to that group, then anyone who requires access just gets added to that group. That's not to say expanding Rules to allow for individuals is not a good idea, but in the meantime, i think my method would be quicker for you. Graham

Here's a cute bit of CSS I was asked for to hide the Saturday and Sunday columns in the new look Calendar widget. It's not really worth a whole tutorial, but it uses nth-child as the individual table cells don't have class names <style> div[data-content-uuid="uuid of the widget"] .frogui_components_calendarweekview th:nth-child(7), div[data-content-uuid="uuid of the widget"] .frogui_components_calendarweekview th:nth-child(8), div[data-content-uuid="uuid of the widget"] .frogui_components_calendarweekview td:nth-child(7), div[data-content-uuid="uuid of the widget"] .frogui_components_calendarweekview td:nth-child(8) { display:none; } </style>

Hi @clangstaff You've probably seen Steve's reply on the ideas portal, but for everyone else: And just for clarity, IAL11 is the internal name and numbering system we use for FrogPlay development. The question engine's code is built on I Am Learning's code. V11 is the next release of their code. Not sure if that will mean you have to wait for Da Vinci (October) or not. And for everyone else. Please continue to vote on Chris' idea. Steve has said we're doing it, but that doesn't mean more votes won't be noted. Also, please keep voting on the ideas portal. Almost all of Dickens and Austen was the result of the ideas portal.