2:23 PM |
Tuesday, March 27, 2012
Google's "Report a Bug" or "Feedback Tool" lets you select an
area of your browser window to create a screenshot that is submitted
with your feedback about a bug.
screenshot by Jason Small, posted in a duplicate question.
How are they doing this? Google's JavaScript feedback API is loaded from here:
https://ssl.gstatic.com/feedback/api.js
Their overview of the feedback module will demonstrate the screenshot capability:
http://www.google.com/tools/feedback/intl/en/learnmore.html
JavaScript can read the DOM and render a fairly accurate representation of that using
canvas
.
I have been working on a script which converts html into an canvas
image. Decided today to make an implementation of it into sending
feedbacks like you described.
The script allows you to create feedback forms which include a
screenshot, created on the clients browser, along with the form. The
screenshot is based on the DOM and as such may not be 100% accurate to
the real representation as it does not make an actual screenshot, but
builds the screenshot based on the information available on the page.
It
does not require any rendering from the server,
as the whole image is created on the clients browser. The HTML2Canvas
script itself is still in a very experimental state, as it does not
parse nearly as much of the CSS3 attributes I would want it to, nor does
it have any support to load CORS images even if a proxy was available.
Still quite limited browser compatibility (not because more couldn't
be supported, just haven't had time to make it more cross browser
supported).
For more information, have a look at the examples here:
http://hertzen.com/experiments/jsfeedback/
edit
The html2canvas script is now available seperately
here and some
examples here.
Ref:
http://stackoverflow.com/questions/4912092/using-html5-canvas-javascript-to-take-screenshots
8:30 PM |
Saturday, March 17, 2012
Have you wondered why certain programs are located under /bin, or /sbin, or /usr/bin, or /usr/sbin?
For example, less command is located under /usr/bin directory. Why
not /bin, or /sbin, or /usr/sbin? What is the different between all
these directories?
In this article, let us review the Linux filesystem structures and understand the meaning of individual high-level directories.
1. / – Root
- Every single file and directory starts from the root directory.
- Only root user has write privilege under this directory.
- Please note that /root is root user’s home directory, which is not same as /.
2. /bin – User Binaries
- Contains binary executables.
- Common linux commands you need to use in single-user modes are located under this directory.
- Commands used by all the users of the system are located here.
- For example: ps, ls, ping, grep, cp.
3. /sbin – System Binaries
- Just like /bin, /sbin also contains binary executables.
- But, the linux commands located under this directory are used typically by system aministrator, for system maintenance purpose.
- For example: iptables, reboot, fdisk, ifconfig, swapon
4. /etc – Configuration Files
- Contains configuration files required by all programs.
- This also contains startup and shutdown shell scripts used to start/stop individual programs.
- For example: /etc/resolv.conf, /etc/logrotate.conf
5. /dev – Device Files
- Contains device files.
- These include terminal devices, usb, or any device attached to the system.
- For example: /dev/tty1, /dev/usbmon0
6. /proc – Process Information
- Contains information about system process.
- This is a pseudo filesystem contains information about running
process. For example: /proc/{pid} directory contains information about
the process with that particular pid.
- This is a virtual filesystem with text information about system resources. For example: /proc/uptime
7. /var – Variable Files
- var stands for variable files.
- Content of the files that are expected to grow can be found under this directory.
- This includes — system log files (/var/log); packages and database
files (/var/lib); emails (/var/mail); print queues (/var/spool); lock
files (/var/lock); temp files needed across reboots (/var/tmp);
8. /tmp – Temporary Files
- Directory that contains temporary files created by system and users.
- Files under this directory are deleted when system is rebooted.
9. /usr – User Programs
- Contains binaries, libraries, documentation, and source-code for second level programs.
- /usr/bin contains binary files for user programs. If you can’t find a
user binary under /bin, look under /usr/bin. For example: at, awk, cc,
less, scp
- /usr/sbin contains binary files for system administrators. If you
can’t find a system binary under /sbin, look under /usr/sbin. For
example: atd, cron, sshd, useradd, userdel
- /usr/lib contains libraries for /usr/bin and /usr/sbin
- /usr/local contains users programs that you install from source. For
example, when you install apache from source, it goes under
/usr/local/apache2
10. /home – Home Directories
- Home directories for all users to store their personal files.
- For example: /home/john, /home/nikita
11. /boot – Boot Loader Files
- Contains boot loader related files.
- Kernel initrd, vmlinux, grub files are located under /boot
- For example: initrd.img-2.6.32-24-generic, vmlinuz-2.6.32-24-generic
12. /lib – System Libraries
- Contains library files that supports the binaries located under /bin and /sbin
- Library filenames are either ld* or lib*.so.*
- For example: ld-2.11.1.so, libncurses.so.5.7
13. /opt – Optional add-on Applications
- opt stands for optional.
- Contains add-on applications from individual vendors.
- add-on applications should be installed under either /opt/ or /opt/ sub-directory.
14. /mnt – Mount Directory
- Temporary mount directory where sysadmins can mount filesystems.
15. /media – Removable Media Devices
- Temporary mount directory for removable devices.
- For examples, /media/cdrom for CD-ROM; /media/floppy for floppy drives; /media/cdrecorder for CD writer
16. /srv – Service Data
- srv stands for service.
- Contains server specific services related data.
- For example, /srv/cvs contains CVS related data.
Ref :
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
6:30 PM |
Tuesday, March 6, 2012
------------------------------------
SimpleLocalizedAndroidApp v1.0
------------------------------------
WTFPL - Do What The Fuck You Want To Public License xD
Original Coder : @geniustd | Ref[R]
Modified By : @harshadura
Last Modified : 03-03-2012
[R] http://tharindudassanayake.wordpress.com/2012/02/25/use-sinhala-fonts-for-your-android-app
------------------------------------
Few Notes
------------------------------------
* You can use this[1] UCSC converter to convert unicode font into ttf related codes which are using in the xml view.
ex: "wessa" > jeiai
"jeiai" is the text you have to put into xml, that will result in "wessa" as output.
[1] http://www.ucsc.cmb.ac.lk/ltrl/services/feconverter/?maps=s_dlm-u.xml
* You can use any Sinhala unicode supported font instead of using "amal.ttf" font. (in case if you dont like that font style)
* No need of Tamil fonts cause Tamil unicode is already consist with Android. (South indians developers might rocking huh!)
Cheers! happy localizings!
Regards,
@harshadura