Just imagine that you speed along the autobahn and realize that there is no a control panel - you don't know a fuel level, speed - anything... "It is impossible", you may say. And now imagine, your business is a car and you drive that car without a control panel, and you don't see the key performance indicators which are vital to "drive" your business. It's just a nightmare!
Similarly to the control panel in a car which helps you to get to destination, an effective digital dashboard helps you make mission critical decisions on the basis of well-structured visually presented information.
With the release of the Instrumentation ModelKit 3.0 the creation of digital dashboards, KPI, scorecards, and other data visualization applications becomes much easier.
Developed for Other Developers
The Instrumentation ModelKit is designed not only to serve as a rich library of ready-made controls: the delivery package includes 80+ instruments. It allows developers to build custom gauges even without the need to code. An intuitive designer makes the process of gauges creation and adjustment a brief! It is very important for a developer to have control over the created instrument. Assign custom style, behavior and appearance to the instrument with a few mouse clicks!
Changes for Improvement
Contemporary technology is aimed at the application development streamlining. Trying to follow the newest technology trends we created version 3.0 of the Instrumentation ModelKit that is specially redesigned for .NET 2.0 and supports the whole .NET 2.0 functionality. We modified the designer. Now the properties are available not only in the property grid but also from the designer toolbar. Fill editor can also be invoked by clicking an appropriate button. Improved visual interface of the designer ensures an automatic layout of the localized interface elements. These new features considerably speed up the process of gauges design.
We Do It for You
We want to help developers be as productive as possible.
To make the process of application development convenient we made it possible to change instruments appearance and behavior with a few mouse clicks. Modify, customize and adjust controls according to your demands!
To make the process of the product exploration fast we designed the unified sample browser which provides a set of comprehensive examples demonstrating the required functionality of controls.
To make the process of complex gauges development simple we included such high-level elements as RangedLevel, LinearLevel, Tank, etc.
To help you create visually stunning applications we developed a great number of features to make controls realistic: support for 3D skins, double buffering, ability to set interactive behavior to the controls, and GDI+ capabilities for elements drawing.
To make you save your money we pursue flexible licensing policy and allow you to distribute your applications with the use of the Instrumentation ModelKit components without any additional charges.
To give you full control over your applications we offer Professional edition of the product which contains full source code.
The Instrumentation ModelKit 3.0 will help you realize your potential and create professional data visualization applications.
About company:
Perpetuum Software specializes in development of high-quality .NET and ASP.NET software components compatible with MS Visual Studio .NET, C# Builder, Delphi .NET and other IDEs supporting .NET Framework. Such use-proven components as Report Sharp-Shooter, Instrumentation ModelKit, OLAP ModelKit, Chart ModelKit and other .NET components by Perpetuum Software are already well known on the software development market and are used by developers in more than 50 countries.
Windows Service Net 2.0
In this article we will talk about the new features in Struts 2.0. Over the years, every developers believes that struts is the best and simple framework to implement. Since last two years, more new frameworks come to the market and the use of Struts is declined. Lack of updation in the Struts framework is the main reason for developers choosing alternative framework. To answer this, Struts team comes with the Struts 2.0, an integration of Struts 1.0 with Webwork. Here we will look into the prominent features in the new framework.
Action classes
An Struts 2 Action may implement an Action interface, along with other interfaces to enable optional and custom services. Struts 2 provides a base ActionSupport class to implement commonly used interfaces. Albeit, the Action interface is not required. Any POJO object with a execute signature can be used as an Struts 2 Action object.
Threading Model
Struts 2 Action objects are instantiated for each request, so there are no thread-safety issues. (In practice, servlet containers generate many throw-away objects per request, and one more object does not impose a performance penalty or impact garbage collection.)
Testability
Struts 2 Actions can be tested by instantiating the Action, setting properties, and invoking methods. Dependency Injection support also makes testing simpler.
Servlet Dependency
Struts 2 Actions are not coupled to a container. Most often the servlet contexts are represented as simple Maps, allowing Actions to be tested in isolation. Struts 2 Actions can still access the original request and response, if required. However, other architectural elements reduce or eliminate the need to access the HttpServetRequest or HttpServletResponse directly.
Harvesting Input
Struts 2 uses Action properties as input properties, eliminating the need for a second input object. Input properties may be rich object types which may have their own properties. The Action properties can can be accessed from the web page via the taglibs. Struts 2 also supports the ActionForm pattern, as well as POJO form objects and POJO Actions. Rich object types, including business or domain objects, can be used as input/output objects. The ModelDriven feature simplifies taglb references to POJO input objects.
Expression Language
Struts 2 can use JSTL, but the framework also supports a more powerful and flexible expression language called "Object Graph Notation Language" (OGNL).
Binding values into views
Struts 2 uses a "ValueStack" technology so that the taglibs can access values without coupling your view to the object type it is rendering. The ValueStack strategy allows reuse of views across a range of types which may have the same property name but different property types.
Type Conversion
Struts 2 uses OGNL for type conversion. The framework includes converters for basic and common object types and primitives.
Validation
Struts 2 supports manual validation via the validate method and the XWork Validation framework. The Xwork Validation Framework supports chaining validation into sub-properties using the validations defined for the properties class type and the validation context.
Control Of Action Execution
Struts 2 supports creating different lifecycles on a per Action basis via Interceptor Stacks. Custom stacks can be created and used with different Actions, as needed.
Both Eugene Akinshin & Krishna Srinivasan are contributors for EditorialToday. The above articles have been edited for relevancy and timeliness. All write-ups, reviews, tips and guides published by EditorialToday.com and its partners or affiliates are for informational purposes only. They should not be used for any legal or any other type of advice. We do not endorse any author, contributor, writer or article posted by our team.
Krishna Srinivasan has sinced written about articles on various topics from Software. Java Tutorials and ArticlesHTML Tutorials and Articles. Krishna Srinivasan's top article generates over 1000 views. Bookmark Krishna Srinivasan to your Favourites.
Accredited Online Accounting Courses Depending on the work ethic of the student, an associated degree in accounting from taking online courses can be earned in as little as six months while a bachelors degree can be completed in around t...