-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script plugin #141
Comments
It's more of personal project. It's centered around plugins especially for reason, that everyone can easily integrate whatever they want and find useful. Lua scripting for example is perfectly appropriate. At some point we might have contrib repository for plugins, while the core is just for basic tiler functionality. E.g. even if I find lua appropriate for plugin, I don't think it belongs to core. For now I'm aware of only one external plugin and that's @sardemff7's notification-area and that's just hosted on his personal repo https://github.com/sardemff7/wayland-notification-area |
That's okay.
I have used Emacs for years and I think the only reason why it is so powerful and adapts to so many scenarios is because it is scriptable. My Emacs isn't customized to extreme levels, but it isn't basic either. One thing I dislike is Emacs Lisp and my config has been just copy'n'paste from snippets on the web. I don't believe this approach would work for C. The recompile cycle would be annoying too. All in all, Enlightenment is too buggy and is not Wayland capable. I think it's time to take responsibility for how my desktop environment behaves. Never again I should be disappointed because some cool theme or a plugin I love don't work anymore. I will give away the fancy config GUI convenience and put my hands in dirty script files to make the desktop behave the way it works better for me. Enlightenment was made for eye-candy and themability, but the theme API breaks so often that the only theme you really can use is the default one. Therefore themability isn't an argument. Also, today I care more about behaviour than eye-candy. Sorry about the rant, I know it went partially OFF-TOPIC. How much time do you think an outsider would need to spend to have a simple plugin done? Do you think there is a large API to create bindings for or is it minimal and I wouldn't have much trouble reexporting functions? Which would be the starter point? Is there any doc or should I start with the examples? How about the support, what is your preferred contact form when the subject is orbment? Is orbment an experimental project that you think it served its purpose and you plan to abandon it or are you using it as your main desktop environment and plan to support for more time?
Sounds reasonable. |
I completely agree. I use vim (and neovim) though :)
Sadly wlc and orbment is buggy as well right now. However I can again agree on your There is experimental vfs plugin in another branch of orbment, that gives plugins
Depends on scope of plugin, but for example dpms plugin should give quite good idea on
For exposing lua API, all you really need is to way to bind the functions and
plugin.h is quite well documented, the core plugins are quite nice and small. I had
IRC is preferred, I'm mainly thinking of going away from github for my future projects.
Orbment in way is not tied to wayland. I think it has potential as modular desktop On Wayland, and why I don't think it suits orbment well (rant time). For now to have functional compositor (from user point of view), you need to do the
This is all quite too much for something that doesn't care about legacy compatibilty at I originally thought I could hide all this crap under wlc. However I don't think it I would really recommend using libweston nowadays for anything wayland centric, as it's As for alternatives to wayland, I've been thinking of arcan https://arcan-fe.com/. But for certainly I can say that wayland experience to me hasn't been very pleasant. |
wow Thanks for the big response/time. Very nice to read. |
Just creating an issue to keep tracking of any efforts to add a plugin to handle scripting languages (e.g. lua).
Feel free to close it if you think it's inappropriate.
Btw, do you intend to "grow the project" or keep it as a personal project? I mean, there is no site or even a "orbment manifesto" where the purposes are stated (e.g. add features, but only if they are secure). Check https://wiki.archlinux.org/index.php/Arch_Linux#Principles to see what I mean.
I'm planning to migrate to a Wayland compositor and I reduced my list of candidates to orbment and sway. I plan to test both of them in the coming weeks.
The text was updated successfully, but these errors were encountered: