Posts by nahuel@social.nahuelwexd.com
(DIR) Post #AUxAANpM7lgviako6q by nahuel@social.nahuelwexd.com
2023-04-23T19:24:43Z
1 likes, 0 repeats
@xerz They tried to support dark mode on Linux when we didn't have the standard yet.When the standard arrived, they got notified it in the corresponding ticket, but it seems they didn't give it priority until now
(DIR) Post #AUxAAbrdw3q7FjvpcO by nahuel@social.nahuelwexd.com
2023-04-23T19:25:44Z
1 likes, 0 repeats
@xerz If I remember correctly, I think Firefox got the support because someone related to the portal added it
(DIR) Post #AVJyI6kYlsXYFwVQWG by nahuel@social.nahuelwexd.com
2023-05-04T19:31:40Z
0 likes, 0 repeats
@xerz is there gnome 44?
(DIR) Post #AVkSBoQ8gKfGICEVzk by nahuel@social.nahuelwexd.com
2023-05-16T23:47:31Z
1 likes, 1 repeats
So I finally managed to create the #GTK widget I wanted so much to have: a height-for-width widget, to which you pass a URL of an image, and it renders it occupying all the possible width, while keeping the 16:9 aspect ratio.I remember trying it in GTK+ 3, resizing pixbufs in a size_allocate, and @alice telling me it was a terrible approach xdThis time it only took me 90 lines of #Vala code, and about 4 hours of coding, but I did it and I'm happy :')
(DIR) Post #AVrCEqcMSxY7k7QFk0 by nahuel@social.nahuelwexd.com
2023-05-20T20:11:25Z
1 likes, 0 repeats
Uhm... maybe we should try to be less technical in blog posts? I was shared a post from the Purism blog announcing the availability of a PureOS Flatpak remote, but the way it was written seemed 100% aimed at developersHonestly, I know a lot of Linux users who might read that post, and have no idea what terms like "git" or "runtime" mean, but the article seems to assume said knowledge
(DIR) Post #AVrCEtSBvECGXRgfo0 by nahuel@social.nahuelwexd.com
2023-05-20T20:11:31Z
1 likes, 0 repeats
It's somewhat curious, 'cause Purism has a section for technical users, but nevertheless the article was posted in the non-technical section
(DIR) Post #AVtSX62rph1iNySoue by nahuel@social.nahuelwexd.com
2023-05-21T22:23:48Z
0 likes, 0 repeats
@xerz you want to be punished right? :blobovo:
(DIR) Post #AVtT2hu77mcemPRVNw by nahuel@social.nahuelwexd.com
2023-05-21T22:27:28Z
0 likes, 0 repeats
@xerz :blobyes: you wanna be punished
(DIR) Post #AVtTClZoKD9T48k6N6 by nahuel@social.nahuelwexd.com
2023-05-21T22:33:23Z
0 likes, 0 repeats
@xerz good girl :senkofastpat:
(DIR) Post #AVtTPX2BhiqhjD6QvA by nahuel@social.nahuelwexd.com
2023-05-21T22:35:18Z
0 likes, 0 repeats
@xerz I can and I do :patpatpat:
(DIR) Post #AWHq39UX2jCJy1bkCu by nahuel@social.nahuelwexd.com
2023-06-02T16:06:31Z
0 likes, 0 repeats
@cassidy Personally, regarding Flatpak, I always wanted the default behavior to be something like:- runtime and apps are always installed at system level- .desktop files are only exposed to users who hit the "Install" button.That way, you don't have heavy apps installed multiple times, but at the same time each user has only what they are interested in in their app grid
(DIR) Post #AWHq3BRPnHtQ0wAHcu by nahuel@social.nahuelwexd.com
2023-06-02T16:07:57Z
0 likes, 0 repeats
@cassidy it would also be nice if apps like Steam had some special permission to install games at the same system level, instead of using XDG_DATA_HOME.I don't think you want to have Spider-Man installed 3 times, just because 3 users on the PC play it.
(DIR) Post #AWM0K44WDqN2Ftz1UG by nahuel@social.nahuelwexd.com
2023-06-04T16:55:32Z
1 likes, 0 repeats
@TheEvilSkeleton> Separating every dependency would be really inconvenientNot if you do it the right way. Having to become maintainer for each of my dependencies is one of the worst things about Flatpak, and it's something I've said before. And I say that as an extremely pro-Flatpak person.
(DIR) Post #AWM0KKCYFkIqHRrfEG by nahuel@social.nahuelwexd.com
2023-06-04T16:55:56Z
1 likes, 0 repeats
@TheEvilSkeletonCurrently, the SDK extension system for certain dependencies is great, but we need to simplify it and extend it to more dependencies. It should be as simple as specifying the dependency name, its major version in a notation such as "^1.2.3", and have flatpak-builder look it up in some dependency repo and bundle the correct version. In fact, that way we would take advantage of OSTree's deduplication system.
(DIR) Post #AWM1Gy1GMvikZMXzRA by nahuel@social.nahuelwexd.com
2023-06-04T17:06:51Z
0 likes, 0 repeats
@xerz Yes and noThe current package managers are managed by the users themselves on their systems. They download packages of apps, and the dependency packages of those same apps, and install them all on their systemsWhat I was proposing is that the "package manager" should be flatpak-builder, not Flatpak. For Flatpak, everything would stay the same. The only change would be that as a dev you no longer have to write the recipe to compile libsass and sassc for every app you have that uses sass
(DIR) Post #AWM44bBPkPDQ8D5bJg by nahuel@social.nahuelwexd.com
2023-06-04T17:37:09Z
0 likes, 0 repeats
@TheEvilSkeletonNot really. While shared-modules was an attempt to achieve common modules between various Flatpak packages, to thereby take advantage of OSTree's deduplication system, it has the problem that it's not really versioned....... mainly because it's just a set of JSON/YAML files that you reference from your manifest
(DIR) Post #AWM44bnhS3qA2x0AzY by nahuel@social.nahuelwexd.com
2023-06-04T17:37:34Z
1 likes, 0 repeats
@TheEvilSkeleton What I would prefer is that the dev of each dependency should be able to publish it in a dedicated repo, and have proper versioning system. Then each app developer simply references the dependency, with the specific version they need
(DIR) Post #AWM45098vzFlYPDdkO by nahuel@social.nahuelwexd.com
2023-06-04T17:38:18Z
1 likes, 0 repeats
@TheEvilSkeleton I mean... there are lots and lots of devs who are very used to how Node and NPM works nowadays. They simply have a package.json where if they need a dependency, they write:"dependencies": [ "my-dep": "^1.2.3"]and then it's up to NPM to install a version of "my-dep" that meets those requirements (i.e., any version of "my-dep" that is >= 1.2.3 and < 2.0.0)
(DIR) Post #AWM45W0kSjYINdXO6a by nahuel@social.nahuelwexd.com
2023-06-04T17:38:45Z
1 likes, 0 repeats
@TheEvilSkeleton The difficulties and challenges Flatpak presents for devs I saw clearly reflected when @elementary decided to use Flatpak as the primary means to distribute their apps, as in the Slack I started to find a lot of people who had no idea how to compile and bundle their dependencies... and do they really need to know? It also triggered the appearance of this website: https://flatpak-modules.vercel.app/
(DIR) Post #AWM47tTYC0w5jX8xuK by nahuel@social.nahuelwexd.com
2023-06-04T17:38:57Z
1 likes, 0 repeats
@TheEvilSkeleton (there's also the fact that I've had to assist people outside elementary on how to compile in Flatpak the libraries they didn't even know they needed for their apps)