Profile cover photo
Profile photo
Sudarshan Pant
168 followers
168 followers
About
Posts

Post has shared content
English follows.

이번 주 우리는 매우 슬픈 소식을 접하게 되었습니다. IRK 커뮤니티의 소중한 친구 @BearCris 가 머나먼 타지에서 저희 곁을 떠났다는 참으로 안타까운 소식입니다. 평소 등산을 사랑하던 그가 절실히 동경하던 안나푸르나를 향해 새로운 도전을 펼치던 중이었습니다. 그의 꿈을 이루기 위한 여행을 우리 모두 응원하고 있었지만, 갑작스런 비보에 많은 이들이 슬퍼하고 있습니다.

그가 생전에 우리에게 보여준 삶의 열정과 도전정신, 그리고 산을 향한 순수한 애정은 많은 이들에게 영감과 행복을 주었습니다.

그의 가치있는 삶을 기리며, 마지막 인사를 하기 위해 한국에서는 그가 빠른 시일 내에 돌아오길 기다리고 있습니다.

현재 그의 절친한 친구 @KimGom 이 그를 고국으로 데려오기 위해 현지에 가 있으며, 한국에선 그를 기리기 위한 추모식을 준비중입니다.

그가 생전에 네팔 지역에 남긴 흔적이 있습니다. 단 2개의 오너 포탈.

포카라 지역의 Pokhara Mural
https://www.ingress.com/intel?ll=28.21044413163288,83.95958041204722&z=15

카트만두 지역의 North Swayambu Shrine #19
https://www.ingress.com/intel?ll=27.717212,85.290411&z=17&pll=27.717212,85.290411

이 메세지를 보고있는 현지 혹은 전세계 요원분들에게 호소드립니다.
한국에서 추모식이 진행될 때까지, 그의 흔적이 계속 유지되었음을 희망합니다.

그와의 추억을 기리기 위한 포탈로 기억될 수 있게 당분간 현 상태를 유지했음 합니다.
도움을 주실 수 있는 요원들의 연락 바라며 곧 있을 추모행사와 메세지는 추가적으로 공유할 예정입니다.

@BearCris 를 기리며...

아래 인그레스 스크린샷은 @BearCris님의 마지막 포스팅에서 가져왔습니다.

Ingress Resistance Korea is deeply saddened by the loss of our good friend @BearCris. We received word this week that he had passed away in a faraway land. To summit Annapurna was a dream come true for him, who made no secret of his love of climbing. We all supported him and cheered him on when he announced his dream trip. The sudden tragic news was heartbreaking.

The passion, determination and genuine affection he had for the mountains inspired and delighted many others.

To remember his meaningful life and say our last goodbyes, we now await his final journey back to Korea.

At this moment, his best friend and fellow agent @KimGom has traveled to Nepal to bring him home, and in Korea we have begun to prepare his memorial service.

He left behind traces of his visit to Nepal. Just two portal captures; one in Kathmandu (https://www.ingress.com/intel?ll=27.717212,85.290411&z=17&pll=27.717212,85.290411) and the other in Pokhara (https://www.ingress.com/intel?ll=28.21044413163288,83.95958041204722&z=15).

We sincerely ask all Ingress agents this message reaches for your assistance and understanding. We hope to keep these portals recharged in his memory, at least until his friends back home are able to give him a proper sendoff.

If you can help, please contact us. We will post again regarding the details of his memorial service.

@BearCris, rest in peace.

The photos and Ingress screenshots below were taken from @BearCris's last post in our community.
PhotoPhotoPhotoPhotoPhoto
16. 9. 2.
5 Photos - View album

Post has attachment

Post has shared content

Post has shared content
StrictMode for enforcing best practices at runtime

StrictMode isn't just for performance checks - it also offers some runtime checks for ensuring that you're sharing files correctly and encrypting your network traffic.

Watch the video, read the blog (https://medium.com/google-developers/strictmode-for-runtime-analysis-on-android-f8d0a2c5667e) and continue to #BuildBetterApps!

https://www.youtube.com/watch?list=PLWz5rJ2EKKc-lJo_RGGXL2Psr8vVCTWjM&v=BxTfwT7mkB4

Post has shared content

Post has shared content
알파고와 이세돌9단의 세 번째 매치가 시작되었습니다. 대국은 유튜브 https://goo.gl/PCe0zo 에서 생중계로 시청하실 수 있습니다.

Post has shared content
Android Support Library 23.2.1 available now

This release of the Android Support Library fixes a number of bugs in Support v4, AppCompat, CardView, RecyclerView, MediaRouter, Leanback, Design, and Vector Drawable Compat. See the revisions page (http://goo.gl/S5dxsR) for a full list of closed issues.

For AppCompat users, the flags for enabling support vector drawables described in the 23.2 blog post (http://goo.gl/073Mpo) are no longer required for usage of AppCompat. However, you can still take advantage of the app:srcCompat attribute if you wish to use support vector drawables for your own resources.

Please continue to file any Support Library bugs at https://goo.gl/FxTlom

Post has shared content
Why runtime permissions shouldn’t scare you
Pro-tip by +Joanna Smith

Marshmallow introduced Runtime Permissions, and that seems to be all anyone is talking about this summer. But that’s because prompting for a long list of permissions at install can intimidate users, and that’s not good for anyone. So apps targeting Marshmallow now have to put these permission requests into a context, by asking for them when the user is trying to use the relevant feature.

As great as this is, I’m sure that you’ve thought to yourself “that’s okay, I just won’t update to Marshmallow until I have to.” Updating your app isn’t as daunting as you might think, though. You simply need add a few lines of code that build in checks and graceful failures. So here’s a handy guide to walk you through it.

Step 1: check the platform. If the device is running Lollipop or earlier, then the user granted permission at install time, and you’re good to go. But if the device is running Marshmallow, you can’t be so certain. Clever developers can use the support library, though, which will do this check for you. That’s one less line of code for you to add.

Which brings us to step 2: check the permission status. A simple call to checkSelfPermission() (http://goo.gl/T7vE7b) will let you know if the permission is currently granted. The only scary thing here is that you can’t rely on assumptions here, because even if the user granted the permission in the past, they may have revoked it later on. So with one conditional statement, you’ve completed step 2.

If you don’t have permission, you may need step 3: explain the permission. In some instances, you’ll want to update the UI to clarify what that permission enables and why the feature needs it. This can be as simple as a toast or as complex as the fanciest layout. The cool thing here is that you don’t need to figure out what those moments are. A call to shouldShowRequestPermissionRationale() (http://goo.gl/bFyfVj) will indicate whether this is one of those clarifying moments. Easy enough, right?

And now, the heart of it-- step 4: request the permission. The requestPermissions() (http://goo.gl/yNuizg) method will prompt a dialog to the user to get their answer and then trigger your onRequestPermissionResult() callback to handle the response. This is only two lines of code to add. One to make the call, and one to declare the request code, which is indicative of where the user is in your app and what they are trying to do.

Finally, step 5: handle the response. Here is your biggest change, and all it is is overwriting your callback with a switch statement based on that request code. Your request code will help you restore the app to the right state if the permission has been granted. If the user rejected the request, though, you’ll need to update the UI to disable the feature or indicate that it won’t be available without the permission.

So, you see, it isn’t so scary to add support for runtime permissions. Take a crack at it and #BuildBetterApps ! And if you want some more context and implementation guidelines, check out the blog post from last week (http://goo.gl/JMnKQw).
Photo

Post has attachment

Post has attachment
Wait while more posts are being loaded