Open Evidlo opened 5 years ago
I agree with @azmeuk in my case I often use weight too.
Having a way to split the bills with weights on a per-bill basis makes sense to me, and I believe is filling a different gap than per-project weights.
+1 to opening a new conversation and making this clearer, hoping this time we will make it trough.
Any progress being made here? It's the only feature stopping me from using this app.
After a discussion with @zorun, we're leaning towards having two mechanisms for the weights:
When a change occurs in the default per-project weights, all bills without a specific weight defined would now use the new weights.
I am interested to help with this feature, this is dearly wanted at home :) To make echo to the past discussion, we are 6, including 3 people totally uncomfortable with tech.
I also feel not so comfortable with weights. Weights are good at project level, but for bills, it should be really easier to show percentage.
My 2 cents: this really depends on the situation but there are examples where percentages are hard to compute and don't really make sense.
For instance, 6 people go in vacation together during a week and they rent a house. They all come and go at different times. They want to split the bills by the number of days passed in the house. With percentage it is not obvious at all, with weights you just assign the number of days to people. The usecase I encounter the most is food bills repartitions for roomates : with weights you just have to count the number of meals were people were present. To that regard I find the comment of @ thoelze1 pertinent, I think I can tell real-life examples I encountered for almost all of those.
Could you please recap what is blocking this to be merged? Thanks :-)
I am interested in reopening the discussion before spending time in the code. Sadly Jimbo's branch is too outdated now to be testable out-of-the-box but at least the code is still there. @Glandos would you have a bit of time to talk about this and summarize your thoughts 🙏? Maybe we can open a new ticket too to clean all the history.
To me, the way a bill is split between members is up to the participants. It could be easy or complex, the duty of the participants is to decide based on their split criteria. In the end, their duty is to come up with a split, in either percentages, parts, or amounts. The only things the SW needs to do are: 1/ to offer the possibility to select the slit method (percentages, amounts, parts) 2/ to ensure that the total amount of the bill is covered: A/ for percentages, each should be a decimal number between 0 and 100, and the sum should be 100 B/ for amounts,each should be a positive decimal and the sum of contributions should be equal to the amount of the bill C/ for parts, each should be a positive integer.
I hope this can be developed, For my use, this is,THE missing feature (I am willing to replace Tricount).
Certain applications like Kittysplit and GroupTabs allow for splitting a bill unequally. This is useful in situations like a restaurant where one person may pay for multiple people's meals.
This can be emulated by separate bills for each check, but really the bills should be grouped together logically and the alternative is tedious.