Hi,
The hackathon went really well. I think it was extremely useful to have
both DevS and ESB team together to understand the improvements/flaws of the
current graphical editor. Here is the progress we made during today's
session.
- Our main objective of today's session was to identify the fundamental
usability and design problem with ESB graphical editor. We started the
session with the evaluation of the current use experience from the
perspective of a new/average ESB user.
- We did a live session with the whole team, from the initial step of
starting dev studio up to implement a integration solution with it. There
were lot improvements that we can do give a better user experience.. and
there were lot of areas where things can go wrong when designing ESB flows,
which we have to fix.
- One of the fundamental problem we currently have in DevS editor is that
the mediation flows easily getting messed up on unhappy paths/complex use
cases (specially when designing service chaining , clone-aggregate etc).
The root cause seems to be the complexity involved in handling the
free-style drag and drop support for mediators, where you can place a given
component (mediator/ep etc) at any preferred place in the graphical editor
and the automatic wiring done by the editor. Either we have to fix this or
introduce fixed ares that we can place mediators in the flow. IMO, from the
prospective of an ESB user there is no any significant advantage of a
free-style drag and drop support for mediators over a fixed design areas
for mediation flows.
- We evaluated most of the commonly used mediators and how well they fit in
to the current graphical editor.
- We will completely focus on the integration scenarios and user stories
tomorrow.
- Here, we have listed all the improvements that we have discussed and we
will create jira out of these.
(Notes taken by the team)
Issues/Improvements
-
Sequence Editor - remove “mediator” word for mediators in the palette
-
Compress the items of the palette when proxy is created (first view)
-
Palette groups should be collapsed position
-
Reduce icon size
-
Reduce the item height/gap between item
-
When an endpoint mediator is added
-
need to fix overlap with border issue
-
arrow issue
-
Add a new title bar with proxy name and keep only the icon within the
editor (remove name).
-
Do we need to keep the icon ?
-
What about remove both name and icon since header title is given?
-
Add new set of icons with names within the icon.
-
Icon size need to be small
-
text within the icon (by looking at the icon we can identify the
mediator)
-
icon colors is not contrast enough
-
When component is selected
-
Remove the sizable corners
-
Border need to be rounded corners
-
A light color fill gives a nice look n feel
-
Add a new description attribute to synapse and use that as the
description under each mediator
-
When an item is added
-
It should initially contains the item name. If user gives a
description the default name will be changed into description
-
Fixed view for sequence editor and do not allow to move the mediators. -
(send a mail and discuss further)
-
Remove extra arrows which is there to add a sticky note + strats
-
Remove the default connection arrows
-
Reduce initial size of the proxy ui
-
Providing different color to out path
-
Group all endpoint that goes out from one sequence (ie: In seq,
clone-aggregate, switch) and connected them back to the response path
-
Nodes pallet has to be renamed either API or whichever suitable name,
currently nodes confuses customer.
-
Named sequence support in Proxy services (inSeq and outSeq can define
externally)
-
Reduce the initial size of the editor and expand it as items are added
-
When typing a particular item name (for ex. Mediator name) it will
automatically point to the matching item (i.e. search facility)
-
Add a splash screen to DevS
-
Avoid default value serialization (if user hasn't specify any value for
such attributes)
Day 2 plan
1. Evaluate Mediators
Specifically Evaluate following mediators :
Filter
Initial size is too large, reduce the width and expand as items being added
outer box drawing is not nice we can avoid boxes (like x studio) and
implement with dash lines
Switch
‘Default’ case need to be in the bottom of the cases.
Clone
Iterate
Aggregate
Enrich
PF
2. Scenarios to be implemented using dev studio
- Healthcare Scenario (Service chaining, enrich, xslt, pf, iterate,
aggregate)
- Starbucks (REST API)
- Message Store and Proc scenario
- Clone - Aggregate scenario
- Iterate Aggregate Scenario
- Switch with multiple case which goes to different endpoints
- Complex user stories
On Tue, Jul 23, 2013 at 7:01 PM, Samisa Abeysinghe <[email protected]> wrote:
>
>
>
> On Wed, Jul 17, 2013 at 11:49 AM, Viraj Rajaguru <[email protected]> wrote:
>
>> Since Monday is a holiday we can do this on Tuesday and Wednesday.
>>
>
> Guys, did we find issues out of Hackathon? I do not see new issues
> created in Jira.
>
> How is the hackathon progressing, and what issues has been found?
>
>
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
