Devlog #21
Updating the README so I can release version 0.7 tomorrow!
Devlog #21
Updating the README so I can release version 0.7 tomorrow!
Devlog #20
Today, with the help of ChatGPT, I created the dependency system.
The ZAP can now resolve package dependencies and find the correct versions required by each package. It can also handle multiple versions of the same dependency and create launchers with the required dependencies added to the PATH.
This means different packages can use different versions of the same dependency without conflicts.
Devlog #04
Starting to make a calculator app. and adding more icons.
Devlog #03
Today I added the incons and the about the os app.
Devlog #02
Today I added a start menu and other things in the back. The next step is add apps to the web os
DevLog #01
Today, I started developing WEB-DOS with Interface 85.
The system is still very raw, and it is heavily inspired by Microsoft’s Windows 95 interface.
Devlog #18
Today, I added a new parameter to the database for dependencies, and I started working on the dependency system.
I don’t know if I mentioned it in the previous devlog, but I also created the confirmation button.
Thanks for reading! And if you want to launch your project on Zap, please contact me.
Thanks for reading!
Devlog #03 Today I write the readme for the sigma bot
devlog #02 makling the cpu show the instructionson the srceen and deciding the arquitctura. sorry for the English is 12 of the night in portugal and I’m tired.
Devlog # 1.5 After I don’ know I finally manage to make this work
Devlog #1
So today i build the sigma bot, but it was 80 % working!
DevLog #2
Today I cooked on this README.
Hello! Today I finally started working on the scary part of a package manager: dependencies ⛈️⛈️.
Warning
Today I only worked on the system that grabs the dependencies.
The way dependencies will work is through the .cmd launchers stored in:
C:/Users/Your_User/AppData/Local/Zap/sl
Each package will have its own launcher, and that launcher will be responsible for setting up the environment required by that package.
For example, imagine your program uses lib_a version 1.0, while another program uses lib_a version 2.0. Instead of putting everything in the same place and causing conflicts, each .cmd launcher will temporarily add the required dependencies to the PATH.
This means that both versions can coexist without interfering with each other.
Dependencies can also have their own dependencies. When one package depends on another package, its launcher can create its own environment with the dependencies it requires. This creates a kind of lightweight sandbox for each package.
The goal is to keep dependencies isolated while keeping the system simple and transparent.
This is definitely one of the more complicated parts of the package manager, but I’m finally starting to figure out the architecture.
Warning
This changes are not avaiable yet!
Today, I changed the way you configure Zap.
The example below shows how to hide the logo.
Before:
zap config hl
Now:
zap config set show_logo true
Previously, you couldn’t view the configuration from the program. Now, zap config list shows the current configuration.
Warning
The configuration is currently only used to enable, disable, or change the logo and debug settings.
I’m also finally using Python’s virtual environment to work on the project.
These changes will be included in the next release. For now, they are available in the dev branch.
And thank you to everyone who has checked out the project and given feedback. If anyone wants to publish their projects and make them available in the Zap repository, please leave a comment or try to contact me.
Devlog #1 So you can see this is my portfolio.