After a half year of tumbling the end is clearly near, MeeGo is dead and Tizen is born. Bad news for MeeGo. Maybe the year 2011 will be go down in history as "the mobile device os dying". MeeGo and WebOS were both exciting pieces of software. Especially WebOS with its Mojo SDK was far more ahead. But when big players shows there teeth, something dies.
So lets start, again, from the scratch and write a new OS for mobile devices.
So whats Tizen all about?
Tizen is an open source, standards-based software platform supported by leading mobile operators, device manufacturers, and silicon suppliers for multiple device categories, including smartphones, tablets, netbooks, in-vehicle infotainment devices, smart TVs, and more. Tizen will offer an innovative operating system, applications, and a user experience that consumers can take from device to device.
This application allows you to capture the entire screen, the active window or a selected region. You can set the delay that elapses before the screenshot is taken and the action that will be done with the screenshot: save it to a PNG file, copy it to the clipboard, open it using another application, or host it on ZimageZ, a free online image hosting service.
Thats what the developer site is writing about this tool.
On my point of view, it is easy to use, has a small memory footprint and works quite well.
If you have another tool that is better or has other advantages, throw it in as a comment :-).
While you are using something like "fbrun", a softlink in your "/usr/bin" as "ln -s xfce4-screenshoot screenshoot" should speed up your daily business (so you have to tip "screen" and hit the "tab"-button).
Another book from apress and another one i am impressed of.
As easy as the cmd zend framework book written and with 276 pages full of knowledge, this book kickstarts your feelings for a java script framework.
From my point of view, this book is smart as the MooTools Framework. Especially if you consider that in my world, java script means always "double the work for a bit better of user experience".
But as AJAX evolves, the java script frameworks sprouting out as fresh grass on a damp ground.
So back to the book. I have already "index" the book by using some stickers and it finaly covers all ... well as the book title labels it ... the essentials.
More or less then 15 pages explain the philosophy of MooTools and of Java Script itselfs. Nice to know, the author writes about the pro's and con's of MooTools and on the major other java script frameworks (like jquery, prototype and so on).
After this, the reader learns about the basic of java script and of using common techniques to implement the features you are searching for. There are some pages about the prototype concept in Java Script and also all about the MooTools Core.
The Core is represented by a bunch of core files. Depending of how you are using the MooTools, here is the first part where you can downsize your whole Java Script library!
After that, you learn about native objects, in particular for arrays and hashs (aka objects). Following this, there is a chapter about the elements and some methods and filters.
When you have reached chapter seven. The basics and theoretical stuff starts to blur. As in the other apress book i have mention some weeks ago, the theory is implemented by real problems. This implementations are getting complexer and of course better, so you learn more by refactoring you code. You learn about requests, respons, json and cookies, swiff and classes and there inheritance concept, also about writing your own class and extend them with options, events and chains.
The book also covers the basics of the fx.js (where all the wonderfull magic for effects are stored ;-) ). Even more, you read about plug-ins.
Finally, the appendix is rounding off the book.
If you are interested in a robust and modern java script framework (or if you have to be concerning of request by customer ;-) ), mootools and this book is your way to dig in.
I know it is an important feature of netbeans but sometimes it is scanning a lot, especially when you have to use a trunk and a bunch of branches, all separated as different projects.
If you want to stop auto-scanning that often (netbeans also does it after you unchecked it ;-), go to "Tools->Options->Mscellaneous->Files" and uncheck "Enable auto-scanning of sources".
Thats it! The downside of this option is, that you have to manually refresh folders by using "rightclick->Refresh Folder" in your project- or filestree.