Offering uncompromising and trouble free performance, it can manage the growing complexity and issues of the daily college activities. It helps various departments to communicate each other and thus bring better service to staff and students. The software is designed to meet the information need of all level of management, planning, monitoring and control of daily activities.

Monday, February 24, 2014

Nokia announces the X and X+, its first Android phones

Nokia is officially launching its very first Android devices, known as the X and the X+, on stage at its annual Mobile World Congress press conference. We were all taken aback by the second (and third) device (since only one leaked), so it's incredible to see Nokia make such a huge foray into enemy territory. The X will have a 4-inch, 840 x 480 IPS screen, 512MB RAM, 4GB of storage expandable storage via microSD slot and 3-megapixel camera, while the X+ sports the same specs but more RAM (768 MB) and an included 4GB microSD card. You won't be getting Google's apps or Play store, however as both handsets will be based on the forked AOSP Android OS. Nokia says that'll have the advantages of the Android ecosystem, but with a "differentiated experience." So far, Here Maps, MixRadio, Skype and Outlook are being featured on the Nokia Store. You can access the Nokia and third party stores using the devices, but not Google Play, obviously. We've heard SwiftKey will be available on the Nokia X range (and for free, too), as will BBM, which is also coming to Windows Phone sometime "this summer."
The new devices are featuring a ported version of FastLane for Asha devices as a sort of skin, to give a similar experience as its other budget handsets. When you swipe across it, it'll bring up a sort of notification bar showing recently used apps, missed calls and texts and other activities. During the demo, Elop showed both the Nokia Store also Yandex, where he pulled down Aero Express, a Russian-flavored app. The X will be available immediately in growth markets (ie, not the US) and run 89 euros. The X+, meanwhile, will run 99 euros but won't arrive until sometime in Q2 this year.

Friday, December 6, 2013

Bharti Airtel to launch 4G voice service in Bangalore

NEW DELHI: India's leading GSM service provider Bharti Airtel is set to launch voice call facility on its 4G LTE network in Bengaluru. The company has been offering 4G data services in Pune, Kolkata, Chandigarh, Mohali, Panchkula and Bengaluru.

Bharti Airtel through its Twitter account announced that Bengaluru customer will be able to use Airtel 4G services on LTE enabled smartphones in 3 weeks.

"ET Telecom did not get any response over the development from the company".

The telco has adopted Circuit Switched Fall Back (CSFB) technology for providing voice calling facility over its 4G LTE networks in the country. With CSFB technology deployed within the newtork, the telco would be able to offer voice to its LTE subscribers through its 3G and even 2G network.

Bharti Airtel, in February this year, announced the successful completed the trials of CSFB technology in the cities of Pune, Kolkata and Bengaluru.

The telco has a tie-up with Huawei for 4G devices in the country. Last year, it announced Huawei's 4G enabled Ascend P1 LTE exclusively for its 4G LTE network.

Airtel has been testing 4G LTE smartphones from Samsung, ZTE and other Indian smartphone vendors such as Micromax on its 4G LTE network.

A few months back, Bharti Airtel acquired 100 percent stake in Wireless Business Services (WBSPL), a company founded by US chipmaker Qualcomm. The acquisition allows the company to offer high-speed 4G services in New Delhi, Mumbai, Haryana and Kerala.

Microsoft leads disruption of largest infected global PC network

Microsoft Corp said on Thursday it had disrupted the largest network of compromised personal computers, involving some 2 million machines around the world, since it stepped up its battle against organized online criminals three years ago.
The Redmond, Wash.-based software giant filed a lawsuit in Texas and won a judge's order directing Internet service providers to block all traffic to 18 Internet addresses that were used to direct fraudulent activity to the infected machines.
Law enforcement in many European countries served warrants at the same time, seizing servers expected to contain more evidence about the leaders of the ZeroAccess crime ring, which was devoted to "click fraud."
Such rings use networks of captive machines, known as botnets, in complicated schemes that force them to click on ads without the computer owners' knowledge. The schemes cheat advertisers on search engines including Microsoft's Bing by making them pay for interactions that have no chance of leading to a sale. Microsoft said the botnet had been costing advertisers on Bing, Google Inc and Yahoo Inc an estimated $2.7 million monthly.
The coordinated effort marks the eighth time Microsoft has moved against a botnet and a rare instance of it doing serious damage to one that is controlled with a peer-to-peer mechanism, where infected machines give each other instructions instead of relying on a central server that defenders can hunt down and disable.
But the ZeroAccess botnet still had a weakness: The code in the infected machines told them to reach out to one of the 18 numeric Internet addresses
Microsoft recently opened a new Cybercrime Center in Redmond and is using new tools in its efforts. They are helped by a provision in trademark that allows pretrial seizure of suspected counterfeit goods, including websites that, as in the present case, are spreading tainted versions of the Internet Explorer browser.

Karbonn Titanium X Android smartphone unveiled at Rs 18,490

Karbonn on Thursday launched its Titanium X smartphone at an inaugural price of Rs 18,490. Powered by a full HD display combined with IPS screen, the phone is designed for the youth.
The Android 4.2 Jelly Bean device has a 1.5 GHz quad-core processor with 1GB RAM, 16GB internal memory and 2300 mAh battery. Both the 13MP rear and 5MP front camera have flash.
"The Titanium X brings best in class industry features to the affordable smartphone market of the country. With top of the line product innovations like One Glass Screen (OGS) enabled with IPS Display for wide viewing angles, NFC, OTG Support up to 32GB, Sleek Unibody Design," Shashin Devsare, Executive Director, Karbonn Mobiles said in a release.

Tuesday, November 12, 2013


Model–view–controller (MVC) is a software architecture pattern which separates the representation of information from the user's interaction with it. The model consists of application data, business rules, logic, and functions. A view can be any output representation of data, such as a chart or a diagram. Multiple views of the same data are possible, such as a bar chart for management and a tabular view for accountants. The controller mediates input, converting it to commands for the model or view.

The purpose of many computer systems is to retrieve data from a data store and display it for the user. After the user changes the data, the system stores the updates in the data store. Because the key flow of information is between the data store and the user interface, you might be inclined to tie these two pieces together to reduce the amount of coding and to improve application performance. However, this seemingly natural approach has some significant problems. One problem is that the user interface tends to change much more frequently than the data storage system. Another problem with coupling the data and user interface pieces is that business applications tend to incorporate business logic that goes far beyond data transmission.
How do you modularize the user interface functionality of a Web application so that you can easily modify the individual parts?
The following forces act on a system within this context and must be reconciled as you consider a solution to the problem:
  • User interface logic tends to change more frequently than business logic, especially in Web-based applications. For example, new user interface pages may be added, or existing page layouts may be shuffled around. After all, one of the advantages of a Web-based thin-client application is the fact that you can change the user interface at any time without having to redistribute the application. If presentation code and business logic are combined in a single object, you have to modify an object containing business logic every time you change the user interface. This is likely to introduce errors and require the retesting of all business logic after every minimal user interface change.
  • In some cases, the application displays the same data in different ways. For example, when an analyst prefers a spreadsheet view of data whereas management prefers a pie chart of the same data. In some rich-client user interfaces, multiple views of the same data are shown at the same time. If the user changes data in one view, the system must update all other views of the data automatically.
  • Designing visually appealing and efficient HTML pages generally requires a different skill set than does developing complex business logic. Rarely does a person have both skill sets. Therefore, it is desirable to separate the development effort of these two parts.
  • User interface activity generally consists of two parts: presentation and update. The presentation part retrieves data from a data source and formats the data for display. When the user performs an action based on the data, the update part passes control back to the business logic to update the data.
  • In Web applications, a single page request combines the processing of the action associated with the link that the user selected with the rendering of the target page. In many cases, the target page may not be directly related to the action. For example, imagine a simple Web application that shows a list of items. The user returns to the main list page after either adding an item to the list or deleting an item from the list. Therefore, the application must render the same page (the list) after executing two quite different commands (adding or deleting)-all within the same HTTP request.
  • User interface code tends to be more device-dependent than business logic. If you want to migrate the application from a browser-based application to support personal digital assistants (PDAs) or Web-enabled cell phones, you must replace much of the user interface code, whereas the business logic may be unaffected. A clean separation of these two parts accelerates the migration and minimizes the risk of introducing errors into the business logic.
  • Creating automated tests for user interfaces is generally more difficult and time-consuming than for business logic. Therefore, reducing the amount of code that is directly tied to the user interface enhances the testability of the application.
    The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:
  • Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).
  • View. The view manages the display of information.
  • Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

  • Figure 1 depicts the structural relationship between the three objects.
    Figure 1: MVC class structure
    It is important to note that both the view and the controller depend on the model. However, the model depends on neither the view nor the controller. This is one the key benefits of the separation. This separation allows the model to be built and tested independent of the visual presentation. The separation between view and controller is secondary in many rich-client applications, and, in fact, many user interface frameworks implement the roles as one object. In Web applications, on the other hand, the separation between view (the browser) and controller (the server-side components handling the HTTP request) is very well defined.
    Model-View-Controller is a fundamental design pattern for the separation of user interface logic from business logic. Unfortunately, the popularity of the pattern has resulted in a number of faulty descriptions. In particular, the term "controller" has been used to mean different things in different contexts. Fortunately, the advent of Web applications has helped resolve some of the ambiguity because the separation between the view and the controller is so apparent.


    In Application Programming in Smalltalk-80: How to use Model-View-Controller (MVC) [Burbeck92], Steve Burbeck describes two variations of MVC: a passive model and an active model.

    The passive model is employed when one controller manipulates the model exclusively. The controller modifies the model and then informs the view that the model has changed and should be refreshed (see Figure 2). The model in this scenario is completely independent of the view and the controller, which means that there is no means for the model to report changes in its state. The HTTP protocol is an example of this. There is no simple way in the browser to get asynchronous updates from the server. The browser displays the view and responds to user input, but it does not detect changes in the data on the server. Only when the user explicitly requests a refresh is the server interrogated for changes.

    Figure 2: Behavior of the passive model
    The active model is used when the model changes state without the controller's involvement. This can happen when other sources are changing the data and the changes must be reflected in the views. Consider a stock-ticker display. You receive stock data from an external source and want to update the views (for example, a ticker band and an alert window) when the stock data changes. Because only the model detects changes to its internal state when they occur, the model must notify the views to refresh the display.
    However, one of the motivations of using the MVC pattern is to make the model independent from of the views. If the model had to notify the views of changes, you would reintroduce the dependency you were looking to avoid. Fortunately, the Observer pattern [Gamma95] provides a mechanism to alert other objects of state changes without introducing dependencies on them. The individual views implement the Observerinterface and register with the model. The model tracks the list of all observers that subscribe to changes. When a model changes, the model iterates through all registered observers and notifies them of the change. This approach is often called "publish-subscribe." The model never requires specific information about any views. In fact, in scenarios where the controller needs to be informed of model changes (for example, to enable or disable menu options), all the controller has to do is implement the Observer interface and subscribe to the model changes. In situations where there are many views, it makes sense to define multiple subjects, each of which describes a specific type of model change. Each view can then subscribe only to types of changes that are relevant to the view.
    Figure 3 shows the structure of the active MVC using Observer and how the observer isolates the model from referencing views directly.
    Figure 3: Using Observer to decouple the model from the view in the active model
    Figure 4 illustrates how the Observer notifies the views when the model changes. Unfortunately, there is no good way to demonstrate the separation of model and view in a Unified Modeling Language (UML) sequence diagram, because the diagram represents instances of objects rather than classes and interfaces.
    Figure 4: Behavior of the active model


    Windows Presentation Foundation (WPF) is a next-generation presentation system for building Windows client applications with visually stunning user experiences. With WPF, you can create a wide range of both standalone and browser-hosted applications.

    The core of WPF is a resolution-independent and vector-based rendering engine that is built to take advantage of modern graphics hardware. WPF extends the core with a comprehensive set of application-development features that include Extensible Application Markup Language (XAML), controls, data binding, layout, 2-D and 3-D graphics, animation, styles, templates, documents, media, text, and typography. WPF is included in the Microsoft .NET Framework, so you can build applications that incorporate other elements of the .NET Framework class library.
    This overview is intended for newcomers and covers the key capabilities and concepts of WPF. Experienced WPF developers seeking a review of WPF may also find this overview useful.
    WPF exists as a subset of .NET Framework types that are for the most part located in the System.Windows namespace. If you have previously built applications with .NET Framework using managed technologies like ASP.NET and Windows Forms, the fundamental WPF programming experience should be familiar; you instantiate classes, set properties, call methods, and handle events, all using your favorite .NET Framework programming language, such as C# or Visual Basic.


    C# programs run on the .NET Framework, an integral component of Windows that includes a virtual execution system called the common language runtime (CLR) and a unified set of class libraries. The CLR is the commercial implementation by Microsoft of the common language infrastructure (CLI), an international standard that is the basis for creating execution and development environments in which languages and libraries work together seamlessly.
    Source code written in C# is compiled into an intermediate language (IL) that conforms to the CLI specification. The IL code and resources, such as bitmaps and strings, are stored on disk in an executable file called an assembly, typically with an extension of .exe or .dll. An assembly contains a manifest that provides information about the assembly's types, version, culture, and security requirements.
    When the C# program is executed, the assembly is loaded into the CLR, which might take various actions based on the information in the manifest. Then, if the security requirements are met, the CLR performs just in time (JIT) compilation to convert the IL code to native machine instructions. The CLR also provides other services related to automatic garbage collection, exception handling, and resource management. Code that is executed by the CLR is sometimes referred to as "managed code," in contrast to "unmanaged code" which is compiled into native machine language that targets a specific system. The following diagram illustrates the compile-time and run-time relationships of C# source code files, the .NET Framework class libraries, assemblies, and the CLR.

    Language interoperability is a key feature of the .NET Framework. Because the IL code produced by the C# compiler conforms to the Common Type Specification (CTS), IL code generated from C# can interact with code that was generated from the .NET versions of Visual Basic, Visual C++, or any of more than 20 other CTS-compliant languages. A single assembly may contain multiple modules written in different .NET languages, and the types can reference each other just as if they were written in the same language.
    In addition to the run time services, the .NET Framework also includes an extensive library of over 4000 classes organized into namespaces that provide a wide variety of useful functionality for everything from file input and output to string manipulation to XML parsing, to Windows Forms controls. The typical C# application uses the .NET Framework class library extensively to handle common "plumbing" chores.