Skip to content
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

Pizza Order Composer #18

Closed

Conversation

davearonson
Copy link
Contributor

Added Pizza Order Composer app idea.

This is an idea I've had for literally decades but never got around to even trying to implement.

First it stores people's topping (and maybe crust) preferences (optionally, just each device's owner's preferences, and then they communicate by Bluetooth, and then add any non-owners on the fly), including what they like, love, dislike, hate, or are neutral to.

Then when it's time to put together an order, say who's present and how hungry. It should look online to see what pizza places are nearby, with what toppings, crusts, sizes, etc. available for what prices. It should compose a pizza order, such as "1 thin-crust medium half-pepperoni half-mushroom plus 2 large normal-crust Hawaiians, from the Domino's at 3rd and Main", to make sure everybody gets enough to eat, maximizing their satisfaction with the choice of toppings and crust, and minimizing total price.

@sindresorhus
Copy link
Member

Can you add the description above to the readme?

See: #11

@davearonson
Copy link
Contributor Author

Okay. It would look a little odd since none of the others have a description yet, but I could make them all "###" headings and just leave space for descriptions to be written.

(It could get prices,
and maybe locations,
from assorted online sources TBD,
or just make assumptions.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you not hardwrap?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I did is called "semantic linebreaks". Yeah, it looks fugly in the actual code, but if anybody changes anything, it makes spotting the actual change much easier than if it's one long line, or wrapped to a given column size. Would you accept a compromise of putting a hard return after each sentence, rather than each concept that might get rephrased?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub supports inline diffing, so that's not a concern.

sindresorhus pushed a commit that referenced this pull request Jan 29, 2016
@sindresorhus
Copy link
Member

Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants