Contributions?

[Krorenshima]

So, I recently found your program through a web search (or youtube video, I can't remember) and I decided I'd like to help in possibly contributing to the project.

With my projects I mainly do JS programming, though I've dabbled within Python quite a bit.

I didn't see a contribution section within your README or site (unless I missed something), and I was wondering if you're welcome to contributions or not.

[leon-thomm]

Hi! Yeah, you didn't miss anything, there just isn't a contribution section yet, sorry. I'm really glad that you are motivated to contribute though.
The best way to contribute is by creating new nodes. Ryven itself runs quite well (at least for something I have made :P ) the only thing that's missing is content (nodes)... On the website you can find guides regarding creating new nodes.
wait, what the hell happened...

[leon-thomm]

sorry, I pressed a key on my keyboard, and all of a sudden it closed the issue. Did I mention I'm a professional?
I am opening this again since there isn't a contribution section yet.

If you know some special python libraries well or are going to dive into some, you could create nodes that include all the basic functionality of the library, that's the best contribution possible. Creating intuitive GUI for it would be the end goal, but that requires some Qt skills. And even if you're just using Ryven's built-in features (especially right-click operations aka special actions), you can still make very intuitive nodes. Although it might seem like a lot initially, it really isn't hard to program nodes but it's a quite powerful system due to the lack of restriction.

[Krorenshima]

Ah I see, so adding small features like adding a way to search by module or making settings permanent, being able to run the package through a cmd from a different directory and so on would not be good?

[leon-thomm]

Depends. I really want to keep the implementation simple (for a lot of reasons). The relationship between practical improvement of the software and increase of complexity quickly exceeds a practical value for the philosophy of this project.
However, if there are ideas for changes or features that might improve intuitiveness without significantly complicating the internal implementation (like searching for nodes by module or something), I am always open for them. For that, you can just open issues to discuss details for possible improvements.

So these kinds of contributions are appreciated as long as you follow Ryven's philosophy, that it's meant to be a simple, transparent and flexible tool instead of a highly optimized ecosystem of software.

[Krorenshima]

Aye I see, well alright then.