WP 43S

[rprosperi]

(05-24-2019 05:05 AM)Dan Wrote:  

(05-23-2019 04:11 PM)Paolo Wrote:  Years ago, when the WP 43S project was taking shape, I made some suggestions to the members of WP 34S team on what I would have liked on the new machine...Of course, I will rely on the usual good will of the developers :-) I’m in no way able to code them.

Mmmm...you can't help even a little? I don't think it's realistic (or fair) to make a wish list of what you would like to see implemented and then sit back with your arms crossed and say "I'm in no way able to code them".

I agree it's not reasonable to simply post a request for such a simple list and then hope/expect it will be included, but for a different reason than Dan, as not everyone that could contribute has the necessary coding skills.

Perhaps some people involved with the project know what these features are intended for, what type of applications could use them, what type of problem they help to solve, etc. but I sure don't and I imagine most folks in the community don't either.

When making such a request, I suggest you describe how such features are useful and try to seek support for some or all of them from the community. Perhaps with some insight as to how such features could be used, more members would join in and support your request and show the team creating the 43S that there is indeed widespread demand for them.

Also, regarding the updated constants, why not include a link to the source of the items, discussion of the changes, etc.

In short, a collaborative approach to requesting features, accompanied by support from lots of potential users is far more likely to be considered for inclusion by the dev. team. For a volunteer project, the request to add some complex totally new features, coming from a single user that doesn't even attempt to justify said inclusion is not likely to be given any realistic priority. Offered as food for thought, not criticism.