On September 7th we will begin our next Daily Study Group series that will focus on “Creating Custom User Interfaces”. Attendees will learn to develop graphical user interfaces using the Wolfram Language through short live lessons hosted by Wolfram-certified instructors, and also work on practice problems and mini projects for a hands-on experience.
A certificate of program completion will be available.
It’s gratifying to see so many people excited to learn about user interface technologies available in the Wolfram Language. Looking forward to the enthusiasm at this upcoming study group!
I am wondering is there a way to vary what type of color setter is presented to the user with the Manipulate function. For example, is it possible to use a LAB Color setter instead of the default color selector in the Manipulate function?
Today’s quiz is a disaster. My answers to questions 2, 5, 9 and 10 are being ignored. I can change my answers to any of these and my score remains unchanged.
Also, according to the Day 1 notebook, Introduction, slide 8, item 2 under Entirely cloud-based interfaces, the answer to question 3 is being graded incorrectly.
Thank you everyone for your enthusiastic participation in this week’s sessions. I hope that you have been enjoying and finding the sessions helpful.
In this week, we covered some fundamental concepts of dynamics and Manipulate.
In the next week, we will discuss more about certain pragmatic concepts related to the development of User Interfaces and look at several User Interface examples.
Our apologies for few things here and there not working properly in the notebooks. We are making the corrections and will make an updated set of notebooks available to you at the end of the series.
I know Jayanta mentioned how to abort the evaluation once it gets in a loop. I tried command + “.” (Mac) but wasn’t having much luck. I’m working on Exercise 3 on Dynamics II and have had to restart MMTA twice now.
[Cmd]+[.] unfortunately can’t always abort a given computation instantly. The abortion request goes to the kernel instantly, but depending on the type of computation the kernel is busy with it may check the queue of requests frequently or infrequently. Besides, the abortion itself may take some time.
That said I did not encounter any such problems with Exercise 3. If we are using preemptive evaluation, we should get an $Aborted in 6 secs. With queued evaluation I get back the image in about 10 seconds (this time will depend on your internet connection).