$30 off During Our Annual Pro Sale. View Details »

Techie Corner: September 2nd week

cogzidel
September 03, 2012

Techie Corner: September 2nd week

Presentation created by G.K. Nagarajan- Senior Developer, Cogzidel Technologies

cogzidel

September 03, 2012
Tweet

More Decks by cogzidel

Other Decks in Technology

Transcript

  1. TECHIE CORNER
     Smesh
     MeeGo
     GNU/Linux
     Code Review

    View Slide

  2. MeeGo
     The MeeGo project provides a Linux-based, open source
    software platform for the next generation of computing
    devices.
     The MeeGo software platform is designed to give developers
    the broadest range of device segments to target for their
    applications, including netbooks, handheld computing and
    communications devices, in-vehicle infotainment devices,
    smart TVs, tablets and more – all using a uniform set of APIs
    based on Qt.
     For consumers, MeeGo will offer innovative application
    experiences that they can take from device to device.
    MeeGo

    View Slide

  3. HISTROY
     It was first announced at Mobile World Congress in February
    2010 by Intel and Nokia in a joint press conference. The
    stated aim is to merge the efforts of Intel's Moblin and Nokia's
    Maemo former projects into one new common project.
    MeeGo

    View Slide

  4. COMPANIES SUPPORT
    MEEGO
     Acer-Iconia M500 tablet will run MeeGo
     Linpus-Created the Linpus Lite Computer with a MeeGo OS
     ST-Ericsson-The U8500 Platform will include MeeGo
     Mandriva-The Mandriva minis will run on MeeGo
     Nokia-Nokia currently has two MeeGo handsets, the N9 and
    N950.
     Gameloft-Verbally supports MeeGo and has declared its
    intention to use it for future mobile games
     Jaguar Land Rover-They plan to use MeeGo for their New
    car Infotainment
    MeeGo

    View Slide

  5. MEEGO PRODUCT
     The N9 rocks — it has an awesome UI and it’s pretty slick.
    However, without a major handset maker on board,
    there’s only so much Intel can do about it. And so far all
    other major players seem focused on other platforms,
    most notably Android and Windows Phone.
     To make things even worse for the MeeGo’s prospects,
    the Nokia N9 is super expensive. It costs more than 600
    EUR, which is a lot of money considering its hardware —
    the same cash get you a faster device equipped with a
    dual-core processor.
    MeeGo

    View Slide

  6. MEEGO PRODUCT (Con…)
     There is a new site called N9-Apps.com which serves as a hub for all
    Nokia N9 applications. The site features three categorized to choose
    from. You have the Hot, Top, and Fresh sections so that you could
    easily browse apps for your N9 depending on your preferences.
    There are paid and free apps listed in the site plus each app has a
    lists of features and as well as demo and screenshots. Unlike on the
    Nokia Store, you can check or see paid/premium apps here that are
    not available in your region. But of course you need other resources
    to download these paid apps.
     If you have Nokia N9 check the site: N9-Apps.com
     Meanwhile, there is also a dedicated site for MeeGo devices (N9 and
    N950) that you can visit and easily check for the latest apps for your
    said devices. The my-meego.com/software is a software catalog one.
    Go check out the free and new apps in this site too.
    MeeGo

    View Slide

  7. Smesh
    Smesh
     SMesh IS seamless wireless mesh network being developed
    by the Distributed System and Networks Lab at Johns
    Hopkins University
     It provides peer-to-peer connectivity, Internet connectivity,
    and fast handoff to mobile clients across the mesh
     Clients get connected automatically through standard DHCP.
    No software or drivers need to be installed on the mobile
    devices.
     SMesh takes care of providing end-to-end connectivity
    transparently for the clients
     seamless wireless mesh network

    View Slide

  8. Introduction
     Penetration of internet usage is increased day by day in media services
     To promote the media services we believed only server-based streaming
     In server-based streaming has high delays and high link stress , to over come we
    using peer – to – peer (P2P)
     In the streaming services two kinds of users group there
     Stable Group -whose never disturb the services
     dynamic group -whose frequently hop from one channel to another
     We propose a novel framework called ―SMesh‖ to serve dynamic groups.
     Faster response time for the global operations in this service
     Provided a reasonable problem –solving solution
     Provisioning cloud from multiple domains and interconnection
     Resolve the workload balance of the datacenters.
     Save time by distributing media stream.
     control messaging and guiding the construction of overlay trees
     Does not require a central server for mesh maintenance
     It is used in order to reduce control and delivery overhead
     Low maintain cost
     Supports multiple groups and hence effective distribution of data
     Availability of portion of their resources
    Smesh

    View Slide

  9. Modules
     Peer to Peer Network Module
     Distributed partition detection Module
     Dynamic Joining Host Module
     Path Aggregation for QoS Provisioning Module
    Smesh

    View Slide

  10. Control Flow
    Smesh

    View Slide

  11. Triangulation Details
    For P consisting of n points, all triangulations contain 2n-
    2-k triangles, 3n-3-k edges
     n = number of points in P
     k = number of points on convex hull of P
    Smesh

    View Slide

  12. Delaunay Triangulation
    Smesh

    View Slide

  13. Delaunay Triangulation
    Smesh

    View Slide

  14. Delaunay Triangulation
    Smesh

    View Slide

  15. Linux
     A free Unix-type operating system developed under the
    GNU General Public License.
     Open source
     Popular
     Support of most of platform available
    GNU/Linux

    View Slide

  16. History
     In 1991 Linus Torvalds writes 1st version of Linux Kernel
     Initially a research project about the 386 protected
    mode
     Linus UNIX to Linux
     Combined GNU with other tools forms a complete
    UNIX system
     1992: First distribution emerge
     Linux Kernel
     GNU and other tolls
     Installation procedure
    GNU/Linux

    View Slide

  17. Benefits of Linux
     Free & Open source
     A modern, very stable, multi-user, multitasking
    environment.
     Advanced graphical user interface. Ex. KDE , GNOME.
     Dozens of excellent, free, general-interest desktop
    applications.
     Freedom from viruses.
    GNU/Linux

    View Slide

  18. GNU & Distribution
     use the software at no charge, without any limitations
     copy, and distribute or sell unmodified copies of the
    software in the source or binary form
     use the software with proprietary (e.g., your own)
     modifications, free of charge, as long as you do not
    distribute or sell the modified version
     modify, and distribute or sell a modified version of the
    software as long as the source code is included and
    licensed on the same terms as the original you received
    (the GPL),
     sell support for the software, without any limitations.
     All Distribution list
     https://lwn.net/Distributions/
     https://en.wikipedia.org/wiki/List_of_Linux_distributions
    GNU/Linux

    View Slide

  19. Code Review
     Become more popular in recent years to help increase
    the quality of code that comes out of development
     Every developer known the pain of banal mistakes
     Wrong attribute here
     Misspelled property there
     An accidentally duplicate line of code
     Code review is simply the act of having someone else
    look at your code to find the mistakes you missed.
     It is intend to find and fox mistakes overlooked in the
    initial development phase, improving both the overall
    quality od software and the developer skill.
    Code Review

    View Slide

  20. Code review ways
     Over the shoulder – this is how small team usually
    handle the code review. A developer will write decent
    amount of code and call another developer over to
    have a look at it.
     Tool assistant review – dynamic type of code review
    ―hot seat game‖ for two developer in which one
    developer code and other follow the programmer by
    sitting beside him. After a couple 100 line of code,
    break switch phrases.
    Code Review

    View Slide

  21. Best practice
     ―Know your common mistakes and actively fight them‖
     Code review difficult to implement. But once done , It will
    not only decrease the number of defects in your code of
    will also increase collaboration and help to team building.
     Improve ―bother hood‖ among the developer and improve
    skills across an entire team.
     Any type of code review is better than none.
    Code Review

    View Slide

  22. Reference
     GNU/Linux
     http://en.wikipedia.org/wiki/Unix
    http://en.wikipedia.org/wiki/Linux
     Download Source Code from: http://www.kernel.org
     Books: Unix User Guide – Rebecca Thomas Your UNIX: The Ultimate
    Guide-Sumitabha Das
     Code Review
     http://smartbear.com/CMSPages/GetFile.aspx?guid=429d6abc-7d6d-4863-
    9118-848e4b135029
     http://en.wikipedia.org/wiki/Code_review
     https://code.google.com/p/gerrit/
     MeeGo
     en.wikipedia.org/wiki/MeeGo
     wiki.meego.com/ARM
     Smesh
     http://www.smesh.org/
     www.smesh.org/smesh_mobisys_presentation.ppt
    More…

    View Slide

  23. Thanks to
     Thanks to CL, PM, COO, CTO, CEO.
     Special Thanks to
    1. Balaji G.D - Smesh
    2. Gopinath T – GNU/Linux
    3. Kausalya R.D – MeeGo
    4. Valarmathy R – Code Review
     This presentation combined by Nagarajan G.K
    Thanking

    View Slide