【正文】 網(wǎng)思維玩轉(zhuǎn)日歷 (02) [8] custom Desktop calenders with ,(275) [9] LiulijuanDesign and Simulation of Calendar Circuit Based on Proteus Software2020 [10] Gerhard EFFECTS IN MONTHLY TIME SERIES (02) 專業(yè)班級(jí) 學(xué)生 要求設(shè)計(jì)（論文）工作起止日期 2020 年 3 月 23 日 ~2020 年 7 月 3 日 指導(dǎo)教師簽字 日期 2020 年 3 月 23 日 教研室主任審查簽字 日期 系主任批準(zhǔn)簽字 日期 碼農(nóng)畢業(yè)設(shè)計(jì)下載網(wǎng)： i 桌面日歷系統(tǒng)的設(shè)計(jì)與實(shí)現(xiàn) 摘 要 隨著網(wǎng)絡(luò)的快速發(fā)展，電腦的使用及辦公越來越貼近人們的生活。 我認(rèn)為他們沒有真正意識(shí)到一個(gè)系統(tǒng)的最大的用處方便人們的生活，因此各種各樣的功能才是真正為用戶提供方便。 calendar。日歷系統(tǒng)在人們的生活中很常見，為了對(duì)桌面日歷做一個(gè)創(chuàng)新，我在這次畢設(shè)中添加了自己的元素。 本設(shè)計(jì)按照功能模塊分為菜單模塊，顯示模塊，查詢模塊，節(jié)假日模塊，存儲(chǔ)數(shù)據(jù)模塊，附加功能模塊，其中附加功能模塊又分為：計(jì)算器模塊，時(shí)鐘模塊，皮膚模塊等等。 然后這次畢設(shè)主要用的技術(shù)就是 java 的 gui 編程技術(shù)。在實(shí)現(xiàn)了查看日期信息的同時(shí)，也提高了它的價(jià)值和綜合性，真正達(dá)到了為用戶提供方便，為辦公人員提高效率的好處，我相信從這些方面出發(fā)，才會(huì)從各個(gè)日歷系統(tǒng)中脫穎而出。還有就是不僅僅局限于日歷，為了讓它的使用性和綜合性更強(qiáng)，給它附加了一些小功能，比如計(jì)算器，時(shí)鐘，鬧鈴，換皮膚等。包括： AWT 包和事件模型、常用的 AWT 包中的容器組件和控件組件以及布局管理器，和 Swing 包中的組件類?！? 碼農(nóng)畢業(yè)設(shè)計(jì)下載網(wǎng)： 5 2 需求分析 需求分析概述 本次畢設(shè)里面沒有設(shè)置登陸模塊，我感覺日歷系統(tǒng)應(yīng)該是大眾化的需求，不需要設(shè)置用戶登錄。 需求分析獲取 ，和關(guān)于日歷系統(tǒng)的一些設(shè)計(jì)。經(jīng)濟(jì)成本小，雖然規(guī)模小，但是在功能上卻很豐富。通過解決問題，我也發(fā)現(xiàn)了自己的不足，在知識(shí)的儲(chǔ)備度還有所欠缺，對(duì)已學(xué)知識(shí)不能熟能生巧的運(yùn)用，深度上也不夠。 ：鬧鈴和計(jì)算器。主要的算法有農(nóng)歷和公歷的算法，公歷日期號(hào)與星期的求解算法，相應(yīng)節(jié)日信息的生成算法，界面換膚算法，實(shí)時(shí)日期顯示算法等?？梢渣c(diǎn)擊相應(yīng)功能，然后彈出。 相應(yīng)公歷節(jié)日信息顯示模塊 該模塊主要通過把網(wǎng)上查詢的節(jié)日，存儲(chǔ)到文件中，然后給相應(yīng)的日期添加監(jiān)聽，當(dāng)點(diǎn)擊該日期時(shí)以彈框形式顯示節(jié)日信息。 模塊結(jié)構(gòu)圖 用戶查詢主界面設(shè)計(jì)模塊 該模塊主要是講用戶查詢主界面按 BorderLayout 方式分成幾個(gè)區(qū)域，再對(duì)每個(gè)區(qū)域的組件進(jìn)行分區(qū)布局。在發(fā)生操作事件時(shí)，調(diào)用該對(duì)象的 actionPerformed 方法。 String Msg = getHoliday(d)。 } 碼農(nóng)畢業(yè)設(shè)計(jì)下載網(wǎng)： 18 if(() == bLastYear){ ((y))。 ((m))。 //調(diào)用 Tool 構(gòu)造函數(shù) x = () + 150。 //根據(jù)分針傳入的弧度和指針的長(zhǎng)度兩個(gè)參數(shù)，計(jì)算指針末端相對(duì)于圓點(diǎn)的 x 坐標(biāo) y = 150 ()。 //根據(jù)時(shí)針傳入的弧度和指針的長(zhǎng)度兩個(gè)參數(shù)，計(jì)算指針末端相對(duì)于圓點(diǎn)的 y 坐標(biāo) ()。 這個(gè)小小的創(chuàng)意可以帶給人們枯燥的生活中一點(diǎn)點(diǎn)歡樂，還可以幫助你進(jìn)行表白等不好意思說出的話。 ().add(p5,)。 i 0x8。 //獲取日歷實(shí)例 Calendar calendar = ()。 } //如果點(diǎn)擊綠色選項(xiàng)，設(shè)置背景色為綠 if((green)){ ().setBackground()。 (null, Msg,confirm, )。 //根據(jù)所得字符串獲得農(nóng)歷日期 String Msg = getHoliday(d)。 } return (sum + leapDays(y))。 (0x10000 m)) == 0) return 29。 界面方面我會(huì)準(zhǔn)備一些圖片甚至主題供用戶選擇。希望通過這次畢設(shè)能讓我順利畢業(yè)，以一個(gè)好的結(jié)局離開學(xué)校，步入社會(huì)，以一個(gè)完美的狀態(tài)去迎接未來的挑戰(zhàn)。原來是計(jì)劃把背景設(shè)計(jì)成自己想要的圖片，然后多準(zhǔn)備一些主題或者背景圖片供用戶選擇，就像手機(jī)桌面一樣，人們可以根據(jù)自己喜好隨意改變。 總結(jié) 通過這次畢設(shè)，能感覺到在軟件開發(fā)領(lǐng)域自己所知識(shí)太少了，在學(xué)校所學(xué)的 也都是一些基礎(chǔ)知識(shí)，想要完成一個(gè)作品，我們還需要上網(wǎng)查詢很多資料，也就意味著這個(gè)行業(yè)的學(xué)習(xí)永無止境，我們只有通過不斷學(xué)習(xí)，不斷探索新的知識(shí)，才有可能完成自己想要的軟件或系統(tǒng)。 最后我還要感謝培養(yǎng)我長(zhǎng)大含辛茹苦的父母，謝謝您們 ! 最后，再次對(duì)關(guān)心、幫助我的老師和同學(xué)表示衷心地感謝！ 碼農(nóng)畢業(yè)設(shè)計(jì)下載網(wǎng)： 39 外文原文 Java and the Inter If Java is, in fact, yet another puter programming language, you may question why it is so important and why it is being promoted as a revolutionary step in puter programming. The answer isn’t immediately obvious if you’re ing from a traditional programming perspective. Although Java is very useful for solving traditional standalone programming problems, it is also important because it will solve programming problems on the World Wide Web. What is the Web? The Web can seem a bit of a mystery at first, with all this talk of “surfing,” “presence,” and “home pages.” It’s helpful to step back and see what it really is, but to do this you must understand client/server systems, another aspect of puting that’s full of confusing issues. Client/Server puting The primary idea of a client/server system is that you have a central repository of information—some kind of data, often in a database—that you want to distribute on demand to some set of people or machines. A key to the client/server concept is that the repository of information is centrally located so that it can be changed and so that those changes will propagate out to the information consumers. Taken together, the information repository, the software that distributes the information, and the machine(s) where the information and software reside is called the server. The software that resides on the remote machine, municates with the server, fetches the information, processes it, and then displays it on the remote machine is called the client. The basic concept of client/server puting, then, is not so plicated. The problems arise because you have a single server trying to serve many clients at once. Generally, a database management system is involved, so the designer “balances” the layout of data into tables for optimal use. In addition, systems often allow a client to insert new information into a server. This means you must ensure that one client’s new data doesn’t walk over another client’s new data, or that data isn’t lost in the process of adding it to the database (this is called transaction processing). As client software changes, it must be built, debugged, and installed on the client machines, which turns out to be more plicated and expensive than you might think. It’s especially problematic to support multiple types of puters and operating systems. Finally, there’s the allimportant performance issue: You might have hundreds of clients making requests of your server at any one time, so any small delay is crucial. To minimize latency, programmers work hard to offload processing tasks, often to the client machine, but sometimes to other machines at the server site, using socalled middleware. (Middleware is also used to improve maintainability.) 碼農(nóng)畢業(yè)設(shè)計(jì)下載網(wǎng)： 40 The simple idea of distributing information has so many layers of plexity that the whole problem can seem hopelessly enigmatic. And yet it’s crucial: Client/server puting accounts for roughly half of all programming activities. It’s responsible for everything from taking orders and creditcard transactions to the distribution of any kind of data—stock market, scientific, government, you name it. What we’ve e up with in the past is individual solutions to individual problems, inventing a new solution each time. These were hard to create and hard to use, and the user had to learn a new interface for each one. The entire client/server problem needs to be solved in a big way. The Web as a giant server T