@Dineatriz

Since the last devlog, I’ve focused on thoroughly finalizing the electrical logic before moving on to the visual interface.

Since then, I’ve completed the circuit validation. Now, in addition to detecting when a resistor is missing, the program also detects when the chosen resistor is too low and the current would exceed the LED’s limit (always with an explanation and suggested value, never just “error”):
“Current above LED limit
With this resistor (100 Ω), the current would be 70.0 mA, but this LED
can only handle up to 20 mA.
💡 Use a resistor of at least 350 Ω.”

I also started the “Learn” mode, creating a Lesson class that generates a statement (e.g., “9V and 1kΩ, what is the current?”), accepts the user’s answer, checks it with a tolerance margin, and always explains the formula used:
“You have a 9V source and a 1kΩ resistor. What will the current be?
Your answer in mA: 9
✅ You got it right!
I = V / R = 9 / 1000 = 9.0 mA”

This project, Learnware, is intended to be an electrical circuit simulator in Python, designed to teach electronics interactively to those who want to work more with hardware, focusing on explaining the why of things, not just showing results.
The ultimate goal is to have an area where you drag and drop components (batteries, LEDs, resistors, buttons, capacitors, motors, Arduino/ESP32, etc.), connect them with wires, and the program calculates everything in real time. There will also be a “Learn” mode with lessons, and later, connection to real hardware (ESP32/Arduino).

So far I’ve created classes for the components (Battery, Resistor, LED) using dataclasses, a SeriesCircuit that connects battery + resistor + LED and calculates voltage, current and power, and the part I found most interesting is that, instead of just giving an “error” when the circuit is poorly assembled (e.g., LED connected without a resistor), the program explains the problem and suggests the correct resistor to use, such as:
⚠️ Excessive current
This LED does not have a resistor to limit the current.

In a real circuit, this can damage the LED.

💡 Try adding a 350 Ω resistor.

And when the circuit is correct, it shows:
Voltage: 9 V
Current: 7.0 mA
LED Power: 0.01 W
Status: 🟢 Functional circuit

(In the initial development phases, everything will be written in Portuguese from Portugal, but I plan to add support for more languages ​​in future updates)

It’s been about 6 days since the last update as I haven’t had much free time to work on the project lately, but I managed to make some good progress today.
In this update, I introduced preview information for non-image files and specific plugins. Previously, the app only displayed a simple preview for images and fell back to showing just the filename for everything else. To make the interface much more informative, I added a new optional method, get_preview_info, to the base plugin contract. Any plugin automatically inherits a default behavior that calculates and formats the file’s size (in KB or MB) alongside its name. Individual plugins can easily override this method to display metadata unique to their format. For instance, the Image Plugin now pulls exact dimensions and displays them right alongside the file size (e.g., 1920x1080 • 2.4 MB). The main window updates dynamically based on the active plugin, instantly giving useful context as soon as a file is dropped into the app.
In the development of this update I found a pretty usefull website full of symbols and wanted to share it here: https://coolsymbol.com/

In this update I added support for STL and 3MF files, making the app even more useful for 3D printing. The new plugin currently includes two actions. The first one shows the model dimensions and volume, while the second estimates the print’s weight and material cost based on the material density, filament price and infill percentage. The results are saved into a text file so they can be easily viewed later. To support this, I also extended the parameter system by adding a new float parameter type. This means plugins are no longer limited to integers or predefined choices and can now request decimal values whenever needed. Adding support for two completely new file formats only required creating a new plugin, without changing the plugin manager or the overall application structure. I also think these features will be genuinely useful for anyone who regularly works with 3D printing models.
This update was very simple and I was able to do it pretty fast(I has already started working on it but forgot to mension in the last devlog)

In this update I added 2 more plugins, .zip and .pdf, I also added support for dropping multiple files at the same time. This allowed me to implement the first action that actually requires more than one file (merge PDF). Now, when you drop a single PDF, the app shows the actions that make sense for one file, like rotate and extract text but if you drop multiple pdfs together, those actions are replaced by merge, which combines all the selected pdfs into a single document while keeping the original order. To make this work, I had to change the plugin architecture so that plugins now receive a list of files instead of just one. This means that every plugin can decide which actions should be available depending on the context, without requiring any changes to the UI. I really like this update because it makes the project much more scalable.
The .zip plugin is pretty simple, it lets you extract a .zip file or convert it into .7z

It’s been a little while since my last update(2 days) because I haven’t had much free time recently, so I’ve only been able to work on this project in short sessions, making small improvements whenever I had the chance.
For this update, I focused on connecting the UI with the plugin system. Now the app can detect the correct plugin for the dropped file, displays messages saying what was done and has options that were missing before, like image dimensions or output format.
Although these aren’t the most exciting features, they’re an important thing to be done, because the application is becoming truly modular, which means future plugins (PDFs, videos, archives, STL files) should integrate with very little additional work.

The idea behind Flow is simple: instead of opening multiple applications to perform common tasks like compressing an image, converting a file, or extracting text from a PDF, users can simply drag and drop a file into Flow and instantly access the actions available for that file type/extension. My goal is to reduce the number of steps required for common tasks.
So far I have designed the overall architecture of the application, created a plugin-based system to make the project easily extensible, implemented a plugin manager that automatically discovers and loads plugins, defined a base FlowPlugin class that all plugins will inherit from, built a simple test plugin to verify that the plugin system works correctly, started developing the graphical interface using CustomTkinter and tkinterdnd2(basically a window that only detects when something gets dropped in there).

This is probably my final update and I’m very proud of how this app ended.
This update was focused on polishing the app to look and work better. I finally added multi-language support and this was what took most of the time because I encoutered some bugs along the way(incorrect translations and displaced things) but now its working great.
Also added a tutorial(only appears the first time you use the app) that explains how to use the app and has a very important warning. You should read it very carefully.
I changed the app behaviour so that now it starts visble until you hit alt+v(before it started “closed).
Although individually small, these fixes significantly improved the application’s overall quality and reliability.

I really liked this update because, even though it took a long time, it basically makes the app look more professional and “modern”.
I focused on improving the user experience by making the interface cleaner, faster and easier to use(but had to fix some of bugs that were occuring for weird reasons).
With this update, managing tags became much more convenient and now, when you are adding a tag you can write a new one or choose between the ones that you already have.
I also improved the search/filtering system. Now you can view all clipboard entries(as always) but you can also show only favorite items or filter them by their tags(I really liked this one because now you can have a lot of items with a tag for a project and view them at once instead of looking for them).
And now what I would like to say that was the biggest improve(but everything on this update was awesome:)), the interface. I completly remade the interface because it was kinda ugly. Now it has a really nice dark theme, with much more recognizable widgets(items) layout, better spacement and aligment and so, a cleaner layout.
The only thing left to add is multilanguage support(for now its in Portuguese but I’ll add English), and I would also like to make a simple “Tutorial”.
FORGOT TO MENTION EARLIER, but I also changed the hotkey to alt+v because ctrl+shift+v would always paste something

In this update, I’ve added two things that, in my opinion, are the most important in this project:
I added a search bar that, as the user types, the clipboard history is filtered, searching both the clipboard content and any assigned tags. To support this, I refactored part of the interface by creating a single function responsible for drawing the clipboard list. This eliminated duplicate code and greatly facilitated future interface updates.
The biggest addition in this update was automatic content detection, whenever something is copied, the application now analyzes it and classifies it automatically. Currently, it can detect youtube links, github links, generic urls, email adresses, code, and, as always, normal text. Each detected type is stored in the database and displayed with its own icon(emojis), making the clipboard history much easier to identify.

During development I encountered an issue where copied code snippets were being detected as plain text instead of source code .After debugging the detection logic and verifying the values stored in the database, I identified and fixed the problem. The application now correctly classifies supported code snippets and displays the appropriate icon.

The code has already achieved its original objective of providing a persistent and more intelligent clipboard history than the default windows clipboard. The only thing left to do is to create a better interface.

I made it work more like a real background application and to achieve this I configured the application to launch when the computer turns on, run silently in the background and keep the shortcut always available.
I also added some simple organization features, Favorites and Tags. Now you can mark an item as favorite by selecting it and pressing “F”, favorite items are displayed with a ⭐ icon, and by pressing “T” you can also add a Tag that is displayed next to the item

I made a simple interface that lets you see what you have in the clipboard and select what you want to paste(pretty similar to the function that windows already has). Also made it so that you can open/close the windows with ctrl+shift+v and changed the code a bit so that now it can all work just by running main.py instead of running diferent files. For now, the interface is pretty basic but I want to update it latter

My goal for this project is to create a clipboard history application, using python, that permanently stores copied content, even after the computer is restarted.
The project is still in an early stage. At the moment it only supports text, basic duplicate prevention (consecutive duplicates only) and console output. It does not yet support(but it will at some point) images, search, favorites, graphical interface or running automatically in the background.
For now, the interface looks like this(just copied random things from the code and sorry but for now it only supports Portuguese):