Youtube daily google Mar 28 2017

Rivne (Ukrainian pronunciation: [ˈrʲiwne]; Russian: Ровно; Polish: Równe)

is a historic city in western Ukraine and the historical region of Volhynia.

It is the administrative center of the Rivne Oblast (province),

as well as the surrounding Rivne Raion (district) within the oblast.

Before World War II the city was located in Poland

and during the German occupation in 1941–44 the city

was designated as a capital of the German Ukraine

(Reichskommissariat Ukraine).

Rivne is an important transportation hub,

with the international Rivne Airport, and rail links to Zdolbuniv,

Sarny and Kovel, as well as highways linking it with Brest, Kiev and Lviv.

The estimated population was around 250,242 as of 2013.

Rivne was first mentioned in 1283 as one of the inhabited places of Halych-Volhynia.

From the second half of the 14th century it was under the Great Duchy of Lithuania

and from 1569 in the Polish-Lithuanian Commonwealth.

In 1492 the city was granted Magdeburg rights.

Following the partition of Poland, in 1793 Rivne became a part of Russian Empire,

and in 1797 it was declared as a regional town of the Volhynian Governorate.

During World War I and the period of chaos shortly after, it was briefly under German,

Ukrainian, Bolshevik, and Polish forces.

In April–May 1919 Rivne served as the temporary capital of Ukrainian People's Republic.

At the conclusion of the conflict, in accordance with the Riga Peace Treaty of 1921

it became a part of Polish Volhynian Voivodeship for the period between the two World Wars.

In 1939, as a result of the Molotov-Ribbentrop Pact

and the partition of Poland, Rivne was occupied by the Soviet Union.

From December of the same year Rivne became the centre

of the newly established Rivne Oblast, within the Ukrainian SSR.

On June 28, 1941 Rivne was captured by Nazi Germany,

which later established the city as the administrative centre

of Reichskommissariat Ukraine.

On February 2, 1944, the city was liberated by the Red Army

in the Battle of Rovno, and remained part of Soviet Ukraine

until the break-up of the Soviet Union in 1991.

In 1958, TV tower began broadcasting in the city;

in 1969, the first trolley ran through the city;

in 1969, Rivne airport was opened.

In 1983, the city celebrated its 700th anniversary.

On 11 June 1991, the Ukrainian parliament has officially adopted

the name of Rivne for the city which was known as Rovno.

For more infomation >> Часть 5. Город Ровно. Part 5. City Rivne - Duration: 8:50.

-------------------------------------------

Now I'm an idiot ? ▌What is Google's top result for ▌Idiots.win - Duration: 5:26.

Hi, my name is C

Uhhh my back

I'm OK

Don't worry I'm ok

Here's the game today

What is google's top result for

I just need to choose the answer

And that's all

Right the first time

Who asked this ******* thing on google ?

I feel sorry for you

One Puch Man, do you know that ?

WTF am I playing ?

59 failure

24 bad and only 10 perfect

Are you kidding me?

So you wanna trick me ?

Let me show you

Thanks for watching

Don't forget to subscribe

And leave a comment

Brofist

For more infomation >> Now I'm an idiot ? ▌What is Google's top result for ▌Idiots.win - Duration: 5:26.

-------------------------------------------

SKATEARE MARSHMALLOW A PIEDI NUDI! - Duration: 12:50.

For more infomation >> SKATEARE MARSHMALLOW A PIEDI NUDI! - Duration: 12:50.

-------------------------------------------

10 Trucos Que No Sabías De Google | TOP 10 | Vídeo en Español HD (CC) - Duration: 4:54.

For more infomation >> 10 Trucos Que No Sabías De Google | TOP 10 | Vídeo en Español HD (CC) - Duration: 4:54.

-------------------------------------------

How to archive in the smartphone version of "Google Keep" app notes in swipe operation - Duration: 1:30.

How to archive in the smartphone version of "Google Keep" app notes in swipe operation

Hello everyone

This time, we will introduce how to archive swipe a note in the smartphone version of "Google Keep" app

Android version of "Google Keep" app earlier than by swiping a note to the left and right, but I was not able to operate to the archive,

Also iPhone version of "Google Keep" app corresponding to the swipe operation, can now be a note to archive swipe

Smartphone version of how to archive a note in the "Google Keep" app,

All you have to do is either the left or right swipe to the subject of the memo in the memo list screen

You can return to the original as soon as it is within a certain period of time, even if you've been to the archive if you accidentally

Since the other notes that the archive is stored in the "archive" is displayed by touching the upper right corner of the menu icon,

To release the archive can also be returned to the list of memo

Try to make a note management of the smart to take advantage of the features that can be archived in swipe operation of the "Google Keep" app

Above, it was the introduction of how to archive swipe a note in the smartphone version of "Google Keep" app

For more infomation >> How to archive in the smartphone version of "Google Keep" app notes in swipe operation - Duration: 1:30.

-------------------------------------------

Google Sheets Bilingual Conversation - Duration: 2:18.

Hello everyone I am Jaymian Campbell-MIlner and today we are going to look at how to hold

a typed conversation between two people of two different languages.

For this lesson we will be working with English and Spanish, however this can be done with

many different languages.

To do so we are going to use Google Sheets and the Google translate function =GOOGLETRANSLATE

In my scenario, I have set Language 1 or English to type in Column A, and Language 2 or Spanish

to type in Column G

Using the =GOOGLETRANSLATE, I set Column J to translate Column A from English or "en"to Spanish or "es",

and Column D to translate Column G from Spanish "es" to English "en"

Let me show you an example by typing a sentence in English in Column A.

As you see it is automatically translated into the Spanish in Column J.

A response then can be typed in Spanish in Column G and is translated to English in Column D

The conversation can continue down the rows as long as needed.

I can see this being used by teachers communicating with students or parents, by students communicating

with other students, or by a student practicing another language.

That's it, thank you for joining me and feel free to give it a try by clicking on the link to the Google Sheets posted in the description below.

For more infomation >> Google Sheets Bilingual Conversation - Duration: 2:18.

-------------------------------------------

Virtual Tour Google - Immagini panoramiche 360 scheda local - Duration: 2:44.

For more infomation >> Virtual Tour Google - Immagini panoramiche 360 scheda local - Duration: 2:44.

-------------------------------------------

Mengatasi Link Google Drive Kena Limit - Duration: 2:27.

For more infomation >> Mengatasi Link Google Drive Kena Limit - Duration: 2:27.

-------------------------------------------

MapsZen Seeing the Lite 100 Days of Google Dev (8/100) - Duration: 2:49.

You need to show a collection of places.

And at first, it seems pretty stock standard.

Just throw together a bunch of place names,

and you're done, right?

It's not that simple.

I'm Ankur Kotwal, and I'm going to show you two ways

to display such collections.

First is on the map itself.

Here, we remove the UI and let the map markers

be the primary point of interaction.

This makes for a very immersive experience.

However, it's only effective if the markers fit comfortably

on one screen.

If the user has to zoom or scroll,

the emphasis of your collection is lost.

For example, train stations near me

works well since the result are co-located.

So what should you do about the location if they're spread out?

Well, you could show a list with map thumbnails.

Is that even possible, is what I hear you saying.

How can you show multiple maps at the same time?

It is possible.

The maps API for Android offers an ideal mode

for such scenarios.

It's called Lite mode.

Lite mode provides a static map, effectively just

the image of a map without the ability

to pan or tilt the camera.

This limited functionality, however, comes with a huge win.

It's super fast, uses less memory,

and you still get click listeners,

markers, and polylines.

Lite mode makes it possible to show lists of maps.

They're just images, so you can instantiate many of these.

Best of all, enabling Lite mode is simple.

On creation, simply specify Lite mode in the Google Maps options

object or add the XML property in your layouts.

At some point, you may need to replace the Lite mode map

with the fully interactive one.

In that situation, you can gracefully transition

into a regular map based on the touch event.

Here we're using Android Lollipop transitions

to navigate across screens.

For older versions of Android, a reasonable fallback

is to create a map fragment and animate it into place like so.

By doing this, we're able to mix and match Lite mode

and regular maps seamlessly.

I hope you've now seen the light, Lite mode that

is, which enables you to show multiple maps simultaneously

while staying performant.

Check out more info about Lite mode here.

I'm Ankur Kotwal, and I look forward

to seeing your amazing maps.

[MUSIC PLAYING]

For more infomation >> MapsZen Seeing the Lite 100 Days of Google Dev (8/100) - Duration: 2:49.

-------------------------------------------

Introduction to Voice Interaction API 100 Days of Google Dev (7/100) - Duration: 3:29.

SUNIL VEMURI: Hi, I'm Sunil Vemuri,

and I can't wait for the day when

I can talk to my watch and phone like they do in the movies.

We're still a ways away from that.

But the good news is we're introducing a new API

in Android M that takes us an important step

in that direction.

It's called voice interaction API,

and it lets apps have spoken dialogues with users.

I love listening to the radio on my commute,

and the TuneIn app gives me great choices.

OK Google, play music on TuneIn.

GOOGLE APP ASSISTANT: Which genre would you

like to listen to?

SUNIL VEMURI: Classical.

GOOGLE APP ASSISTANT: Playing classical.

SUNIL VEMURI: Handling voice input can be complex.

Also I didn't just give a command.

I had a conversation where TuneIn asked me a question.

That conversation part is what's new.

My colleague Barnaby and I will show you how voice actions,

together with the voice interaction API,

make it possible for you to build conversational voice

experiences like TuneIn's.

Let's first look at a brief system overview.

It starts with "OK Google" also known as the hot word.

That triggers the assistant, in this case, the Google App.

It starts listening to the user.

The speech-to-text, cloud-based natural language,

and Knowledge Graph work together

to determine what should be done.

If it's an action, an Android intent is triggered.

In our example, the intent is handled by TuneIn.

Now Barnaby will tell you how to do this in your app.

BARNABY JAMES: Hi, I'm Barnaby James,

and I work on the Voice Actions team at Google.

For some voice actions, it's clear what an app should do.

What if the user's command isn't clear,

and your app isn't sure what to do,

and wants to ask the user a question?

Or maybe it needs to confirm something is safe.

The Voice Interaction API lets your app focus on the questions

to ask the user while Google handles

the speech-to-text, microphone setup, and parsing

the responses.

Suppose your app wanted to confirm with the user

before playing something that may not be

suitable for younger listeners.

You would call the voice interactor

and submit a request for a confirmation

along with your prompt.

Google recognizes many of the common ways

people give a confirmation such as yes,

please do it, go ahead, or make it so.

Or if you wanted to ask the user to pick from a list

like TuneIn did, you'd create an array of options

when you submit the voice interaction request.

If your user speaks something not on the list,

Google will take care of reprompting for you.

OK Google, back to Sunil.

SUNIL VEMURI: Thanks, Barnaby.

There's one important thing we left out.

How does a user launch your app by voice?

For many of the common things users do with voice,

such as searching, playing music, setting alarms,

and so on, you should use system voice actions.

Google recognizes when a user asks for these

and fires the intent.

This is what TuneIn used, and these

are documented on our website.

You can use these right away, and we're

adding more all the time.

If system actions don't fit your app,

we recently introduced custom actions.

For example, I can say, "OK Google, Shazam this song."

Here's the URL to learn more about Custom Voice Sections.

Voice is a great way to drive traffic to your app

and engage users.

Next, check out our CodeLab and try out voice interaction.

Thanks and see you next time.

[MUSIC PLAYING]

For more infomation >> Introduction to Voice Interaction API 100 Days of Google Dev (7/100) - Duration: 3:29.

-------------------------------------------

Get OAuth Credentials in Google Developer Console - Duration: 2:37.

The redirect URL is used to redirect users from the Google auth screen to your site, once user approved your app to access the data listed in the auth screen.

For more infomation >> Get OAuth Credentials in Google Developer Console - Duration: 2:37.

-------------------------------------------

How to Restore Google Chrome Theme to Default Theme - Duration: 1:04.

Welcome guys.

In this tutorial I will be talking about how you can restore your Google Chrome theme to

your default theme.

So here you can see that I have installed a custom theme to my Google Chrome, because

usually the background is white and the text is black.

The way you do this, you need to go to settings, so go here and then settings.

And then you can see here, appearances, get themes.

If you press that it will open a new tab, where you can see other themes, if you want

to change your current theme to another one.

Or you can press reset to default theme.

Press that and there you go.

As simple as that the theme has been restored to the default one.

I hope you found this useful and see you guys in the next tutorial

For more infomation >> How to Restore Google Chrome Theme to Default Theme - Duration: 1:04.

-------------------------------------------

Suchmaschinenoptimierung Deutschland: Was ist Quality Content? - Duration: 7:22.

For more infomation >> Suchmaschinenoptimierung Deutschland: Was ist Quality Content? - Duration: 7:22.

-------------------------------------------

Tzedaka Campaign By Chabad of Google - Duration: 2:40.

a new campaign to help the chabad of google

and many special organizations awesome

the sponsorship that you get that

dedicates to kobato google $1 take it

out from that sponsorship talk about a

rule and the rest of it goes to

organization of your choice and we also

offer our services which are of course

video editing singing music making music

video directing beaches sorry telling

anything you need just call 1347 5839

I'm 42 again 1347 5839 42 if you want

email us that email you feel now at

gmail com again muzio nass @ gmail.com

and the first sponsorship or the first

hire Minh will get a shout-out on the

next episode or video alphabat of Google

and don't do it just for a lot of Google

just do it for all the wonderful

organizations and meets our and your

help see you next time

For more infomation >> Tzedaka Campaign By Chabad of Google - Duration: 2:40.

-------------------------------------------

Using LINT for Performance Tips 100 Days of Google Dev (9/100) - Duration: 3:58.

자막제작: Stanleykou (http://stanleykou.tistory.com/)

자막제작: Stanleykou (http://stanleykou.tistory.com/) While I'm normally opposed to using puns in videos, 일반적으로, 제가 동영상에서 말장난을 할 때는

this one's pretty good, you gotta admit. 이건 괜찮은 겁니다. 그냥 그러려니 하세요.

Anyhow, my name is Colt McAnlis. 어쨌거나, 제 이름은 콜트 맥카닐스입니다.

And after posing a question to the Android Performance Android Performance Patterns 구글 플러스 커뮤니티에 질문을 몇 개 던져보았는데요,

Patterns Google+ Community, we realized that it might be 저희는 안드로이드 스튜디오에 포함된 유용한 기능을

beneficial to cover a very useful tool inside of Android 소개해 드리면 모두에게 유용할 것이라는 결론을 얻게 되었습니다.

Studio.

See, one of the biggest problems with fixing performance 성능향상 작업에서 제일 큰 문제가 되는 것은,

in your applications is that it's mostly a reactive process. 당신의 앱이 "반응을 해야 하는" 프로세스라는 것입니다.

You build an app, ship it to users, 당신을 앱을 만들고, 이용자에게 배포하고,

and only after they've started complaining about it do you 그러면 이용자들이 당신에게 불평을 하고,

know where the problems are. 그러면 어디가 문젠지 확인하겠죠.

It seems like it would be tons easier 수십배는 더 쉬운 방법이 있는데,

to identify the problems ahead of time 악플이 달리기 전에 어디가 문제인지

rather than having to wait for bad reviews to come in. 알아내는 것입니다.

Now historically, the Android toolchain 역사적으로도, 안드로이드 툴체인에서는

provided a tool named LINT, a static code analysis tool which LINT라는 이름의 static 분석 툴을 함께 제공했는데요,

checks your Android project source 안드로이드 프로젝트의 소스파일을

files for any potential bugs alongside 분석하여, 잠재적인 버그를 찾아내고

potential optimizations for correctness, security, 최적화, 오류수정, 보안성,

performance, usability, accessibility, 성능향상, 이용성 향상, 장애인을 위한 편의 향상,

and internationalization. 그리고 다국어 앱 개발에 도움을 줍니다.

For example, if you're allocating objects inside 예를 들어, 당신이 오브젝트를

of the onDraw function which, as we all know, onDraw 함수 내에서 할당했다면, 다들 알듯이,

can lead to excessive amounts of memory churn, 엄청난 메모리 파편화를 만들어내게 됩니다.

LINT can detect that and spit out a nice warning for you, LINT는 이런 것을 찾아서 친절한 경고를 뱉아냅니다.

pinpointing the exact line that the problem occurs at. 정확하게 어느 라인이 문제를 일으키고 있는지 말이죠.

Simply boot up your favorite command 그냥 커맨드 프롬프트를 열고,

prompt, run some commands, and LINT will do the rest. 커맨드 몇 개를 실행시키면, LINT가 나머지를 다 알아서 해줍니다.

Well, the good news is that this handy tool, by default, 좋은소식은, 이 유용한 툴이

is now integrated into Android Studio 1.0, 안드로이드 스튜디오 1.0에 기본탑재 됐다는 거지요.

and it's useful in a couple of ways. 이건 다양한 방법으로 써먹을 수 있습니다.

Firstly, anytime you want to kick off a release build, 먼저, 언제든 릴리즈 빌드를 찍어내고 싶다면

LINT will run a subset of its checks LINT가 그 검사목록 중 일부를

against your compiling code. 컴파일하는 코드에 대해 수행할 수 있습니다.

Secondly, if you want feedback on a more regular basis, 두 번째로, 좀 더 일상적으로 피드백을 받고싶다면

you can configure Gradle to run the full suite of LINT tests 그래이들 설정을 바꿔서 LINT의 모든 테스트를

during any various random build you may kick off 낮 동안에 어떤 종류의 빌드 릴리즈하고,

during the day. 밤에 테스트를 하도록 설정할 수 있습니다.

And thirdly, if having LINT run during your builds 세 번째로, 빌드하는 중에 LINT를 돌리는게 마음에 안드시면,

isn't really your thing, you can kick off manual builds 매뉴얼 빌드를 하도록

at your discretion. 설정하실 수 있습니다.

And just for the sake of introductions, 소개를 해드려야 되니까,

let's take a look at that third step for now. 그 세번째 과정을 지금 한 번 해보겠습니다.

To run LINT on your code inside of Android Studio, 안드로이드 스튜디오 안에서 LINT를 돌리시려면

open up your project, and select Analyze, Inspect 프로젝트를 열고, Analyze - Inspect Code를

Code from the menu. 메뉴에서 선택하세요.

This will kick off LINT and present a handy suite 이렇게 하면 LINT가 실행되고, 유용한 몇 가지 결과가

of results that manifest itself in a window 화면 하단의 윈도우에

at the bottom of the IDE. 표시되게 됩니다.

This bottom window has two main components. 하단 윈도우는 두 가지 컴포넌트를 가지고 있는데요,

On the left is a hierarchical grouping of various errors, 왼쪽 것은 에러의 계층구조,

warnings, and potential issues. warning, 그리고 잠재적인 이슈입니다.

And when you select one of the issues in that left pane, 왼쪽 창에서 이슈를 하나 선택하면

the right pane will be filled in with details 우측 창에 상세한 내용이 나옵니다.

about what that problem means, the line number that causes it, 그 오류가 무슨 의미인지, 오류가 일어난 라인이 어디인지,

information on the test, and how to potentially fix the problem. 테스트를 위한 정보, 어떻게 하면 이 오류를 수정할수 있는지 등등.

If you've noticed by running this tool, 이걸 한 번 해보셨다면,

there's a flood of tests that LINT checks for. LINT가 체크할 수 있는 항목이 산더미 같다는 걸 아실겁니다.

So if you want to control the tsunami of information 이 정보의 쓰나미를 헤쳐나오려면,

that LINT can spit out, you can configure what analysis LINT가 뱉아내는 이 정보를 걸러서 보기 위해서는

you're interested in by opening File, Other Settings, Default File, Other Settings, Default Settings

Settings, and then selecting Inspections. 거기서 Inspection을 설정하시면 됩니다.

This will list all-- and I mean all-- of the inspecting options 이러면 모든, 다시 말하지만 LINT의 모든 옵션을 켤 수 있습니다.

for LINT.

To specifically tune LINT to find performance issues, LINT가 성능향상 관련 이슈만 표시하게 설정하시려면

you can search for the "performance" keywords. "performance"라는 키워드를 찾아 보세요.

From there, you can click through 거기서 클릭을 몇 번 하시다 보면,

and get a better sense of what checks are being run, 어떤 체크를 돌려야 좋은지 깨닫게 되고,

enable them, disable them, and reassign their priority 이걸 켜 봤다가 저걸 꺼봤다가 우선순위도 조정해 볼 수도 있죠.

for performance. 성능향상 위주로요.

But even with that search, there's 근데 검색하시다 보면

lots of data that's being listed. 목록에 정보가 너무 많을 겁니다.

So here are Colt's personal suggestions on which 그래서 저 콜트의 개인적인 추천이 있는데요,

ones to keep an eye on. 이 항목을 켜 주면 좋습니다.

Firstly, make sure you set memory allocations 먼저, draw 코드에 메모리할당이

within drawing code to throw an error. 들어가 있으면 에러가 출력되게 하세요.

As we've seen with the Memory Churn videos, 메모리 파편화 비디오에서 말씀 드렸듯이,

this can quickly cause a problem. 이건 굉장히 빠르게 문제를 발생시킬 수 있습니다.

And it's worth keeping an eye on in order to avoid issues here 이 옵션을 켜시면, 여기있는 이슈가 발생하는 걸

in the future. 미래에는 더이상 안 보실 수도 있습니다.

The Layout Has Too Many Views and Layout Hierarchy "The Layout Has Too Many Views"와 "Layout Hierarchy Is Too Deep"도

Is Too Deep are good to keep an eye on. 켜놓으면 좋습니다.

Although if your users are running on modern devices, 또한 당신 앱의 이용자들이 최신 기기를 이용한다면,

this may be fine to just leave as a warning. 그냥 경고를 남기는 식으로 처리해도 괜찮겠지만요.

And finally, I like to leave the Overdraw check set 마지막으로, 저는 Overdraw check를 설정하는 것을 권하는데,

to a warning, if anything, just to keep an eye on what's 뭔가 빌드 간에 변경사항이 있으면

changed between builds. 체크해도 됩니다.

But remember, at the end of the day, 기억하세요.

these are suggestions based upon what the tooling team has 저희가 제안한 이것들이 툴 팀에서는

seen as common problems. 자주 보이는 문제들이니까요.

Your code may get flagged for a particular issue, 당신 코드에 특정 이슈가 있다고 나와도

but if it's not actually eating into your frame rate, 그게 정말 프레임 레이트를 떨어뜨리는 것이 아니라면,

don't actually worry about it. 걱정할 필요 없습니다.

So keep that in mind before you run off into the weeds 불필요하게 상세하게 접근하지 말고, 기억만 해 두었다가

and start refactoring things. 나중에 리팩토링을 하세요.

Now if you run this tool and end up 이제 이 툴을 돌렸는데 만약

with a flood of performance issues, 산더미 같은 성능관련 이슈가 나오다면

then make sure you check out the rest of the Android Performance 다른 "Android Performance Patterns" 동영상을 보시고

Patterns content for tips and tricks 팁과 노하우를 배워가셔서

on how to address these issues. 이슈 해결에 도움이 되시길 바랍니다.

And of course, don't hesitate to join our Google+ Community 그리고 저희 구글 플러스 커뮤니티에도 가입 해주세요.

to get more information on tips and tricks from people that are 거기서 주로 출몰하는 고수들이 팁과 노하우를

in the trenches. 알려드릴 겁니다.

So keep calm, profile your code, and always remember 그러니 차분하게, 코드를 프로파일링하고, 항상 기억하세요.

perf matters. 성능이 항상 중요합니다.