【正文】 OM的解析：首先解析器讀入整個文檔，構建一個駐留內(nèi)存的樹結構，然后使用DOM API來訪問樹形結構，并獲取結構。還有就是該模塊的視圖，采用自定義的視圖方式CornerListView繼承自ListView，該方式可以實現(xiàn)更好的顯示效果，可以根據(jù)自己想要的結果進行顯示，比如實現(xiàn)ListView的圓角顯示，設置點擊之后的效果，設置手勢效果onInterceptTouchEvent() 該函數(shù)根據(jù)相應的事件顯示不同的效果。 結臺模塊的設計與實現(xiàn)結臺模塊主要根據(jù)訂單編號查詢訂單的詳細信息，將詳細信息通過一個WebView來顯示，這個是一個查詢的過程，服務器返回html格式的信息，通過WebView來顯示。 查臺模塊 客戶端結臺模塊的設計與實現(xiàn) 服務員點擊結賬按鈕之后，將數(shù)據(jù)庫服務器中OrderTbl表中的isPay列數(shù)據(jù)更新為“1”，表示已經(jīng)結算(默認值為0表示未結算)。 注銷模塊的設計與實現(xiàn)注銷模塊主要實現(xiàn)該系統(tǒng)的順利退出，當用戶點擊注銷按鈕時會彈出一個確認對話框，當點擊確定時會退出該系統(tǒng)。而Android和IPhone是手機操作系統(tǒng)的兩大巨頭，IPhone因其手機產(chǎn)品而獲得眾多消費者的青睞。Android還運用于平板電腦，電視等，具有廣闊的發(fā)展方向。另外，雖然本系統(tǒng)較小，但是卻具有很好的適用價值，能滿足用戶的基本要求。 展望該電子點菜系統(tǒng)在設計的過程中充分考慮了系統(tǒng)的可擴展性，為以后的添加新功能做了很好的鋪墊，比如比如在服務員模塊中設置一個每日推薦模塊，在這個模塊可以對菜進行分類，如涼菜和熱菜，進而滿足不同用戶的需求，另外菜的圖片的上傳，可以采用手機拍照的方式進行上傳，也可以直接從手機讀取，當然這個最好用jsp做成一個后臺管理頁面，進而方便管理員對菜的價格進行修改，或者添加新的菜，因為時間的緊迫這個功能咱暫時還沒有完成，只是在手機端做了一個管理員的界面進行了代替，簡單的實現(xiàn)了服務員帳號的增刪改功能以及菜的增刪改。本系統(tǒng)的難點在于對一些控件比如GridView和ListView，在使用時用adapter進行界面的顯示以及顯示時的系統(tǒng)的優(yōu)化問題，以及遠程操作數(shù)據(jù)庫，從服務器端封裝數(shù)據(jù)（xml和json）時遇到的一些問題，最后就是使用wifi和藍牙進行通訊，由于時間緊迫我們在本機上建立服務器，然后采用協(xié)議進行通訊，這些功能在以后都可以進行擴展。 最后還要感謝我們班的同學，同學們給我提了不少建議關于系統(tǒng)的設計方面，還要感謝張玉華老師和其他老師的幫助，特別是張玉華老師，由于原來沒有寫過這么大的論文因此張老師一點一點的幫我們看自己的論文，然后打上批注，便于我們修改自己的不準確的地方，發(fā)現(xiàn)了好多錯誤，對于我們的畢業(yè)設計起到了關鍵的作用。 it is not really seen as an overwhelming achievement of technological plexity. When any button is pressed, a chip interprets the signal in a way that has been programmed into the device. This allows the device to know what to expect from the input device (key pad), and how to respond to those mands (for example, turn on the television). This is a simple form of embedded device programming. However, believe it or not, simple devices such as these are definitely related to the roots of early cell phone devices and development.Most embedded devices ran (and in some cases still run) proprietary operating systems. The reason for choosing to create a proprietary operating system rather than use any consumer system was really a product of necessity. Simple devices did not need very robust and optimized operating systems. As a product of device evolution, many of the more plex embedded devices, such as early PDAs, household security systems, and GPSs, moved to somewhat standardized operating system platforms about five years ago. Smallfootprint operating systems such as Linux, or even an embedded version of Microsoft Windows, have bee more prevalent on many embedded devices. Around this time in device evolution, cell phones branched from other embedded devices onto their own path. This branching is evident when you examine their architecture.Nearly since their inception, cell phones have been fringe devices insofar as they run on proprietary software—software that is owned and controlled by the manufacturer, and is almost always considered to be a “closed” system. The practice of manufacturers using proprietary operating systems began more out of necessity than any other reason. That is, cell phone manufacturers typically used hardware that was pletely developed inhouse, or at least hardware that was specifically developed for the purposes of running cell phone equipment. As a result, there were no openly available, offtheshelf software packages or solutions that would reliably interact with their hardware. Since the manufacturers also wanted to guard very closely their hardware trade secrets, some of which could be revealed by allowing access to the software level of the device, the mon practice was, and in most cases still is, to use pletely proprietary and closed software to run their devices. The downside to this is that anyone who wanted to develop applications for cell phones needed to have intimate knowledge of the proprietary environment within which it was to run. The solution was to purchase expensive development tools directly from the manufacturer. This isolated many of the “homebrew” developers.Another, more pelling “necessity” that kept cell phone development out of the hands of the everyday developer was the hardware manufacturers’ solution to the “memory versus need” dilemma. Until recently, cell phones did little more than execute and receive phone calls, track your contacts, and possibly send and receive short text messages。 if you want to create an application that utilizes the phone’s internal GPS (if equipped), you have access to it. The potential for developers to create dynamic and intriguing applications is now wide open.On top of all the features that are available from the Android side of the equation, Google has thrown in some very tantalizing features of its own. Developers of Android applications will be able to tie their applications into existing Google offerings such as Google Maps and the omnipresent Google Search. Suppose you want to write an application that pulls up a Google map of where an ining call is emanating from, or you want to be able to store mon search results with your contacts。 this will be discussed in later chapters.Reference：[1]Hello Android. Introducing Google’s Mobile Developmeng Platform ,Ed Burnette,The Pragmatic Bookshelf[2] Building Applications with the Android SDK,James Steele Nelson,AddisonWesley[3] Pro Android Media. Developing Graphics,Music,Video and Rich Media Apps for Smartphones and Tablets,Shawn Van Every,Apress[4] .(Wrox,.2010,.0470565527)附錄2：外文譯文什么是 Android?可以說，于此同時，傳統(tǒng)的桌面應用程序開發(fā)人員已經(jīng)被寵壞了。然而，作為傳統(tǒng)的桌面應用程序開發(fā)人員，我們有能力創(chuàng)建幾乎任何類型的應用程序，我們可以想像。一方面，我們已經(jīng)有足夠的能力去和桌面操作系統(tǒng)互動，已經(jīng)使桌面編程開發(fā)更易接受，從而與任何底層的硬件交互。這種自由、獨立地編程，已經(jīng)不再是那些敢于冒險跳進手機開發(fā)黑水中的小數(shù)量的開發(fā)者能夠獲得的。理解成一個小的具有魅力的桌面家族成員后來的網(wǎng)絡Web開發(fā)，嵌入式設備開發(fā)代表性地得到聞名的短的結局，遠至硬件和操作系統(tǒng)特色，因為嵌入式設備制造業(yè)在特色支持方面惡名昭彰地吝嗇。嵌入式設備不同于桌面系統(tǒng)是一個嵌入式設備是一個典型的“片上計算機”。它不是真正看上去像一個無法實現(xiàn)的復雜技術的實現(xiàn)。這允許設備從輸入設備（鍵盤）知道用戶期望干什么，和如何對這些命令響應（例如，打開電視機）。然而，信或不信，諸如這些簡單的設備被明確涉及到早期手機設備和開發(fā)的根源。選擇創(chuàng)建一個專有的操作系統(tǒng)而不是使用任何消費者系統(tǒng)的理由是：這是一個產(chǎn)品正真必需的。作為一種設備產(chǎn)品的發(fā)展，大約2年前左右，許多復雜的嵌入式設備，例如早期的PDAs，家庭安全系統(tǒng)，和和GPSs，被移植到有點標準化的操作系統(tǒng)平臺上。圍繞這個時間段的設備發(fā)展，手機從其他的嵌入式設備分支成他們己的路線。幾乎從他們起初，當運行專有的軟件（被制造廠商擁有和控制，幾乎也總是被考慮是“封閉”系統(tǒng)）時，手機就