I just wanted to get right picture of design cycle. I have gathered list as follows,
Requirement gathering
Wireframe design
Visual design (user interface)
Mockup (prototype)
Development
Do you have different view?
However I have gathered the flow, it may be suggested or commented by community. And I wanted to enhance its technical names, I don’t know I much I’m success.
Consultation
Content/ Functionality outline
ite diagram
Page description diagram
Technical design
Wireframe
Prototype
Usability
Visual
Concept
Design Presentation/ UI Architecture
Fine tuning
Development
xHTML/ CSS/ JS
Accessibility
Compatibility
Test
UI
Content
Accessibility
Compatibility
Your ideas make this flow rich, for sure.
Analysis
Specification Building
Design and development
Content writing
Coding
Testing
Promotion
Maintenance and Updating
Related
I have a hybrid mobile app.
The framework is vanilla Javascript (i.e. no React, Angular, Vue, etc..).
The GUI work as expected (i.e. the buttons trigger the correct functionality) but the UI is lucking.
I have a UX / UI design in place, in form of an idea and example sketches, but not in any framework (e.g. no Figma files).
I use Bootstrap inconsistently in the app, for some of the buttons and found about Material Design Bootstrap.
I see many blogs about UI design and design tools, such as Figma, Sketch, Adobe XD, etc.
In my case, I already have the UX/UI design results. (although just conceptually - not in any files).
So I'm looking for UI implementation (not design) tools / packages / approaches.
What is the best way to implement the UI?
Could I just start implementing bits and pieces of the UI?
Or should I use a specific framework/platform/mockup ?
Thanks
i would advice you implement the ui in bits as you would have better understanding about the code running your ui and how to easily connect the gui to functionality. tools like figma have features that can convert designs to html/css code buut that would require having to work on design files.
I need a UI library with Angular components to display and edit state chart diagrams with data bindings, so the diagrams can be translated bidirectional between the visual diagram and the native statemachine model entities in my application. I have pored over pages of google search to no avail.
I must admit I am a newbie to Angular and my expertise is to the level of using standard components available from npmjs repository. So far, I have been comfortable using different ui components such as ngx-bootstrap, valour, etc. I do not have the competence or know-how to build new components using diagram libraries with JS/JQuery inside my angular project to realise the requirements. I would really appreciate if any UI Toolkit/Library available for this. Even reasonably priced commercial frameworks are acceptable for me.
Thanks in advance for any help.
I have already checked out free/open-source/commercial frameworks such as Telerik Kondo, SyncFusion, Ionic, JQWidgets, etc. I have pored over their documentation published for free. However, I always end up in either (a) they do not suit my needs, or (b) it involves developing this component myself. I know how it sounds, but my need is similar to needing a car; not design & build one myself. I do not have the ability to do it.
I need support for Angular 7 or 8 to be precise.
We are maintaining a web based tool (written in Play 2.x Framework) which over the years has gained a lot of different technologies used. It is a mix between regular server generated pages with old school html/javascript/html buta also som jQuery and misc components that the developer at that time liked. The more lately added stuff are more interactive and uses a REST-API and React.
Usability is pretty good but the graphical design of it is awful. In the best of worlds we would redo the entire front and make it single page and extend the REST-API fully.
however, we don't have those resources but still apply a material design to it with a dark theme.
I have previously done a makeover on a similar but smaller web tool using Material Design Lite and that was quite smooth. However, that framework from what I can see does not support a dark theme and is also discontinued in favour for the Material Components.
Any suggestion on a good alternative?
Main requirements:
Uses a dark theme
Easy to integrate with both our old and newer stuff.
If you're use React you can try Material-UI.
If not you can simply make custom theme using Material Design.
What I want to create is a Silverlight app with a few tabs/modules that will all be separate DLLs.
I see PRISM has the Shell/Module concepts that seem directed towards doing UI and I find a nice demo (showing how to search digg/twitter).
But it sounds like MEF will be included in VS2010 so I would like to go with that option.
Can anyone somehow clearly explain the differences? (I am not a advanced programmer)
MEF and Prism serve two very distinct goals.
Prism is basically guidance for designing composite applications - where you have a shell and "regions" that are dynamically assigned, and integrated. It includes an IoC container (Unity) that it uses for it's injection.
MEF is a dependency injection framework - it's main goal is to "fill in" depedencies at runtime for an application. In this respect, it's filling the same goal as Unity does within Prism (and, in fact, you could pretty easily rework Prism to use MEF instead of Unity).
Prism fills a broader scope, in some respects, but is also really limited to GUI applications. MEF is just doing one thing (Dep. Injection), but geared to be more general purpose, for any type of application.
As for the lifetime of these products -there is no answer here, but this is kind of how they're being developed:
Prism was developed by the Patterns and Practices team. The goal isn't to necessarily make software, but to provide guidance. As such, they update (although somewhat infrequently) the Prism library and sample, but Prism isn't a core part of the framework shipped by Microsoft. It's really a third party library (even though MS funds a lot of it, most of the P&P people aren't MS FTE).
MEF, from the blog posts, sounds like it is planned to be integrated into the framework, and be used directly inside of MS projects. As such, it's getting heavy development, directly from Microsoft, and being used in their products.
I, personally, have read through the Prism documentation (and have the book), and have gone through the samples. It is very helpful to understand how to break apart an application, but it really is guidance more than a complete, usable framework. The samples are very good at doing what they're designed to do - educate an architect in how to design a composite application.
If your goal is to just keep a clean separation of concerns in a silverlight application, I'd focus more on learning MVVM than necessarily just using Prism.
If you want to use MEF, there are other good options. For example, the WPF Application Framework is an entire MVVM framework built on top of using MEF, and fairly nice.
Basically, MEF is a general-purpose extensibility framework:
If you are building extensible applications, extensible frameworks and application extensions, then MEF is for you.
whereas Prism is mostly for building GUIs:
The Composite Client Application Guidance is designed to help you more easily build modular Windows Presentation Foundation (WPF) and Silverlight client applications.
So MEF and Unity are basically the same...
Well, not exactly. MEF is more focused on extensions which aren't known at compile time, while IOC containers generally focus on dependencies which are known at compile time. The top answer to this question gives a good explanation of the differences.
Yes. Check these two posts for more:
http://blogs.msdn.com/gblock/archive/2009/12/02/mef-and-prism-to-be-or-not-to-be.aspx
http://blogs.msdn.com/dphill/archive/2009/12/09/prism-and-mef.aspx
Can I use TDD for gui application?
How to do it.
The answer which has evolved over the last few years is, you don't apply TDD to the GUI, you design the GUI in such as way that there's a layer just underneath you can develop with TDD. The Gui is reduced to a trivial mapping of controls to the ViewModel, often with framework bindings, and so is ignored for TDD.
This is known variously as the Presentation Model (Fowler) the Model-View-ViewModel and DataModel-View-ViewModel architecture.
This approach removes the GUI layer from TDD and unit testing. It does not mean the GUI is never tested but just acknowledges that it is not cost effective to pursue automated GUI testing, particularly as part of TDD. Integration and user testing should cover the GUI.
Josh Smith's 2009 WPF article is a detailed explanation of MVVM with some testing.
More recently, Houssem Dellai's 2016 video Creating Unit Tests for Xamarin Forms Apps shows a XAML UI with bound ViewModel and walks through creating a unit test project
Why not. Here is a good article, from object mentor.
Found another blog post, TDD - Introduction to Moq. Its related to C# and VB.NET.
Checking out Myth and Misconception regarding TDD is a must.
Here is a book related to .NET, TDD in Microsoft .NET.
Chad Myers has a nice walk through testing the controller:
http://www.chadmyers.com/Blog/archive/2007/11/27/tdd-with-asp.net-mvc-3.5-extensions.aspx