Search
452 results for “matzipan”
-
Finished the tasks for Envoyer 0.2 milestone.
Usability is improved but this doesn't mean much since the app was unusable to begin with.
Release notes here: https://github.com/matzipan/envoyer/releases/tag/0.2
Give it a spin and give some feedback!
Next big chunk of work will be to support non-Gmail IMAP and adding integration tests!
-
@matzipan 😂 Yeah the purpose is too find leaked credentials.
This is the same as #trufflehog that is written in #golang https://github.com/trufflesecurity/trufflehog -
@matzipan 😂 Yeah the purpose is too find leaked credentials.
This is the same as #trufflehog that is written in #golang https://github.com/trufflesecurity/trufflehog -
@matzipan 😂 Yeah the purpose is too find leaked credentials.
This is the same as #trufflehog that is written in #golang https://github.com/trufflesecurity/trufflehog -
@matzipan 😂 Yeah the purpose is too find leaked credentials.
This is the same as #trufflehog that is written in #golang https://github.com/trufflesecurity/trufflehog -
@matzipan 😂 Yeah the purpose is too find leaked credentials.
This is the same as #trufflehog that is written in #golang https://github.com/trufflesecurity/trufflehog -
@matzipan @divclassbutton Oh my, looks like we may have a common interest (though I think my specific problem is mostly solved at this point)!
Have you heard of #Mailspring and #JMAP?The former is an Apple Mail-Like IMAP client and the latter is an IMAP alternative that eases building clients.
-
This sent me on a months long chase (https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4476#note_1474978). I told myself this was worth it because it impacts a lot of people.
After a few months of frustration and very little input from the maintainers, I gave up and wrote my own simplified version. This actually took less time. My MR is still a WIP (https://github.com/matzipan/envoyer/pull/232) but today is the first day where displaying the large list of emails works again end to end.
-
I've been working on this ticket (https://github.com/matzipan/envoyer/issues/227) for way too long.
The main reason for the ticket was that when I would load new emails as they are received from the server, with ListBox you would not be able to keep the currently open selection.
So I moved to ListView, the new API. But then I hit a GTK bug which impacts a lot of people (https://gitlab.gnome.org/GNOME/gtk/-/issues/2971). So I did what any good samaritan would do: (try to) fix it upstream.
-
That time of the year when I feel the urge to write my own build/integration system again.
#Bazel is a pain to extend and has many idiosyncracies. Also code base is way too complex and hard to penetreate. It feels generally stuck in a local maximum.
#Buildstream is pretty cool and extensible but variation support is not very elegant. It also still needs an inner build system. Also yaml 😒
#Pants seemed to be a step in the right direction. Amazingly simple extensibility. But still felt like the the build variation capabilites were not that strong. Also no support for C++.
I like starlark itself.
Does anybody know of any build system "framework" which I can just plug an play on a build tree so that I don't have to write the ugly parts of dealing with the compiler and focus on building the nice constructs for describing that build tree?
-
That time of the year when I feel the urge to write my own build/integration system again.
#Bazel is a pain to extend and has many idiosyncracies. Also code base is way too complex and hard to penetreate. It feels generally stuck in a local maximum.
#Buildstream is pretty cool and extensible but variation support is not very elegant. It also still needs an inner build system. Also yaml 😒
#Pants seemed to be a step in the right direction. Amazingly simple extensibility. But still felt like the the build variation capabilites were not that strong. Also no support for C++.
I like starlark itself.
Does anybody know of any build system "framework" which I can just plug an play on a build tree so that I don't have to write the ugly parts of dealing with the compiler and focus on building the nice constructs for describing that build tree?
-
That time of the year when I feel the urge to write my own build/integration system again.
#Bazel is a pain to extend and has many idiosyncracies. Also code base is way too complex and hard to penetreate. It feels generally stuck in a local maximum.
#Buildstream is pretty cool and extensible but variation support is not very elegant. It also still needs an inner build system. Also yaml 😒
#Pants seemed to be a step in the right direction. Amazingly simple extensibility. But still felt like the the build variation capabilites were not that strong. Also no support for C++.
I like starlark itself.
Does anybody know of any build system "framework" which I can just plug an play on a build tree so that I don't have to write the ugly parts of dealing with the compiler and focus on building the nice constructs for describing that build tree?
-
That time of the year when I feel the urge to write my own build/integration system again.
#Bazel is a pain to extend and has many idiosyncracies. Also code base is way too complex and hard to penetreate. It feels generally stuck in a local maximum.
#Buildstream is pretty cool and extensible but variation support is not very elegant. It also still needs an inner build system. Also yaml 😒
#Pants seemed to be a step in the right direction. Amazingly simple extensibility. But still felt like the the build variation capabilites were not that strong. Also no support for C++.
I like starlark itself.
Does anybody know of any build system "framework" which I can just plug an play on a build tree so that I don't have to write the ugly parts of dealing with the compiler and focus on building the nice constructs for describing that build tree?
-
Watching @AdrianVovk 's systemd-homed talk streamed from Denver #guadec at Berlin #miniguadec
-
Watching @AdrianVovk 's systemd-homed talk streamed from Denver #guadec at Berlin #miniguadec
-
Watching @AdrianVovk 's systemd-homed talk streamed from Denver #guadec at Berlin #miniguadec
-
Watching @AdrianVovk 's systemd-homed talk streamed from Denver #guadec at Berlin #miniguadec
-
Enjoying #gnome #miniguadec in my new stack t-shirt
-
Enjoying #gnome #miniguadec in my new stack t-shirt
-
-
Enjoying #gnome #miniguadec in my new stack t-shirt
-
@lebout2canap Most of the stuff just works, since it's just adwaita. But I was just writing about this on the matrix channel. As far as I can tell iOS does some (clever) lightness inversion in some contexts (presuambly when there's no background color defined). This should not be difficult to achieve.
If you have any ideas, feel free to chip in: #envoyer:gnome.org on matrix
-
0.3 milestone progressing.
Non-Gmail IMAP is usable now. Just finished redesigning the setup dialog with support for IMAP.
Next up will improve the email renderer, dark mode support and folder content updates.
-
Cleaned up the hackfest work and got it merged. Email rendering is also back!
I should probably not delay writing the integration tests any longer, so I can keep posting interesting screenshots without leaking personal info.
-
-
Had a great time hacking on Envoyer at the GNOME 45 Hackfest.
Finally got the chance to adopt Adwaita!!!!
This also means that I could play with the adaptive layout work introduced by @alice. Screenshots below show Envoyer adapting its layout.
Some bugs in the Envoyer list widgets meant that emails don't show up yet - I need to follow-up on this soon.
-
@omgubuntu @cassidy I honestly prefer App Center. Store implies buying and consuming which is a different nuance. #bikeshedding
-
-