Shorten blog article descriptions, fix image links
This commit is contained in:
parent
a16fe23d3f
commit
9709e33c8b
12 changed files with 21 additions and 22 deletions
|
|
@ -6,6 +6,8 @@ draft: false
|
||||||
|
|
||||||
I'm very sorry about the delay, but a new release of Astra is upon us!
|
I'm very sorry about the delay, but a new release of Astra is upon us!
|
||||||
|
|
||||||
|
<!--more-->
|
||||||
|
|
||||||
I have been working hard to get the Flatpak repository working (after some very troubling GPG issues) but the install process is now refined enough that it's a one-click install from the website. I hope Steam Deck users will enjoy the Flatpak, and I plan on making more exciting changes soon - such as Steam Proton support, Steam login, and a proper controller interface :-)
|
I have been working hard to get the Flatpak repository working (after some very troubling GPG issues) but the install process is now refined enough that it's a one-click install from the website. I hope Steam Deck users will enjoy the Flatpak, and I plan on making more exciting changes soon - such as Steam Proton support, Steam login, and a proper controller interface :-)
|
||||||
|
|
||||||
You can read the full patch notes [here](https://xiv.zone/astra/changelog/0.4.0). Please note that I have pushed a quick bugfix update (0.4.1) for users that might have already downloaded a version of 0.4.0. Linux users are recommended to update as it fixes an issue with case-sensitive filesystems. Astra is now available for Linux (tarball or Flatpak), macOS and Windows, enjoy!
|
You can read the full patch notes [here](https://xiv.zone/astra/changelog/0.4.0). Please note that I have pushed a quick bugfix update (0.4.1) for users that might have already downloaded a version of 0.4.0. Linux users are recommended to update as it fixes an issue with case-sensitive filesystems. Astra is now available for Linux (tarball or Flatpak), macOS and Windows, enjoy!
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,7 @@ tags:
|
||||||
- Review
|
- Review
|
||||||
---
|
---
|
||||||
|
|
||||||
Hello again! This is my figure review of the [Mari Figure from Sega](https://myfigurecollection.net/item/945032). She was released around 2020 as a prize
|
Hello again! This is my figure review of the [Mari Figure from Sega](https://myfigurecollection.net/item/945032). <!--more--> She was released around 2020 as a prize
|
||||||
figure celebrating the launch of "Evangelion 3.0+1.0", before it got pushed back to 2021. I
|
figure celebrating the launch of "Evangelion 3.0+1.0", before it got pushed back to 2021. I
|
||||||
didn't preorder her on your typical reseller website but instead got her a little bit earlier by buying her on [buyee.jp](https://buyee.jp).
|
didn't preorder her on your typical reseller website but instead got her a little bit earlier by buying her on [buyee.jp](https://buyee.jp).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,7 @@ tags:
|
||||||
- Review
|
- Review
|
||||||
---
|
---
|
||||||
|
|
||||||
Today we're reviewing the Flare reissue of the YoRHa No. 2 Type B released by Square Enix, a company that despite being very, very controlling of their merchandise has the absolute worst online store ever. This isn't just a single case, you can read online where people have similiar experiences with Square Enix's online store.
|
Today we're reviewing the Flare reissue of the YoRHa No. 2 Type B released by Square Enix, a company that despite being very, very controlling of their merchandise has the absolute worst online store ever. <!--more--> This isn't just a single case, you can read online where people have similiar experiences with Square Enix's online store.
|
||||||
|
|
||||||
## The Buying Process
|
## The Buying Process
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,8 +7,7 @@ tags:
|
||||||
- sourcehut
|
- sourcehut
|
||||||
---
|
---
|
||||||
|
|
||||||
Recently I've moved pretty much all of my repositories over to sourcehut! This is a huge change, as I haven't changed
|
Recently I've moved pretty much all of my repositories over to sourcehut! <!--more--> This is a huge change, as I haven't changed my primary code hosting provider, Github, since 2-3 years ago.
|
||||||
my primary code hosting provider, Github, since 2-3 years ago.
|
|
||||||
|
|
||||||
**Edit:** There is a follow up to my sourcehut migration located [here]({{<ref "moving-to-sourcehut-followup">}})!
|
**Edit:** There is a follow up to my sourcehut migration located [here]({{<ref "moving-to-sourcehut-followup">}})!
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,9 +7,7 @@ draft: false
|
||||||
date: 2022-06-23
|
date: 2022-06-23
|
||||||
---
|
---
|
||||||
|
|
||||||
Over the past few hours I did some serious cleaning up on my [GitHub account](https://github.com/redstrate), I basically removed every single original repository I had. I still need GitHub in order to contribute to some projects, so my forks are kept.
|
Over the past few hours I did some serious cleaning up on my [GitHub account](https://github.com/redstrate), I basically removed every single original repository I had. <!--more--> I still need GitHub in order to contribute to some projects, so my forks are kept. For people trying to find my missing repositories, I added a profile README to direct people to my sourcehut instead.
|
||||||
|
|
||||||
For people trying to find my missing repositories, I added a profile README to direct people to my sourcehut instead.
|
|
||||||
|
|
||||||
There were many reasons why I ditched GitHub, a couple are detailed below:
|
There were many reasons why I ditched GitHub, a couple are detailed below:
|
||||||
* I disliked the “social media” features that were just getting more and more prominent. I didn’t really care for these and I just saw it as introducing bloat and spam to the platform (cue small PRs just for a one line README change just to get a contribution award).
|
* I disliked the “social media” features that were just getting more and more prominent. I didn’t really care for these and I just saw it as introducing bloat and spam to the platform (cue small PRs just for a one line README change just to get a contribution award).
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,7 @@ tags:
|
||||||
- sourcehut
|
- sourcehut
|
||||||
---
|
---
|
||||||
|
|
||||||
This is a follow-up post to my blog post detailing the changes I've made to how my source code is hosted. Basically, I'm trying to
|
This is a follow-up post to my blog post detailing the changes I've made to how my source code is hosted. <!--more--> Basically, I'm trying to
|
||||||
move away from GitHub for my primary code hosting to a (in my opinion, better suited for me) platform. After some deliberation, I
|
move away from GitHub for my primary code hosting to a (in my opinion, better suited for me) platform. After some deliberation, I
|
||||||
ultimately landed on sourcehut, and plan to detail the benefits I've gained, and the things I've losted. Hint, it works pretty well,
|
ultimately landed on sourcehut, and plan to detail the benefits I've gained, and the things I've losted. Hint, it works pretty well,
|
||||||
so I'm excited to dig into my new workflow :-)
|
so I'm excited to dig into my new workflow :-)
|
||||||
|
|
|
||||||
|
|
@ -6,7 +6,7 @@ tags:
|
||||||
- KDE
|
- KDE
|
||||||
---
|
---
|
||||||
|
|
||||||
This is probably the most specific use case I'll ever post on this blog :-p I noticed whenever I click an address in [KAddressBook](https://apps.kde.org/kaddressbook/), it opens it in [OpenStreetMap](https://www.openstreetmap.org/) in your web browser by default. Huh?
|
This is probably the most specific use case I'll ever post on this blog :-p I noticed whenever I click an address in [KAddressBook](https://apps.kde.org/kaddressbook/), it opens it in [OpenStreetMap](https://www.openstreetmap.org/) in your web browser by default. Huh? <!--more-->
|
||||||
|
|
||||||
**Edit:** Recent Plasma versions now have the ability to select KDE Marble as the default maps application, and KAddressBook dropped support for setting the "Show Address" function like as pictured below. However, KDE Marble still lacks a way to properly decode addresses, making this functionality useless still. I will further update the article once I find a workaround, or I contribute something upstream.
|
**Edit:** Recent Plasma versions now have the ability to select KDE Marble as the default maps application, and KAddressBook dropped support for setting the "Show Address" function like as pictured below. However, KDE Marble still lacks a way to properly decode addresses, making this functionality useless still. I will further update the article once I find a workaround, or I contribute something upstream.
|
||||||
|
|
||||||
|
|
@ -14,7 +14,7 @@ But I learned that [KDE Marble](https://marble.kde.org/) exists, a native KDE ap
|
||||||
|
|
||||||
1. We set the "Show Address" to open an "External Application", this is where we'll call our python script `geo.py`:
|
1. We set the "Show Address" to open an "External Application", this is where we'll call our python script `geo.py`:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The full command is:
|
The full command is:
|
||||||
|
|
||||||
|
|
@ -44,7 +44,7 @@ This is actually quite interesting, as I would think KAddressBook would have thi
|
||||||
|
|
||||||
So this is where Nominatim comes in, which as said before - is a service run by OpenStreetMap. It's API is extremely simple, which is perfect. I originally tried to only do this in Shell and CURL, but it turned out to be much easier just to use GeoPy and Python.
|
So this is where Nominatim comes in, which as said before - is a service run by OpenStreetMap. It's API is extremely simple, which is perfect. I originally tried to only do this in Shell and CURL, but it turned out to be much easier just to use GeoPy and Python.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Then, you'll notice if you don't add any extra arguments to Marble, it'll open up super far away and also in a weird default view that's not suitable for viewing addresses. Luckily, the developers already added some nice arguments to allow us to change this default behavior:
|
Then, you'll notice if you don't add any extra arguments to Marble, it'll open up super far away and also in a weird default view that's not suitable for viewing addresses. Luckily, the developers already added some nice arguments to allow us to change this default behavior:
|
||||||
|
|
||||||
|
|
@ -52,4 +52,4 @@ Then, you'll notice if you don't add any extra arguments to Marble, it'll open u
|
||||||
|
|
||||||
This will set the initial distance to "0 km" and also changes the map view to OpenStreetMap, perfect!
|
This will set the initial distance to "0 km" and also changes the map view to OpenStreetMap, perfect!
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -6,7 +6,7 @@ tags:
|
||||||
- Prism
|
- Prism
|
||||||
---
|
---
|
||||||
|
|
||||||
These two months contain some pretty big changes I made to Prism, following a short hiatus from the project. These include some pretty important changes to the project moving forward and I hope to keep documenting these in this nice and concise, visual way in the future! Also before you ask, this is Feburary _and_ April, I only made one small commit in March which is why it's not Feburary _to_ April.
|
These two months contain some pretty big changes I made to Prism, following a short hiatus from the project. These include some pretty important changes to the project moving forward and I hope to keep documenting these in this nice and concise, visual way in the future! <!--more--> Also before you ask, this is Feburary _and_ April, I only made one small commit in March which is why it's not Feburary _to_ April.
|
||||||
|
|
||||||
If you've never heard of Prism before, it's my ultimate graphics study project that is the culmination of everything I've learned in graphics development so far. It is built upon years of hard effort/learning and also extremely valuable help from multiple people in the graphics community. You can find the complete source code and even more information on it's [Github repository](https://www.github.com/redstrate/prism).
|
If you've never heard of Prism before, it's my ultimate graphics study project that is the culmination of everything I've learned in graphics development so far. It is built upon years of hard effort/learning and also extremely valuable help from multiple people in the graphics community. You can find the complete source code and even more information on it's [Github repository](https://www.github.com/redstrate/prism).
|
||||||
|
|
||||||
|
|
@ -16,7 +16,7 @@ The Vulkan backend is moving very quickly to reach feature parity soon with the
|
||||||
fully usuable for most tasks on Windows and Linux! The main roadblock right now is implementing the last of the
|
fully usuable for most tasks on Windows and Linux! The main roadblock right now is implementing the last of the
|
||||||
functionality required for IBL and some other graphical features.
|
functionality required for IBL and some other graphical features.
|
||||||
|
|
||||||
|
|
||||||
_This is the Material editor running on Vulkan, on Windows_
|
_This is the Material editor running on Vulkan, on Windows_
|
||||||
|
|
||||||
### SDL2 is the new default windowing system for Windows and Linux
|
### SDL2 is the new default windowing system for Windows and Linux
|
||||||
|
|
@ -41,7 +41,7 @@ This is a pretty and clear nice benefit from using the SDL backend, because now
|
||||||
|
|
||||||
Before if you wanted to render to another window, static image, viewport you were required to create a whole new renderer instance. This was bad design for a multitude of reasons - duplicated work, resources and lack of proper cohesion or synchronization. This was because a single renderer instance only supported rendering to one target. Now everything is reworked and I can use just one renderer instance for the whole engine, even down to the tooling!
|
Before if you wanted to render to another window, static image, viewport you were required to create a whole new renderer instance. This was bad design for a multitude of reasons - duplicated work, resources and lack of proper cohesion or synchronization. This was because a single renderer instance only supported rendering to one target. Now everything is reworked and I can use just one renderer instance for the whole engine, even down to the tooling!
|
||||||
|
|
||||||
|
|
||||||
_This is two editor viewports running at the same time in two different windows, something not possible before under the old system._
|
_This is two editor viewports running at the same time in two different windows, something not possible before under the old system._
|
||||||
|
|
||||||
The new render target system is also the backbone of the new cross platform dear imgui multi-viewport support (try saying that 5x fast!) The API is also extremely easy to use:
|
The new render target system is also the backbone of the new cross platform dear imgui multi-viewport support (try saying that 5x fast!) The API is also extremely easy to use:
|
||||||
|
|
|
||||||
|
|
@ -22,7 +22,7 @@ It wasn't unitl I realized that I'm pulling apart my engine for no good reason j
|
||||||
|
|
||||||
I recently was able to get a [nice Windows setup going](https://knockout.chat/thread/25747/28#post-1207745), so now DX12 support is going to finally begin. This is one of the last APIs I plan to support officially, so this is exciting. Now I don't have any real excuse to not support this API.
|
I recently was able to get a [nice Windows setup going](https://knockout.chat/thread/25747/28#post-1207745), so now DX12 support is going to finally begin. This is one of the last APIs I plan to support officially, so this is exciting. Now I don't have any real excuse to not support this API.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Moving away from Objective-C
|
### Moving away from Objective-C
|
||||||
|
|
||||||
|
|
@ -52,7 +52,7 @@ right in the source code repository. This has technically been around since the
|
||||||
{{< rawhtml >}}
|
{{< rawhtml >}}
|
||||||
|
|
||||||
<video width=100% controls>
|
<video width=100% controls>
|
||||||
<source src="/articles/img/JezVKVk.mp4">
|
<source src="/blog/img/JezVKVk.mp4">
|
||||||
</video>
|
</video>
|
||||||
|
|
||||||
{{< /rawhtml >}}
|
{{< /rawhtml >}}
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ date: 2022-06-28
|
||||||
draft: false
|
draft: false
|
||||||
---
|
---
|
||||||
|
|
||||||
In my series of purging my content on propietary platforms I don't align with anymore, the next on the chopping block is Twitter. Just like GitHub, I have several personal reasons why I'm not supporting Twitter any longer:
|
In my series of purging my content on propietary platforms I don't align with anymore, the next on the chopping block is Twitter. Just like GitHub, I have several personal reasons why I'm not supporting Twitter any longer. <!--more-->
|
||||||
|
|
||||||
* Focus on alogrithmic discovery as opposed to a simple, linear timeline.
|
* Focus on alogrithmic discovery as opposed to a simple, linear timeline.
|
||||||
* Supporting NFTs which I don't personally agree with.
|
* Supporting NFTs which I don't personally agree with.
|
||||||
|
|
|
||||||
|
|
@ -9,7 +9,7 @@ tags:
|
||||||
---
|
---
|
||||||
|
|
||||||
In under an hour, I was able to port my already existing Vulkan code from [Prism](/projects/prism)
|
In under an hour, I was able to port my already existing Vulkan code from [Prism](/projects/prism)
|
||||||
to Metal using [MoltenVK](https://github.com/KhronosGroup/MoltenVK). Here's a screenshot (very exciting):
|
to Metal using [MoltenVK](https://github.com/KhronosGroup/MoltenVK). <!--more--> Here's a screenshot (very exciting):
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -17,11 +17,11 @@ To clarify, Prism running on macOS is nothing new. In fact, a large portion of t
|
||||||
developed natively on macOS using Metal. Vulkan was actually added after the fact, and since I already had plenty of
|
developed natively on macOS using Metal. Vulkan was actually added after the fact, and since I already had plenty of
|
||||||
Vulkan experience it was no trouble. I initially chose to use Metal natively (over MoltenVK at the time) because the tooling was still too new, and I wanted to learn Metal. However something big has come along since then, the rise of the [Vulkan Portability Initiative](https://www.vulkan.org/portability)!
|
Vulkan experience it was no trouble. I initially chose to use Metal natively (over MoltenVK at the time) because the tooling was still too new, and I wanted to learn Metal. However something big has come along since then, the rise of the [Vulkan Portability Initiative](https://www.vulkan.org/portability)!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The biggest thing to come out of this is the introduction of _first class macOS support_. If you've used the Vulkan SDK before on macOS, you _must_ give this new version a try. The new Vulkan SDK has an installer that takes cares of everything for you. Even the **Vulkan Configurator works**! This gets you the _same exact experience_ like as if you were developing with Vulkan on Windows or Linux. Yes, even the _Vulkan CMake module works out of the box_, thank you to every developer who worked on this!
|
The biggest thing to come out of this is the introduction of _first class macOS support_. If you've used the Vulkan SDK before on macOS, you _must_ give this new version a try. The new Vulkan SDK has an installer that takes cares of everything for you. Even the **Vulkan Configurator works**! This gets you the _same exact experience_ like as if you were developing with Vulkan on Windows or Linux. Yes, even the _Vulkan CMake module works out of the box_, thank you to every developer who worked on this!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
What does this mean for Prism? .. Not much yet except that it's awesome that it works pretty much of the box. However for any future graphics endaveours for me **I unfortunately won't be supporting Metal anymore**, there just isn't a reason to. I learned as much Metal as I wanted, and the Metal backend fullfilled that purpose. However, there's still a purpose to abstracting GFX away in Prism, _to make way for DirectX support_ :-)
|
What does this mean for Prism? .. Not much yet except that it's awesome that it works pretty much of the box. However for any future graphics endaveours for me **I unfortunately won't be supporting Metal anymore**, there just isn't a reason to. I learned as much Metal as I wanted, and the Metal backend fullfilled that purpose. However, there's still a purpose to abstracting GFX away in Prism, _to make way for DirectX support_ :-)
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ date: 2021-07-21
|
||||||
draft: false
|
draft: false
|
||||||
---
|
---
|
||||||
|
|
||||||
So around 2018 I was busy writing my own Matrix client, as anyone does. It was called Trinity, and it featured a Discord-like interface:
|
So around 2018 I was busy writing my own Matrix client, as anyone does. It was called Trinity, and it featured a Discord-like interface. <!--more-->
|
||||||
|
|
||||||
TODO
|
TODO
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue