I completed a two year degree at a community college and now it's my first year away from home. I study Computer Science at the University of Houston. This is my first time away from home, so I'm still busy trying to figure out what I want to do with my life. I picked History as my major because even though I know it can be tough to find a job with the degree, it's something that I'm passionate about. American history is my favorite area of History and that's what I hope to focus on during times when I'm off school.
To live a happy, successful life, I believe it's important to have many hobbies and connections with other people. Staying close to my family is important. I have two brothers that I frequently hang out with in order to explore my hobbies, which include camping, playing basketball, and going to movies. When I'm not doing these things in a social setting, I like time to myself. I blog and write to help me sort through things that happen to me everyday and to reach out to people online that want interesting things to read.
Activity wise, I love going to movies, reading, pets, and walks. When I have time, I take my animals on a two hour hike that gives them a chance to explore their loves too.
I want to eventually graduate and work in an American history museum. For now, though, the fun of life is in the search.
We wrapped up the elementary work, now we will look into the technical issues that are still left. If you were afraid of buggy betas, it has gotten to a point where its pretty decent for daily use.
We rewrote the original AOSP control pretty much from scratch now. Even if it was once based on the Google control, you wont be able to recognize much when you see the code (which comes out soon). It is blazing fast now and responsive due to hardware acceleration and optimized drawing. The old betas were a bit laggy due to test code, we cleaned up completely. It should not be heavy on your battery either. Flicking or navigating it blind is simple. Until now we can do:
- Per app color, it has its own theme aswell but when switched off it picks up colors you define per app (see video)
- Recents key transforms into /// kill-all-button inside the recents view
- Rubberbanding for fast navigation
- Displays status informations like clock, date, notifications on touch
- We wrote our own custom panels for notifications and toggles that can be flicked into view - these are still basic though
- It can be on either of all the four sides, you can even set up multi trigger areas
- It is resolution independent and scalable - it will not look distorted on tablets and phablets anymore
- You can control the animations, even switch them off
- It supports per-app-expand, meaning that it can jump into PIE mode for apps you chose
First updates starting to roll out soon. 1-2-3 hours.
The typical web app development workflow involves using some clever window arrangement to display your editor and the DevTools side-by-side, or having to switch back and forth between them. This can sometimes feel cumbersome and time-consuming. Wouldn't it be useful if you could instead just edit the source for your web apps directly in the DevTools?
Just find an error, fix it and save to the file from just one place.
This workflow becomes easier today with Workspaces, an in-progress experimental feature that’s landed in Chrome Canary. Workspaces allow you to select custom directories in your file system which are always available for you to edit within the Sources panel. This can be the directory for an app you're working on or even a whole list of different projects.
Workspaces can greatly simplify your workflow, however they're certainly not for all types of development. For those scenarios when you just want to be able to debug and bug-fix, you may find not having to leave the DevTools a time-saving experience and we hope this is where they will help the most.
To get started with Workspaces in Canary, enable the DevTools experiments in chrome://flags then head over to Settings > Experiments and enable “File system folders in Sources Panel”. Next, restart the DevTools by closing and re-opening them. You should now see a “Workspaces” tab in Settings.
Under this tab, you will see an “Add file system” link allowing you to add local file systems for editing. Directories you would like to add as a workspace require an “.allow-devtools-edit” file to be present (for now), which you can create via “touch .allow-devtools-edit” at the command-line or using your text editor of choice. When you’ve added a file system, you’ll be able to view and edit files within that directory anytime you’re working in the Sources panel.
No having to leave the DevTools - just find issues, fix them and save. This better enables workflows like the one described in his “Never having to leave the DevTools” video http://remysharp.com/2012/12/21/my-workflow-never-having-to-leave-devtools/.
We hope that Workspaces will open the door to fully developing within the DevTools, without the need to switch to other applications. Stay tuned for more on this in the coming months
Please note that Workspaces are highly experimental and are subject to change.
Written by . Reviewed by