NeXt - Mirror of the OpenDaylight NeXt UI Toolkit gerrit project

  •        23

NeXt UI toolkit is an HTML5/JavaScript based toolkit for network web application. It provides a network centric topology UI component featuring high performance and rich functionality. NeXt can display large complex network topologies, aggregated network nodes, traffic/path/tunnel/group visualizations and it includes different layout algorithms, map overlays, and preset user friendly interactions. NeXt can work together with DLUX to build ODL apps.

https://wiki.opendaylight.org/view/NeXt:Main
https://github.com/CiscoDevNet/NeXt

Tags
Implementation
License
Platform

   




Related Projects

People-MVVM - Android Sample to explain Model View View Model and DataBinding in android applications

  •    Java

Example android Model View View Model and DataBinding used to explain how to use this pattern in our android applications. This example was created to support an article explanation Escribiendo android apps con Data Binding (spanish) and also it was created for a talk MVVM-android Meetup Androidinights by GDG Androidtitlan Mexico City March 2016.

RxCoordinator - 🎌 Reactive navigation library for iOS based on the coordinator pattern

  •    Swift

“How does an app transition from a ViewController to another?”. This question is common and puzzling regarding iOS development. There are many answers, as every architecture has different implementation variations. Some do it from the view controller, while some do it using a router/coordinator, which is an object that connects view models. Setup the root view controller in the AppDelegate.

XCoordinator - 🎌 Powerful navigation library for iOS based on the coordinator pattern

  •    Swift

⚠️ We have recently released XCoordinator 2.0. Make sure to read this section before migrating. In general, please replace all AnyRouter by either UnownedRouter (in viewControllers, viewModels or references to parent coordinators) or StrongRouter in your AppDelegate or for references to child coordinators. In addition to that, the rootViewController is now injected into the initializer instead of being created in the Coordinator.generateRootViewController method. “How does an app transition from one view controller to another?”. This question is common and puzzling regarding iOS development. There are many answers, as every architecture has different implementation variations. Some do it from within the implementation of a view controller, while some use a router/coordinator, an object connecting view models.

RxViewModel - ReactiveViewModel-esque using RxSwift

  •    Swift

The Model-View-ViewModel (MVVM) pattern is an application pattern that isolates the user interface from the underlying business logic. MVVM belongs to a class of patterns called Separated Presentation. These patterns provide a clean separation between the UI and the rest of the application. This improves the testability of the application and allows the application and its UI to evolve more easily and independently. The Model-View-ViewModel (MVVM) pattern helps you to cleanly separate the business and presentation logic of your application from its user interface (UI). Maintaining a clean separation between application logic and UI helps to address numerous development and design issues and can make your application much easier to test, maintain, and evolve. It can also greatly improve code re-use opportunities and allows developers and UI designers to more easily collaborate when developing their respective parts of the application.

MVVM Light Toolkit

  •    WPF

The MVVM Light Toolkit is a set of components helping people to get started in the Model - View - ViewModel pattern in all XAML/C# frameworks.


CoreMVVM - A Simple MVVM Framework

  •    

CoreMVVM is a simple basic MVVM framework that covers the *most* common development scenarios. Its a good place to start with MVVM. Its not as barebones as the MVVM Toolkit and neither is it as heavyweight as Prism\Cinch. Developed in C#.

mvvmlight - The main purpose of the toolkit is to accelerate the creation and development of MVVM applications in Xamarin

  •    CSharp

The main purpose of the toolkit is to accelerate the creation and development of MVVM applications in Xamarin.Android, Xamarin.iOS, Xamarin.Forms, Windows 10 UWP, Windows Presentation Foundation (WPF), Silverlight, Windows Phone. More information about the MVVM Light Toolkit can be found on http://www.mvvmlight.net.

ChangeDetection - Automatically track websites changes on Android in background.

  •    Kotlin

This app also showcases all the Android Architecture Components working together: Room, ViewModels, LiveData, Paging, WorkManager and Navigation. The app uses a Model-View-ViewModel (MVVM) architecture for the presentation layer. Each of the fragments corresponds to a MVVM View. The View and ViewModel communicate using LiveData and general good principles.

JulMar MVVM Helpers + Behaviors

  •    WPF

The MVVM Helper + Behavior library is a set of classes for WPF developers to help them build Model-View-ViewModel oriented applications. It includes some useful WPF classes, a base framework for MVVM and a bunch of Blend behaviors, triggers and actions.

MVVM Validation Helpers

  •    DotNet

MVVM Validation Helpers is a little framework that makes it easier for developers to implement validation in their WPF/Silverlight MVVM applications. You'll no longer have to implement IDataErrorInfo and INotifyDataErrorInfo interfaces manually in your view models. With th...

Fast MVVM

  •    

Fast MVVM ! The faster way to build your MVVM (Model, View, ViewModel) applications. It's a basic and educational way to learn and work with MVVM. We have more than just a pack of classes or templates. We have a new concept that turn it a little easier.

MVVM Foundation

  •    WPF

MVVM Foundation is a library of classes that are very useful when building applications based on the Model-View-ViewModel philosophy. The library is small and concentrated on providing only the most indispensable tools needed by most MVVM application developers.

SwinjectMVVMExample - An example to use Swinject in MVVM architecture with ReactiveCococa

  •    Swift

This is an example project to demonstrate dependency injection and Swinject in MVVM (Model-View-ViewModel) architecture with ReactiveCocoa. The app asynchronously searches, downloads and displays images obtained from Pixabay via its API. The following blog posts demonstrate step-by-step development of the project.

StateViewController - Stateful view controller containment for iOS

  •    Swift

When creating rich stateful view controllers, a single view controller class is often tasked with managing the appearance of many other views, controls, and other user interface elements based on a state. That state, in turn, is often inferred from multiple properties that need to be synchronized to correctly represent a single state. Usually the end result is known as the Massive View Controller problem, often solved by deviating from the MVC pattern used and endorsed heavily by Apple. While other patterns, such as MVVM or MVP, can solve your issues, going with the grain rather than against makes interacting with UIKit a whole lot easier. This repository houses one dependency-free class, called StateViewController, which is tasked with solving this issue. StateViewController is a container view controller that presents one or more view controllers for any given state that you define, such as loading, list, or editing. It manages the appearance cycles of each content view controller, making sure that the view lifecycle of the content view controllers are intact and in order, notifying you about state transitions and which content view controllers are about to appear or disappear from the view hierarchy. This allos you to compose multiple view controllers and re-use them throughout the app. The state view controller also provides extensive support for animating the transition between states.

Model View ViewModel AdventureWorks

  •    

This is a sample starter kit for Visual Studio 2008, which exposes the pattern MVVM (Model View ViewModel) using WPF, C# 3.5 and Linq to SQL as the data repository.

CleanArchitectureRxSwift - Example of Clean Architecture of iOS app using RxSwift

  •    Swift

The Platform is a concrete implementation of the Domain in a specific platform like iOS. It does hide all implementation details. For example Database implementation whether it is CoreData, Realm, SQLite etc. Application is responsible for delivering information to the user and handling user input. It can be implemented with any delivery pattern e.g (MVVM, MVC, MVP). This is the place for your UIViews and UIViewControllers. As you will see from the example app, ViewControllers are completely independent of the Platform. The only responsibility of a view controller is to "bind" the UI to the Domain to make things happen. In fact, in the current example we are using the same view controller for Realm and CoreData.

Xtreme MVVM Framework ( Loose XAML )

  •    

This project is an implementation of MVVM in WPF that works with loose XAML. The project is called Xtreme MVVM as there does not need to be a reference from the View to the ViewModel or vice-versa. All bindings, events and routed commands are resolved at runtime.

MVVM T4

  •    WPF

T4 Templates for generating view models, and views for WPF, Silverlight, Windows Phone using T4 Toolbox and MVVM Light

Simple MVVM Toolkit for Silverlight, WPF and Windows Phone

  •    Silverlight

Simple MVVM Toolkit makes it easier to develop Silverlight, WPF and Windows Phone applications using the Model-View-ViewModel design pattern.

HRM System MVVM sample code

  •    

This is the sample WPF MVVM application that i've described in my blog posts. I hope to give you a clear view of mvvm and other commonly used patterns.






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.