유진 : 로이! 네가 부탁한 자료 여깄어!
Roy! Here is the material you asked for!
로이 : 고마워 유진
Thank you! You-jin.
유진 : 맨 입으로?
no payback?
로이 : 맛있는거 사줄께
I’ll treat you at a nice restaurant.
뭐 먹을지 생각하고 있어.
Think about where you want to go.
유진 : 알았어.
Got it!
유진 : 흠…로이한테 뭐 사달라고 그러지?
hmm…What do I want? Chinese cuisine? shabu shabu?
상진 : 간만에(a simple expression of 오래간만에) 갈비 뜯으면서 포식했네.
I haven’t had gal-bi in so long. That was a great meal.
로이 : 형! 한국 갈비 너무 맛있어요.
Korean ribs are so delicious!
유진 : 로이!
Roy!
로이 : 유진아! 미안해! 깜박했어.
You-jin. I’m so sorry! I forgot.
유진 : 어떻게 나랑 한 약속을 잊을 수가 있어?
How could you forget having made plans with me?
로이 : 유진아, 미안해.
You-jin, I’m sorry.
로이 : 유진아, 미안해.
You-jin, I’m sorry.
지금이라도 나가서 사줄께. 가자!
I’ll take you to dinner now. Let’s go!
유진 : 됐어!
It’s too late.
로이 : 배 많이 고프지? 뭐 먹고 싶어?
You must be very hungry. What do you want to have?
내가 사<=get, buy(사다)> 가지고 올께.
I’ll go out and get it for you.
유진 : 됐다구!
Forget about it!
로이 : 유진, 이것 좀 먹어봐.
You-jin, try to have this.
유진 : 흥!
hmmph!
로이 : 아 제발, 화 좀 풀어.
please, stop being mad at me.
유진 : 흥!
hmmph!
로이 : 아 유진, 나도 몰라. 마음대로 해!
ah Y-J, I give up. Do whatever you want!
유진 : 어~~? 한번만더 권하지. 배고파…
darn…why didn’t he ask me one more time? I’m starving…
로이 : 유진아!
You-jin!
유진 : 헉!? 몰라 다 너 때문이야!
What? This is all because of you!
—————————————————————————————————————
Wow… So long… huuu….
Wingcom형아~ I finished one episode… hahaha…. (There are too many;;;;)
I guess that you can understand everything!
but, additionally speaking, I guess that you can’t understand this perfectly…
유진 : 맨입으로?
no payback?
맨 is the word which means ” no, not, out ” ex) 맨몸(no clothes) 맨발(no socks)
입 is mouth as you know.
So… “맨입으로?” contains the following mean,
“Do you think that I don’t have mouth? Otherwise, You should pay back?”
But You should say this expression to your friends, not senior…
———————————————————————————————
I hope that You can understand my fool english… ;;;;
절대 말하지 마 Don’t you dare tell.
비밀이야 It’s a secret.
고장 냈지? Did you break it?
절대(絶對) absoluteness:
절대로 안 돼! No way! or Absolutely not! or Definitely not! or Not on your life!
비밀(密) a secret;secrecy;mystery
고장(故障)a defect;something wrong
32회 바쁜 척 하지마
어떻게 된 거야? What happened?
바쁜 척 하지 마 Don’t pretend to be busy.
아이고, 깜짝이야 My goodness! You scared me!
“들은 거야, 못 들은 거야?” : “Did you, or did you not, hear me?”
척 pretense ⇒체
보고도 못 본 체하다 : pretend not to see
33회 엄살 부리지 마
아파 죽겠어. It hurts so much, I could die.
엄살 부리지마 Don’t be a crybaby.
너 꾀병 아니야? Aren’t you faking it?
아이고 아파라 Ouch! How it hurts.
맞아죽다 be struck dead
엄살꾸러기 a crybaby
꾀병: feigned[pretended, fake] illness
34회 생일 축하합니다
생일이 언제야? When is your birthday?
아무도 내 생일을 기억 못하네. No one remembers my birthday.
생일 축하합니다. Happy birthday!
기억: memory
35회 멋있기는요
뭘요. Nah, that’s not true.
참 멋있게 생겼다. You are very good-looking.
멋있기는요. I’m not so good-looking.
Mobile Challenges: screen (size, pixel, depth), memory, CPU, fragmentation, bandwidth, security, connectivity, data input, distribution & deployment. Despite theses challenges, the number of mobile devices is growing at a staggering rate. By the end of 2007, there will be 2713 million mobile devices and over 300 different models in use worldwide, compared to 755 million PC’s. (Gartner Dataquest). Along with the number of mobile devices offering Flash support, there is also a direct correlation to the growth of application users. Mobile application matters to those wanting to get out their brand recognition in a more personal method, beyond television and desktop computers.
The mechanics for mobile device design is different from normal design. There isn’t a mouse pointer, usually, or a touch-pad. There might be a touch-screen interface or a more common directional pad. The use of a zoom allows the user to instantly recognize focus to an object. You’ll also want to omit labels and headers to obtain every pixel of available screen real estate. You can use this code: fscommand2("fullscreen", true); to display your content in full screen mode. The "fscommand2" has access to specific device features like the signal strength and vibrate. You can make use of these in your project design for interesting affects.
Flash Lite couples rich presentation with solid programming, anything that the object oriented library facilitates. The following steps are an example of the ease at which one might create the code for navigating a mobile device menu:
Using the scroll pad on the mobile device to control our phone games is likely how you will create player control and movement. The up, down, left, right and enter key are the usual keys available. For each menu item, you will create one layer. Create a movie clip and make sure to have a stop action on the first frame. Create the text for your menu items; new game, instructions, exit. You will now make a layer for the background environment or image. (This will likely be the bottom most layer.) You may also want to build a square, oval or rectangle and fit it behind your menu item. On the next frame, move your shape to fit behind the next menu item, and so on. The “up” and “down” events will allow you to navigate through your menu structure. Here is sample code:
on(keyevent “<Up>”){
// go to previous frame or stop at frame 1
tellTarget(”target path to mc”){ prevFrame(); }
}
on(keyevent “<Down>”){
// go to next frame or stop at last frame
tellTarget(”target path to mc”) {nextFrame();}
}
This opens a Scottrade “Switch” page. Their content=”If you’re tired of brokerage account and transfer fees, make the switch to Scottrade online brokerage. We’ll not only help you consolidate your stock trading, IRA and mutual fund accounts, we’ll give you up to $100 back!”
The only popup I could spot is the “open a new account” text link or button. It opens up a new smaller window: https://apply.scottrade.com/applyonline/apply.aspx
If you choose to you may click on the link under, “Contact Us 1-800-619-SAVE” which is an email address: support@scottrade.com If you select the email address, you will have another popup window open: https://apply.scottrade.com/applyonline/SendEmail.aspx
I think that the pop-up windows are very low in number and controlled by the user and therefore not very annoying. For the company, it allows for the main page to remain open and on the user’s desktop.
This is a McAfee site whose content=”PCI Compliance and Secure Website Certification from McAfee Secure. Automated network security audits provide an affordable means of ensuring your customers’ transactions remain secure.”
Where to find the pop-up is the “Questions?” banner on the left side: Click here to chat with a customer service representative. It opens up a chat window allowing the customer to chat and ask for help while staying on the page. This is valuable tool for both the website owner and the user.
This is great: http://www.popuptest.com/ If you want to find popup windows, there you have it. My popup blocker is working fine. On the first link, there is supposed to be 10 popup windows and it caught all of them (but only notified me of 6).
Firefox 3.0 stopped all except: http://www.popuptest.com/popuptest8.html and this one: http://www.popuptest.com/popuptest6.html
So, of course, while each of these might be annoying, the point is to test your browser’s pop-up defense and thus useful.
Obviously, not all pop-ups are unwanted. The browser and/or pop-up killers should be smart enough to recognize or allow you the choice to view the pop-ups you actually want to view.
In the code example below, the _y property of the duplicated movie clip is extracting hard-coded values from an array. In contrast, the _x property is determined programmatically, by first calculating the width of the stage, and then placing the duplicate movie clips based on the resulting values of the calculation.
var clipNum = 3
var xLocate = Stage.width/ (clipNum+1);
var yArray = new Array (30,40,50);
for(x=1; x<=clipNum; x++){
var tempMc = attachMovie("block",
"block"+x, x);
with (tempMc) {
_x = xLocate*x;
_y = yArray[x-1];
}
}
People will access your project on different mediums and devices. They may even use a stylus or their finger to press buttons. Users will expect standard key presses will be used and followed. (Become familiar with common mobile device conventions.)
The options for functionality should be flexible and not device dependent. The general practice of keeping the functionality of your project separate from the events that trigger it will allow more compatibility and possibility of your project to operate on many different devices.
As you begin your project you should with a commonly used screen size (176×208 or even 240×320 pixels). These will allow you to port your game to devices much easier.
Your project files should be able to meet the needs of different displays. Perhaps allowing for resizing or rescaling the graphics and text will allow for greater display needs. Think about text size and legibility as well as graphics and bitmaps.
It’s important for the user to interact with the device and the application. You will use a broadcaster-listener model and handler method to allow the application to respond when the user has interacted with the device.
Use of variables should be utilized to help keep your code flexible. All of us have coded for “hitTest” functions now. Considering mobile devices, The method below is easy on the mobile processor and uses the objects x and y values as well as the objects dimensions.
This code checks the relationship of obj.x1’s left edge in relation to obj.x2’s left edge. Next it evaluates the right edge, top edge and finally the bottom edge of both.
〕
“