#Sketch-Making Flask App

[basement-bird]

Alright, I have been convinced but please please pleeeeeeeeeeease remember this has been abandoned and unpolished and my first attempt at writing. Lmk if i should pick it up again ig! Also you guys can thank @cowsuponcows for accidentally reminding me i even had this in my notes app.

1.5k words

@caillousweave you wanted me to tag you 💜

Beep beep beep. Beep beep beep. The lights on the Engineers alarm clock chimed and flashed 07:00 with its annoying red light. He sat up in the cot he had set up in his workstation and stretched, his vertebra popping as he straightened up.

Engineer hopped out of bed and started getting ready for his day. It was an off day, so there was no need for him to wear his combat uniform. He threw on a blue sweatshirt and work jeans and started heading to the mess hall to grab breakfast. As he strolled through the base, he looked over a notepad of his projects and muttering about supply runs needed. “Can’t you ever take break?” A deep voice bellowed as Engi walked into the room. Heavy sat at one of the tables, Medic sitting across from him. Heavy stared at Engi and chortled at his own comment. Engi looked up and chuckled, “Naw, no can do, big man. There’s too much to get done.” He retorted and set his stuff down next to Medic, freeing his hands to get some grub. “You ought to take some time to decompress, you know-“ The Medic commented, sipping on a cup of black coffee, “-Your smarter zhan to vork yourself to death.” He glanced up at his book towards the Texan man. “ Yeah yeah, I know” Engi rolled his eyes and plopped down on the uncomfortable plastic chair.

The general peace of the hall was suddenly met with the sound of a loud holler from the world’s drunkest man. Medic winced at the sound and glanced up from his book once more, shooting a glance towards his friends as Demoman came crashing into the hall. “GOOD MORNING LADS!” He shouted, smiling as he hobbled his way over to his friend Sniper. Sniper had already set out a mug of joe for Demo, so all the Scot had to do was take out his flask and pour in the alcohol.

Engi met Medic’s glance and gave a little shrug. “Could always take this to my workshop.” He suggested. Medic took the last bite of his toast and nodded, “Heavy?” He asked, but the Russian man was barely done with his mountain of food. “Go on without me; I will catch up.” He urged and continued his breakfast. Medic and Engi stood up and started walking towards the workshop, Engi digging his nose back into his plans and Medic sipping his coffee, making sure his friend didn't bump into anything while distracted. They made it to the workshop, and Engi threw himself to his work desk, “Make yourself cozy, pardner.” Medic walked over, kicked off his boots and situated himself onto the cot and continued reading, setting his coffee on the side table.Engineer pulled out blueprint papers from a cabinet under his desk and sprawled them onto the desk, grabbing his sketch pencils from a tin. His eyes couldn’t help but trail over to his friend sitting on the cot as he worked on his sketches. He’d force himself to focus, but for some reason he’d end up looking back. He took my suggestion a lil too seriously, didn’t he? He thought, then his eyes started scanning the cover of his book. Medic looked up from his book and Engineer pulled his eyes back to the paper. Medic cleared his throat and looked around the worn down workshop, eyes landing on a radio sotting on a shelf “Mind if i turn zhat on?” He asked. The Engineer looked up “Oh, uh.. go ahead.” He nodded “Don’t know what’s playin, but I’m sure somethin good must be on.” He laid down his pencil and watched the tall man fiddle with the radio. The labels were worn with time, so it was quite hard to figure out what buttons did what, but once he did Medic situated it on a station for classical music. He hummed blissfully and made his way back towards where the two were hanging out in the workshop. Engineer smiled at the music choice and looked back to his can of pens. I guess anything is better than that silence, He thought to himself as he leaned over his desk to keep working. He felt a warm breath on his ear and snapped a look over his shoulder. Medic stood over him, scanning the blueprints quietly, “Oh did I startle you?” He asked when Engi snapped his head back “Startled? Nah, you just took the damn piss outta me.” He joked and snorted, “You’re much quieter than you appear Doc.” He added and stepped a little aside to avoid being stood over and to give him a better view. Medic pulled his pipe out of his vest as well as a tobacco pouch, filling the bowl while still examining the blueprints for further sentry upgrades “ I see… vell, it looks like you have your work cut out for you.” He commented, feeling around his pockets for a match. He frowned and pulled his eyes away when he couldn’t find one, stressfully searching his coat pockets next. Engineer shuffled through his jean pockets and pulled out a lighter, “Need a lil help?” He flipped it open and struck the spark wheel. He lit the crushed up leaves and watched as the German took a long drag from his wood carved pipe. Smoke bellowed from his nose and his nervous face relaxed “ Danke, freund.” He smiled. Engineer felt his face heat up as he watched him place one hand on the desk, the Medic’s body weight shifting to lean over the paperwork.A eternity passed in just a few seconds as their gaze met, the music now filling the quiet room. Engineers mind scrambled to think of anything to do, but he couldn’t pull his eyes away. Come on fuckin idiot, do something he thought; then as if a prayer had been answered, the two metal doors swung open, and Heavy burst in “I finished breakfast! Time for bookclub, Doktor.”

Medic blinked and broke the shared gaze to look at their Russian friend “ah, Sehr gut! I was just finishing up the last chapter.” He commented and lightly pushed off the desk to move towards Heavy. Bookclub was their Saturday thing to keep sanity, and thankfully they can get books in when supplies come in. Engineer quietly sighed in relief from the broken gaze and buried himself into his work “Y-you guys have fun with that… stay if you wish! But I’ll be doing work in the back” he pointed without facing the men and scurried off, face burning with… embarrassment? What am I embarrassed by? He questioned as he walked away.

The morning melted into the evening; Engineer had skipped lunch and dinner due to his work, and didn’t even notice how he was alone now. Classical music played out of the staticy radio as he stared at his new sentry. He was tweaking the problems, but new ones kept arising. The guns weren’t firing, but once they did, now the rockets weren’t launching. Once those worked, the new electric traps were just string and no spark. Engineer cussed and kicked his toolbox in frustration, lifting his goggles and pacing in a circle God damn these machines. He looked and watched as one of the legs buckled and the turrets fell to the ground, this angered him further and he threw off his helmet in frustration.“Hey, hey, vas ist the matter here?” A familiar voice rang as someone walked into the workshop, hearing the angry commotion. Engineer made his way to the front “ Doggum turret fell apart! Parts ain’t workin neither” He complained, turning a corner and seeing Medic at the door with a box of food “Is zhat so? Hmm…” His free hand lifted to set a knuckle on his chin to think, “I vas looking at it earlier; it could be too much veight on it? Ack, but take a break!” He discarded his thoughts and held up the box of food, “You veren’t zhere for lunch or dinner, I bet you haven’t left zhat spot all day.” He walked over to the desk and set the box down. Engineer walked over to him, the smell of steak and potatoes flowing out the box “Well… I reckon I can take a break for a moment.” He agreed and sat down, opening the box to look at the delicious steak. He picked up his utensils and started chowing down, the realization that he was actually very hungry set in after ignoring it first hours. Medic had pulled up a chair next to him and just looked around the dusty shop “ You know, you do need to do more zhan just vork, right?” Medic looked at him “ I love my craft as much as zhe next guy, but zhe brain cannot be vorked like zhis 24/7.” He added, concerned. Engineer shrugged “Sure, but I like it.- Plus I wouldn’t know what to do otherwise. Your lil’ bookclub with Heavy looks nice but I ain’t a fiction reader” He chuckled. Medic leaned back into his chair and shook his head “ Maybe you can join me for bird feeding? I do it Sunday mornings, so that I can be outside without a bomb heading directly towards my face.” He suggested

[himanshu123]

How to Build Web Apps? A Step-by-Step Guide 

In today’s digital-first world, web application development has become a vital skill for businesses, startups, and individual developers alike. Whether you’re building a web app for personal use, as a business tool, or to create a product for the public, knowing how to approach the development process is essential. From the initial planning phase to deployment, building a web app involves a series of steps that, when executed properly, result in an intuitive and functional online application. 

In this step-by-step guide, we’ll walk you through the process of creating your own web app, from understanding the basics of web app development to the final launch. If you're new to web development or looking to enhance your knowledge, this guide will provide a solid foundation. 

Step 1: Define the Purpose and Scope of Your Web App 

Before jumping into the development process, it’s crucial to define the purpose and scope of your web application. Ask yourself: What problem will this web app solve? Who is the target audience? Is the goal to provide a service, sell products, or offer a platform for users to engage with? The answers to these questions will shape the overall architecture of your app. 

Additionally, you should define the features your web app will include. Start with the core functionalities and consider future expansions. Sketch out your app’s user flow and design wireframes, as these early visuals will help communicate your app’s structure to developers and designers. 

Step 2: Choose the Right Tech Stack 

Choosing the right technology stack is one of the most critical decisions you'll make during web application development. The tech stack defines the tools, languages, and frameworks that will power your app. Here are some key components to consider: 

Frontend Development: This is the part of the app users will interact with. HTML, CSS, and JavaScript are essential for creating the user interface (UI). Frameworks like React, Angular, or Vue.js can be used to build dynamic and responsive web pages. 

Backend Development: This part handles the business logic, databases, and server-side functions. Popular backend technologies include Node.js, Ruby on Rails, Django, and Flask. 

Database: Choose a database that matches your app’s needs. Relational databases like MySQL or PostgreSQL are common for data-heavy applications, while NoSQL options like MongoDB are used for more flexible data structures. 

Hosting & Deployment: Platforms like AWS, Heroku, and DigitalOcean are popular for deploying web applications. 

Your tech stack decision will be influenced by factors such as the complexity of the app, expected traffic, and available resources. 

Step 3: Design the User Interface (UI) 

The user interface (UI) is the face of your web app. It should be intuitive, user-friendly, and responsive. When designing your UI, consider your target audience’s preferences and needs. Tools like Figma, Adobe XD, and Sketch are excellent for designing prototypes and wireframes. 

Focus on creating clean, minimalistic layouts that allow users to navigate easily. Make sure the app is mobile-friendly, as many users access web apps from their phones or tablets. Responsive design ensures that your app adapts to different screen sizes, improving the overall user experience. 

Step 4: Develop the Web Application 

Once your design is in place and your tech stack is chosen, it’s time to start coding. Divide the development process into manageable stages: 

Frontend Development: Using HTML, CSS, and JavaScript (along with any chosen frontend framework), you’ll implement the design and make the app interactive. This includes creating forms, buttons, and other UI elements. 

Backend Development: Write the server-side logic that powers your app. This could involve user authentication, payment processing, data handling, and more. You’ll also connect your app to the database and ensure secure data storage. 

APIs & Integrations: Many web apps need to interact with external services (such as payment gateways, social media platforms, or email services). This is where APIs (Application Programming Interfaces) come in. You’ll need to integrate third-party APIs for features like payments, user authentication, or notifications. 

Step 5: Test the Web App 

Testing is crucial in web app development to ensure your app functions as expected and is free from bugs. Perform different types of testing: 

Unit Testing: Testing individual components of your app for functionality. 

Integration Testing: Ensuring that the components work together as a whole. 

User Acceptance Testing (UAT): Testing the app from a user’s perspective to ensure it meets their needs. 

Automated testing tools like Jest, Mocha, and Selenium can help streamline this process. 

Step 6: Launch and Monitor Your Web App 

After rigorous testing, it’s time to deploy your web app to a live server. Choose a reliable hosting provider, and make sure your web app is scalable and secure. Once launched, monitor performance to ensure everything is running smoothly. 

Use analytics tools like Google Analytics, Hotjar, or Mixpanel to track user behavior, identify any potential issues, and gather data to improve future iterations of your app.    If you're interested in exploring the benefits of web application services for your business, we encourage you to book an appointment with our team of experts. 

Book an Appointment 

Step 7: Maintain and Update Your Web App 

Web app development doesn’t end after launch. Regular updates and maintenance are necessary to keep the app secure, functional, and aligned with user needs. Ensure that you’re fixing bugs, updating libraries, and adding new features based on user feedback. 

For businesses, understanding the mobile app cost calculator can be helpful when deciding whether to expand your web app into a mobile app. By estimating the cost of developing a mobile version of your web app, you can better allocate resources and plan your next steps. 

Web App Examples: What Can You Build? 

If you're still unsure about the kinds of web apps you can create, here are some web app examples that might inspire you: 

E-commerce Platforms: Build an online store with features like product catalogs, shopping carts, and payment processing. 

Social Media Apps: Create a platform where users can interact, share content, and engage with each other. 

Project Management Tools: Develop an app to help teams collaborate, track tasks, and manage deadlines. 

Content Management Systems (CMS): Build a platform that allows users to create, manage, and publish digital content. 

By starting small and gradually expanding your web app, you can create something truly unique and valuable for your users. 

Conclusion 

Building a web app is a multi-step process that requires careful planning, development, and ongoing maintenance. By following this guide, you can navigate the complexities of web application development and create a successful, user-friendly product. If you're looking to develop a robust, scalable web app, consider reaching out to experts who can help guide you through the process and ensure your project’s success. 

[completeconnection]

Essential Guide to Web Application Development in Simple Terms

In today's digital era, web applications have become a vital part of our daily lives. They power our favorite social networks, streamline online shopping, and even assist our productivity. Developing these web applications requires a blend of technical skills and creativity. This article will walk you through the essentials of web application development in a straightforward manner, suitable for anyone interested in learning about this fascinating field.

What is Web Application Development?

Web application development involves creating application programs that run on remote servers and are delivered to users over the internet through web browsers. Unlike traditional software that needs to be installed on a local device, web applications can be accessed online, making them versatile and easily updatable.

Key Components of Web Applications

Web applications are built using three primary components:

1. Front-End (Client-Side)

This is the visual part of the application that users interact with.

Technologies Used: HTML for structure, CSS for styling, and JavaScript for interactivity.

Frameworks and Libraries: Popular tools like React, Angular, and Vue.js help developers create dynamic interfaces.

2. Back-End (Server-Side)

This component handles the server, application logic, and database.

Languages and Frameworks: Common choices include Node.js, Python (with Django or Flask), Ruby on Rails, Java (Spring), and PHP (Laravel).

Database Management: Databases such as MySQL, PostgreSQL, and MongoDB play a crucial role in storing data.

3. API (Application Programming Interface)

APIs facilitate communication between different software components.

Types of APIs: RESTful APIs and GraphQL are widely used for developing robust and scalable APIs.

Steps to Develop a Web Application

Let's break down the web application development process into several key steps:

1. Gather Requirements

Stakeholder Interviews: Talk to those who have a stake in the project to understand its goals.

User Stories: Detail what users need and expect from the application.

Feasibility Analysis: Ensure the project can be completed within time and budget constraints.

2. Design Phase

Wireframes and Mockups: Create simple sketches or models of the application's layout.

Prototyping: Build interactive prototypes to test user interface (UI) and user experience (UX).

System Architecture: Plan how different parts of the application will interact.

3. Development Phase

Front-End Development: Use HTML, CSS, and JavaScript to build the user interface.

Back-End Development: Write code for the server, application logic, and database integration.

Integration: Ensure seamless communication between the front-end and back-end components.

4. Testing Phase

Unit Testing: Test individual pieces of code to ensure they work correctly.

Integration Testing: Check if different modules work together without issues.

System Testing: Test the entire application as a whole.

User Acceptance Testing (UAT): Let real users trial the application to identify any usability issues.

5. Deployment Phase

Hosting: Choose a reliable hosting service like AWS, Heroku, or Azure.

CI/CD Pipelines: Implement Continuous Integration/Continuous Deployment to streamline the release process.

Monitoring: Use tools to keep track of application performance and detect any issues promptly.

6. Maintenance and Updates

Performance Optimization: Regularly check and improve the application’s speed and efficiency.

Security Updates: Keep the application secure by applying the latest patches.

Feature Enhancements: Continuously add new features based on user feedback.

Emerging Trends in Web Application Development

To stay ahead in web development, it's essential to be aware of the latest trends:

Progressive Web Apps (PWAs): Combining the best of web and mobile apps, PWAs offer offline access and fast load times.

Serverless Architecture: This approach allows developers to focus on writing code without worrying about server management.

Artificial Intelligence (AI) and Machine Learning (ML): Integrating AI and ML can enhance user experiences with personalized content and advanced analytics.

Microservices: Breaking down applications into smaller, independent services makes them easier to manage and scale.

Conclusion

Web application development is an exciting and evolving field that requires a mix of technology write for us creativity and technical know-how. By understanding the components of web applications and following a structured development process

[foone]

Technical details: So the minecraft side is relatively simple. It's 30 ComputerCraft computers running identical code that simply monitors the back of the computer for a redstone signal. When it sees one, it makes an HTTP call to localhost:3000/<COMPUTER ID>.

(Computer IDs are simply the order in which I placed them down, and are effectively random.)

that local webserver is a small Flask application:

It manages shift key state (since the keys don't know about each other, the "A" key can't know if it should send "a" or "A") by toggling an internal shift value when the shift key is pressed. It translates the scankeys to ASCII values, and UDP's them to the microcontroller.

The microcontroller is a Raspberry Pi Pico W, running a simple arduino sketch that connects to the wifi and listens for UDP packets. When it gets one, it presses that key to the attached computer.

I ran minecraft on my main laptop (windows 10), and opened firefox to bluesky on my linux laptop, with the Pi-Cow plugged in via USB. It worked quite well, other than having to synchronize OBS across both computers to record this video.

this heavily minimalist keyboard can't type numbers or special characters other than space and !, but it can be trivially expanded: Simply place down another computer with a button on it in Minecraft, copy the code onto it (I did this using ComputerCraft floppy disks, because I'm Me), and then modify the Flask app to turn that new computer-id "scancode" into the proper ASCII value.

The minecraft modpack is ATM9:To The Sky with Alphabet Blocks by DragonSlayr15001 added:

https://modrinth.com/mod/alphabet-bloc

My latest Bad Keyboard: The MCKeyb!

I built a keyboard in modded Minecraft, then hooked it up through a webserver and a wireless microcontroller, so it appears as a USB keyboard on a different computer. I then used it to post "Hello World!" to bluesky, from minecraft.

[abhijeetomninos1122]

The Ultimate Guide to Developing an Instagram Clone App

Creating an Instagram clone app is a complex task that involves several steps, from designing the user interface to implementing features like photo sharing, commenting, and liking. In this ultimate guide, we'll walk you through the key steps to develop an Instagram clone app using Omnino Solutions.

Step 1: Define Your App's Goals and Features

Before you start development, you need a clear understanding of what your Instagram clone app will offer. Key features to consider include:

User Registration and Authentication: Allow users to create accounts and log in securely.

Profile Management: Users should be able to edit their profiles, including adding a profile picture and bio.

Photo Sharing: Enable users to upload and share photos and videos.

News Feed: Display a feed of posts from users the current user follows.

Likes and Comments: Users should be able to like and comment on posts.

Notifications: Implement real-time notifications for likes, comments, and follows.

Search Functionality: Users should be able to search for other users and posts.

Direct Messaging: Include a private messaging feature.

Step 2: Choose the Tech Stack

Select the technologies you'll use to develop your app. Common choices include:

Frontend: React Native, Flutter, or native development (iOS and Android).

Backend: Node.js, Python (Django or Flask), Ruby on Rails, or other frameworks.

Database: PostgreSQL, MySQL, or MongoDB for storing user data and posts.

Cloud Services: AWS, Google Cloud, or Azure for hosting and storage.

Step 3: Design the User Interface (UI)

Create wireframes and mockups to plan your app's design. Tools like Figma, Sketch, or Adobe XD can be helpful. Ensure a user-friendly and visually appealing design that mimics Instagram's interface.

Step 4: Backend Development

Set up your backend to handle user accounts, posts, likes, comments, and other features. Use a RESTful API or GraphQL for communication between the frontend and backend. Implement user authentication using JWT or OAuth.

Step 5: Frontend Development

Build the frontend of your app using the chosen technology stack. Develop screens for user registration, login, profile management, news feed, post creation, and user interactions like likes and comments.

Step 6: Implement Features

Integrate the core features one by one:

User Registration and Authentication: Implement user registration and login with secure password storage.

Profile Management: Allow users to edit their profiles, including adding a profile picture and bio.

Photo Sharing: Develop the feature to upload and share photos and videos.

News Feed: Create a feed that displays posts from following users.

Likes and Comments: Add functionality for users to like and comment on posts.

Notifications: Implement real-time notifications using WebSocket or push notifications.

Search Functionality: Enable users to search for other users and posts.

Direct Messaging: Build a private messaging system.

Step 7: Testing

Thoroughly test your app to identify and fix bugs. Conduct user testing to gather feedback and make necessary improvements.

Step 8: Deployment

Deploy your backend and frontend to a hosting platform and configure your domain. Ensure your app can handle traffic and scale as needed.

Step 9: Security

Implement security measures, such as data encryption, to protect user data and prevent unauthorized access.

Step 10: Maintenance and Updates

Regularly update your app with new features and bug fixes. Monitor user feedback and analytics to make data-driven improvements.

Step 11: Legal Considerations

Ensure your app complies with data privacy regulations and Instagram's API usage policies. Create a terms of service and privacy policy for your users.

Step 12: Marketing and Launch

Plan a marketing strategy to promote your app. Create social media accounts, build a website, and use app store optimization (ASO) techniques to increase visibility. Launch your app on app stores (Google Play Store and Apple App Store).

Remember that building a successful Instagram clone app takes time, dedication, and continuous improvement. Stay updated with the latest trends in social media and adapt your app accordingly. Good luck with your Instagram clone app Script development using Omninos Solutions!

[liamcreativetech]

Integrative Lost Blogs 3

Click here for main post

At this point I’m trying to get workable test data to get the computing side running, then when that is up and going, get the physical pointer movement working.

Processing Sketch

I have found a site to get reliable data for the sun’s position of the next two days from https://ssd.jpl.nasa.gov/horizons.cgi#results.

The type of ephemeris (Latin word for record of star’s apparent position) was OBSERVER, because the direction of the pointer will be relative to its own position.

After checking the other options, I found a “VECTOR TABLE” option, which not only comes in Cartesian for, it can take custom lat, long and alt. This would work well with a GPS module on the unit. For the tests I will use the rough coordinates of the WG building: -36.853359, 174.765944.

I found a stack overflow question asking exactly what I needed to know, and luckily there was an answer:

https://math.stackexchange.com/questions/15323/how-do-i-calculate-the-cartesian-coordinates-of-stars

I knew the basics of converting from polar to Cartesian, but the question was in the exact same context as my project, which was useful and reduced possible error from trying to remember year 13 calc.

04/08

I have set up one of the stepper motors so that it can move to an angle from a serial input, and I’m trying to automate the process. The numbers are sent to the Arduino over serial from a processing sketch, which in turn gets the altitude and azimuth of the sun from a flask server running locally. The server has the pySolar library imported which can calculate where the sun will appear given the observer’s coordinates, and the time in Julian format. For these tests, I have the long and lat hard coded into the server, corresponding to the studio, and the time retrieved with every request. From the compass app on my iPhone, the 11th floor is at 40m of elevation, but currently the pySolar system doesn’t take that into account. Later on, I will have to change the server to take long and lat as URL variables, and use the request’s exact position.

Output from a processing sketch displaying the parsed CSV data from the NASA website. The range of -90 to 90 degrees is mapped from the left to right sides of the canvas. The trail of dots near the center shows the sun’s movement, with text date labels at set intervals, connected to the corresponding sun position dot by the lines.

The current issue is the communication of angles from the laptop to the Arduino, there is some issue where characters are dropped, and if the pointer is at angle 200, and it receives a ‘20’ it will try and spin all the way back. This could be stopped by checking the difference between the current angle and the newly sent one, but this doesn’t solve the issue and makes it more difficult to test.

I will try changing the way that I receive serial characters, polling if serial is available every loop instead of the serial event function.

I tested another cable, but still the same issue. Because it’s only one in every couple of message that drops a character, I changed the processing sketch to send the same value 5 times, and the Arduino to take serial event readings in batches of 5 and then only use the largest value. I’m pretty sure this will work in every possible dropped character, and that any drop of character will result in a smaller number.

From early tests, it looks like it solved the issue! The new angles are sent in 5 second intervals, and so far the pointer is staying the same location. This is different from before when it would move towards to angle, then turn around and move towards an incorrect value.

At the moment the system is using groups of 5 messages, which is good and will cut out most of the dropped number issues, but it is possible (probably) that it could receive 5 ‘corrupted’ messages in a row. I could be certain it was getting the right angle by increasing the batch size to 50 or even 500, with marginal performance hit. Might change to pyEphem for elevation data to be taken into account.