It is now time for a member statement to member from Nipissing. Thank you, Speaker. I ask the members here, did you brush your teeth today? Did you take any prescription pills? Are you wearing a rayon shirt or blouse? You may ask what do these have in common, Speaker, and I can tell you all of those products contain wood pulp. Does your car have an airbag? If so, the detonator has wood fibre. Was there shredded cheese on your lunch? If so, the cellulose gum that stops them from sticking, well that's wood pulp. Are there paper clips in your desk? Wood fibre stops those from rusting. Did you get flowers in a cellophane wrap or candy in the crinkly package? That's all wood pulp, cellulose from wood chips. Speaker, tomorrow members at the Justice Committee will be asked to stand up for the forestry sector and for Northern Ontario. There are amendments to Bill 52 to ensure the legislation isn't manipulated to the detriment of the North. The bill is meant to protect the voices of the people who are unable to protect themselves, not the multi-million dollar antiforrestry special interest groups. I urge the government to support the amendments and stand up for the people of Northern Ontario. Thank you. Speaker, I'd like to talk about the ongoing concerns about layoff notices at Community Living Elgin in the London area. My colleague, the member from Hamilton Mountain, has written a letter to the Minister of Community and Social Services about the seriousness of these layoff notices and their impact in our region. This government has already slashed programming and services for some of our province's most vulnerable people and non-profits and transfer payment agencies like Community Living are left picking up the slack. And to add further injury, the government has not supported pay equity obligations with funding that allows these organizations to make ends meet. The government has promised to reduce wait lists for services like those offered by Community Living Elgin and yet we are seeing unprecedented workforce cuts and more damage to an already precarious system. And this says nothing of the ripple effect of the impact of the resultant job losses. Southwestern Ontario is suffering from serious unemployment and continues time and time again to be the victim of this government's inability to manage the economy. The Minister has said that she and her ministry are monitoring this situation at Community Living Elgin extremely closely. We would be very interested to know what this extremely closely monitoring has revealed. The minister also stated on September 17th in a response to a question that the review would take a number of weeks. It has been nearly a month and I would like to know when can we expect to see the results of this review. Thank you, Speaker. Thank you. Further member statements? The member from Durham. Thank you, Mr. Speaker. Another great festival in downtown Bowmanville. South Ulai October 17th is historic downtown Bowmanville's Apple Fest. This is the 25th year for this incredible popular event and if you know Durham, you know the importance of apples to our local agricultural sector and economy.  My plan is to get there early. There is always a line of fresh hot apple fritters, but it's always worth the wait. I know how hard our local apple producers have worked to ensure the best crop possible under some tough spring conditions this year. I also know that historical downtown Bowmanville, BIA, puts in a huge effort to ensure events like this is a go ahead and a wonderful success. I would like to thank them for all they do in advance of this year's event, which I'm sure, as always, will be fantastic. So if you don't have plans for October 17th, I would invite you to join us in Bowmanville. It's well worth the trip. I'll even share some of my fritters with you. So please come and join us on October 17th. Thank you, Mr. Speaker. Thank you. Further member Stegas, the member from York Central. Thank you, Mr. Speaker. Mr. Speaker, today I rise to speak about the province-wide opposition to the Premier's fire sale of Hydro-1 and specifically to the overwhelming opposition in my own writing of York Simcoe. Mr. Speaker, this summer the Simcoe County Council supported a resolution from the Western Ontario Wardens Caucus, which cautioned that, and I quote, privatization partial or whole of electricity has led to higher rates and less control. In their resolution, they both called on the provincial government to stop the sale of any part of Hydro-1 and maintain Hydro-1 as a wholly public asset for the benefit of all Ontarians, as well respect the autonomy and local decision-making powers of local distribution companies by not forcing these companies into mergers or sales. They argued that the government has no mandate to sell any part of Hydro-1, and I agree. Mr. Speaker, they are worried that Hydro-1 will no longer be subject to scrutiny by the Auditor General, the Ombudsman, or the Integrity Commissioner. Further, they will no longer have to respond to freedom of information requests. Voters know that this government is ignoring their voices on this matter and are rallying to other levels of government in the hopes of being heard. This resolution must sound familiar to the Premier as it was sent to her in a letter from the County of Simcoe on August the 11th. It may also sound familiar to the Minister of Energy and the Minister of Finance. Thank you. Further member statements? The member from Tomiskini, Cochrane. Thank you, Speaker. On Wednesday evening, September 23rd, Mr. Sam Bryant was doing something we commonly do in Northern Ontario. He was out bird hunting, bird hunting, just outside of Latchford, something a lot of us do. But the hunter became the hunted. When a fairly large black bear came out of the trail, Sam did what we were told to do and tried to stand off the bear, but the bear wasn't in the mood for doing what he was supposed to do. So Sam did what every person, I think, in this house would do when the bear started coming. Sam ran. And I don't blame Sam a bit. Sam had a 22 and he turned and he shot the 22 in hopes of scaring the bear. And when Sam reached town, thankfully the bear wasn't there. But that is not an isolated incident in Northern Ontario. People have to deal with bears all the time. And although we spend, according to the Minister, more educating people with bear wise than any other jurisdiction, no one in the MNR is actually protecting people from nuisance bears. It shouldn't be up to the municipalities. It shouldn't be up to the police because they're not trained to protect against bears. It's up to the MNR and people shouldn't have to risk their lives doing the things they enjoy in Northern Ontario. Thank you, Speaker. Thank you. Member Stevens, a member from the Topical Center. Thank you, Speaker. Speaker, we have world-class post-secondary institutions in Ontario. The choice a student makes about their program of study in the institution at which they will study is one of the most pivotal and important decisions a person will make in their life. It is one of the largest financial investments we make in our early lives and the choice of post-secondary study shapes the path we follow in our careers. That is why it is so important that students are able to access the information that they need to make an informed decision about their post-secondary studies. After being elected, I met with student groups, businesses, colleges, universities, and others, and some spoke about the struggles of choosing a post-secondary path. It is not an easy decision to make, and many students and their families sometimes struggle to find the information they need to make an informed decision. Today, I'll be introducing a private member's bill that tasks the Higher Education Quality Council of Ontario with the creation of an online resource that would help students make more informed decisions as they decide on which university or college to attend and which program of study to pursue. The resource would do this by providing a more comprehensive picture for students about access, student experience, and graduate outcomes for each program offered at each of Ontario's post-secondary institutions. I'd like to thank the Canadian Federation of Students, the College Student Alliance, the Ontario Undergraduate Student Alliance, and the Ontario Graduate Student Alliance for their advice in the drafting of this bill and their subsequent endorsement. This bill would have helped students and families make more informed decisions leading to more satisfied students and stronger outcomes, and I humbly request my fellow members here in the legislature for their support as it works its way through the House. Thank you, Speaker. Thank you for the member's statements. The member from Carleton, Mississippi Mills. Mr. Speaker, this year is the 25th anniversary of the Carp Farmers Market. The Carp Farmers Market was founded in 1990 by Hildegarda Anderson. She was a farm girl from Saskatchewan who had a vision of a producer-based farmers market in the village of Carp. She found a location. She found the people. She established a board of directors. She found vendors, and the Carp Farmers Market began. The main guiding principle that she insisted on was that all the vendors be producers of what they sold, in other words, a producer-based farmers market. That principle has been the guiding light and strength of the market to this day. The Carp Farmers Market has flourished, and today is the most successful producer-based farmers market in Ontario. Delicious foods and wonderful handmade products are available in Carp every Saturday. The number of vendors and customers continues to grow each year. The Carp Farmers Market celebrated their 25th anniversary on July 4th of this year. Hildegarda Anderson died in a car crash in 1993. But her legacy lives on. She would be proud of the Carp Farmers Market if she were here with us today. Thank you. Thank you. Member from Mississauga Brampton South. Mr. Speaker, on September 16th, I had the opportunity to attend the community policing dinner hosted by the Mississauga Chinese Business Association in the great riding of Mississauga Brampton South. The association advocates for community development through private business and support for local partners, such as Peel Regional Police. At the dinner, the association paid tribute to the local police officer whose career best represents the qualities of community policing. This year, Constable Tom McKay with Peel Regional Police was chosen to receive their prestigious award for his community engagement and years of work in crime prevention. Constable McKay has an impressive resume as a 30-year veteran of Peel Regional Police and author, lecturer, and a leader in the field of crime prevention. Mr. Speaker, I would like to thank Constable McKay for his commitment and also the Mississauga Chinese Business Association for building a safer, more dynamic, and vibrant community. Thank you, Mr. Speaker. Thank you. Further member Seamus, the member from Barry. Thank you, Speaker. Imagine this, you're rushing around in the morning, you shout goodbye as your husband, son, or daughter heads out the door to work. Sounds pretty normal. However, that loved one never makes it home or has a horrible accident that changes everyone's life forever. Although workplace deaths and accidents have been reduced considerably, one death is still too many. Over the weekend, I had the honor of speaking at the Threads of Life event on behalf of the Minister of Labor. Threads of Life helped families of workplace tragedy along their journey of healing by providing unique family support programs and services. Threads of Life is supported by a network of volunteers from across Canada who have been personally impacted by workplace tragedy. They assist families by providing a family support program which offers one-on-one peer support to family members and friends who have suffered from a tragedy such as this. And they are matched with a volunteer family guide. They also give regional family forums, bring families together in a community of support to benefit from coping skills, active listening, and healing. Speaker, I want to commend Threads of Life for the amazing work that they do for families impacted by these terrible workplace tragedies. Thank you. I thank all members for their statements. It's now time for re-


Now I've started recording. Hello everyone. This is Circuit Python Weekly for May 31st, Tuesday, May 31st, 2022. This is the time of the week when we get together to talk about all things Circuit Python. This week we're delayed a day because of the Memorial Day holiday in the US. I'm Dan and I'm sponsored by Adafruit to work on Circuit Python. And Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit. So if you want to support them and Circuit Python, consider purchasing hardware from Adafruit.com. We host this meeting on the Adafruit Discord server. You can join any time by going to adafruit.com. You hold the meeting in the Circuit Python Dev text channel and the Circuit Python voice channel. Usually this meeting happens on Mondays at 2 p.m. US Eastern time, 11 a.m. Pacific time, except when it coincides with the US holiday, which was yesterday. In the note stock, there's a link to a calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you would like to receive these notifications, ask us to add you to the Circuit Pythonistas Discord role. There's a note stock to accompany the meeting and recording. The note stock contains timestamps to go along with the video, so you can use the dock to view only the parts of the video that interest you most. The meeting tends to run 45 to 90 minutes. You can skip around because of that. Let's see. What else would I like to say? If you want to see the meeting notice, it's always pinned in the pinned messages in the Circuit Python channel. For instance, here I'll show you by looking at the pinned messages. Just go there and you can find a link to the note stock and the information about the next upcoming meeting. We hold the meeting in five parts, community news, the state of Circuit Python, libraries in Blinka, hug reports, status updates, and finally in the weeds. I won't explain those in detail right now, but I will in the beginning of each one. Let's go ahead. I built a cadney told me she built a timestamp generating engine, which was written in Circuit Python and I did the same thing with the CPX. We'll try that. It might help if I plug it in. In which case, it's time is off, so never mind. Next time I'll do that. All right. Let's start with community news. This is news from the weekly, our weekly Python for microcontrollers newsletter, which usually goes out via email on Tuesday mornings this week. It'll be Wednesday morning. Visit Adafruit.daily to subscribe to the newsletter. Thanks to Ann for putting the newsletter together. If you have any Python or on hardware projects to share or find content you like to see included, please continue, consider contributing to the newsletter. You can open a PR on GitHub, tag at sign Ann underscore engineer on Twitter with the hashtag sort of Python or email CP news at Adafruit.com with the news and the link to whatever the news is about. So let me go ahead and go over the community news that we have for in the upcoming newsletter. I'll put a timestamp in here. The Circuit Python GitHub repo has reached 3,000 stars. Those are stars you can star your favorite repos in GitHub. It exceeded 3,000 star gazers this week. Thank you all the people who have chosen to star this Circuit Python code repository. Thank you very much. It helps our visibility. Next, Ann Barela talks Circuit Python with crowd supplies, Helen Lee. The crowd supply teardown sessions, a series of interviews and hands-on learning sessions with crowd supply creators, staff, and lots of special guests host Ann Barela, your editor of the newsletter, to discuss Circuit Python and more. Ann, did this happen already or it's going to happen? It happened Friday. Okay, great. So go to the links and you can see the interview. Thank you very much. Okay. Next, MicroPython is up to 112 sponsors. MicroPython sponsorship fundraising continues with 112 people and organizations providing monthly support for MicroPython development. Their new target is $10,000 a month, which would allow them to hire more folks to work on the software. Please consider sponsoring, especially if you use MicroPython and or Circuit Python, which derives from MicroPython. We are immensely grateful to MicroPython and we continue to pull down code from it whenever they have a release. Without MicroPython, Circuit Python would not exist. Adafruit's been sponsoring MicroPython and we encourage everyone else to do that as well. Thank you. Finally, this week, Naomi Cedar, who gave the keynote, a keynote at the recent PyCon US, her keynote is available. You can see it on YouTube and the text of the talk is online. There are links in the in the notes. Okay. And as I mentioned, the newsletter is published every Tuesday, except this week it's on Wednesday because of a holiday. Please contribute to the newsletter whenever you find interesting news related to Python and MicroControllers. Thank you. Next up is the state of Circuit Python libraries in Blinka. This is kind of a statistical overview of what's going on in Circuit Python in the past week. We'll start with describing pull requests overall. In the last week, there were 24 pull requests merged by 17 authors. A new author I see is ML Hakeems, I think, is the name. Thank you very much. If you're not new, thank you anyway. There were 17 authors, six reviewers. There were 16 closed issues by 10 people and eight opened by seven people. So we closed eight issues successfully and we were reducing the number of issues, which is always great. Scott, would you like to discuss the core? Sure. I'm happy to do that. Sorry for the laundry noise. Numbers for the core. We had 15 pull requests merged from 12 different authors, so thank you to all of those authors. I think most of these folks have been around, so thank you to all the authors. We had three reviewers, Dan Jeff and myself, so always looking for more reviewers. We have 17 open pull requests. Three of those are over 100 days old. Only one is 200 or more days old, so you should take a look at that. And then a lot are kind of in the middle ground between zero and 86 days. So again, we should take a look at those. We have 16 closed issues by four people, or six closed issues by four people have four open by four people, so we're net down, which is good. We're hovering right around this 510 open issues mark, which is good. We have five active milestones. 44 are open for 8.0. We're going to want to triage those for 8.0. But we did tag main as 8.0, so we've been able to get some changes, some breaking changes into the main code base. So if you are using absolute latest, be aware that that is going to be changing, and we're going to be breaking some stuff. But yeah, that's where we are in the core. Thank you very much, Scott. Okay, libraries, Katnene, who would like to talk about libraries. Fair thing. So this applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore, CircuitPython underscore, as well as a couple extras like our cookie cutter and the community bundle. So we had across all of these repos, eight pull requests merged with five authors and five reviewers. Of those merged pull requests, most were zero or one day old, and one was four days old. Leaving 27 open pull requests across all of these repositories. We had seven closed issues by six people and four opened by three people, leaving us with 641 open issues. 187 of those are good first issues. If you're interested in contributing to Python or to CircuitPython on the Python side of things, consider going to circuitpython.org slash contributing. You'll find all of this information and more. If you're interested in reviewing, check out the open PRs. If you don't have the hardware, you can look at it for syntax, spelling, so on and so forth. If you do have the hardware, please test it. Leave a comment. Let us know you did. And once you are comfortable with that, we can look into leveling you up to our review team. If you're interested in providing code or documentation, check out the open issues. As I said, the 187 of our issues are good first issues. So if you're new to everything, check that out. If you are looking for something a little more complicated or that sort of thing, you can look for bugs or enhancement labels. And if you're new to everything, we have a guide on contributing to CircuitPython using Git and GitHub, and we are always available on Discord to help you out. So please don't let that intimidate you away from considering joining our contributing members. There were no new libraries in the last seven days, but there were three updated libraries which I will not read through, but they're available in the notes. That's what I've got. Thank you, Katny. Okay. Next up is Blinka. And Melissa, can you read? Melissa, are you there? If you're not, I'll go ahead. Okay. So maybe having trouble, so let's, or out of the room. So I'll go ahead. So Blinka is a compatibility layer. Hey, I'm sorry I'm back. That's all right. I had to walk away for a second. Okay. Blinka is our CircuitPython compatibility layer for MicroPython, Raspberry Pi, and other single board computers. And this week we had one pull request merged by one author and one reviewer. There are currently four open pull requests among the repositories. There were three closed issues by three people and zero open by zero people leaving a net of 78 open issues. And there were 8,974 PiWheels downloads in the last month, and we are currently supporting 88 boards. And that's it. Okay. Thank you very much, Melissa. Okay. We'll move on to, to Hug Reports now. Take another timestamp. Hug Reports is where we highlight folks in the CircuitPython community and beyond for doing awesome things. We do this in a round robin fashion. I'll start and then we go in alphabetical order after that. If somebody isn't here, I'll just read their contribution. I'll start. I'll take a timestamp for myself. So first, thanks very much to Jeff for fixing things even while he's on vacation. I guess it's probably vacation is relaxing, but working on CircuitPython may also be relaxing in some way. So that's great. But Jeff always feel free to take vacation instead. And he's fixing things that sort of may come to mind and they've been, they're things that have been annoying us for a while. And that's very nice. Thanks to Scott for experimenting with space savings last week. He discovered some things with, he'll talk to you about, about the translations, which we might be able to save a lot of space on certain builds. Thanks to Tectric for tracking down incompatibilities with the new version of Sphinx, the documentation system 500. It's not quite as painful as it could have been, but there were plenty of changes that we need to make. And thanks to Deso Robin, who's testing Matrix Portal Network issues and has been really helpful in figuring out what works and what fails after a certain period of time. Okay, I'll move on to C Grover now. And I'll read since they're not here. Thanks to FOMI guy for taking the Titanobaclight issue and running it towards the finish line with changes to the CircuitPython core. Also appreciate FOMI's comments on the touchscreen calibrator example, Paul Request. And that brings us to FOMI guy, take another timestamp. Thanks to C Grover for submitting touchscreen calibration example for requests. Thanks to Jerry and for everything they contributed, especially around radio modules. Testing some of the older PRs in those libraries was my introduction to RF and Jerry was very helpful. And a group hug. Next up is Jeff, who also gives a group hug. And the next up is Catney. I have a few hugs today. First up for TechTrack for finding an issue with the libraries over the weekend and immediately fixing it. Thanks, updated and something we had in our conf.py for the documentation was no longer happy. So Sphinx was failing and TechTrack took care of that. To Jerry for helping me out with a project that I got the pieces for ages ago and of course left to the last minute to finish. He's super excited to help me out with this. So that's really good because with help I can probably get it done in time. And to Liz for doing all the code and firmware testing for the QT Pi ESP32 Pico guide that I'm doing. It turns out she had the hardware for the guide I was working on and I have the hardware for the guide she's working on but we stuck with it and we're gonna just you know power through testing each other's code. And that's what I've got. Okay, thank you Catney. Okay, next up is Maker Melissa. I just wanted to give a hug report to Catney for helping me with updating fritzing. To Paul Cutler for contributing to the OpenSame project. To Ann Burrell for your great interview on Tom's hardware and a group hug to everyone else. All right, thank you Melissa. Okay, next up is Mark Gambler who's not able to speak who gives a group hug. And then also next up after that is Tammy Makes Things who also gives a group hug. And next up is Scott. Hello. I also just I just wanted to say thank you to everybody who's here and who participates in Good Faith on our Discord. It's so nice to work with you all and the context is that I woke up to a kind of mean message from somebody on a different Discord this morning. So it was just made me appreciate the space that we've built and that we all invest our time and patience into. So thank you everybody for that. All right, thank you Scott. Okay, next up is Tectric who is in the chat but can't speak. So I'll go ahead and read theirs. Thanks to Catney for the quick help getting an adabot patch going to support the Sphinx 501 upgrade we just talked about. Thanks to Dan H for helping to get the manual fixes for other issues regarding the Sphinx update reviewed and merged. And a group hug. All right, thank you Tectric. Okay, next up is Status Updates which is also a round up Robin where we just say what we're up to which could be Circuit Python or other things if you have other things occupying your time that you'd like to talk about. That's fine. So I'll start. Last week right after the meeting I released Circuit Python 730 final which has not, up to now it does not seem to have had a lot of regressions or problems which is great. It has really shaken out in advance. I did fix a problem with multiple rotary encoders on Espressif. That fix will be in 731 assuming we have a 731 release which we probably will but I'm holding off on that until we add a few more other bug fixes. Over the weekend I fixed some buffer and buffer size issues with the ESP32 SPI library. Someone had found a problem where it wouldn't talk properly to certain kinds of web servers. A review of that is in progress and also I decided to clean up that library in general. It has a lot of deprecated methods in its classes and stuff and could really use a cleanup to make it more compatible in particular with the socket part to make the socket board more compatible with the way sockets work in regular Python. And I'm now debugging other network problems, specifically problems on the matrix portal but I think they apply in general to ESP32 SPI and maybe even to Adafruit requests in general. All right. Next up is Cgrover. Take a timestamp. Wrapped up touch screen calibration example poll request for built-in displays supported by Adafruit touchscreen. The Cgrover NAU7802 circuit Python library was placed into the community bundle for use with the new NAU7802 breakout and a couple of custom feathering boards was an interesting and complicated learning experience or adventure. Developing a prototype gamma sensitive brightness control helper for the matrix portal that currently works with display AIO object color and fill attributes as well as bitmap palettes. A bonus is that the algorithm algorithm works nicely with NeoPixels and other RGB LEDs. Now I'm going to steep learning curve trying to figure out how to walk a multi-layer display IO group tree to one, capture initial full brightness color information and two, modify display AIO object colors based on the prototype's gamma sensitive color brightness algorithm. The goal is to create a helper or class that can you literally adjust linearly adjust display brightness similar to TFT backlight. Lower brightness means less heat, lower power consumption and a display that's easier to photograph. Okay, thank you Cgrover. Next up is Catney. So last week I started the Qtipy ESP32 Pico guide. I worked with Liz for testing code and firmware on the Pico guide and I updated the feather ESP32 V2 guide with new drivers. This week I'm planning to finish the ESP32 Pico guide however it is on hold until I have hardware. I really appreciate Liz's testing things however it was running into I need gifts and I have to actually like iterate on code and to make anything work and I wasn't sure whether she had time to do that and so on and Lamar put the board in the shop this morning so it is on the way so that guide should be up soon enough. The next thing I'm up to is a whipper snapper needs circuit python board reset bootloader reset gifts for seven different boards. Basically they just need showing the right rhythm to get into the bootloader and I agreed to help out with that so I will be doing that. Then after that is the github fancy profile guide basically using tools to make your github profile more fun and attractive. Light tower and next is a light tower github action status light. It's something you plug into your computer by USB and it runs desktop python. I still have on my list but lower priority is the add a project to pi leap guide which was started but never completed and then to set up the repository for the x squared c addresses guide migration to mark down and that's what I've got going on. Okay thank you catney. Okay next up is maker melissa. Last week I finished updating the feathers and feather wings guide. I deprecated an old general eink guide in favor of four separate guides I wrote. I added a bunch of new checks to circuit python.org repo and fixed any issues found with those checks. I worked on some miscellaneous github issues and I went through guide feedback for the neopixels on raspberry pi guide. This week I'm going to work on some more github issues. I'll possibly be circling back to working on touchscreens on the raspberry pi and I'm not sure what else at this point. Okay thank you melissa. Okay next up I'll read mark gamblers. Did a small pr to add setting static ips for wi-fi that was asked for in an enhancement issue. Thank you that should be very useful to a number of people. Next up I'll read tammy makes things. Didn't work on circuit python stuff last week sad face. This week aiming to get back into my regular groove. All right next up is scott. Hello Last week wrapped up the .env stuff which should be cool. That allows you to do os.getenv from a .env file on the root file system. And then I kind of got sidetracked into the world of trying to find ways to optimize our code space. Along that sidetrack well I made a repo called elf section graph which keeps track of the dependencies between individual elf sections which are like per function per data thing and then if they're not used we can the the linker will just discard them. So I did some research there did not find quite as much as I had hoped and then I got a little distracted. I made treemap.dev which is just like a upload a json file and it will allow you to view it as a treemap which is a very common visualization for like how much file space is my file system taking and things like that so that that's kind of useful for this sort of thing. I did find one thing in terms of code size optimization which is the way that we do translations is we have a function called translate that gets generated where it takes in the regular english string and then it has this big long if statement if statement chain that does string comparisons between that and the other copy and then it returns the compressed data that works pretty well on lto builds where lto is link time optimization so basically that whole function disappears and all you're left with is the the compressed data at the end. However that's not the way that was working on non lto builds such as all of the esp stuff and so I figured out all right I thought of a way to to be able to do that kind of optimization pass a compile time and basically we generate that translate function for every c file that we're compiling and each one of them independently can optimize it away to what it needs which should give us some space back on esp which is nice and so there's still some ci failures it's draft pr i'll have to follow that up later today but that should be good and that should get us some some space wins on everything that's not lto so the things that are lto are like nrf some of nrf and all of sam d i think are all lto but on all the other builds this should this should get us some wins uh i also i i had like a few hours on friday so i was like let me just see dan and i had talked about this a little bit um there's we used gcc to do the compilation but there's also another compiler called clang um that is very uh doing a lot of development and and iterating a lot um it's used by big companies like apple and google and stuff like that but the problem is is that not a lot of embedded stuff is done um so uh it has really good warnings and i got certified in compiling with it but the reality is that gcc still does better in terms of code size which is kind of critical for us uh specifically uh the lto versions of clang can't do dash os or dash oz which are the size optimized versions so um i tried that there's a there's a branch there just to see what uh you need to do for it but i that's all i'm going to do on that um i did also start prototyping the new serial output so i figured out like the magic vt100 commands to like put a status bar at the top um and so that's something i'll probably work on along with uh that's i think that's kind of the next step to go along with the wi-fi work workflow work um but we'll see it might be a bit slow going um that's it for me okay thank you scott uh next step i'll read tectrix contributions after a time steal uh last week developing more tools to check libraries for build issues and patch library bundle problems a very accidental yet timely happenstance writing documentation for said tools so others can eventually use them helped get the majority of libraries fixed for the new sphinx version 500 via adabot that is using adabot to automate the changes needed in a lot of libraries started playing bug whack-a-mole for a few libraries with additional sphinx issues due to deprecations and new features in sphinx 500 this week continue developing patch tools wrap up manual patch fixes fixes for sphinx upgrade start manual patches for the previous pilot adabot patch and taking time to hang out with my girlfriend's family all right and um finally we have uh in the weeds but there are no weeds this week the lawn the garden has been cleaned up so we have no weeds and we're pretty much done is anybody else have anything they'd like to bring up before we wrap up the meeting okay i guess not um let me take a time stamp for the ramp up this has been the circuit python weekly for tuesday may 31st 2022 usually we're on mondays thank you to everyone who participated even though it was on an off day this time if you want to support adafruit and circuit python and those of us that work on circuit python consider purchasing from the adafruit shop at adafruit.com the video of this meeting will be released on youtube at youtube.com slash adafruit and the podcast will be available on major podcast services newsletter will also be in the python for micro controllers newsletter you can visit adafruit daily dot com to subscribe next week's meeting will be held on monday at the regular time 2 p.m eastern u.s time 11 a.m pacific and it's 1600 uh you hours utc this summer in the summer um the meeting is held on adafruit discord you can join by going to adafruit dot it slash discord and if you want to find out about this meeting asked to be added to be notified you can uh uh be asked to be added to the at sign circuit python east is roll into discord thank you everyone uh short meeting 30 30 minutes or so but we appreciate your contributions and i will stop recording now


na okote ni iti tulaitu inenu wa the other. Definitely the ammo advice would be that you had to hold on, please wait on a little bit until the situation normalizes. You remember there's a lot of workforce that was recruited for I some companies expected to have what you call a boom and most of them did not use what you call the labor force at that time. So meaning that we still also have some access that was recruited. You remember not all companies recruited


Papal came down here, down that county road behind me with the mules, and they say the ruts were so deep that it was up to the belly of the mules, a lot of it was swamp, a lot of it was timber. In 1935, cleared a lot of the land with a cross cut saw and started farming. My dad and mom married in 55, 56, I hope I don't get that wrong. And I came along in 64. And together everybody built a farm with our extended family, my uncles, my mom, my dad, everybody. We farm rice, soybeans, corn, cattle, and been doing it for a while. The soils here are mixed, they're anywhere from sandy to mixed to heavy, heavy clay, very poorly drained. We fight the cash river that continues to flood due to the plugs, the beaver dams, the grubs that we need to get dug out. Today we'd like to talk about the unfortunate inflation and the cost of things we're having to buy. This is really no different from what people out in town are having to buy. It's bad here too. I made a few notes. For a 1,000 acre rice farm, fuel is up $55,000 from 21 to 22. Our nitrogen fertilizer is up $111,000 per 1,000 acres. Other fertilized costs are up almost that much as well. The sad thing about it is there seems to be plenty of fertilizers available. It's somebody just making some money here. The COVID hasn't helped, the close downs hasn't helped, the war in Ukraine, you know that hasn't helped because a lot of fertilized comes from there. But it seems to be plenty of fertilized in the country, next year might be ugly. It's been tough. Prices are up for our stuff. They're not up as much as these increases. It's just overwhelming when you look at it like on a 1,000 acre basis. I don't know where we're headed with this. I really haven't offered any solutions because I don't have them. But I know I need this to work out and I think the public need this to work out. This needs to work out. We're making a good quality product and I'm proud to be part of it.


Suppose we want to find the sine or cosine of the sum of two angles. To begin with, suppose we can draw the right triangles with angles phi and theta and place them in a rectangle as shown. Now, since A, B, C is the right angle, let me know the sum of the angle CAB and ACB is 90. And so, angle ACB must be 90 minus theta. Now, since ACD is also a right angle, we know that these three angles, ACB, 90, and DCE, add to 180. And so, that says that DCE is theta. So, we want to find the sine of theta plus phi. And we know that the sine of theta plus phi is opposite. We'll draw that perpendicular and call it DF over hypotenuse AD. So, let's try to find DF. So, DF is the same length as BE, and that's CE plus CB. Now, let's consider CB that's in this right triangle. And so, we know that sine of theta is CB over AC, or CB is AC sine theta. Likewise, CE, well, that's in this right triangle. And because this is the angle theta, then the cosine of theta is CE over CD. And so, CE is CD cosine theta. So, in our equation, we can replace, but wait, there's more. We now need to know something about CD and AC. Now, CD is in this right triangle. And so, we know the sine of phi, well, that's CD over AD. And AC is in this right triangle. And so, that's the cosine of phi is AC over AD. And so, we can find AC and CD, which will be. And substituting them back gives us, and if we divide everything by AD, we get, but the ratio DF to AD, well, that's just the sine of phi plus theta. And so, we have our relationship. And this generalizes even if we don't have acute angles. And giving us a useful theorem, the sine of a sum can be found by a formula. So, for example, let's find the sine of 75 degrees. And we know that 75 degrees can be rewritten as the sum of 30 and 45. And here's the important thing. We know the sine and cosine of 30 and 45. And so, we can rewrite sine of 75 is the sine of 30 plus 45. Our theorem gives us a formula, substituting in our values, and simplifying. What about the sine of a minus b? So, we know that a minus b, well, that's really the same as a plus negative b. And so, we can treat this as the sine of a sum. But the cosine of negative b is just the cosine of b. And the sine of negative b is negative the sine of b. And so, we have... And so, we can extend our result to include the difference of angles as well. So, let's find sine of 75. Wait, didn't we just find that? Well, while we already found sine of 75, we can verify that our new method gives us the same result. As a general rule, if you have a new way of doing something, make sure it gives the same answer as the old way. So, I want to write 75 as a difference. How about 120 minus 45? And so, the sine of the difference is, substituting in our values, and simplifying. Uh-oh. Oh, wait, they are the same. We're good.


Hello everyone. I have a crazy idea. Let's remove color from design. Now I'm not talking about designing in black and white. What I'm talking about is taking color out of the equation completely because it's actually quite irrelevant. But hear me out. I'm talking about the early stages of a project and everything that comes before visual design. That is when we need to forget color exists because that will allow us to focus on what's really important. Crafting an engaging experience while solving problems for people. So that means that first and foremost we need to focus on the user and the content not on the design. Visual design is important. Yes, but it's only one piece of the puzzle. What we truly and ultimately want to achieve is impact. So I argue that a visually beautiful website isn't really worth the pixel it occupies on the web if it isn't usable, useful and speaks to its audience. So let's explore the most important fundamentals of creating an engaging experience that creates impact. We as designers we often just dive right into visual design, right? And without even understanding the full project or doing any research.  I certainly have. That looks like a lot of you have too. And that's totally normal because we are visual creatures. We get excited about design. But what we want to do is we want to create a solid foundation. But we can't do that if there are too many unknowns. So what do we do? We ask a million questions and don't hesitate to question the obvious answers. Who are we designing for? What problems are we trying to solve? And I'm using the word we and our a lot today because we as designers we need to put ourselves into our client's shoes. Their goals become our goals. Their audience becomes our audience. While we still keep a bird's-eye view and see all the pieces of the puzzle come together and form the full picture. Let's think of this as a first date. What do we do on a first date? We meet the person for the first time and we get to know each other, right? So we have a conversation. We ask a lot of questions and at equally important we listen. That's basically your discovery phase, the early stages of your project. We get to know the project and the client. But by removing design from the equation, we foster better conversations without distracting. Because in my experience clients often focus on what a finished website looks like and we need to refocus them because in the early stages of a project that is not important. And if we don't we don't allow ourselves to truly define the goals and audience of a project what sometimes could happen is that we're trying to cater to too many audiences and we're going to water down our message and we're actually not reaching anyone at all. We're just going to confuse people and we're going to turn them away. So we want to not over complicate things. We want to keep it simple. So we're still on our first date and we kind of get to know the person better and we like them and if we want the day to end well or we're hoping for a second date, what do we do? We want to try and keep the conversation flowing. Equally when somebody, equally with your website, you want to bring the right people in and once they're there you want to keep them interested and engaged. To do so we need to guide them. We need to guide their attention and make sure that they find what they're looking for and I use the word guide a bit loose here. What I actually mean is we want to create an intuitive experience by creating clear and helpful user paths. But what we need to do here is listen to our audience and observe them because if we design something that people use in a very different way we might need to adjust it. We create truly natural user paths when we allow people to discover and explore content and then allow them to dive deeper into it contextually. So I'm talking about a teaser content for example and then learn more so they can dive deeper into it. But we want to make sure that we do that on every single page of our website because not everybody comes in through the front door or our home page. So we want to link and guide people to related content or more content from every single page. One thing I kind of want to touch on that we might sometimes forget, but it's very important. If our design is complicated and hard to navigate, it's not the user's fault. It's actually our fault. We need to do our research. We need to understand what people are trying to do on our website and we need to adjust it and guide them well because what we want to design is something that's logical and that's easy to inject with. To be truly impactful, give your audience the feeling that you know them well and that you care, that you feel their pain and that you can solve their problems. We want to relate to them, empathize. That's where the true magic of connecting to people is at. There's a simple tool that we can use to achieve that. It's the power of storytelling. Storytelling has been used throughout the beginning of mankind to entertain, educate and to share information. Stories evoke emotion. People tend to relate to the characters and they cheer them on. They want them to succeed. So we can use storytelling to connect to our audience. Let's go back to dating real quick. How do we get to know people? We share stories about ourselves and by doing that we build trust. So on our website we should use storytelling to tell our story and we want to do that in a human way. We want to be approachable. But what tone language and mood is appropriate is always a good question to ask. Let's just think about a law firm who creates a website targeting people that seek legal help. They can't use legal speak because nobody understands that, right? So they want to communicate trust. They want to take people's fears away. They want to make sure people understand that they can help them in their most impossible situation. So that will guide the way that they communicate on the website. And it's different for every single project, the mood and language that we use. When we're able to truly relate to our audience, we create a connection. We build trust and we develop a lasting relationship with our audience. And that's ultimately what we want to do. So visual design is important, yes. And by implementing the fundamentals that Hugo and Beth were talking about earlier, you can truly create and complement a well-crafted experience. But you can only do that if you have a solid foundation. So if you raised your hand earlier, for the beginning of your next project, I want you to forget color exists, period. Because I want you to understand your audience. And I want you to guide them intuitively. And most of all, I want you to relate to them. Because if you do that, you can truly leave a mark and make an impact in people's lives. Thank you.


Hi everyone, Joe for Jasmine's casebreaks.com doing our final Chronicles Fat Pack to unlock Contender's Optic Picker Team Four which is coming up in a separate video. This is Pack Break number 503. As always, we're gonna do the break itself first and we'll re-randomize everybody's names, the full list of names, and match you up with a team. Name on top gets the gris. That's pretty nice. Second name with the Lakers, so on and so forth. Remember we just randomized your names, not the teams. But as always, the break first. Big thanks to these folks here. Good luck. There are the teams right there. Let's roll it and randomize each list five and a four, nine times for each list. One, two, and a ninth and final time. After nine, we've got Wester down to, down to Ron Wester. Five and a four, nine times for the teams. One, two, eight, and ninth and final time. After nine, we've got the Denver Nuggets on top down to the San Antonio Spurs. All right, here's the first half of the list right here.  Some interesting possibilities I could pop out of a little, a little set low pack here, a little fat pack. Let's sort by column B by team. No trade windows for filler breaks. Unless that trade I guess happened really fast, I suppose I allow it. Let's print, let's rip and then we'll re-randomize that list. What time is that, is that an ESPN hoops game? Yeah, we've got NBA countdown and then heat Celtics tonight. So we're just wrapping up the sports center. So we still have a little ways to go. All right, there's Deandre Hunter, Ptadze, Nasred, Carson Edwards, Reddish, Terrence Davis, Kobe White, Nicianus, Jordan Poole and Kendrick Nunn at the end right there too. The honest goes to the Bucks of course, Chris Hoyt. Kobe White is I think a bronze parallel which is exclusive to these packs. That's for the Bulls, that'll be for Robert. And there's Kendrick Nunn right there too. Tyler Hero's been getting most of the minutes here between these two youngsters but he's got plenty of upside as well. Nice Kendrick Nunn for the Miami Heat, Aaron Clark. All right, let's flip back to this screen. Let's grab everyone's names from Scott down to Mark. Let's, oh, I don't have a new list set up. New dice, new list. There's the new dice, here's the new list. Let's put all your names here and then we'll match you up with some teams. Let's roll it, let's randomize it two and a four, six times for that list. One, two, three, four, five and sixth and final time. Name on top gets the Grizz and that's gonna be James Connell, Jimmy Connell with the Grizz. So congrats to the top seven right here. Jimmy with the Grizz, Matthew Shear, you got my Lakers and you have the Wizards. Ron with the Knicks, Jason with the Hawks, Sean Maddock with the Bucks, Richard with the Cavs and pick your team four. You can see the tab down there, teams and contenders optic pick your team four. Everyone else from number eight down to 30, we'll get them next time. I'm sure there'll be another small little filler for the next particular set of contenders optic breaks. So keep an eye out for that. Maybe try again if you want to. Jaspeasecasebreaks.com. I'm Joe, congrats again to the winners. We'll see you for the break soon. Bye bye.


What's up everyone on our rooftop. Hopefully it's not too windy. We just wanted to bring out the two pieces that we did live out in the sunlight. Let us know if it's too windy. I don't know it might be too windy up here and to let you guys know it's a very bad connection.  What's up abstract? Is it getting with this hair blowing that got the Beyoncé fan going? Beyoncé. It doesn't sound too windy. It's pretty windy up here. So we're going to I think we're gonna go well thanks Alexander. Buzzy. Buzzy Lizzie. So what time are we going to go live today? Well it's due six o'clock today. So we're going to do six o'clock. What is that? Central, Eastern? Central or six central? Six p.m. Central. Middle of the United States time. Yeah it's eScience. So we wanted to show you guys these pours that we did in the sunlight. Because sunlight is the best light to do any... Sunlight is the best light to take of your work. Look at that silver. Watch that piece baby. It's windy up here. Hello Anthony. We're not doing a pour right now. We're just letting y'all know that tonight at six for sure our time. Video quality is not perfect. Well we're on the roof. I'll try not to mess around with it too much. Also we'll post these again in our video at six p.m. Central standard time today where we're going to do some live artwork again. So we'll have a better internet signal then and we'll show you guys these paintings again then. But we just wanted to show you what they look like so let's go live update on. And basically we've seen it. I'll also show these again later because you probably can't see it that well or hear that well. Well they said it's fine. Also this is one we did yesterday. This is one of the yeah with the leftover resin from this piece. This is what the bottoms look like before. Before after. Like night and day. And then we had some some of these guys. My friend Cory griped to me for a couple days because there's only three these guys on here. He likes to think he's OCD. I said you are more ACDC. I wish we had these for the festival. Anyways we just want the easiest way to sand the back. Just get like a like a 60 grit with an orbital sander. I'll link the sander we use. Yeah we'll link the sander we use. Just a 60 grit sander or sand paper. And uh just go to town. Kujo you say hi. Can you say hi? He needs his sunglasses. No. I want to show you guys their lovely beads. We just use 60 grit sandpaper um or 80 grit is fine. You don't really want to go too much lower because you might damage the back of them. I don't think we did a tutorial on how. Hey Paula. Christina. Kujo baby. Can't wait to get to Dallas to meet you guys. Oh also. Hey Brenda let us know. A painting from us. There's shipping out tomorrow. Yeah just buy it. It's totally worth it. That's what we got. Just uh uh the green. The green. Raobi. Raobi or something. I don't know. They work fine. You don't have to spend a lot of money on those things unless you're constantly constantly using them. So what's up Dee? We should take this party inside. I guess is it a uh is it really crappy stream? Sorry Jody. We could say we're on our rooftop. So our live stream this afternoon. We'll be better. 6 p.m. Central. We're gonna do some more artwork for y'all. Yeah we're thinking about doing a uh a lip print like a disco video is much better when the camera doesn't move. Yeah I'm trying. I'm I want to get one of those the little rig things.  Yeah if there's a uh there's not too many festivals here and if they are they won't wait too much for a booth or they're just out of things to abstract Petra from the Netherlands. All right so here's uh if you guys just joined us these are the pieces that we did yesterday and the day before. I'll try not to move the camera around. Sorry about the wind. I think we'll never do a live feed from the rooftop ever again. We just won't do it on such a windy day. Yeah these are the sunlight really makes it amazing and yes they are for sale. This piece is 125. This piece down here is 100. Oh just catch us tonight 6 p.m. Central Standard Time. Central Standard Time US. And let us know uh if you guys want to see us do any other stuff we're thinking about doing a uh a lip piece tonight as well so I know you guys like the core. We're gonna have a whole art day just put our camera up and just let it let it go live all all night. It would take a month to see you guys later. Wrap it up live from the Dallas. Look at that and if you guys didn't know inside of that is a restaurant right there and it spins. I don't want to walk with this. We're done.


How do I, is it just page down for this, just making sure I know how to, okay, how to make it go back. Hi, good afternoon, I'm Cheri Kizan and I'm presenting this paper on behalf of myself and my co-author, Fe Magpayo Bagajo, who could not join us, she is a retired biologist in the Ateneo de Davao and I see with the red in the bios, right, that she's actually currently right now the, back at the biological collections, right, taking care of the biological collections, which is kind of like FES baby, right. And so this paper is really a small part of a larger study and I'm, we're focusing this particular one just on the plant identifications because we feel that that's important. So let me begin. So indigenous peoples in Mindanao are often visualized as men and women dressed in denotative ceremonial attire, clothes that signal belonging to specific locales or territories, or membership in a particular ethnolinguistic group, similar to Benedict Anderson's observation on the generative power of certain images as a kind of logo, quote, unquote, for a newish nation. Mindanao itself is sometimes signified by colonial era photographs of its autochthonous inhabitants, a pattern that we observe, right, with this digital material, such as the one used in this particular conference. Now I couldn't resist doing this, so I'm doing this. So clearly this image shows us a Bogobo family, in fact on the lower left there is a caption that says Bogobo's dash family Davao PI, which leads me to believe that this was probably as one of those souvenir postcards that people would purchase, right, and send on, and it's most likely to be, right, definitely early American period. And so I thought that for this kind of narrative, when we actually see it as some kind of, you know, emblematic of the indigenous peoples of Mindanao, I couldn't resist. So I said, well, let's look for other, my work being the Bogobo Tagabawan and Jangan family images. So I got this on Facebook, right? And this one is a picture of a young girl in Jangan Bogobo dress. The Facebook is the Bogoboklata public Facebook, and they just called it at Kalina, Davao City, which also tells me this is a Jangan girl. So certainly photos of themselves dressed in traditional clothing, it's certainly significant and important and has some kind of, you know, memorializing content. But I also couldn't resist including this, which was sent to me by Viber, of essentially my god son, Dato, and his sister, Kaikai, in contemporary dress taken just within the month of June, to kind of give us a sense of, you know, how these photos actually have many possible purposes, right? But my task today is actually not going to be talking about that particular kind of work, but another aspect of this work. So indigenous textile practices in Mindanao are certainly synchronously distinguishable from each other by resultant cloth and clothing styles. It allows us to accurately characterize individuals in a historical photograph, such as we saw before. The concept of group specific style or attributes organized more than a century of photographic and museum collections and publications, which include some of my work, for instance, on Mindanao cloth and dress, both in colonial and post-colonial contexts. So there's lots of work on this, right, from Colin Benedict in the American 20th century, as well as Reyes, Roses, afterwards, there's a lot of work that thinks about Mindanao in terms of this notion of group style. So it's not necessarily an empty referent. However, the concept of group style is limitations when dealing with phenomena that transcend social boundaries, interdisciplinary, historical, and cultural studies, examining translocal long view social processes in Mindanao, not bound to group specific material practices, provide some insight, whether through the framing of zones of plural interaction in indigenous agency. This is kind of like what Hayase is doing with this notion of East maritime, Southeast Asia, or Edgerton in northern Luzon or Paredes among the Higaonon, or theorizing episodes of stochastic political and economic engagements, such as what Abinales does as well as too. So in this paper, we focus on what we call indigenous textile practices, which we define as... I'm sorry, I should talk a little bit more about this before I leave this on. So just to give you a real kind of quick primer on Mindanao textile styles. On the extreme left, you have here in the Apa, and at the bottom two are two examples from her own private collections. She's a Jangan Bogobo herself, but her husband is Tagabao Bogobo, and I met her in the Tagabao Bogobo territory, so she would identify as Tagabao Bogobo until I asked her and then I find out she's Jangan too. So these are two pieces in her collection. So the center piece is what the Bogobo would call Dakinayan or Dakinaino, which would be a three panel skirt, which is a high status skirt. And then on the middle, you will see the Mandaya, one panel, Dagmai Klaw. So in the Bogobo, you would have them sewn in separate pieces, the center panel being the mother panel, and the reds are what they call the Bata, right, the child panel, whereas the Mandaya would make this in one entire single panel of cloth. They don't kind of sew them pieces together, where you would have the crocodile motif in the Bogobo one separate, and the Mandaya one incorporated in this larger panel. So they're both crocodiles, but you can see that stylistically they're quite different, right? Because the Mandaya call their cloth, the Ibaka cloth, Dagmai, the Bogobo do not. And then on the far end would be an example of Tiboli textile, where, and this is a very special one because it shows Langdulae, those of you might know who Langdulae was, the late Langdulae, it shows her interpreting a signature. So he actually signed her work, right? But I'm showing it to you here because it's an instance of the Tiboli tricolor style, so that Tiboli can actually do Ikat, you know, doing three colors in one particular row. But that's not the focus of this, but just to show you that it's certainly not an empty reference to talk about groups, there is such a thing that we could talk about this group style. But we're thinking here of something that kind of underpins the notion of even creating something in terms of style. So in this paper we focus on what we call indigenous textile practices, right? Which we define here, pattern material processes and social arrangements organized around the production of cloth and dress. So these processes tend to produce culturally distinct clothing assemblages, which we can describe as group style, that can express or delineate identities of historically marginalized people, but they're not constituted by it. We more narrowly focus on plant know-how in this particular paper as part of material processes and observe through social arrangements that make their utilization as well as collection and documentation possible. In the title of our paper we even call it rather grandly botanical knowledge, right? Therefore we think of it as it consists not only of information or unusable or desirable plants, but also the practices such as labor sharing arrangements that make such knowledge actionable, right? So that's what we mean by knowledge. That's knowledge that's actually actionable. So we're interested in textile specific plant knowledge that may be generalized regionally across culture groups, while also maintaining awareness of distinct ways that local communities organize make use of and transmit such knowledge. We broadly draw on anthropological and historical ideas that consider macro surveys of material culture at the regional level, such as for example what Brodel is doing right for the Mediterranean or Brodel wants to do right as far as that kind of history from below. Cultural history is both of resource used by normatively invisible peripheral populations such as that Eric Wolf does, right? For what he calls peoples without history and the specific challenges and opportunities in interdisciplinary method and theory in the interpretation of material evidence from archeological and ethnobotanical fields such as the work of Ian Hodder writing archeology, Yaro Ludwig in ethnobotany and so on. So the methodology that informs what I'm presenting actually occurred in kind of three phases, right? So the first phase, when I started this work in 1993, it was really interesting because everyone would tell me that there's no more weaving and therefore I'm going to end up with an empty set. I said okay fine, if that's my finding, that's my finding, but I have to start somewhere. So it was a survey in sampling 1994 and at that point in time I had to kind of decide on how to limit or how to systematically define what I'm looking at. So I said well let me look at what kind of a production is still happening out there in the historically known communities that do, I'm interested in abaqa and ikat, so abaqa the banana fiber and ikat the technique. So in 1994, there was a survey of bagobo, tagabawa, and jangan, those are two subgroups of the bagobo today. There's a third one, Ubo, which I was not able to study. The Mandaya, the Tagawalo, Tiktoboli sites, I didn't include here, but I also was able to visit some Zimbabwe sites, which I mentioned in the previous panel, only in the Malungon in Matanau area. And the second phase was mixed methods, right? In this case I decided that I was going to work only with a multi-site between two, Tagabawa and Jangan, for gopo sites in 1987. And finally community-based shadowing, photography and specimen collection. So the first two phases have actually already been published. And so I'm just going to summarize our findings from there. It's the last that we're, that I'm presenting, Fair Naya presenting in this case. By the way, Fair has basically helped me with all my plant IDs from the get-go. She was introduced to me by a friend, a mutual friend, and her generosity has sustained me quite over the years. But let me summarize the earlier phases that have been published, right? So the first thing, by the end of the first two phases, we know that there is a broad distribution across regions of what I call an indigenous semantic category, right? Of prestige of cloth. So in other words, across the region, and I'll show you a map in a little bit, right? There is an understanding that there is a separate category. It's an indigenous semantic category, right? Of a prestige category of cloth. Because the peoples of Mindana are major textile consumers from for centuries, right? So they've always been consumers of textiles as well as producers. So this is very specific categories, so that's the first. And the second is that's a narrower distribution of people who actually still own them or use them, right? And an even narrower distribution of people who actually still make them, right? So that's the second. And the third one, it's established by phase one and phase two, is that there is a shared plant repertoire, right? And so I've known this, it was in my dissertation and all that, but we've not really set out to actually establish this, but in this specific way, which I feel is important, and that's too. So here's kind of like, it's not a very pretty map. It's a kind of like homemade map with PowerPoint, right? So bear with me. But essentially it's a schematic map that shows to you. So all of the areas named here, right? Going, I'm going left to right from the Zambuaga Misamis region, Western Mindanao, where you have the Sabanan, right? Then going counterclockwise, Kalinan, Talomo area, Sibulan area, Bansalan area, Lake Sibu area. Coastal Southwestern Mindanao, Western Gauch, Malungan, Matanao, Karaga-Lamiawan, and finally Agusan region, East Central Mindanao. These represent what we would correspond to the first phase, right? This areas, which there is this indigenous semantic category, right, of ceremonial cloth, but it exists. So you might go to those phases and they might not have the cloth anymore, but if you show them pictures, they will say, yes, we know that, and that's for this purpose, right? So that's very, very important. So this first phase is like really a semantic thing. It's not necessarily a physical thing. So I call all of these regions of heritage use, right? So there's this category in people's heads, right? This understanding of the importance of the cloth. And then the red bits are the places that I actually visited, right, in the first phase of research, in the attempts to kind of determine, right, where there is still some production going on. So the Karaga-Lamiawan area would be the Mandaya. The Mandaya, of course, are in all over, but this is the place where I went. Malungan, Matanao, of course, there, Dlaan are more widespread, but that's where I went. So this is really basically snowball sampling. So I would go where people were willing to have me, right? That's kind of like how it worked out. So this is kind of like a schematic map of this prestige category, right? Which people understand a baka-ikat to be important, indigenously, right? So not for collectors or the collectors like them too, right, but indigenously speaking. So for weddings, they have to be important, right? So for certain occasions, they have a certain significance. So the yellow bits are the areas of what I call, you know, active production, right? So the Mandaya areas and the Karaga-Lamiawan area, whose work ends up right in Davao City, in mostly at the Lake Sibu area, of course, whose work ends up not only in the Gen San City, but also in Davao area. Those are the areas of like the most active weaving, and much of it goes, it's indicated also in the tourist industry, right? So that's kind of what's going on there. So we're looking at plant use in this prestige category of textiles, right? So when you go to these areas in Mindanao, people who belong to indigenous cultural communities, they tend to not look indigenous in our minds, right? So you go there and individuals of self-identify as belonging to one of the many attractiveness groups in Mindanao can appear to be fully assimilated. So they would look like they're fully assimilated into settler populations. However, field research since the 1990s determined that this special semantic category, right? This is very, very important to persist. This category is sometimes referred to by this one of Visayan term, karaan, right? Which means ancient antique or archaic. Or by the neologism among the Tagabawa Bogobo, costume, you know, costume, but they say costume, right? I used to think of costume as just costume in English, but it's not, it's a completely different term. It's a term they use for outsiders to talk about their cloth. But when you're over to Tagabawa, they talk to you in, right? They call them Umpat Bogobo. So it's very, very different, right? So it includes, so this category of karaan stuff or costume, right, includes tailored garments, jackets, shirts, head, shoulder cloths, as well as cloth not intended to be worn. So these are actually two types, right? Cloth to be worn and cloth that is not to be worn. So cloth not to be worn are usually hung on the walls. They're usually what we call the bride wealth cloth, but not for all groups. It really depends on the particular group. So ikad pattern pieces made of abaca, was a textileist, sit at the very top of this classificatory hierarchy. Some groups use these only for dress, and some of these uses only for today anyway, in the since the 90s, right? For not for dress. So the patterns are specific to each group, each locality. Consequently, the cloth known by many groups, specific names, for example, Tinanlaki Niboli, Dagmayan Mandaya, and are distinct from special garments they are made with, for example, bride wealth grade women's skirts, or Tabimlato, right, and blaan, or Sinodgnayan, or Sinodksabadgato, Sintagabawa, right? They kind of confuse us, right? Because they're all these different names, but they actually refer to different categories of textile, some dress and some not. But for sure they all share this kind of like, abaca, ikad kind of matrix. The characteristic red and black ikad motifs are derived from endemic dye plants, red from orinda citrifolia, and black from the ospirus netida, which we'll discuss below. So the cultural value assigned to ikad pattern, abaca cloth, is affected not only by the scarcity of finely made vintage pieces, but also the degree of difficulty and expense in commissioning a new one. So in our study of plant use, we're focusing right on plants used to make abaca ikad. So how do I define active weaving communities? So the shortest way to say this, that when you get there, we basically do snowball sampling and interview different people, right? So we distinguish heritage ownership, right? We already know that. So families that actually own pieces because it was passed down to them, or it was acquired through past Bridewell exchanges, right? Heritage ownership tends to also be mapped to economic ability. So well-lawed families tend to hold on to their pieces. Economically challenged families tend to lose them. Even if they don't want to, there's always gonna be a story of some no good nephew that stole it from their grandma and sold it to the shopkeeper, right? Without their permission. So you always have those types of stories, right? So that's part of it, but that's their people who own them and use them, right? Active weaving communities also include owner users, but they're more now distributed, right? And so by active, I mean like if we went there, is there evidence of weaving concurrently? And the ones who do we were knowledgeable weavers have their recollections or participating in the making of any cloth in the last 10 years, right? That's kind of like the general way we would do it. So ethnobotanical research is conducted around the same time by a fair, right? Around the Lake Sibu area, she was working with the Ubo, right? Who live in areas surrounding the Tiboli. She also learned from them that the Ubo supply dye plants to the Tiboli. Specifically, canalum leaves, right? Because you need copious amounts of it as well as morinda. So the botanical domain knowledge cannot be fully studied and understood without the collaboration of weavers and dyers. Such knowledge is clearly not limited to craft practitioners, right? And maybe fruitfully investigated in broader populations who directly engage with culturally relevant textile practices. So they might not weave themselves, but the Ubo supply, right? And the Ubo value, the cloth, right? So we have to kind of clarify these things when we speak of weaving and who weaves and who doesn't weave and who owns and who values, right? Those are very important things. And the first and second phases of research also established that the shared fiber in that plant repertoire, among the extant weaving, oh, sorry, this one shows you the Cibulan area where the initial collection of actual dye plants were done. And then I had a photo album and I used that to go to various areas in the Bonsalon areas where we actually did this specimen collection, right? So it's a table that's been previously published, except the new bit now is that it's diospiros netida, which was not known before and we'll talk a little bit more about that. So, but in this particular table, we summarize, we summarize, right? The terms, right? The first column is the terms for the Bagobo Tagabao, because that's the principle group I work with. So for the dye plant, it's Cicari, but if you go across, you'll see that the Bagobo Jangan have their own term for it, Calig, the Blaan, called it Lagu, the Tibole Loco, and so on and so forth, right? So it's important to understand that each group will have their own names for these plants. So the first phase of research, right? It took place in Bitaug, produced, maybe I can skip ahead to the next slide. Okay, yeah, so this is the dye plants that were basically brought to us and we photographed them, right? This was initially in Sibulan, right? So you would have Abacah, I'm using the Tagobo Tagabao terms here, right? Boho, Cicari, for the Morenda here, Kinarem, which stores of black, and then the lumber for the tree, which is Pola, right? And the lumber is Bahi, which is also a Visayan word, but it's also the term they use for the lumber, right? So those would be the sources for those. So these identify these forests, like the major plants, you would say, for Abacah-Ikat production. So the collection of plant materials in each visit was, so basically what happened was, because I only have five minutes, right? Basically what happened was once, we used this album of photographs, right? When I went to the Mandaya, went to the Blaan, and I went to the Poli, right? To basically determine, right, so what's this? And then they would immediately identify, right? That's Kinarem, that's Cicari, right? So it was non-controversial, these four major plants. And so there was no additional botanical, whatever work done in those areas, except in instances when they would identify a plant that wasn't here. And so I have, for instance, if anybody in the audience is right, would be interested, I have a whole bunch of plants that we don't have such specific IDs for the Mandaya, for example, as well as other groups, right? But these are the four that are consistent across all of them. And so once we knew of this in 1997, we conducted, I guess, looking back, we didn't think of it that way, of course, but it turns out that that's essentially what happened, right? Salinta Monon, many of you know her as one of the Gaudman and Likha Nambayan from the Bogobo. I was actually the one that nominated Salinta for this, why she's late. Salinta Monon died in 2009. She was my principal informant. Salinta agreed to be shadowed. And so we commissioned her to make some cloth following Tagabawa Bogobo's instances of commissioning a new cloth being made. But the new bit was to ask her if we could also document her in the process of dyeing a cloth and therefore learn about the plants. So that process, I was assisted in this process, of course, in the second phase, right? By Doris El Nakano, who's a Tagabawa Bogobo from Davao City, Miguelito Bancas, Jangan Bogobo also from Davao City, who eventually ended up getting married afterwards. And so the two kids at the beginning, those are their kids and this is my grandson and my godson and they call him Datu. And so they were the ones that basically did this, but it was Salinta who determined when they would come and she was assisted by affiliated households, the household of her sister. Indo, her brother, Uktog, who's a blacksmith and one of her married sons, Saiko, up in Bitaoog. And so it was her that basically said, okay, now you come and then they came, right? So the whole process was essentially determined by her. And the specimens were collected based on FES input. She told Doris El what was needed and it was brought over to Ateneo, the Davao for photography, Exito photography by Fe, and then for depositing. So what are the results? I gave a copy of this paper to Prisina as well, right? So basically, no new information, but we do determine, right? It's basically Musa Textilis, right, for the Abaka. Again, the first name you see there would be Tagabawa, but the alternate names would be Woho for, right? Janganbogo, Bulutai for Blahan, right? Abaka or Lannar for Mandaya, et cetera, et cetera. Arekasiye, right? Which is the Pola, Cariota-Romfiana for Lumbar, right? And that's also a cross group, especially for the beater, right? The sword, the weavers call it the sword, the great big sword in the loom that's always across the board. It's always made of lumber from the Cariota Palm. We're in the Citrifolia, which is kind of well-known all over Southeast Asia as a source of red. Theospirus netida, again, this is the important one, that it's netida, right? Not all the other, not Pociflora, it's netida because of the small fruit. And again, Nalum for the Janganbogo, Kinalum for the Blahan, Kinalum for the Tiboli, Kinalum for the Mandaya, right? Kinarum for the Obo, right? So we have all these specific local names. And then we have some minor plants. So the colorants, these are field photos, not from Bitaug, but from earlier phases, right? Kalaug, which is well-known to everyone. Kunil, Kunib, right? It's this yellow ginger, right? And then of course, Tagalog is called this Achuete, right, the Luga, right? The Luga, which is the source of, these are the minor colorants, right? But more minor plants, which is very important would be the mordant, right? So morenda citrifolia is a red source and for the color to stick to the cloth, you need to add other plants that would actually make it stick to the cloth. And so all over Southeast Asia, morenda is used, but what's unique is that morenda in Mindanao is only used on Abaka, right? So morenda on Abaka is completely different from morenda on cotton. So these are the mordant plants. Asange, balia, libago, right, that were used, added to the dye bath because morenda dyeing takes quite a long time, like a couple of weeks of dyeing and red dyeing, right? However, what's interesting is that the way you get black is very easy with the osperos netida. When you compare it to Southeast Asia, the way they achieve black on cotton is usually through indigo. And indigo requires mordants as well. But for some reason, the osperos netida does not require mordant, so black's easy to get, right?  And I make the argument in another paper I'm working on, right, about the aesthetic impact of getting black easily and how difficult it is to get red. Another minor plant, I like it. This is a bottom right, this packaging plant. It's a big leaf, alokasia, they're common, right, used for wrapping the root. And in the middle is a bunch of plants used for what's called the ritual bundle, right after the dyeing, they actually hit the dye threads with it in order to make sure that the color doesn't go away. The bottom is my favorite, it's called the ole-ole, because they say you hope that ole-ole is to actually not forget. You hope that the fiber doesn't forget the color you put in it, which would be red. So bunch of generalizable statements we can make about translocal shared plant knowledge and local aesthetic expression, right? So we know that there's a shared plant botanical inventory, right? Across abaca-icot-producing groups in Mindanao. I haven't done any fieldwork among the Subanan. I would love to have people do that, and if people have, I would love to know more about what they have. There's some publications about them, but there's no plant information on that. This was done through multi-phase collaboration with indigenous specialists. I've been having a conversation with Una, and this was before FPIC, so before the whole informed consent process. So this was like an old-fashioned way of doing it. But it was through essentially the notion that you as a researcher are there as a guest, right? So it's really about this notion of guesthood, right? Material processes and social arrangements. So when we think of them, we have to think of not just as things, but also the social arrangements, right? That make these things meaningful. Generalizable practices also vary when you get to the local level. And finally, that there is, I would say, a textile grammar that ultimately shapes specific meanings, valuations, uses and distributions of ceremonial cloth, which is really quite specific to Mindanao. And that's the end of my presentation. Any questions while... Yes, please, yeah. Basile, well, Basile is quite well known. It's the Yaqan. I think you're thinking of the Yaqan, right? The Sulu and Magindanao have a, it's like a much different kind of dynamic, right? But Basile, I don't think that they've stopped. I think it's still going on, but perhaps you're not as aware of it. But it would be cotton. They would be using cotton, and it's an important silk if they have it, right? Yes, it would be cotton. There would be some home-spun cotton. What's interesting is that Magindanao, for example, I now know of Abaka. But they say, and also go south of this, they look up on Abaka as a low fiber. It's like, it's a low, status one. So it's used for, right, poor people, right? Although I do know that Magindanao has been mentioned in some of these shipping lists as an export item, right? But yeah, when you talk about Abaka, right? Then they're aware of it, but it's not seen the same way, right? Whereas for these communities, it's actually, they write poetry, right? They sing songs to welcome the cloth, if it's seen in that very special way. But for the people, as far as what I've been so grateful for, from Sulu and Magindanao, Abaka cloth is nothing compared to, especially to silk, right? Silk is the, and the Indian trade cloth that they have to wear. Therefore. We'll have a few more questions after, but let's have Carlito.


In this module, I'll talk about the server side programming.  That helps a lot. It results into a thin client and it does not require installation at all the clients. It's easy to maintain and there are many many benefits. Now the standard that the de facto standard for interfacing the web application with the database is CGI common gateway interface. Remember one thing CGI is not a library, it is not a programming paradigm. It is a protocol. It is a protocol and whenever there is a CGI call, a process is spawned, generated. But remember that the server which spawns the process, these processes are not remembered by the server. They cannot be shared by the server. They are closed also, they're terminated also. And by default CGI does not offers distributed processing. But CGI has been around for a while and it has been used and it is in use also. And of course it was followed by fast CGI. Let me go into more details. So this is what I'll be covering in this module, what is CGI, how to execute CGI, step by step, step by step, not in a lot of details, but you will get the idea and the CGI header, which tells that for a certain step, it is an image, it is text, it is HTML, it is code, whatever. The advantages and disadvantages of having CGI and finally the fast or extended CGI. So let's go into more details. So as I said earlier, CGI is not a library, it is a protocol. It means that it is language independent, okay, is a protocol and a library. You can write CGI script in C, you can write CGI script in C++, you can write CGI script in Java also and so on. So it is language independent and CGI enables web servers to launch external programs. What happens is that when I click on a link, traditionally the corresponding server opens a file for me, if it's a text file, but for a CGI environment, when I click on a link and at the other end, I have CGI script, then the server launches that CGI script. And if it computes something, it returns that result as a computed contents of a file to the end user. This is how it works and enables database access from the browser. This is a much better approach than the client side approaches which were covered in the last module. So it helps me get the data from the database from using the CGI script. Remember it is language independent. So how did it works? You invoke the CGI program by a click by loading a page and then you must have the permission to launch the CGI program. The permission is set, then check for authorization if it's needed and prepare the environment variables. And then it outputs and terminates and there is no remembrance, there is no record, there is no memory. The server sends the data and closes the connection. This is a disadvantage that whenever I make a request, I open a connection, I get the data, the connection is closed. I make another request, again make a request, process is spawned, open a connection, get the data and the connection is closed. This is very inefficient way of doing something which is done repeatedly. Of course it will not result in a high performance solution but it offers a solution. And of course whatever is returned the browser displays it on the screen. It could be the contents of a database, it could be the result of certain computation and so on which is done at the server end. Then of course this is the CJ header I was talking about. So it can help if it is HTML, plain text, it could be a GIF, compressed image, it could be a movie, it could be audio and so on. So all those things are included in the header. It is a comprehensive header and that contains all the information which is required for the CGI script to run which I showed you in the last slide. So what are the advantages and disadvantages of having CGI? There are many of such advantages. One, the biggest is the simplicity. It is very simple, it is simple, it is efficient, it is effective and it is not only language independent, it is server independence also. Independent of the server, independent of the language is a protocol, how you do certain things. Okay, and that is built into the browser can support it and it is widely accepted. These are the biggest advantages of CGI scripting. Disadvantages is the server in the middle because everything has to go through the server. Okay, go through the server and that creates a bottleneck. There is a lot of traffic, right? Or if there is a scenario like Yahoo where hundreds and thousands of processes are spawned, there is a lot of congestion that will hurt the performance. And lack the transaction support. Remember, it is stateless, stateless. Server generates new thread for each CGI program which I already mentioned, there could be 100,000 or such of them. There's no built-in security. It's not very secure. These are some of the disadvantages of CGI scripting. So how or what is done to take care of these issues, which is extended or fast CGI. What is there in the extended or fast CGI? It is language independent as before. It is open standard as before as before independent as before, but it is distributed computing. It means that the CGI script can be made to run and retrieve data from not a single database server from different database servers, combine the results and give you higher performance solution, better performance. Remember, high performance is not in the context of high performance computer architecture, but better performance, quick results. Allocating the processes, the programmer can set the processes which will be allocated to the CGI script instead of having a single process spawned for each request. It means it will give better performance instead of doing something repeatedly. So this is all I have for this module. Thank you very much.