-
Why in Turkey we see the Letter Waw 9 Everywhere? | Rumi Museum, Bursa Grand Mosque, Topkapi, ...
Shafa’at (intercession) ya Rasulul Kareem (The Most Generous Messenger).
00:13 - “Bismillahir Rahmanir Raheem. Wa Atiullah wa atiur Rasul wa Ulil amre minkum. ” And reminder for myself ana abdukal ‘ajeezu, dayeefu, miskinu, zhalim, wa jahl, and but for the grace of Allah (AJ) that we are still in existence.
00:26 - In this holy month, like a formula we put the ‘92’ then equals ‘Muhammadan reality’.
-
OA21: Breakout (3) Building a modern discussion tool backed by scholarship and usability research
free to send me a a direct chat and i’m glad to help out in any way that i can so with that it is it is 12 12 and let’s get started uh hannah’s saying that when she leaves and tries to join it just gives her the headphones listening option well maybe we can change it once we get her in there and josh no we can’t hear you oh yeah that’s me she might need to try with a different browser hannah maybe maybe you and i can work on this offline while the presentation gets started okay with that note i am going to bring in the presentation does everyone see a um slide almost no loading for me at least there we go okay great well hello and welcome to our presentation i’m heather valle and i’m here with heather hans and hannah rogers we hope we’re from duke university’s learning innovation team and we’re going to discuss the development of a new asynchronous communications tool as the use of online education tools increased to meet the needs of learners during the recent pandemic some new pain points became apparent to address an unexpected hole in our teaching and technology portfolio duke university decided to create a new online discussion platform to facilitate compelling 21st century learning conversations by leveraging its commitment to learning innovation dedication to open source open source software deep engagement with the duke community expertise in user informed design and strong partnership with the with longsight a trusted education technology vendor duke has reached an advanced prototype stage of development on this tool with the goal of piloting it for this coming fall semester here is our full team from duke learning innovation duke creative and user experience and longsight but as you’ll see the range of people providing input is much broader the recent transition to online education has demonstrated how valuable online conversation is to our learning experiences unfortunately our faculty are not enamored with sakai’s forums tool so projects like piazza have become increasingly important even before the pandemic their use increased dramatically during last year’s higher education pivot to online education when piazza changed its business model in 2020 we at duke took the opportunity to evaluate some competitive projects like ed discussions and campus wire at the same time we began the development of an entirely new discussion tool within sakai our goal is to replace the current discussion forums with a tool designed to better meet our community’s needs and facilitate meaningful compelling learning conversations in order to transform our current discussion tool we brought together a wide variety of stakeholders students instructors teaching assistants lms administrators user experience designers and vendors we delved deeply into pedagogical research and leveraged modern web development technologies and we asked our primary users instructors and students to provide input and feedback at every stage of the process this holistic approach to course discussions aims to make them strongly aligned with both user needs and pedagogical best practices and see yes now hannah will dig a bit deeper into the research side of things thanks heather i’m hannah rogers so on the slide that you’ll see in just a second you can see some but not all of the research categories we explored relating to online discussion so by exploring topics as diverse as gamification and social media we sought to gain a holistic understanding of effective online discussions we centered pedagogical research from the beginning of this process initially collecting reviewing and summarizing about 70 articles from there we crafted 42 online discussion design recommendations directly tied these findings about directly type defines about 50 articles at the heart of every recommendation is the understanding that user experience plays a key part in not just using a tool but in learning itself we are in the process of connecting these research recommendations with other forms of data to see where the needs of instructors graduate students and undergraduate students align with the findings from teaching and learning scholarship we are currently working with a group of six instructors from across schools and disciplines at duke who are providing sustained consultation on the process as we began the process of designing the new discussion tool we collected user stories from faculty once we had our recommendations from pedagogical research we presented these recommendations to duke instructors to see what overlapped with their needs and what questions we had not yet asked additionally we have provided faculty with our findings from the undergraduate focus groups that heather will talk more about in a moment and ask for their reflections the faculty themselves pushed for us to consider how to build values directly into the tool spurring our team to integrate these questions into our design and research methodologies we are coding each user story based on the values underlying each action and pictured on this slide you can get a peek of our workflow in air table after we code these user stories we will be running a values exercise with faculty and now i’ll turn it over to heather who’ll speak more about our user research process thanks hannah to complement the work we are doing with our faculty group we conducted several focus groups with undergrad and graduate students in addition to conducting user testing of prototypes with students and faculty after completing initial interviews with two student interns to gain some valuable background information we recruited undergrad students for three one hour focus groups and the students were compensated for their time we kept these groups relatively small at three to seven participants and we intentionally recruited students from a variety of disciplines in total we spoke to 18 undergrads from duke and duke kunshan university about their experiences with sakai forums piazza and online discussion in general the focus groups were held via zoom and included several formats we broke up the group into smaller groups based on their experience with sakai forums and or piazza and asked them questions about their use of those respective tools then we encouraged them to use jamboard to identify what they liked and disliked about each tool here you can see one group’s feedback on sakai forums in jamboard we also had larger group discussions about the tools the online discussion experience in general and related topics including privacy and gamification uh the focus group methodology was designed by bendy fagg a lead information architect ux designer here at duke who is part of our project team we are currently recruiting for two rounds of focus groups with graduate students ideally from a variety of disciplines again we will use the same methods as the undergrad focus groups but some of the questions will be different to account for graduate students experiences as tas and instructors of record again the grad students will be compensated for their time all of the information from our focus group research is being collected grouped by theme and synthesized in reports that we then compared to the other data collected for the project we will share some of the most common themes across our research a bit later in the presentation on another note another major component of user research in this project was of course usability testing of two prototypes by faculty students and community members during the design phase since we already had a weekly meeting with our faculty group we sent them into individual breakout rooms to test the first prototype of the tool then brought them back into the main room to share their feedback with us also we are doing usability testing with undergrad and grad students currently in 20 to 30 minute one-on-one slots in which we ask them to complete a series of tasks and then ask some follow-up questions about the experience in addition we will be doing usability testing with community members very soon uh more information on that at the end if you’re interested and we plan to test uh one more prototype with these user groups but hopefully with different participants later in the summer now i’ll turn it back to hannah to talk a bit about some of our findings from all this research so in designing this tool we ask ourselves where does the pedagogical research student and instructor needs overlap so i’ll just take you through three quick examples the need for asking questions and holding more extensive discussions was represented by both instructor user stories and student focus groups students in particular spoke about how current tools like sakai and piazza work at cross purposes so on this slide you can see a current version of sakai forums where there is not a specific question and answer option and if you look at the next slide you will see pictured a sample screenshot of what we’re currently calling forums next the tool when users create a new topic they can choose between asking a question and engaging in q a and starting a discussion another big uh thing that was important to both students and instructors was keeping posts organized through tagging on this slide you can see some example tags from ed discussion and piazza sakai forums does not currently support tagging posts so on the next slide you can see a screenshot of our initial tagging layout in the forms next tool instructors can also edit tags for the course to make sure the organizational flow fits the needs of the course and in order to build on improving organization for the forum’s next project we sought to improve upon the long list of forums and topics that sakai forums currently displays as you can see in this screenshot sakai forum’s vertical list of texts can make it difficult to easily find topics important to the user so in our final screenshot of the forms next you can see a new left-hand organizational column that displays alongside the topic you are currently viewing instructors can pin important topics to the top of this column so that members of the course can easily find them individual users can also add topics to something we’re currently calling my list so that they can follow along with discussions important to them and while we have a solid research basis for these changes we still have some open questions about how we might design this tool as we continue further along this plot process so what questions remain based on our research firstly we value student privacy and instructors have emphasized this as have students but what should we show instructors to help them measure their pedagogy another topic in the consideration is gamification gamification can increase student motivation if integrated properly into a course but how should we approach this especially with sakai’s overall goals and now i’ll turn it back over to heather who will talk us through some final next steps thanks hannah so our next steps in addition to the graduate student focus groups and the values exercise with faculty are uh pulling in experts from duke to evaluate the accessibility of the tool as well as maybe help us test that a bit in the usability testing uh prototyping the next iteration of the interface uh we’ll leave that to adrian and jen and others we are planning to do two prototypes in total and do additional usability testing on the second prototype and our plan is to launch the tool in very early fall so in august so with all that being said uh thank you all for joining us we hope this presentation gave you an overview of the holistic work we are doing to develop a new discussion tool for sakai which as you can see is currently in progress now we’d be happy to answer any questions you have about this presentation josh are there any questions that we missed as we were talking i was i was muted twice no there there were no questions in the chat so this this is really good a couple of people are typing in the shared notes so this is uh there’s a whole lot of activity there one person notes that uh the comments tool is a great way of finding balance between anonymous posting and analytics for the faculty members and uh wonders is such a principle possible in forums next i wonder could that person say more about what they mean about the comments tool or how they would suggest using it if you can identify yourself in the public chat i’ll be glad to uh unlock you so that you can unmute yourself and explain or not if you decided to you know um while we wait for that let’s uh oh actually heather go ahead and we can move to the next question while the first question mutes well i’m not sure i’m the person to talk about sk how this is going to scale but and as far as question about the tool being made open source i believe our current plan is to contribute it back to the sakai community so tonko was the first questioner tonko from the uh the hotel school in in the hague um tonka you’re unlocked you can turn on your microphone and uh um and explain further if you want to do that tonko looks like he’s on with headphones only so while he uh works out that audio issue uh matt writes the interface looks great any thoughts on performance and reaching new scales i.
-
OA21: Breakout (2) Building Open Source Identity Infrastructures
good morning everybody welcome to the building open source identity infrastructure session uh presenters are francesco and misagh please leave yourself muted and cameras turned off during the presentation if you’d like to ask a question wait until the q a portion after the presentation or use the shared notes to the left above the user list to ask the presenter questions please use the chat box only for chat not for presenter questions if you have any tech issues please send me kenny aragon direct message and we will assist you in any way we can with that i’ll hand it off to you francesco thank you very much kenny uh hello everyone uh welcome to this talk um it will be myself and my colleague misagh we will be talking about our experience in building uh open source identity infrastructure so just a few words about myself i am managing director at Tirasa tirasa is a company that is building services around open source identity and access management tools but i’m also a member at the apache software foundation and vice president apache syncope with me i have my colleague misagh yes hi good morning good afternoon good day to everybody here thank you for attending the presentation as francesco mentioned my name is misagh moayyed i work as a software architect at tirasa and likewise i am also a member of the apache software foundation and work with francesco and other folks on the apache syncope project and in parallel if there’s any time left i also sort of chair the apereo cas project and i’ve been with the project for over 10 years or so so thank you i’ll hand it back to francesco to get started with the presentation thank you misagh so let’s first start with with establishing some common ground and vocabulary to name the same things the same way so first of all when we say identity what are we talking about um it’s something that it’s all uh in everything in every system we interact with so we have accounts we have identity and the the most important thing is to uh understand the difference between them and to say uh with more confidence that account is what our computers are about so they are representing of information that are stored somewhere and each account rip is representing only a portion or a view of the overall identity an identity is uh conversely you can see it as the the composition of the partial views that are constituted by account so it seems to be crucial to establish a relationship uh that is correct and as much complete as possible between accounts and identity so how we deal with identity issues essentially we recognize two approaches one is identity management or uh that is the the the everything that you can do to keep identity data consistent and synchronized across repositories so uh essentially is the art of keeping all accounts that are sparse in different resources different formats different network protocols so to keep all this information collected together and consistent over time access management instead is everything that is attaining to user authentication and authorization so who you are and what you are entitled to do on my system identity management and access management are complementary when you use one you can use the other often they work very well together and out of our discussion here would be we show uh some use cases and the way how we keep them together so overall a high level the problem you are trying to solve is starting from a situation like this where you have uh from the top part of the screen several different actors of your systems and and on the bottom part of the screen all all of your systems naturally uh this is when we say um your systems they could be on-premise or on cloud there is no difference anyway no so uh we over time some relationships um are established between actors and systems that are often uh going out of control to the the teams that are supposed to uh make some order out of it so uh with enough complexity enough time and enough requirements you reach up to a situation like the following we represent in a picture the idea of establishing a centralized identity and access management system is to move to a situation like this where you have a point where you can take control of what’s happening where is happening and you from which you can query uh reporting auditing uh you can centralize the checks you can define policies you can establish approvals and essentially in one word you can take things all under control both from a technical and a business point of view one important thing is if you note the top right box is named former employees uh this is typically one of the the biggest troubles when you are not enforcing an iam system that is you are still allowing for former employees for some time to interact with your system so securities of course just this just while i security is of course one of the important items we are discussing here so um we we have a number of uh in the identity and access management tooling landscape we have essentially we recognize essentially three types of technologies the first being the identity stores so an identity store is a place where the account information is stored so you can have traditional or legacy identity stores like active directory ldap or relational databases or you can have nowadays identity stores in the cloud you have azure you have google suite you have any uh cloud you can mention but the principle is the same so we are talking of places that have the storage plus some apis on top to interact uh so to place the objects move the objects uh around uh the store uh what’s the point the identity store historically the first identity technology that came out or when you with identity source each application is uh can be managing its own applica authentication or provisioning separately because a store is a store so a place where to uh store information um from an authentication point of view users for example may or may not use the same password for all the applications but why this is this technology is not enough it’s not enough for several reasons essentially because you and end up by dealing with different technologies and technologies that could be very different like an old uh relational database and a cloud provider but uh you don’t also you don’t have any hierarchy in the the information so you don’t have a clear way to establish um the which system you can trust more uh often then you as a by experience you don’t have it’s very difficult also to enforce policies on uh identity stores when you have more than one of course you don’t have workflow uh available or then there are other additional issues like the fact of not being able to uh consistently foresee the infrastructure uh management cost because uh as as much as the organization is growing uh you will find even more difficult to correlate the various identity stores to each other and finally this is by experience uh very often you have applications that despite of having already available several identity stores in your infrastructure some applications might still require a local database for some purpose to store some dedicated profile information to uh to to work the way that they were meant to et cetera so for various reasons second the second technology we are introducing here are provisioning engines so the idea for the the job of a provisioning engine is to keep things synchronized as much as possible uh by uh defining a high-level concept that we call the identity life cycle management so the identity itself becomes becomes something you can track and you can uh for which you define a lifetime with a start and an end um of course provisioning engines need to need to follow to accompany the the the the real identity uh they are mapped from so uh everything starts with provisioning uh and but then the the identity can move inside the organization by getting promoted by being assigned to save certain uh project by making requests by had to change their password by being notified doing administration etc so uh and at the end of this life cycle there is that provisioning because the user is leaving the organization uh one primary need for provisioning engine is to be as much customizable and flexible as possible because a provisioning engine needs to adapt itself to exist to the existing infrastructure to existing need to existing flows or need also to evolve with company needs uh for several reasons we that might be appear clearer later um provisioning engines are focused on backhand because they are connect essentially they do their job against applications against identity stores as we said before provisioning engine finally can communicate with applications or with an entity source uh in a in a in two distinct ways they could be a connector uh oriented meaning that the the target application and entity sort of need to be changed to interact with the provisioning engine or they might require some sort of agent which is usually more invasive but also often more efficient the third type of technology that we use in the identity space we name it access managers so at the components that take care of authentication and authorization so several concepts or the standards are involved here we’re talking about single sign-on multi-factor authentication or protocols like oauth openid connect xacml so all these concepts are related to what we call access manager since access manager’s job is to deal with user and user authentication and authorization we realize that they are focused instead on front-end uh we if we try to put all the elements we’ve been introducing so far all together in a single picture we can we come out with something like this where we have the provisioning engine on the left side the access manager on the right side and then all the other components of a typical software architecture where several applications are uh available uh some of them are insisting on a given identity store but there are also other applications like hr and crm uh all controlled by the provision or identity store in the cloud that are controlled by the provisioning engine the provisioning engine is also connected somehow here we are imagining the the the simplest way uh we access managers an access manager will take care of authentication so everything that is required on front-end authorization etc while provisioning engine will offer specialized views to business help desks this admin for example and reporting and auditing and governance and administration to them uh so this to summarize the picture so let’s move to another section now that we have a common vocabulary and background let’s let’s talk about selling open source identity and access management so this is the iconic sentence we always by experience are learning and hearing from our customers or prospects when we start talking about identity management in the open source space um you can replace ibm here with any other vendor you can name the space so you can say oracle you can say for drop you can say octa cell point ntq ib whatever you want in the past you could even say some microsystems but the point here is uh finding a way to justify or to uh highlight the the benefit of open source in the iam space against what vendor could offer so what can we offer as open source iam producer not of course mentioning the price no because we are talking about hundreds of thousands of dollars for just the the license and then you have the project to do so in our case let’s uh leave the price aside what we could offer that vendor solutions don’t so first of all it’s the flexibility there is nothing more flexible than a tool you can inspect or you can extend by yourself or you can hire someone to extend and if you’re not satisfied anymore you can replace this one with someone else uh so that’s also why you don’t have vendor lock in you don’t have a black box on your infrastructure that is you know anything about uh that is driving your identity flows then you have security security management in open source especially when we talk about open source software that is ruled over uh large foundations like apereo or the apache software foundation they have a very well established and clear and reliable uh security policy for disclosure for reporting for security freight etc there is uh you have all the advantages of security management this way and of course uh customers can be and often are required to be involved in this solution because the solution itself is will be designed and very flexibly adapt to the the the requirements that customers might offer one important thing to beg to beat vendor lockin is that if you are not satisfied of your contractor because you’re not serving anymore you can go and seek into the open source the backend open source communities and find someone else that can support or you can just have your ict team to work this way the open source identity stock in our reference is composed by two pillars one being apache syncope for identity provisioning and governance so it’s the provisioning engine from the slides before the other one being apereo cas for authentication authorization etc uh that was mentioned as access manager uh in the slides before so now we are going to uh into some detail from some technical detail about these two products and also something about their roadmaps um let me leave the the the the presenter role to misagh thank you francesco um so this is the part of the presentation where as francesco said we keep talking about the the solution stack and the components that uh make up the stack in terms of open source identity access management and the first component is the part that handles well the access management and authentication authorization it sits at the front end of this entire stack and this is where the cas project comes into play cas is of course short for central authentication service many of you in the presentation might already know and be familiar with the project and it is a single sign-on manager an identity provider an access manager depending on your mood in the day you know any of those names seem might be appropriate and it is a multi-lingual platform in the sense that it can speak many or multiple standard authentication protocols uh to integrate with applications and you know verify identity and collect user attributes and claims and so on and so forth and it’s been a project that has been part of the jasig slash apereo portfolio from almost the beginning if not the very beginning and has been around since i don’t know mid 2003-ish five-ish and so in one sense it’s it can be seen as legacy software it’s been in production since 2000 mid-2000s so the current the current uh version and the current status of the cas project is is as follows the current release line is based on top of version 6.
-
Shadow Figure At Disney World
there it is guys this is the beginning of the all-star music resort which is one that i said was currently closed down due to the pandemic we actually saw a shadow figure it’s a little bit eerie during the day even it doesn’t even have to be late at night to be eerie welcome to the all-star movies resort we are so excited to be staying here tonight what an awesome value resort this is one of three there’s the all-star movies which is this one the all-star music and the all-star sports resort hopefully the all-star music and the all-star sports resort will be reopening again soon i do believe they are currently refurbishing their rooms but they have been closed for one year since the pandemic go back here and show you guys some of the different theming that they have going on here this is the 101 dalmatians area that is actually where we’re staying currently which we thought was pretty cool since the 101 dalmatians movie just came out i love the fire hydrants i think that’s a cool touch one other thing that i really think is a neat touch is down here let me show you guys immediately you can tell something’s up because there are bones everywhere here on the sidewalk which i think is an amazing touch sorry it’s a little bumpy here but you got the cruella de vil car there and there’s the bad guy with the box truck and there are some giant dalmatians down here we are gonna go check them out you can already see pongo there and there’s purdy i love how they have the dalmatian markings on the building right behind them i think that’s so cool i love all the little dalmatians running around looks like little film strips they’re running through the film strips that’s pretty cool okay guys so check it out our room number is 47.
-
OA21: Breakout (2) Developing the Sakai Dashboards - Web components and Widgets
sorry about that welcome everyone uh to the developing sakai dashboards web components and widgets session the presenter today is adrian fish my colleague from longsight so just a few housekeeping details please be sure to leave yourselves muted and cameras off that should be locked but you don’t want to turn those on during the presentation if you’d like to ask a question wait until either the question and answer portion of the presentation or you can use the shared notes in the left hand um menu bar so above the user list you can click there to ask your questions you want to use the chat primarily for chat and post any questions in the shared notes area so that we can find them a little bit easier and if you have any technical issues please send me a direct message you could do a individual chat by clicking on the user’s name so i’m wilma hodges um click on my name and send me a direct message if you’re having any technical issues and i’ll try to help you out any way i can so with that i am going to turn it over to adrian okay thank you wilma um hi everybody i’m adrian fish and i uh i work for longsight and i’ve been doing um quite a bit of work on things like the new dashboards and the grader and quite quite a lot of front-end stuff right so this presentation is hopefully going to give you a little bit of insight into how to maybe do some of this stuff yourselves right that’s that’s that’s the goal right so i’m just going to get into it i’m going to go through some slides and then hopefully towards the end the last few minutes i’ll i’ll look at a bit of code right and we can check out some of the some of the coding some of the dashboard widgets that we’ve already got in place off we go okay so we’re using web components why why are we doing that what’s what’s the kind of reasoning behind that right well first of all web components are future proof and you can use them anywhere you can use them in frameworks like react or view or whatever you can use them just in a normal web page um they’re a web you know they’re a web standard they’re a w3c standard well actually it’s a group of standards together but they are a w3c standard they’re going to be with us into the future of the internet right of the worldwide web so it’s i think it’s a good choice um web components are particularly good um for us in sakai right because we’ve got all these diverse um frameworks that we use for rendering content so you know we’ve got you know kind of jsf you know velocity wikit rsf you know loads of stuff like that right so the good thing about web components is you can write a web component and it’s just a tag and the tag will work it’ll work in in a view app or a react app or well anywhere basically so um you know it works everywhere and we can put it in velocity we can stick it in our jsf markup it doesn’t really matter it’ll it’ll work it’ll work uh wherever you put it so again it’s great because that means that we can start to actually think in terms of um extracting common functionality from our tools into web components without having to rewrite the entire tool right you know which i i think’s a pretty useful thing um yeah you know the way you develop a web component you you basically you write some markup and then you have a few fetch calls in there where you pull some data you know you render the data and we’ve already got all of that stuff in place uh with our direct endpoints right you can write you could write web components just to talk to our current direct you know direct endpoints uh and it’ll work just fine yeah um i’ve been working on a new kind of a new um spring mvc type location for um for implementing rest endpoints and it’s under the um some of the um path api the actual project’s called web api but i’ll show you this i’ll show you that kind of stuff later yeah just fetch your data and render it you know it’s pretty easy doing these things once you start once you write a web component you can use it anywhere yep just attack so let’s move on so this is the example that i always i always kind of like um invoke in these in these talks uh because it’s a it’s perfect you know it’s the permissions web component so anybody who’s done any any um you know sakai tool development in the past is probably aware of this kind of um helper pound that we have right so we have a we have a pound where we we basically offload um the current render to a uh to a helper servlet right and that’s server that will do some stuff uh and then he’ll return back to the sender yeah um it’s it’s it’s great it’s it’s served as well um but what you often end up with is having you have to maintain quite a lot of state in between those calls and make sure that you reset that state or you know reinsert that state and things like that so permissions was one of those helpers so basically what what i did was i took the markup from my from the current helper right which was like it was like like a velocity template right so i took i took that mark up um i made it into a web component and now that web components are used across quite a few tools um i think announcements uses it i think assignments uses it the commons tool used quite a few tools are basically now using this web component to do permissions and this is this this is good because what you don’t what you can get away you can throw away a lot of states by doing that right you don’t you you’re not redirecting to a helper then coming back and having to pick up states again literally the tag just renders it renders into a div on the screen you pick some options in it and that uses fetch to write those options back to an end point right and then the permissions are then set right so it’s been it’s a perfect example of taking a common piece of functionality um put into a web component and throwing away some boilerplate it’s nice it’s it’s that that is that is one of the things i love about um using web components in sakai it lets us you know refactor get rid of um you know get rid of technical debts this is great uh yeah some blood there yeah that’s right yeah permissions tiger okay he can read that later okay anatomy of the sakai web component right so we’re using a um i don’t really like using the word framework because framework implies something heavy and something that usually becomes technical debt later right but so lit element is like it’s like a micro framework right and it’s a it’s a framework that is designed you know destined to eventually disappear right it’s it’s maintained by a guy from google who wrote it and they basically they they eventually want this to go this is just a way of um gradually improving the standards in the w3c and browser support for web components right making it easier to use web components yeah so it’s a great it’s a great it’s a great little little tool right and it gives you um it gives you reactivity so when you set up properties in your web component you change those properties your markup will change automatically that kind of stuff right um it’s nice anyway but again uh we’ll look at some code later and then you’ll you’ll understand better yeah a basic compartment is literally an es6 class um so if nobody knows what es6 is es6 is the javascript standard from 2015 right where they actually added class semantics onto javascript it was the first time you could step away from from using prototypes all the time yeah most of it’s just syntactic sugar right but it it bridges the world between javascript developers and java developers or anywhere you know whatever c sharp developers whatever right the syntax is quite familiar to somebody who comes from a uh object-oriented background in like java or c-sharp yeah so um it’s it’s nice so it’s it’s a lot it’s a lot easier writing javascript you don’t have to be such a kind of a kind of guru right you know like standing prototypes really well a lot of stuff you can get away with a lot more um you know always want more leeway in the way you write these things yeah it’s just an es6 class um you define your tag when you have a render method in it and then you can use that tag that’s all you need to do that’s just the basics you can use that tag then anyway yeah after that you start to kind of flesh it out you put your reactive stuff in you know the watched properties um you know you had attributes you add internationalization well the basic thing is just literally it’s in es6 class with a render method and the definition for the tag it’s great right okay um so anatomy of a sakai tool wc style that’s not that’s not water closet it’s web components it’s just important that you i’m not talking about toilets okay um what can you do you know you got so much room on the slide you know right okay so um so this is this is like this is i’ve literally just written this this is the um this is kind of what’s in a sakai tool when you when you when you use web components yeah well what this is what’s been the ones that i’ve been writing yeah so one to many web components um communicating by attributes and events and some translations you’ll have some rest controllers which is using a technology called spring mvc uh you’ll have a service you’ll have some tests you know no excuse not to write tests anymore we’ve got nice things like mokito and stuff like that um you’ll have some jpa entity beans for your database stuff so you don’t need to write hibernate xml anymore it’s a lot nicer you just you just write a javabean with annotations to kind of define what the columns are going to do yeah and then you’ll have one too many jpa repositories um yeah i’ll talk about the spring crud repository a little bit later it’s let’s get into code a bit okay yeah yeah later on cool um yeah that’s that’s that’s the kind of that’s usually what you end up with right so the reason you you’d have let’s say you’re around at all right you might think well why have we got a lot of web components i think it’s nice to have a good few web components because you encapsulate markup in a web component so instead of having a lot of markup in one big thing like um like i know we use macros and stuff in velocity right but so you know so say you’ve got a lot of markup in in one page right it’s nice to actually break it up into tags and that’s what web components in the end that’s what they are they’re tagged right and each of those tags is responsible for its own area of the markup you don’t have to reuse those across sakai to justify actually breaking your monolithic chunk of markup up into some separate web components that just communicate with each other i think i think i think it’s a nice it’s a nice approach plus you can you can kind of test each of those individually as well right you know what i mean you can have a story for each of those things we’ll get to stories later but but you know you don’t have to reuse web components you can just say this tool has 20 website rubrics is a classic example rubrics has a load of web components um you may think well there’s why there’s so many web components in that i’ve thought it many times but i mean i think there could be a few less web components in rubrics but you know the strategy of having a set of web components that just work together but they’ve got their own chunk of the market that they’re rendering i don’t think it’s a bad strategy at all i think it makes it easier to uh you know to load up the code in an editor and and make sense of what’s going on right when the tag you know there’s one tag so anyway moving on uh right okay um yeah right so i’m going through the steps here of um you know how you go about you know what what you need to actually do to uh you know to go down this path right so the first thing i i work from the front to the back right that’s that’s what i usually do right so i mean with things like storybook i think it’s it’s a great approach to it so i don’t initially think of the back end stuff right so typically i’ve been working with designers so obviously they are working out the front right they’re doing the design so it makes it makes a lot of sense when you’re working with a designer to start from the front but too much i always have i’ll think about the front-end movement between screens and uh and then i’ll i’ll kind of like propagate that back into rest controllers then i’ll propagate that further back into a service you know they’re around my tests you know when i’ve written a service or test before here that’s what you should do that’s what you should do um so yeah so you create your basic web component and again it’s literally such a small amount of code just to create the basic tag you just create and yes in es6 class and you register the tag name right you define the tag name so so the browser knows about it when you render something in your render method you can say hello world so whatever bear text it’s fine that’s that’s how you want to start right let’s create that basic thing so you know it’s going to render yeah the next thing i would do is i would um i would get to know storybook um if you go into our um our git repo the sakai the sakai git repo there’s a project called web components and under there there’s a project called tool and under there if you keep drilling in you’ll find a you’ll find a directory called front end and that is where all the kind of um npm type stuff is like package json and all that and our stories are also in there right so you know i recommend going actually going in you know if if you’re interested in this stuff whatever kind of platform you’re working on but particularly if you’re working on sakai i recommend going in into that those directories and having a look around and seeing how the land lies with that stuff so you create a basic story now you’ve got your component um you’ve called it whatever it just renders hello world so the next thing you want to do is actually create a story to render it on the screen right because you want to start you want to start round tripping on them you know adding content to it and things yeah so you know check it works in the first place at all right the browser knows about the tag um you know storybook can then render it and you know you’ve got a working tag yet yeah i’ve been creating these sub directories on the stories now you know if if i think there’s going to be a fair bit of stuff for that component you know translations or whatever then i think it’s it’s a good idea to actually create a sub directory under there and try and structure because it the stuff that’s on the web components is growing massively right you know it’s like you know a lot of this stuff is still emergent i’m trying to do these talks and trying to kind help people along on this path right but a lot of this stuff is still emerging still with me and i’ve still got things that i feel i want to i want to bottom out and work out what is the best approach for them right but um so it’s a bit of a journey yeah but so i’m just trying let’s try my best here but i think i think that you know creating a sub directory of the stories where you’re going to put your story data so i mean you may you’ll put typically you’ll put styles on under your story directory you’ll put data mocked up data under your story directory um and you’ll put translations under your story directory as well so it’s quite a lot of stuff that’s specific to your component needs to be created and so it makes sense to create a directory um yeah there’s the path right so you run storybook so your sakai source route whatever that is web components tool source made from end and then there’s a script i’ve set up a script called storybook uh in there so all you have to do is go npm run storybook and hopefully it’ll take a while because it kind of like it pulls quite a lot of stuff from um from npm but uh when you run that you’ll get a tab opening up in your browser um with all the kind of like stories down the left hand side with and story for your new component should be there we’re going to look at some code later um right okay let’s go later well we’ve got another longer level ah right okay give me that layer yeah back-end stuff right so you can round trip a lot on on design if you’re working with a design a storybook is great because you can have two screens um you can work on your component in one you might be using something like um zeppelin or figma from your designer where your designers putting mock-ups in there um and typically what you’ll do is you’ll write your round-trip in storybook for quite a good while right you’ll you’ll mock up some data in there and you’ll be just you’ll be just basically you know copying style sheets in from from figma or zeppelin and you’ll be um you know just building the design up right and then working out what your endpoints are gonna be from that design as well right so while you’re working on these things in storybook what you’re effectively doing is you’re specking up your end points as well which is a great thing because the next stage after this is going to be working on my rest controllers and you’ve already got your endpoints because you’ve had to mock them up in storybook yeah and you know i’m going to skip that’s that’s i mean that’s that’s stuff about shadow dom and white diamond styles and stuff for me i just recommend you kind of google that you know it’s it’s pretty heavy stuff the you know the the um you know the the long and short of it is shadow dom’s great because everything’s sculpt you can just use whatever ids you want in your markup doesn’t matter right they’re not going to leak outside they’re not going to clash great stuff but shadow dom doesn’t work great with seek editor or with jquery dialogues or anything that tries to inject markup into the body it always breaks so that’s the um yeah there you go right sorry the elephant in the room right front end build chain is the elephant in the room so we we are so if anybody knows it has done some front-end stuff right there’s this thing called bare paths right which is a node.
-
OA21: Lightning Talks (3) - Software Tips & Tricks
get started this should be a lot of fun so this is the third session of lightning talks at open apereo i am not martin ramsay i am not from the lamp learning consortium i’m josh wilson from long sight martin had to step away and i thought it would be fun to gain a few extra gray hairs and step in his place so i’m gonna do my best to be my very best martin and we’ll see how that goes all right so let’s let’s get to it um so just want to note that we have we’ve got about let’s see how many people we have one two three four five six seven eight presenters in a total of six lightning talks so we’ve got people from all over the world we’ve got people from indiana and florida in the states we’ve got folks from france um we’ve got people from south africa and we’ve got people from pepperdine university in california and the university of virginia so so some folks from the states some folks from europe some folks from south africa it should be a pretty interesting session uh martin always talks about the the global nature of these of these lightning talks and that’s that’s always pretty exciting so presenters kathy has made you all moderators so what that means is that you can grab presenter rights when it’s your turn i’m not going to introduce you beyond just giving your name because these sessions are short and i want to make sure that that you have the time that you need i’m going to give you a five minute warning and a one minute warning um i don’t have martin’s clock so i’ll have to use fingers instead but that’ll be part of the fun of this session so with that said let us get started so we’re going to start with derek ramsey who’s going to talk about new features in sakai 21.
-
Connecting Quant & Qual: How Brands Are Leveraging Continuous Consumer Insights
- Hello and welcome. My name is Avi Savar and I’m the president of Suzy.
00:05 - I am so thrilled to be here with you today and excited for the lineup we have in store.
00:10 - Today’s topic is about connecting qual and quant.
00:14 - And this is something that we’ve been talking a lot about here at Suzy, because if you remember at the end of last year, we launched Suzy Live.
-
Katana Fittings, the Making of a Simple Fuchi
should really clean up the shop getting caught on everything well today i’m working on some sword parts remaking some katana fittings got the old fittings hermetically sealed in this plastic container so they don’t get dirty or messed up this is the suka took all the wrapping and stuff off just had this real synthetic ray skin got some nice real ray skin to put back on there got the old suva here less cast aluminum didn’t even bother cleaning up the brake out here when they made it replace that got the old fuji here more cast aluminum doesn’t even properly fit let’s see what else we got in here the old kashida fits fairly well but also cast aluminum didn’t clean up the casting marks got the replacement here still needs finish and of course the old ito just i think polyester and some shiny vinyl and there’s some sepa down in there yeah i already got the nutsuba basically made i have a few things left to finish out on it nice rustic finish gonna go with a darker finish on the iron i’ve got a smoother finish for underneath compare that to the old one get it in focus less decorative but you know really nice look i think this one also has a raised rim unlike this one compare the two fushi no the kashira come on come on iron aluminum should be a lot stronger with the new iron and come on come on come on focus the new future part it’s braised together don’t have the hole cut out yet but still working on it i was testing some other parts i had a silver soldered version i wasn’t too happy with the silver solder is not quite as strong as the brazing was for me brazing was a lot stronger so i wanted that it’s going to turn out pretty nice so i’m going to get back to work on this okay so i got my rotary tool all set up hung up on the ladder beside me to get some tight can’t see it it’s over there though but i’m gonna need a carbide burr because i’ve got a good bit of brass probably can’t see it in there but some leftover braising i need to take out there you go switch over to a carbide so i can take off a good bit of material without it taking me forever and this is just a rotary tool on a flex shaft from grizzly it’s been really really nice so far way better than a dremel and no cost a lot less than a fordham i think it was like i don’t know 200 or so something like that fordham’s like 800.
-
The Endless Knot Podcast ep 92: Canuck, and re-thinking Canadas story (audio only)
Aven: Welcome to the Endless Knot Podcast where the more we know Mark: the more we want to find out Aven: tracing serendipitous connections through our lives Mark: and across disciplines Aven: Hi, I’m Aven Mark: and I’m Mark.
00:17 - Aven: And today we’re talking about Canada.
00:20 - So before we get started we’re going to say thank you to a couple of new Patreon supporters, specifically Rhiannon Evans, who’s one of the people who works on the Emperors of Rome podcast, Menai, and Samantha.
-
Do This To Balance Neurotransmitters | Prostration: A Natural Remedy For Eliminating Confusion
As salaamu alaykum Sayyidi. Walaykum as salaam wa rahmatullah.
00:13 - In meditation what does it mean to put your hand on the floor? Yeah in the meditation and then in the teachings of the meditation, we have our meditation book coming out soon inshaAllah ‘A Timeless Reality’ that has two years of question and answers, so it has like a complete encyclopedia of tafakkur (Contemplation), everything is… under the sun is in there for the tafakkur inshaAllah.