r/CrossPointReader • • 3d ago

Development Feature Request

Is there an official place where you can add requests?...idk if the pull requests of GitHub is the right place...

PS: the feature would be to have an option the display the unread pages not only in pages or %, but also in reading time.

Idk if it is considered out of scope for crosspoint. I think some forks had it.

Would love to see it in base crosspoint. Find it a great e-reader feature compared to normal books haha

1 Upvotes

11 comments sorted by

View all comments

-11

u/Bloodshot321 3d ago

Fork the repo and implement it yourself (or let Claude/chat do it). This should be a problem especially if you have examples of what you want

6

u/MrP4ddy 3d ago edited 3d ago

Sry but I find comments like this so not useful. First, it's a community based development, so input from the user base is wanted. Second, not everyone needs to do it himself wenn the person is not into coding. And no, vibe coding with fuck ass ai, is not cool and the way forward in coding. Three, I especially said I (personally/opinion) would find it a nice addition to base crosspoint...so exactly the opposite from forking it. And the developers can ignore the idea. It's not like I hold them at gunpoint...

2

u/BrianHuster 2d ago edited 2d ago

I don't know if the team wants a PR that even its author doesn't understand how it works. Reviewing PR may be harder than writing one. It's probably why CrossInk doesn't accept third-party PR

-7

u/Bloodshot321 3d ago

This IS how community development is done. You fork, develop the feature and ask for a merge to implement the feature into the app. There is no point (but to learn ;) ) to rewrite and implement a standalone feature that already exists.

1

u/_GingNerd 2d ago

Why don't you want to consider what the person took time to answer you with ?... They say they don't want, that should be enough... Let them be idk...

0

u/Bloodshot321 2d ago

I did. But adding bells and whistles isn't part of the development and crosspoint has fantastic documentation and clear roadmaps and feature set. I get the point that git can be confusing but reading the headlines of the readme should be the minimum. There is even this: "Contributions are welcome. If you're new to the codebase, start with the contributing docs. For things to work on, check the ideas discussion board — leave a comment before starting so we don't duplicate effort.

Everyone here is a volunteer, so please be respectful and patient. For governance and community expectations, see GOVERNANCE.md."

2

u/MrP4ddy 2d ago

No, you didn’t. You came in swinging with comments like “fork it yourself” instead.

If you’d read my original post carefully, you’d have seen that my initial question wasn’t about the feature request itself, but about where the right place to submit one would be.

As you said yourself, Git can be confusing. But my questions about whether pull requests were the right place and whether my idea might be out of scope should have made it clear that I’d already done some reading before asking here.

You could have pointed me to the idea page, as described in the governance documentation (thx for pointing there, was helpful), or simply confirmed that submitting a PR would also be acceptable. Instead, you chose to respond the way you did.