wayland-explorer
lowdefy
wayland-explorer | lowdefy | |
---|---|---|
25 | 49 | |
175 | 2,553 | |
- | 0.7% | |
7.8 | 9.6 | |
13 days ago | 5 days ago | |
TypeScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wayland-explorer
-
PCSX2 Disables Wayland Support
Wayland is good until you hit the corner cases that they decided to abandon, without leaving any alternatives. We can always have extra protocol that can be optionally enabled, but good luck with standardizing that. It feels as if Wayland people are abusing their committee to keep Wayland as-is, instead of extending it. The protocol dashboard[1] doesn't look exactly good.
[1]: https://wayland.app/protocols/
-
Inter-process Communication between two programs on Linux.
Wayland is itself an IPC system (that uses UNIX domain sockets). I would make a custom Wayland protocol (if there isn't already an appropriate one available, look here: https://wayland.app/protocols/). You can define the protocol in XML and generate the boilerplate code in C using wayland-scanner. I assume smithay also has an equivalent of wayland-scanner.
-
The reality of Wayland input methods in 2022
https://wayland.app/protocols/ and https://wayland.freedesktop.org/docs/html/ are just API references.
-
Swingland: Recreating Java Swing for Wayland
Given I will be using most of the Wayland protocol to achieve anything (it's minimal) and Wayland is well specified then the 'start at the bottom and build up' design pattern fits. Wayland has a wire protocol based on a Unix socket, and usefully Java has supported Unix sockets since release 16, so I can write everything in Java to (de)serialise messages. This gets me going quickly, providing positive feedback that I'm on the right track..
-
Red Hat considers Xorg “deprecated” and will remove it in the next RHEL
The core is bare-bones, there are numerous standard protocols since, and many other are in standardization. Here is a site to review their state: https://wayland.app/protocols/
-
Unix philosophy and compositor development
There is some lock-in in some places where tools adopt a protocol that is only implemented by wlroots compositors, or only implemented by KDE, etc, but I suspect this will improve over time as protocols stabilise ( and you can browse the available protocols here: https://wayland.app/protocols/ )
- Wayland Explorer
-
X12
This link comes up in literally every Wayland thread and it is even more bullshit now than it was in 2013 when it was first posted (and it was bullshit then too). It is titled "the real story" but it is quite the opposite.
A few key points:
1) he laughs at how X has a bunch of extensions. https://wayland.app/protocols/ hypocrites much. In 2013, since it was completely unusable, it probably didn't have many. But turns out real world use leads to "useless" features being reimplemented.
2) he complains about how X.org has broad hardware compatibility. As if that's a bad thing. Meanwhile wayland, even now it still doesn't work reliably on half the graphics chips on the market.
3) It complains that certain X features are not fully network transparent. True, but most are and you can detect at runtime and gracefully degrade. Wayland "fixes" this by just dropping the whole feature.
4) it flat-out lies saying the X server does nothing yet it is so much hard to maintain code. The core X protocol provides backward compatibility and is rock solid (and really easy to impelment from scratch btw, someone did it in Javascript for a tutorial for crying out loud). Meanwhile the Wayland compositor keeps accumulating everything because of point 1. Need a screenshot? Add it it the compositor. Need a hotkey? Add it to the compositor. Need drag and drop? Add it to the compositor. Need a notification icon? Add it to the compositor. In X, all those are peer to peer. Graphics are actually a relatively small part of a graphical user interface, something Wayland is still slow to learn.
5) He complains that certain applications are written inefficiently with blocking calls which is inefficient over a network connection. Wayland's calls are ALL blocking and just has no network connection.
6) Complains that X may draw things unnecessarily. Indeed... but there's an extension to disable that. Easy fix. Wayland even uses the same drivers!
- A better way to read Wayland documentation
-
Is it placebo or is X11 more stable than Wayland
So that brings me to Wayland Protocols!. In X11 land, X11 defines a lot of behaviors for you. There is no such definition in Wayland-land by design - this is to give compositors a lot more freedom and flexibility in how they function. It also means that it required time for protocols to develop to cover all of the things that we would need in a desktop window compositor to bring it up to snuff for desktop usage. These protocols evolved through the past 4-5 years of everybody seeing it's shortcomings on a Desktop system compared to a mobile phone based UI. With the latest fractional scaling protocol we have more or less finally "closed the gap" between Wayland and Xorg on the desktop - it's just a matter of compositors implementing full support for all of the protocols people want.
lowdefy
-
Pkl, a Programming Language for Configuration
I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.
I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.
Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?
See Lowdefy:
https://lowdefy.com/
https://github.com/lowdefy/lowdefy
-
Show HN: Retool AI
Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!
Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)
https://github.com/lowdefy/lowdefy
-
Launch HN: Refine (YC S23) – Open-Source Retool for Enterprise
Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy
co-founder here :)
-
The Surprising Power of Documentation
100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.
We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.
This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.
1 - https://github.com/lowdefy/lowdefy
-
how to choose a tech stack for a personal project
https://github.com/lowdefy/lowdefy Co-Founder here.
-
Ask HN: What have you built more than twice and wish someone had built for you?
Check out https://lowdefy.com/ they even have a sample survey app as one of their examples.
-
Looking for a workflow program, any suggestions?
You can build an app that would do this
-
AG Grid Community Roundup July 2022
Lowdefy is a low code tool that uses AG Grid as a block component, allowing you to create apps which render data in AG Grid without a lot of coding knowledge. There is a Lowdefy example using AG Grid here.
-
Story of raising VC funding for my open-source project
Shameless plug, also check out Lowdefy - https://github.com/lowdefy/lowdefy
-
Show HN: ToolJet 1.2 OSS Retool alternative with realtime multiplayer editing
I’m also going to jump in here and say try Lowdefy https://github.com/lowdefy/lowdefy - co-founder here.
We take a different angle and believe that low code should still work like code. We focus on a developer first approach.
What are some alternatives?
Pion WebRTC - Pure Go implementation of the WebRTC API
appsmith - Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
kondo - Cleans dependencies and build artifacts from your projects.
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀
tera - A template engine for Rust based on Jinja2/Django
ToolJet - Low-code platform for building business applications. Connect to databases, cloud storages, GraphQL, API endpoints, Airtable, Google sheets, OpenAI, etc and build apps using drag and drop application builder. Built using JavaScript/TypeScript. 🚀
gnome-gesture-improvements - Touchpad gesture improvements for GNOME on Wayland/X11
streamlit - Streamlit — A faster way to build and share data apps.
Zip Foundation - Effortless ZIP Handling in Swift
QR-Code-generator - High-quality QR Code generator library in Java, TypeScript/JavaScript, Python, Rust, C++, C.
rupy - HTTP App. Server and JSON DB - Shared Parallel (Atomic) & Distributed
authentik - The authentication glue you need.