lasergogl.blogg.se - Licecap mobile

Licecap mobile android#
Licecap mobile code#

This is very useful for taking screenshots, and for seeing how responsive an app is to different device sizes and resolutions. It can masquerade as an iPhone, Kindle, Blackberry, Nexus, and more. With Chrome’s mobile emulation, you can make your desktop browser pretend that it’s something else. What a great way to test an app, get screenshots, figure out the “how to” instructions you need to write, and just see how the user experience feels. I haven’t yet used a device from one of these labs, but the idea is awesome. Smart, enthusiastic people have set up hubs of Internet-connected devices at various locations around the world, and made them available to us all to use. Some people may even want to donate new devices to the cause. The idea is that people may have last year’s mobile phone lying around, that they’d be willing to allow other people to use for testing.

But here’s an exciting initiative that I heard about recently: Open Device Labs. Especially for those of us dealing with mobile apps, there are just way too many devices out there for it to be feasible to have an example of each one. It can be very difficult to try out an application on every supported device or platform. Open Device Labs – Access to real devices and platforms for test-driving an app

Edit HTML on the spot, to see the effect live on a web page before putting my changes into the source code.

Watch the error messages scrolling past on the “Console” tab.

Debug a JavaScript function, using breakpoints and variable watches.

Sometimes the cascading effect of CSS doesn’t seem to follow the laws of gravity! This is particularly useful when there are a number of stylesheets at play.

Check which CSS style is in effect on a particular block of HTML.

These are the functions I use most often: There are many many things you can do with the DevTools. The Chrome DevTools documentation is a good guide. The “Preview” box at the bottom of this screenshot shows the result: You can even choose from a number of styles, such as “colorful”, “friendly”, “fruity”, and so on.įor example, I pasted in a Java “hello world” class, and asked for “tango” style highlighting. You can grab the HTML and CSS code, or copy and paste the highlighted text itself. Then click “Highlight!” to see the result.

Paste in your code, and select the coding language, to get the appropriate highlighting.

Licecap mobile code#

converts a code snippet into styled HTML, which you can copy and paste into your page. Code is much easier to understand if the text is highlighted to indicate method names, variable declarations, and other syntactical essentials. I frequently need to add a code sample to an HTML page, or include a slice of code in a presentation. Now that’s out of the way, let’s look at some super-useful and less-talked-about tools for API tech writers in particular.

Licecap mobile android#

I like to dabble in Android Studio and IntelliJ IDEA, just to see what’s happening. For example, if trapped on a Linux VM where I don’t have my own editor, I may find myself in Pico editor. I do dip in and out of other editors when I need to. I use it primarily for HTML, CSS and JavaScript. Hehe, I can’t resist mentioning my favourite editor, Komodo. So, aren’t you going to talk about editors at all? 😉

From Bret McGowen on the Rackspace blog, My Text Editor Final Four.

Chantel Brathwaite, writing on the TechWhirl blog about Technical Writing on a Shoestring.

It’s well worth following Mike’s blog too.

Mike McCallister’s presentation, Open Source Tools for User Assistance.

The debates about which tool is best can get quite fiery! Particularly when talking about editors and IDEs (Integrated Development Environments) most people have their favourites. There are plenty of blog posts and articles about tools for documentation and code, including open source tools. Those of which you’d say, “When I need it, I really need it.” Since there are already some great resources on the Web about editors and IDEs, I plan to focus on a motley collection of “other” tools. Part of the presentation is about useful tools for API technical writers. I’ll be speaking about API technical writing at STC Summit 2014.