I have downloaded darnifiedUI from here : and it all works fine except for one thing . I can not move anything from Adjustable hud nor can I disable the hud from Immersive Hud ( actually I can disable the hidden/detected thing on the top but nothing else) . The stuff from the Extra Hud mod are both togglable and in DarnUI style . You can see my modlist below but I am putting a spoiler in the end just in case too. Thanks in advance :).
project nevada darnified ui
DOWNLOAD: https://ssurll.com/2vGTmX
There seemed to be two major groups. The Canvas Developer type hacker who wants to spend time talking to people about how to do technical things like make API calls or figure out this one thing, whatever it is, that is the stumbling block keeping them from moving forward with their latest, greatest project. There are people who go to hack night who are not active in the Community and so you don't get to pick their brains, but a few minutes at hack night can reestablish momentum. JavaScript is one language, but there are others. People use PHP, Perl, Python, .Net, Ruby, etc. Most of the problems I saw people having were not language specific, but API questions. Maybe I was at the wrong tables, but there's lots of documentation online about how to get X programming language to do Y. There's less about how to get Canvas to do Z. Of all the things that have been mentioned, API and JavaScript would probably be the two biggest things. You'll probably have people wanting to talk about LTI and Canvas Data.
Some of the difficulties of developing these solutions on top of Canvas and it's awesome open architecture is that we are subject to the very volatile release cycle. For instance, we had just deployed some charts (via LTI) that showed grade distributions across various points in the Fall, and shortly after Canvas released deprecation warnings on two tables we used, and would soon replace them with several more, which I'm totally a fan of. More organized data anytime! However, this increases technical debt, because now we have to go back. I would like to know if anyone else has these pain points, and would they like to collaborate on ways to prevent duplication of effort and keep us developing new tools more often than redesigning them. Maybe this group is already out there, I'd like to sign up. I'm also happy to help contribute to any other projects out there.
Someone already provided the answer to my request but it involves code and I don't know jack about code and our programmer (we have one at our school) is working on too many other institutional projects for this to make his to-do list. Our previous LMS (Pearson) did this quite nicely.
2ff7e9595c
Comments