One of the most important things in AngularJS is the scope. As you might be familiar with jQuery and Javascript, you know that this keyword can have different values in the same function called from different points in your application – one very clear example would be a delete row function for an already existing grid. Even though the same button(or whatever UI representation you chose) is the same, will delete only the specific row – unless there are bugs in code. Normally, the context will be set to the row, and the row element has the responsibility to provide a […]
Category: About MI Master
18 posts
During experimentation with AngularJS and using my previous experience with MV* set of patterns and their implementation I found out some interesting facts that may help you a lot in the future development of a loosely coupled web front-end.
Is AngularJS yet another library or it thoroughly has the capability to change the way we develop applications? What's the difference between AngularJS and other libraries like the mature world wide known jQuery and its plethora of plugins, or Kendo UI /ExtJS? What brings it more in terms of data binding than KnockoutJS? This are the questions I will try to answer in order to decide if I would like to add AngularJS library to my skillset.
Today is a lazy Sunday, so I will be quick. jQuery works better after you have your first coffee. Even better after second!
One of the biggest problems in web UI is to synchronize page elements one upon each other, but by far the hardest is when dealing with multiple dropdowns. A good, clean User Interface is the key to your customer’s heart! This can be achieved in several ways, such as: on the change of the first dropdown, a new page request is issued to the server, with the selected item as current item and the server will figure out which element(s) need to be selected in the subsequent synchronized dropdowns – old style, not so used anymore because it takes time and bandwidth […]
Yesterday I did the last step in my Media Informatics master endeavor: I presented my master thesis. After quite a few months of development on the Microsoft Surface, the application that resulted was a good start for a (possible) commercial product. We started from the idea that a multitouch table device would offer more space, possibilities and opportunities to improve the collaboration and communication in the brainstorming phase of any project. This evolved very much during the development and conceiving the master thesis. It became a tool which not only supported and enhanced collaboration, but also, to name a few: offered clues gathered […]
Overview of my Master thesis, it summarizes the work by presenting the contributions to the research field and also the future work based on the already created prototype. The Breiny application is meant to support the Brainstorming process by using computers in a modern way – Natural User Interface. After creating the prototype, a User Evaluation was used to prove or disprove the theoretical hypotheses
Among all flavours of MVC and its brothers (Model View ViewModel, Model–view–adapter, Model–view–presenter, Observer pattern, Presentation–abstraction–control, Hierarchical model–view–controller), the Microsoft implementation of the pattern in .Net MVC framework is based on Front Controller pattern and Model 2 patterns ["Programming Microsoft ASP.NET MVC" by Dino Esposito].
Overloading methods in ASP .Net MVC is not possible at this time. This article proposes two solutions to overcome this limitation.
The Evaluation session started with the Prototype presentation. This was targeted only on the User Interfaces, explaining how and which actions can be performed with each area of interest (UserControls and Main SurfaceWindow from Implementation Chapter). The users were encouraged to experience the interface and ask questions during the presentation, in order to understand better the interaction with the prototype.
The theoretical evaluation of the thesis work starts with by assessing in which measure the research questions were answered by the proposed concept. Then, the analysis will focus on the comparison of the implemented prototype’s features with the ones presented in Related work, in order to see which ones were implemented and how the prototype’s features map on the array of desired ones.
The prototype implementation tries to follow as close as possible the recommended architectural patterns and guidelines. To support the argumentation, a class diagram will be presented to give a visual orientation through the prototype implementation presentation. The built prototype supporting Brainstorming Sessions on Microsoft Surface, further named Breiny, was developed as part of this thesis and uses all the above framework features.