Hi Damith, Yes, It would be nice, if the design view could maintain the component position (We can maybe add a regenerate button if the user wants to regenerate the view again).
Let's say, it's a complex flow and after creating everything in designer view, a simple switch to code view re-organises the entire view. It will not be an issue in many simple uses cases, but highly complex apps, we can't always guarantee, the design view generated is highly optimal. (View with multiple triggers as an example) Best Regards, *Niveathika Rajendran,* *Software Engineer.* *Mobile : +94 077 903 7536* On Tue, Sep 25, 2018 at 2:45 PM Damith Wickramasinghe <[email protected]> wrote: > Hi Nivethika, > > +1 for first two points. Can you elaborate more on 3rd one. AFAIK design > view will not generate again if we do not do any changes to the flow. I'm > not sure in what level we identify the change eg:- just moving a component > should not take as a change. Are u referring to the flow user has kept. > Like u need the positions user has placed last to be remain same ? > > Regards, > Damith > > On Tue, Sep 25, 2018 at 9:00 AM Niveathika Rajendran <[email protected]> > wrote: > >> Hi Dilini, >> >> Please find some suggestions to the Editor to improve Developer >> Experience, >> >> 1. Keyboard support in editor Design View[1] >> 2. Group select and drag - Only one component can be selected and >> dragged, if the user wants to move a flow, he/she has to drag each >> component separately. >> 3. Save the design view - As of the current implementation, the >> design view is generated every time the view switches. In a complex siddhi >> app design view, if a user rearranges the flow for easy access, this >> cannot >> be persisted. >> >> >> [1] https://github.com/wso2/product-sp/issues/746 >> <https://www.google.com/url?q=https://github.com/wso2/product-sp/issues/746&sa=D&source=hangouts&ust=1537950142287000&usg=AFQjCNFi2NzdPHHOYNWYw9Wfl1H0sRFk3w> >> >> >> Best Regards, >> *Niveathika Rajendran,* >> *Software Engineer.* >> *Mobile : +94 077 903 7536* >> >> >> >> >> >> On Tue, Sep 25, 2018 at 2:10 PM Dilini Muthumala <[email protected]> wrote: >> >>> Hi all, >>> >>> We are in the process of *$subject *so that we can improve the product >>> and consider fixing them for the next release. >>> >>> If you had any usability issues or wished there was a certain >>> feature/functionality (even in SP 4.2.0) and still could not report it, >>> please reply to this thread. >>> >>> We are particualrly looking at improving: >>> >>> - Usability >>> - Deployability >>> - Developer Experience >>> - Administration/Maintenance Experience >>> - Debugging and monitoring >>> >>> Appreciate your inputs. >>> >>> Thank you, >>> Dilini >>> >>> -- >>> *Dilini Muthumala* >>> Senior Software Engineer, >>> WSO2 Inc. >>> >>> *E-mail :* [email protected] >>> *Mobile: *+94 713-400-029 >>> >> > > -- > Senior Software Engineer > WSO2 Inc.; http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > lean.enterprise.middleware > > mobile: *+94728671315* > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
