There are three files which handle the running of Lemonade Stand. They are broken up into data, logic, and GUI drawing.

==Data: constants.py==
The easiest file to get into is constants.py. This file has collections of all the different modifiable elements in the game, along with any important constants, like starting money or lemonade price.

Each section consists of a dictionary or list, possibly containing more dictionaries. To change a value in the game, simply make the corresponding change in the file. For example, to make sugar cost $.07 per unit instead of $.05, change 'cost': 5 to 'cost': 7 under 'Sugar'.

==Logic: LemonadeMain.py==
There are a lot of methods for querying the state of the logic in here, but the most important ones are process_day_logic(), process_change(), and process_day_end()

process_day_logic() is the main method which calculates how many items you can buy, calculates how many customers show up at your shop, and how many drinks you manage to sell to your customers that day. in other words, it gets run to calculate the outcome of the 'day' phase.

process_change() runs the user's input against the change-counting algorithm to see if the user has picked the correct amount. If the amount is right, it allows the player to proceed, otherwise it prompts the player that he has not succeeded and restarts the input.

process_day_end() simply calls all events that happen at the end of the day, like random events, weather changes, etc. If a new type of event is introduced it should probably get called here.

==GUI: LemonadeGui.py==
This file is broken up into a number of small methods each tasked with drawing one discrete element of the GUI. These methods are then called by the draw() method which is in turn called when the game engine detects that something has changed on the screen.

Methods should be as modular as it makes sense for them to be, with an eye towards keeping the XO from having to draw too much too often. In other words, try to build as much as possible at once, but move anything that gets reused often to it's own method.

Lemonade Stand/Developer Documentation

2010-11-11T20:35:46Z

Qalthos:

There are three files which handle the running of Lemonade Stand. They are broken up into data, logic, and GUI drawing.

==Data: constants.py==
The easiest file to get into is constants.py. This file has collections of all the different modifiable elements in the game, along with any important constants, like starting money or lemonade price.

Each section consists of a dictionary or list, possibly containing more dictionaries. To change a value in the game, simply make the corresponding change in the file. For example, to make sugar cost $.07 per unit instead of $.05, cahnge 'cost': 5 to 'cost': 7 under 'Sugar'.

==Logic: LemonadeMain.py==
There are a lot of methods for querying the state of the logic in here, but the most important ones are process_day_logic(), process_change(), and process_day_end()

process_day_logic() is the main method which calculates how many items you can buy, calculates how many customers show up at your shop, and how many drinks you manage to sell to your customers that day. in other words, it gets run to calculate the outcome of the 'day' phase.

process_change() runs the user's input against the change-counting algorithm to see if the user has picked the correct amount. If the amount is right, it allows the player to proceed, otherwise it prompts the player that he has not succeeded and restarts the input.

process_day_end() simply calls all events that happen at the end of the day, like random events, weather changes, etc. If a new type of event is introduced it should probably get called here.

==GUI: LemonadeGui.py==
This file is broken up into a number of small methods each tasked with drawing one discrete element of the GUI. These methods are then called by the draw() method which is in turn called when the game engine detects that something has changed on the screen.

2010-10-01T02:40:17Z

Qalthos:

{{TOCright}}

[[File:Lemonade2.png|500px]]

==Description==
This is your basic "Lemonade Stand" style game, where the player manages a lemonade stand (or similar such store) and tries to make as much money as possible. The game is designed to incorporate money and fractional math skills to teach basic operations.

Localization will be implemented in the final phase, with the stand being written to use more regional ingredients and products.

==Project Status==
{{:Lemonade_Stand/status}}
The project has just been re-written and should be a bit easier to localized in the future.

Any interest in helping can be directed towards project leader [[User:Qalthos|Nathaniel Case]] as well as the other listed members below, under contacts. Lemonade Stand is to be considered an open project, with updates varying based on availability. Nathaniel will continue to have interest in the project and will continue to provide assistance and input as time allows.

==Updates==
* 04/28/09: Wiki reorganized, content added
* 12/03/09: 1.1 release imminent
* 07/20/10: 2.0 release, activity page, wiki update
* 09/21/10: Add a few ideas, restructure

==Releases==
* [http://wiki.sugarlabs.org/f/fe/Lemonade_Stand_Stable.xo 1.0.0]: initial release.
* [http://gitorious.org/lemonade-stand-olpc/lemonade-stand-olpc/commit/aaf4186bf1403a6ee2892f9c606d676d78311f17 1.1.0](git tag): Updated game code.
* [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4321#version-4 2.0, XO Release 4]: Game Rewrite

==Goals==
We're looking to create a workable prototype with the ability to buy materials and sell a product.However, the most important goal is to have a working game. While possibly not feature complete, the game should have basic functions working.

===Additional Ideas & Features===
(Based on available time)

=====Completed=====
* Creating a GUI based game
* Incorporating counting of money (bills and coins) to make change
* Cool Random Events:
** Ants steal your supplies (-10% sugar)
** A lemon truck crashes in front of your stand (+10 lemons)
* Weather patterns impacting sales
* Making materials perishable to increase difficulty

=====In progress=====
* Making the program more intuitive so that it can be easily learned 
* Implementing multiple difficulties
* Redesign UI
* Advanced mode: changing the recipe for your "lemonade" 
** Strawberry Lemonade
** (Implemented but not purchaseable or usable)

=====Wishlist=====
* Creating seasons to vary prices and product demand 
* Random events that may influence supplies and/or cost and/or customers 
* "Tools" to buy to increase efficiency
** Juicer reduces lemon requirement of recipies by 1/2
* Hidden values 'advertising' and 'loyalty'
** Upgrading the stand / buying more recipies increases advertising (does not decrease)
** Prices close to customer's expectations / satisfying demand increases loyalty (decreases over time)
** Both could act as a multiplier to customer demand. (base demand x advertising x loyalty = actual demand)
* Implementing Bargaining / Haggling 
* Potential use of network, competitive, or cooperative modes 
* Choosing location of Lemonade Stand within the town, would influence sales, cost of supplies, etc. 

==Fall 2010 Milestones==
* Week 3:
** Get JT's sketches into image files
** come up with more events and weather ideas
** add recipes

* Week 4:
** new background image
** get into constants.py
** define what difficulties entail, implement lowest difficulty
** nail down ideas about overlays, startup screen

* Week 5:
** implement two difficulties, simple and insane
** Get counting game images
** implement basic splash screen

* Week 6:
** Get store images
** implement counting game

* Week 7:
** Get activity log images
** Implement store

* Week 8:
** Implement activity log
** Get images for other parts of the game (events, weather, etc.)

==Possible Difficulties==
*The current (as of 2.0) difficulty is now referred to as Impossible
*Hard difficulty is the same as Impossible, but tells you your gross profit and expenses before the counting game
*Normal difficulty is the same as Hard, but tells you your net profit as well.
*Easy difficulty is the largest difference, with simpler prices (multiples of 25) and a larger profit margin.

More ideas are encouraged

==Potential Problems==
Localization is likely to be a big problem in this game. Not simply translating the words, but also translating the idea, ie. finding out what kind of shop would be reasonable to open in a country, what it might stock, etc.

This becomes even more difficult when moving to a graphical environment. For every localized region we will need a different set of graphics depending on what the stand is selling.

==Design Decisions==
Is lemonade made at the beginning of the day (make all available lemonade at once) or on the fly (a customer asks for lemonade and it is made for them)? This is important as it impacts the resources from day to day. In the former, normally non-perishable objects like cups will be used if they can make another drink (even beyond demand), however in the latter, it makes the game easy if you stock up on resources and slowly sell them each day. This is usually mitigated by having perishable resources (lemons, etc) and variable prices.

==Educational Standards==
[http://wiki.sugarlabs.org/go/Math4Team/Resources/Curriculum_Chart Standards found here]

4.N.4 Select, use, and explain models to relate common fractions and mixed numbers (1/2, 1/3, 1/4, 1/5, 1/6, 1/8, 1/10, 1/12, and 11/2), find equivalent fractions, mixed numbers, and decimals, and order fractions

4.N.6 Exhibit an understanding of the base ten number system by reading, naming, and writing decimals between 0 and 1 up to the hundredths.

4.N.10 Select and use appropriate operations (addition, subtraction, multiplication, and division) to solve problems, including those involving money.

4.D.3 Construct, draw conclusions, and make predictions from various representations of data sets, including tables, bar graphs, pictographs, line graphs, line plots, and tallies

==Contacts==
=== Current ===
*[[User:Qalthos|Nathaniel Case]]
*[[User:Jlew| Justin Lewis]]

=== Historical ===
*[[User:Mdd8919 | Mitchell DeMarco]]
*[[User:Epsilon748 | Anthony King]]
*[[User:Echo35 | Anthony Lubrani]]
*[[User:Jsang1|Jonathan Sanger]]
*[[User:Sss1406 | Steven Schoenfeld]]

==Links and Resources==
* [http://activities.sugarlabs.org/en-US/sugar/addon/4321/ Activity Page]
* [http://gitorious.org/lemonade-stand-olpc/lemonade-stand-olpc Git Repository]
* [https://fedorahosted.org/fossrit/wiki/LemonadeStand Project Trac]

Lemonade Stand

2010-09-30T15:18:44Z

Qalthos: /* Additional Ideas & Features */

{{TOCright}}

[[File:Lemonade2.png|500px]]

==Description==
This is your basic "Lemonade Stand" style game, where the player manages a lemonade stand (or similar such store) and tries to make as much money as possible. The game is designed to incorporate money and fractional math skills to teach basic operations.

Localization will be implemented in the final phase, with the stand being written to use more regional ingredients and products.

==Project Status==
{{:Lemonade_Stand/status}}
The project has just been re-written and should be a bit easier to localized in the future.

Any interest in helping can be directed towards project leader [[User:Qalthos|Nathaniel Case]] as well as the other listed members below, under contacts. Lemonade Stand is to be considered an open project, with updates varying based on availability. Nathaniel will continue to have interest in the project and will continue to provide assistance and input as time allows.

==Updates==
* 04/28/09: Wiki reorganized, content added
* 12/03/09: 1.1 release imminent
* 07/20/10: 2.0 release, activity page, wiki update
* 09/21/10: Add a few ideas, restructure

==Releases==
* [http://wiki.sugarlabs.org/f/fe/Lemonade_Stand_Stable.xo 1.0.0]: initial release.
* [http://gitorious.org/lemonade-stand-olpc/lemonade-stand-olpc/commit/aaf4186bf1403a6ee2892f9c606d676d78311f17 1.1.0](git tag): Updated game code.
* [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4321#version-4 2.0, XO Release 4]: Game Rewrite

==Goals==
We're looking to create a workable prototype with the ability to buy materials and sell a product.However, the most important goal is to have a working game. While possibly not feature complete, the game should have basic functions working.

===Additional Ideas & Features===
(Based on available time)

=====Completed=====
* Creating a GUI based game
* Incorporating counting of money (bills and coins) to make change
* Cool Random Events:
** Ants steal your supplies (-10% sugar)
** A lemon truck crashes in front of your stand (+10 lemons)
* Weather patterns impacting sales
* Making materials perishable to increase difficulty

=====In progress=====
* Making the program more intuitive so that it can be easily learned 
* Implementing multiple difficulties
* Redesign UI
* Advanced mode: changing the recipe for your "lemonade" 
** Strawberry Lemonade
** (Implemented but not purchaseable or usable)

=====Wishlist=====
* Creating seasons to vary prices and product demand 
* Random events that may influence supplies and/or cost and/or customers 
* "Tools" to buy to increase efficiency
** Juicer reduces lemon requirement of recipies by 1/2
* Hidden values 'advertising' and 'loyalty'
** Upgrading the stand / buying more recipies increases advertising (does not decrease)
** Prices close to customer's expectations / satisfying demand increases loyalty (decreases over time)
** Both could act as a multiplier to customer demand. (base demand x advertising x loyalty = actual demand)
* Implementing Bargaining / Haggling 
* Potential use of network, competitive, or cooperative modes 
* Choosing location of Lemonade Stand within the town, would influence sales, cost of supplies, etc. 

==Fall 2010 Milestones==
* Week 3:
** Get JT's sketches into image files
** come up with more events and weather ideas
** add recipes

* Week 4:
** new background image
** get into constants.py
** define what difficulties entail, implement lowest difficulty
** nail down ideas about overlays, startup screen

* Week 5:
** implement two difficulties, simple and insane
** Get counting game images
** implement basic splash screen

* Week 6:
** Get store images
** implement counting game

* Week 7:
** Get activity log images
** Implement store

* Week 8:
** Implement activity log
** Get images for other parts of the game (events, weather, etc.)

==Potential Problems==
Localization is likely to be a big problem in this game. Not simply translating the words, but also translating the idea, ie. finding out what kind of shop would be reasonable to open in a country, what it might stock, etc.

This becomes even more difficult when moving to a graphical environment. For every localized region we will need a different set of graphics depending on what the stand is selling.

==Design Decisions==
Is lemonade made at the beginning of the day (make all available lemonade at once) or on the fly (a customer asks for lemonade and it is made for them)? This is important as it impacts the resources from day to day. In the former, normally non-perishable objects like cups will be used if they can make another drink (even beyond demand), however in the latter, it makes the game easy if you stock up on resources and slowly sell them each day. This is usually mitigated by having perishable resources (lemons, etc) and variable prices.

==Educational Standards==
[http://wiki.sugarlabs.org/go/Math4Team/Resources/Curriculum_Chart Standards found here]

4.N.4 Select, use, and explain models to relate common fractions and mixed numbers (1/2, 1/3, 1/4, 1/5, 1/6, 1/8, 1/10, 1/12, and 11/2), find equivalent fractions, mixed numbers, and decimals, and order fractions

4.N.6 Exhibit an understanding of the base ten number system by reading, naming, and writing decimals between 0 and 1 up to the hundredths.

4.N.10 Select and use appropriate operations (addition, subtraction, multiplication, and division) to solve problems, including those involving money.

4.D.3 Construct, draw conclusions, and make predictions from various representations of data sets, including tables, bar graphs, pictographs, line graphs, line plots, and tallies

==Contacts==
=== Current ===
*[[User:Qalthos|Nathaniel Case]]
*[[User:Jlew| Justin Lewis]]

=== Historical ===
*[[User:Mdd8919 | Mitchell DeMarco]]
*[[User:Epsilon748 | Anthony King]]
*[[User:Echo35 | Anthony Lubrani]]
*[[User:Jsang1|Jonathan Sanger]]
*[[User:Sss1406 | Steven Schoenfeld]]

==Links and Resources==
* [http://activities.sugarlabs.org/en-US/sugar/addon/4321/ Activity Page]
* [http://gitorious.org/lemonade-stand-olpc/lemonade-stand-olpc Git Repository]
* [https://fedorahosted.org/fossrit/wiki/LemonadeStand Project Trac]

Lemonade Stand

2010-09-24T19:19:36Z

Qalthos: Milestones

Lemonade Stand/status

2010-09-23T15:08:15Z

Qalthos:

{{Template:RIT_Status_Block

|color=green
|status=Released/Active
|status_text=Version 2.0 Released
|group_list=[[User:Qalthos|Nathaniel Case]], JT Mengel, Sarah Wagner, [[User:Mdd8919 | Mitchell DeMarco]], [[User:Epsilon748 | Anthony King]], [[User:Echo35 | Anthony Lubrani]], [[User:Jsang1|Jonathan Sanger]], [[User:Sss1406 | Steven Schoenfeld]], [[User:Jlew | Justin Lewis]]
}}

User:Qalthos

2010-09-21T14:57:57Z

Qalthos: /* Contact Info */

====Skills====
Fair Python experience

====Project====
[[Lemonade Stand]]

Wooo 2.0!

====Contact Info====
email: Qalthos@gmail.com

User:Qalthos

2010-09-21T14:57:38Z

Qalthos: /* Project */

====Skills====
Fair Python experience

====Project====
[[Lemonade Stand]]

Wooo 2.0!

====Contact Info====
email: ndc8551@rit.edu

Lemonade Stand

2010-09-21T14:56:46Z

Qalthos:

Lemonade Stand

2010-09-21T14:30:12Z

Qalthos: Added lots of ideas

2009-05-19T13:44:58Z

Qalthos: /* Additional Ideas & Features */

{{TOCright}}
==Description==
This is your basic "Lemonade Stand" style game, where the player manages a lemonade stand (or similar such store) and tries to make as much money as possible. The game is designed to incorporate money and fractional math skills to teach basic operations.

We plan to begin with a basic framework, e.g. text based command line, and work up based on free time. Ideally, the game will consist of graphics and a refined GUI front end, similar in look to the currently available flash implementations of Lemonade Stand (although more simplistic, being based in Python).

Localization will be implemented in the final phase, with the stand being written to use more regional ingredients and products.

==Project Status==
With the summer break, the work on the project will no longer be updated as regularly. Many of the involved team members have decided to continue development on an open basis dependent on time. As such, outside work on the project would be much appreciated. At this point, we are hoping to open up the project to the entire open source community. The game is ending in a working, albeit bare bones structure that would be easy to pick up from.

Continued work for the Summer of '09 and on includes the finishing of the stated goals that have yet to reach completion. The primary goal at this point is adding a graphical interface to what is still a text based game. Our development will continue to work towards the goals we have outlined, but no milestone dates will be soon forthcoming. The remaining developers have stayed on as strictly volunteer groups.

Any interest in helping can be directed towards project leader [[User:Qalthos|Nathaniel Case]] as well as the other listed members below, under contacts. Lemonade Stand is to be considered an open project, with updates varying based on availability.

==Releases==
Coming Soon! I promise!

Schedule:
1.0.0: initial release.
1.0.1: probable bugfix release.
1.1.0: updated game code.

==Goals==
We're looking to create a workable prototype with the ability to buy materials and sell a product.However, the most important goal is to have a working game. While possibly not feature complete, the game should have basic functions working.

===Additional Ideas & Features===
(Based on available time)

=====Completed=====
- Creating a GUI based game 
- Incorporating counting of money (bills and coins) to make change 
- Cool Random Events:
Ants steal your supplies
-10% sugar
A lemon truck crashes in front of your stand
+10 lemons

=====In progress=====
- Creating seasons to vary prices and product demand 
- Weather patterns impacting sales 
- Making materials perishable to increase difficulty 
- Making the program more intuitive so that it can be easily learned 

=====Wishlist=====
- Advanced mode: changing the recipe for your "lemonade" 
- Implementing Bargaining / Haggling 
- Random events that may influence supplies and/or cost and/or customers 
- Potential use of network, competitive, or cooperative modes 
- Choosing location of Lemonade Stand within the town, would influence sales, cost of supplies, etc. 

==Potential Problems==
Localization is likely to be a big problem in this game. Not simply translating the words, but also translating the idea, ie. finding out what kind of shop would be reasonable to open in a country, what it might stock, etc.

This becomes even more difficult when moving to a graphical environment. For every localized region we will need a different set of graphics depending on what the stand is selling.

==Updates and Milestones==

===Updates:===

4/28: Wiki reorganized, content added

===Milestones:===

4/24: Have everyone look at the current implementations.

5/1: produce a basic 'sugarized' build to work from. Implement price fluctuations.

5/8: Move to a 'graphical interface' based off of pyGTK or pygame. Add any art we have managed to collect where it seems appropriate.

5/15: Finishing code sugarization

==Design Decisions==
Is lemonade made at the beginning of the day (make all available lemonade at once) or on the fly (a customer asks for lemonade and it is made for them)? This is important as it impacts the resources from day to day. In the former, normally non-perishable objects like cups will be used if they can make another drink (even beyond demand), however in the latter, it makes the game easy if you stock up on resources and slowly sell them each day. This is usually mitigated by having perishable resources (lemons, etc) and variable prices.

==Educational Standards==
[http://wiki.sugarlabs.org/go/Math4Team/Resources/Curriculum_Chart Standards found here]

4.N.4 Select, use, and explain models to relate common fractions and mixed numbers (1/2, 1/3, 1/4, 1/5, 1/6, 1/8, 1/10, 1/12, and 11/2), find equivalent fractions, mixed numbers, and decimals, and order fractions

4.N.6 Exhibit an understanding of the base ten number system by reading, naming, and writing decimals between 0 and 1 up to the hundredths.

4.N.10 Select and use appropriate operations (addition, subtraction, multiplication, and division) to solve problems, including those involving money.

4.D.3 Construct, draw conclusions, and make predictions from various representations of data sets, including tables, bar graphs, pictographs, line graphs, line plots, and tallies

==Contacts==
*[[User:Qalthos|Nathaniel Case]]
*[[User:Mdd8919 | Mitchell DeMarco]]
*[[User:Epsilon748 | Anthony King]]
*[[User:Echo35 | Anthony Lubrani]]
*[[User:Jsang1|Jonathan Sanger]]
*[[User:Sss1406 | Steven Schoenfeld]]

==Links and Resources==
Coming soon!

==Code so far==
<pre>
#!/usr/env python
# -*- coding: cp1252 -*-
import random
from counting import play_Money

#Generisize the names of supplys to make it easily editable
#[0] = name of the stand, [1] = first supply, [2] = second supply, [3] = third supply, [4] = the object that is being sold
variables = ['Lemonade Stand','cups','lemons','sugar','cups']

print 'Welcome to ' + variables[0]

#Random weather event, if its a hot day all stock will sell,
# if its a normal day, 90% will sell, and if its a raining day 80% will sell

def weather_Change( ):
global weather
weather = random.randint( -1, 1 )

if weather == -1:
print "It looks like its going to rain tomorrow"
elif weather == 0:
print "Its a normal day tomorrow"
elif weather == 1:
print "Tomorrow looks to be very hot"

#Format the input text, and make it return a 0 if input is incorrect
def take_input(text, default = 0):
try:
in_text = input(text+" ["+`default`+"]: ")
except:
return default
if in_text < 0:
in_text = 0

return in_text

#Declare a random event, More events can be added easily by building a new case statment
def random_Event():
global stored_sugar, stored_lemons, stored_cups
event = random.randint(0, 10)

if event == 0:

if stored_sugar > 10:
stored_sugar -= 10
print 'Ants steal your supplies!'
else:
stored_sugar = 0

elif event == 1:

print 'A lemon truck crashes in front of your stand!'
stored_lemons += 10

elif event == 2:

print 'It starts raining cups!'
stored_cups += 10

print ""

#Decreases currently the supply's by 10% each day
def supply_Decay():
global stored_sugar, stored_lemons, stored_cups
if stored_sugar > 0:
stored_sugar -= 10 % stored_sugar
if stored_lemons > 0:
stored_lemons -= 10 % stored_lemons
if stored_cups > 0:
stored_cups -= 10% stored_cups

return -1

# default values
cup_price = .25
lemon_price = 1.00
sugar_price = .05
weather = 0
product_price = 1.50

#starting resources
bank = 100

stored_cups = 0
stored_lemons = 0
stored_sugar = 0

# take in input
num_days = take_input("How many days would you like to play for?", 30)

for day in range(1, num_days + 1):

print ""
print "____________________"
print " Day number " + `day`
print "¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯"
print ""

random_Event()

print "You have "+`stored_cups`+ " " + variables[1] + ", " +`stored_lemons`+ " " + variables[2] + ", and "+`stored_sugar`+ " " + variables[3] + " left."

print variables[1] + " price: $" + `cup_price` + " " + variables[2] + " price: $"+ "%.2f" % lemon_price + " " + variables[3] + " price: $"+ "%.2f" % sugar_price

expenses = 0

cost_over = 1

#Checks to make sure you dont go over your bank amount while buying.

while cost_over == 1:

potential_expense = 0
in_num = take_input("How many " + variables[1])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * cup_price
stored_cups += in_num
else:
print 'You cant afford that many ' + variables[1]

cost_over = 1

while cost_over == 1:

potential_expense = 0
in_num = take_input("How many " + variables[2])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * lemon_price
stored_lemons += in_num
else:
print 'You cant afford that many ' + variables[2]

cost_over = 1

while cost_over == 1:

potential_expense = 0
in_num = take_input("How much " + variables[3])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * sugar_price
stored_sugar += in_num

else:
print 'You can not afford that many ' + variables[3]

# Find the lowest amount of supplys, and make that many of lemonade that day
sales = max(min(stored_cups, stored_lemons, stored_sugar),0)

# Option 2: make as many as requested
stored_cups -= sales
stored_lemons -= sales
stored_sugar -= sales

if weather == 0:
sales -= 10 % sales
elif weather == -1:
sales -= 20 % sales

print `sales`+ ' ' + variables[4]+ " made for $"+ "%.2f" % expenses

profit = sales * product_price
print `sales`+ " " + variables[4] +" were sold today for $"+ "%.2f" % profit

print "You made $"+ "%.2f" % (profit - expenses)+" today."

if (profit - expenses) <= 0:

print "You lost money today"

else:

#If you didnt lose money that day, play the small money game to put away your change
#If you put away change right, you get to keep the profit, otherwise you lose it

print "You go to put profits away"

if play_Money( int(profit - expenses) ) == 1:
print "you put the money away correctly"
bank += profit - expenses
else:
print "You lost the money when putting it away"

print "Current funds: $"+ "%.2f" % bank

#Decrease the supply's by 10%
#Warn for the next days weather

supply_Decay()
weather_Change()

print

print "Done!"

</pre>

Counting code

<pre>

dollar = 1
quarter = .25
dime = .10
nickel = .05
penny = .01

def take_input(text, default = 0):
try:
in_text = input(text+" ["+`default`+"]: ")
except:
return default
if in_text < 0:
in_text = 0

return in_text

def play_Money( money_Find ):

global quarter, dime, nickel, penny

total = 0

#Takes the amount of money
total += dollar*take_input( "How many dollars? ")

total += quarter*take_input( "How many quarters? ")

total += dime*take_input( "How many dimes? ")

total += nickel*take_input( "How many nickels? ")

total += penny*take_input( "How many pennies? ")

if total == money_Find:
return 1

else:
return -1

</pre>

File:Lemon Icon.svg

2009-05-19T05:37:35Z

Qalthos: uploaded a new version of "Image:Lemon Icon.svg": One that works?

Math4Team/RIT/Projects

2009-05-19T04:37:09Z

Qalthos: /* Image:Lemon_Icon.svgLemonade Stand */

{{TOCright}}
==[[Flash Card Game - Assimilate]]==
This project is one of [http://wiki.sugarlabs.org/go/Math4Team/RIT/Projects many small projects] focused on developing 4th grade math games which will run on the OLPC XO. We are [http://wiki.sugarlabs.org/go/Math4Team/RIT/Students RIT students] who are working on this with the help of other developers who become interested in our projects.
The focus of this project is to turn an existing game ([http://wiki.laptop.org/go/Assimilate Assimilate]) into a math based flash card game which will hopefully be included on future XO's.

Group members:
[[User:Dbj4366|Dennis Jalbert]], [[User:Jck1089|James Kolb]], [[User:bjr9081|Brendan Reen]]

==[[Fun Towers]]==
Fun Towers is a pre-existing game that can be found online in several version (http://www.funnytowers.com/ is one example) that has been ported to the XO, written in Squeak. Our team is modifying this purely numerical/card based game into one that can be used as a teaching tool as part of the 4th grade math project.
Our initial goals in modifying the pre-existing game remain relatively simple and achievable, and our goal is to produce verifiable results that can be used to point to the very preliminary success of the math4 program, while more in-depth projects are still in development.
The game itself is simple, users are given a card and with it are able to remove from one of 3 pyramids of cards a card that is one greater or one lower in value. This card that has been removed is the users new card, and any cards that were covered by the removed card are now in play.

Group members are
[[User:EricMallon|Eric Mallon,]] [[User:eldrac|Tyler Bragdon,]] [[User:Cdaniels29|Chris Daniels]]

==[[Image:Lemon_Icon.svg|24px]][[Lemonade Stand]]==
Lemonade stand (or more likely, *Insert produce here* stand) is a collaboration project at RIT. It is designed to test children on fractions, working with money, estimation, and other math topics. While our time restraints limit the extent to which we can implement features, the current goal is a feature complete program even if lacking in graphics. We plan on having a system based on buying and selling commodities and an eventual season based economy.

The largest and most complex task of the project will be the introduction of a basic AI to handle the economy, the use of graphics, and localization. We are planning on introducing the game with a generic currency model while trying to find a commodity that either works worldwide, or is easy to replace for regional types. At the very least, we plan on having a feature complete text model that can be finished by other interested parties.

The RIT students currently working on the project are [[Anthony King]], [[User:Qalthos|Nathaniel Case]], [[User:Jsang1|Jonathan Sanger]], [[User:Mdd8919 | Mitchell DeMarco]], [[User:sss1406|Steven Schoenfeld]], and [[User:Echo35|Anthony Lubriani]].

==[[Math4Team/RIT/Projects/Muthris|Muthris]]==
==[[Produce Puzzle]]==
The object of the game is to solve a system of equations with unknowns represented by fruits. The player is given the column sums and row sums, and from there he must determine the value of each fruit. The game difficulty can be changed, and it ranges from solving 3x3 fruit equations, all the way up to 9x9 fruit grids.

We, [[Abbi Honeycutt]] and [[Kennedy Kong]] from Rochester Institute of Technology, has taken over this project. Previous creators were Matthew Michihara, Elizabeth Deng, and Aaron Macris from University of Southern California during their "Code for a cause OLPC Hack-a-thon".
==[[/Question Support API|Question Support API]]==
The purpose of the Question Support API is to provide a unified method for Activities to access standardized format question files. The API currently supports the use of multiple choice questions with a single correct answer and no partial credit. Currently, the API only reports questions in a plain text format from Moodle format question files.

Group members are
[[User:Enimihil|Greg Stevens]], [[User:Jfinney|Jameson Finney]], [[User:Bbl5660|Brian Long]]

==[[Teacher Reporting]]==
We, Wesley Dillingham, and Jeremiah Green hope to utilize modified Moodle modules and a customized XS School Server operating system. Our goal is to allow results and / or grades, from student activities to be readily available to teachers. Based on their wants and needs, the teachers can then generate custom reports on a class or student and have the ability to determine what types of problems students are finding most difficult. Additionally we would like to implement logic in the module which analyzes student activity and checks for a strict yes or no interpretation of whether or not each student understands various curriculum standards. In the end we imagine the XS environment running on an XO itself, allowing the teachers the same portability as the students.

==[[Tips & Tricks]]==
==[[Complaints & Problems]]==

[[Category:Idea]]

Math4Team/RIT/Projects

2009-05-19T04:35:38Z

Qalthos:

{{TOCright}}
==[[Flash Card Game - Assimilate]]==
This project is one of [http://wiki.sugarlabs.org/go/Math4Team/RIT/Projects many small projects] focused on developing 4th grade math games which will run on the OLPC XO. We are [http://wiki.sugarlabs.org/go/Math4Team/RIT/Students RIT students] who are working on this with the help of other developers who become interested in our projects.
The focus of this project is to turn an existing game ([http://wiki.laptop.org/go/Assimilate Assimilate]) into a math based flash card game which will hopefully be included on future XO's.

Group members:
[[User:Dbj4366|Dennis Jalbert]], [[User:Jck1089|James Kolb]], [[User:bjr9081|Brendan Reen]]

==[[Fun Towers]]==
Fun Towers is a pre-existing game that can be found online in several version (http://www.funnytowers.com/ is one example) that has been ported to the XO, written in Squeak. Our team is modifying this purely numerical/card based game into one that can be used as a teaching tool as part of the 4th grade math project.
Our initial goals in modifying the pre-existing game remain relatively simple and achievable, and our goal is to produce verifiable results that can be used to point to the very preliminary success of the math4 program, while more in-depth projects are still in development.
The game itself is simple, users are given a card and with it are able to remove from one of 3 pyramids of cards a card that is one greater or one lower in value. This card that has been removed is the users new card, and any cards that were covered by the removed card are now in play.

Group members are
[[User:EricMallon|Eric Mallon,]] [[User:eldrac|Tyler Bragdon,]] [[User:Cdaniels29|Chris Daniels]]

==[[Image:Lemon_Icon.svg]][[Lemonade Stand]]==
Lemonade stand (or more likely, *Insert produce here* stand) is a collaboration project at RIT. It is designed to test children on fractions, working with money, estimation, and other math topics. While our time restraints limit the extent to which we can implement features, the current goal is a feature complete program even if lacking in graphics. We plan on having a system based on buying and selling commodities and an eventual season based economy.

The largest and most complex task of the project will be the introduction of a basic AI to handle the economy, the use of graphics, and localization. We are planning on introducing the game with a generic currency model while trying to find a commodity that either works worldwide, or is easy to replace for regional types. At the very least, we plan on having a feature complete text model that can be finished by other interested parties.

The RIT students currently working on the project are [[Anthony King]], [[User:Qalthos|Nathaniel Case]], [[User:Jsang1|Jonathan Sanger]], [[User:Mdd8919 | Mitchell DeMarco]], [[User:sss1406|Steven Schoenfeld]], and [[User:Echo35|Anthony Lubriani]].

==[[Math4Team/RIT/Projects/Muthris|Muthris]]==
==[[Produce Puzzle]]==
The object of the game is to solve a system of equations with unknowns represented by fruits. The player is given the column sums and row sums, and from there he must determine the value of each fruit. The game difficulty can be changed, and it ranges from solving 3x3 fruit equations, all the way up to 9x9 fruit grids.

We, [[Abbi Honeycutt]] and [[Kennedy Kong]] from Rochester Institute of Technology, has taken over this project. Previous creators were Matthew Michihara, Elizabeth Deng, and Aaron Macris from University of Southern California during their "Code for a cause OLPC Hack-a-thon".
==[[/Question Support API|Question Support API]]==
The purpose of the Question Support API is to provide a unified method for Activities to access standardized format question files. The API currently supports the use of multiple choice questions with a single correct answer and no partial credit. Currently, the API only reports questions in a plain text format from Moodle format question files.

Group members are
[[User:Enimihil|Greg Stevens]], [[User:Jfinney|Jameson Finney]], [[User:Bbl5660|Brian Long]]

==[[Teacher Reporting]]==
We, Wesley Dillingham, and Jeremiah Green hope to utilize modified Moodle modules and a customized XS School Server operating system. Our goal is to allow results and / or grades, from student activities to be readily available to teachers. Based on their wants and needs, the teachers can then generate custom reports on a class or student and have the ability to determine what types of problems students are finding most difficult. Additionally we would like to implement logic in the module which analyzes student activity and checks for a strict yes or no interpretation of whether or not each student understands various curriculum standards. In the end we imagine the XS environment running on an XO itself, allowing the teachers the same portability as the students.

==[[Tips & Tricks]]==
==[[Complaints & Problems]]==

[[Category:Idea]]

Lemonade Stand

2009-05-18T20:21:57Z

Qalthos:

{{TOCright}}
==Description==
This is your basic "Lemonade Stand" style game, where the player manages a lemonade stand (or similar such store) and tries to make as much money as possible. The game is designed to incorporate money and fractional math skills to teach basic operations.

We plan to begin with a basic framework, e.g. text based command line, and work up based on free time. Ideally, the game will consist of graphics and a refined GUI front end, similar in look to the currently available flash implementations of Lemonade Stand (although more simplistic, being based in Python).

Localization will be implemented in the final phase, with the stand being written to use more regional ingredients and products.

==Project Status==
With the summer break, the work on the project will no longer be updated as regularly. Many of the involved team members have decided to continue development on an open basis dependent on time. As such, outside work on the project would be much appreciated. At this point, we are hoping to open up the project to the entire open source community. The game is ending in a working, albeit bare bones structure that would be easy to pick up from.

Continued work for the Summer of '09 and on includes the finishing of the stated goals that have yet to reach completion. The primary goal at this point is adding a graphical interface to what is still a text based game. Our development will continue to work towards the goals we have outlined, but no milestone dates will be soon forthcoming. The remaining developers have stayed on as strictly volunteer groups.

Any interest in helping can be directed towards project leader [[User:Qalthos|Nathaniel Case]] as well as the other listed members below, under contacts. Lemonade Stand is to be considered an open project, with updates varying based on availability.

==Releases==
Coming Soon! I promise!

Schedule:
1.0.0: initial release.
1.0.1: probable bugfix release.
1.1.0: updated game code.

==Goals==
We're looking to create a workable prototype with the ability to buy materials and sell a product.However, the most important goal is to have a working game. While possibly not feature complete, the game should have basic functions working.

===Additional Ideas & Features===
(Based on available time)

- Creating a GUI based game 
- Incorporating counting of money (bills and coins) to make change 
- Creating seasons to vary prices and product demand 
- Weather patterns impacting sales 
- Making materials perishable to increase difficulty 
- Making the program more intuitive so that it can be easily learned 
- Advanced mode: changing the recipe for your "lemonade" 
- Implementing Bargaining / Haggling 
- Random events that may influence supplies and/or cost and/or customers 
- Potential use of network, competitive, or cooperative modes 
- Choosing location of Lemonade Stand within the town, would influence sales, cost of supplies, etc. 

- Cool Random Events:

Ants steal your supplies
-10% sugar
A lemon truck crashes in front of your stand
+10 lemons

==Potential Problems==
Localization is likely to be a big problem in this game. Not simply translating the words, but also translating the idea, ie. finding out what kind of shop would be reasonable to open in a country, what it might stock, etc.

This becomes even more difficult when moving to a graphical environment. For every localized region we will need a different set of graphics depending on what the stand is selling.

==Updates and Milestones==

===Updates:===

4/28: Wiki reorganized, content added

===Milestones:===

4/24: Have everyone look at the current implementations.

5/1: produce a basic 'sugarized' build to work from. Implement price fluctuations.

5/8: Move to a 'graphical interface' based off of pyGTK or pygame. Add any art we have managed to collect where it seems appropriate.

5/15: Finishing code sugarization

==Design Decisions==
Is lemonade made at the beginning of the day (make all available lemonade at once) or on the fly (a customer asks for lemonade and it is made for them)? This is important as it impacts the resources from day to day. In the former, normally non-perishable objects like cups will be used if they can make another drink (even beyond demand), however in the latter, it makes the game easy if you stock up on resources and slowly sell them each day. This is usually mitigated by having perishable resources (lemons, etc) and variable prices.

==Educational Standards==
[http://wiki.sugarlabs.org/go/Math4Team/Resources/Curriculum_Chart Standards found here]

4.N.4 Select, use, and explain models to relate common fractions and mixed numbers (1/2, 1/3, 1/4, 1/5, 1/6, 1/8, 1/10, 1/12, and 11/2), find equivalent fractions, mixed numbers, and decimals, and order fractions

4.N.6 Exhibit an understanding of the base ten number system by reading, naming, and writing decimals between 0 and 1 up to the hundredths.

4.N.10 Select and use appropriate operations (addition, subtraction, multiplication, and division) to solve problems, including those involving money.

4.D.3 Construct, draw conclusions, and make predictions from various representations of data sets, including tables, bar graphs, pictographs, line graphs, line plots, and tallies

==Contacts==
*[[User:Qalthos|Nathaniel Case]]
*[[User:Mdd8919 | Mitchell DeMarco]]
*[[User:Epsilon748 | Anthony King]]
*[[User:Echo35 | Anthony Lubrani]]
*[[User:Jsang1|Jonathan Sanger]]
*[[User:Sss1406 | Steven Schoenfeld]]

==Links and Resources==
Coming soon!

==Code so far==
<pre>
#!/usr/env python
# -*- coding: cp1252 -*-
import random
from counting import play_Money

#Generisize the names of supplys to make it easily editable
#[0] = name of the stand, [1] = first supply, [2] = second supply, [3] = third supply, [4] = the object that is being sold
variables = ['Lemonade Stand','cups','lemons','sugar','cups']

print 'Welcome to ' + variables[0]

#Random weather event, if its a hot day all stock will sell,
# if its a normal day, 90% will sell, and if its a raining day 80% will sell

def weather_Change( ):
global weather
weather = random.randint( -1, 1 )

if weather == -1:
print "It looks like its going to rain tomorrow"
elif weather == 0:
print "Its a normal day tomorrow"
elif weather == 1:
print "Tomorrow looks to be very hot"

#Format the input text, and make it return a 0 if input is incorrect
def take_input(text, default = 0):
try:
in_text = input(text+" ["+`default`+"]: ")
except:
return default
if in_text < 0:
in_text = 0

return in_text

#Declare a random event, More events can be added easily by building a new case statment
def random_Event():
global stored_sugar, stored_lemons, stored_cups
event = random.randint(0, 10)

if event == 0:

if stored_sugar > 10:
stored_sugar -= 10
print 'Ants steal your supplies!'
else:
stored_sugar = 0

elif event == 1:

print 'A lemon truck crashes in front of your stand!'
stored_lemons += 10

elif event == 2:

print 'It starts raining cups!'
stored_cups += 10

print ""

#Decreases currently the supply's by 10% each day
def supply_Decay():
global stored_sugar, stored_lemons, stored_cups
if stored_sugar > 0:
stored_sugar -= 10 % stored_sugar
if stored_lemons > 0:
stored_lemons -= 10 % stored_lemons
if stored_cups > 0:
stored_cups -= 10% stored_cups

return -1

# default values
cup_price = .25
lemon_price = 1.00
sugar_price = .05
weather = 0
product_price = 1.50

#starting resources
bank = 100

stored_cups = 0
stored_lemons = 0
stored_sugar = 0

# take in input
num_days = take_input("How many days would you like to play for?", 30)

for day in range(1, num_days + 1):

print ""
print "____________________"
print " Day number " + `day`
print "¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯"
print ""

random_Event()

print "You have "+`stored_cups`+ " " + variables[1] + ", " +`stored_lemons`+ " " + variables[2] + ", and "+`stored_sugar`+ " " + variables[3] + " left."

print variables[1] + " price: $" + `cup_price` + " " + variables[2] + " price: $"+ "%.2f" % lemon_price + " " + variables[3] + " price: $"+ "%.2f" % sugar_price

expenses = 0

cost_over = 1

#Checks to make sure you dont go over your bank amount while buying.

while cost_over == 1:

potential_expense = 0
in_num = take_input("How many " + variables[1])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * cup_price
stored_cups += in_num
else:
print 'You cant afford that many ' + variables[1]

cost_over = 1

while cost_over == 1:

potential_expense = 0
in_num = take_input("How many " + variables[2])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * lemon_price
stored_lemons += in_num
else:
print 'You cant afford that many ' + variables[2]

cost_over = 1

while cost_over == 1:

potential_expense = 0
in_num = take_input("How much " + variables[3])
potential_expense = expenses + (in_num * cup_price)

if potential_expense < bank:
cost_over = -1
expenses += in_num * sugar_price
stored_sugar += in_num

else:
print 'You can not afford that many ' + variables[3]

# Find the lowest amount of supplys, and make that many of lemonade that day
sales = max(min(stored_cups, stored_lemons, stored_sugar),0)

# Option 2: make as many as requested
stored_cups -= sales
stored_lemons -= sales
stored_sugar -= sales

if weather == 0:
sales -= 10 % sales
elif weather == -1:
sales -= 20 % sales

print `sales`+ ' ' + variables[4]+ " made for $"+ "%.2f" % expenses

profit = sales * product_price
print `sales`+ " " + variables[4] +" were sold today for $"+ "%.2f" % profit

print "You made $"+ "%.2f" % (profit - expenses)+" today."

if (profit - expenses) <= 0:

print "You lost money today"

else:

#If you didnt lose money that day, play the small money game to put away your change
#If you put away change right, you get to keep the profit, otherwise you lose it

print "You go to put profits away"

if play_Money( int(profit - expenses) ) == 1:
print "you put the money away correctly"
bank += profit - expenses
else:
print "You lost the money when putting it away"

print "Current funds: $"+ "%.2f" % bank

#Decrease the supply's by 10%
#Warn for the next days weather

supply_Decay()
weather_Change()

print

print "Done!"

</pre>

Counting code

<pre>

dollar = 1
quarter = .25
dime = .10
nickel = .05
penny = .01

def take_input(text, default = 0):
try:
in_text = input(text+" ["+`default`+"]: ")
except:
return default
if in_text < 0:
in_text = 0

return in_text

def play_Money( money_Find ):

global quarter, dime, nickel, penny

total = 0

#Takes the amount of money
total += dollar*take_input( "How many dollars? ")

total += quarter*take_input( "How many quarters? ")

total += dime*take_input( "How many dimes? ")

total += nickel*take_input( "How many nickels? ")

total += penny*take_input( "How many pennies? ")

if total == money_Find:
return 1

else:
return -1

</pre>