RiverFlow
- 5 Devlogs
- 51 Total hours
Native customizable file manager engine for MacOS meant to be alternative for developers
Native customizable file manager engine for MacOS meant to be alternative for developers
We are getting so close to the first demo launch!
Pushed by my Git fascination I managed to integrate another two important things into the repo: CodeQL and automatic code review by CodeRabbit. However I realised I’ve been doing much more things at the repo itself and I keep forgeting I am trying to code something. So - 4 new features (and first really developer-focused) and incoming REAL readme (because the current one is really crappy).
I just started my last high school year so I’ll be a little more busy but my targets still remain the same: at least 80h on stardance and first beta release until 30th September.
I must admit that I did not write unit tests for Git integration because I kinda don’t know how to approach it. Maybe the next few days in school with my teacher will help me going through it.
Apart from that I struggled with applying some responsiveness to resizable elements (such as InteractivePathView) and eventually failed and will return to this later.
I promised myself that I won’t go beyond those 10h of no devlog but I failed again. My own devlog template is incoming so I will be more eager to make them more frequent.
Apart from that - I am planning demo launch around 14th September so I can gather feedback before beta release around 30th September. Thank you all in advance for reading this and till next time!
I’ve made myself a little break, I admit. It was a good time, I came back stronger and more motivated.
I’ve noticed that the project is terribly documented and tested, files orgranization was also looking bad. I decided to correct those affairs to make the further development more… amicable.
There was also some time for new feature: searching. Maybe not the best but it is already better than Finder’s (modest as always, I know) because it has revelance tier sorting. Of course it is not the final version but for now It’ll work.
Sounds easy right? Swift Testing framework is easy but it took me some time to learn good practics (and I’m still learning).
Also I have plenty of reflections about the technical debt meant earlier. I realized that if I want to efficiently go further with the project I have to think more carefully about planning and organizing the development process. Hopefully the next school year will teach me how real programmers do the thing.
That’s all in today’s Not-So-Daily. I know I say that again but maybe it’s time to try doing devlogs more frequent than 10h of work. I didn’t even realize it went that fast. Till next time!
I tried to write a devlog several days ago but excessive heat beat me up.
To be honest last week was the hardest during the whole project. The amount of documentation and videos I’ve read and watched was enormous. My head is overload and I may be considering a little break. But let’s get to the stuff what was made. As usual the full devlog will be posted on toriyukari.neocities.org website.
Last Stardance devlog was 21 days ago so it was basically the very beginning of the project, so I’ll just write things that are already present:
I am currently preparing the project to move into Test Driven Development, I am trying to cover the whole existing source code with tests to go on with this coding practice.
Soon I’ll start learning about UI testing in Swift Testing framework.
I can’t even think about how many things I’ve read about during the last 3 weeks. Maybe if I would be doing this list regularly… that is actually a good idea.
But most important thing that caused me to almost destroy my repo was: DO NOT LET GITHUB COPILOT CREATE COMMITS FOR YOU. They didn’t improve anything and now I have a freaking Copilot as a contributor in the repo. Worst mistake of my life.
EVERYTHING!
But seriously since I use as little AI as I can I am going through hard time during almost everything. Sometimes it drives me crazy.
The biggest difficulties were:
And that’s all worth to mention.
HEAT WAVE HEAT WAVE HEAT WAVE HEAT WAVE
WHY IN POLAND IT HAS TO BE -15C OR +40C WHY IT CAN’T BE FREAKING NORMAL 20C
HEEEEELP I CAN’T WORK NORMALLY!!!
…
i’m fine
I’ll try to make devlogs more frequently but I don’t think I like doing so. I’ll have to think about some formula, maybe a simpler approach, more reusable scheme or something like that. Until that going off the air for a moment to rest. See ya!
Hi everyone! Little update here: I will be posting full sized devlogs
for RiverFlow and any other project on my website available at this
address: https://toriyukari.neocities.org/
I am an enthusiast of big, bulky devlogs where I do not only write rough
code facts but I’m also sharing a whole development story and 4000
chars is not enough for me.
From now on I will be making a Stardance devlog version and full devlog
version. I will be attaching a link for everyone who are curious about
the whole process. I hope you all understand this.
Also there is a first instance of brand new idea of mine available on the website: daily where I share the status and changes of the development every day. You should check it out cause they won’t show up here.
Anyways, have a great day just how I’ve had! See ya!
Until now the project was simply a prototype to test the idea but I kind of lost track of the time and made way too much before first devlog.
So here it comes: RiverFlow, native file manager alternative for MacOS, part of The Shrimple Project.
Fast as river, no one can stop the flow. It uses all the best stuff Swift language has to make it more resource-efficient than Finder (at least that’s the target) and it’s currently my biggest project.
It is ultimately intended to be developer-friendly and will have a lot of built-in tweaks we as programmers needed a plugin for. I also wanted it to have some Linux-feel and make it customizable in every possible way: from colors and icon sizes to custom windows and built-in plugin maker.
(I had to cut this cause of 4000 chars limit, I will post full devlogs somewhere else)
Alright, I’ve been talking about something entirely different. So here is the flow:
And that’s it! If I would want to I can fit all of this in 50-100 lines of code. The real fun starts in coding user interactions with all those objects. I must admit it wasn’t the easiest challenge.
The list is long. I’ve encountered several walls on my way, some cleared up by different websites, for some I had to use AI tho.
The “minor difficulties”: I’ll spare you this rant
The “major difficulties”:
There isn’t much features yet but taking into account that I am using Swift for real for the first time I am proud of myself.
I hope you all will like this project and find it useful in your every day productivity when it’ll be a finished product. Until next time! I will go make myself a real dinner for the first time since two weeks.