This article has a talk page!This page details development materials of Where's My Mickey?.
|
To do:
|
An obscure GitHub repository known as TalkingScene has the source code for a primitive build of Where's My XiYangYang?. This seems to be related to an unknown developer talk/interview.
Included in that source is the source for Where's My Mickey?, used as a reference. It has a last updated date of February 17, 2014.
Internal Project Name#
According to source path directories, it's referred to as Mickey, com.disney.Mickey_Google, and com.disney.MickeyGameApp.
- This gets a bit confusing, particularly between platforms where terminology is slightly different and the path locations have somewhat different interpretations.
- Furthermore, this changed slightly (!) in moving from Perry to Mickey - in particular, both platforms now share the same database copy/update/reset code. The reason for this is because Where's My Mickey? was built off of Where's My Perry?.
Walaber Engine#
As the name suggests, it was for Where's My Water?. Most of the contents are from Where's My Mickey?, so it's not the exact same one seen in Where's My Water?.
Almost all of the folders in wmw_spl_act_wheresmywater_750x500.swf in the wmw flash version have a direct or close C++ equivalent. The only major one missing is WaterConcept, which in the Flash version contains the code for managing fluids, dirt/rocks, and objects.1
WalaberEngine
This is the new home for the Walaber Engine. All code committed here should be thoroughly tested and passed through a code review. All code should be well documented using the doxygen commenting format and should conform to the standard.
Contents#
- WalaberGame.cpp - lists as com.disney.Mickey_Google
