ok

but i think it's better raise proposal before start work on it.

2018-07-17 15:04 GMT+08:00 Willem Jiang <[email protected]>:

> It‘s no harm if the development is down.  We just need to get more feed
> back from the community and consider to merge the UI to the new UI.
> For the UI, there are some License stuff of java script library we need to
> care about. We may need to address this issue before CSE UI is open
> sourced.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 17, 2018 at 1:36 PM, Mohammad Asif Siddiqui <
> [email protected]> wrote:
>
> > Hi Guyz,
> >
> > The development of these design was already done before and that's the
> > reason we were able to show the snapshots of the new UI. The code is
> ready
> > to be merged but before merging we decided to come here and discuss about
> > this UI for people opinion. Since most of the people are concerned  about
> > the effort needed to re-design this UI, so I would like to tell that
> > development is already done.
> >
> > So in my opinion we can merge this change to make the UI better and
> > whenever ServiceComb-UI gets opensourced then we can plan to merge some
> of
> > these designs to the ServiceComb-UI.
> >
> > Any thoughts?
> >
> > Regrds
> > Asif
> >
> > On 2018/07/16 10:57:00, Zen Lin <[email protected]> wrote:
> > > Hi all,
> > > As we known,  CSE is a initial commercial product of servicecomb and we
> > > have tried our best to ask CSE to open source ServiceComb-UI to
> stronger
> > > servicecomb and let servicecomb service users better.
> > > But I think the discuss should focused on what's  difference between
> > > servicecenter UI positioning and servicecomb UI positioning.
> > >
> > > If we sure the functionality of servicecenter UI is a subset of  of
> > > servicecomb UI which will be opensourceed future, and Asif have willing
> > to
> > > keep on developing and maintaining a servicenter UI, will will have two
> > UI
> > > in future, I think that is allowed with a opensource project also.
> > >
> > > Therefore, to my opinion, I think we can focused on discussing
> > > servicecenter-UI's position, something like, what functionality for
> > > service-center UI is reasonable?
> > >
> > >
> > > Best Regards,
> > > ---
> > > Zen Lin
> > > [email protected]
> > > Focused on Micro Service and Apache ServiceComb
> > >
> > >
> > > wjm wjm <[email protected]> 于2018年7月16日周一 下午12:43写道:
> > >
> > > > maybe we can change our mind to: make sure new feathers all in
> > > > ServiceComb-UI, not design a new one.
> > > >
> > > > 2018-07-16 12:41 GMT+08:00 wjm wjm <[email protected]>:
> > > >
> > > > > as i said that, Proposal of new SC frontend seems to be a subset of
> > > > > ServiceComb-UI
> > > > > if that's true, i think we no need to spend time to do one thing
> > with two
> > > > > way.
> > > > >
> > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui <
> > > > [email protected]>
> > > > > :
> > > > >
> > > > >> Hi Sure,
> > > > >>
> > > > >> If this new ServiceComb-UI(as per your mail) is opensourced then
> > will
> > > > the
> > > > >> exsisting service-center frontend deprecated?, If NO then I still
> > > > believe
> > > > >> it's a good thought to upgrade the exsisting Service-Center
> > frontend.
> > > > >>
> > > > >> Regards
> > > > >> Asif
> > > > >>
> > > > >> On 2018/07/16 00:51:06, "Sure" <[email protected]> wrote:
> > > > >> > -1
> > > > >> >
> > > > >> >
> > > > >> > we will publish the cse-UI in servicecomb(named servicecomb-UI
> may
> > > > be),
> > > > >> this’s the unified console of sc,cc and monitoring. So we just
> need
> > to
> > > > cost
> > > > >> a little of time to fix bugs of SC-UI.
> > > > >> >
> > > > >> >
> > > > >> > The sericecomb-UI will be more valuable in the future
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > 发自我的iPhone
> > > > >> >
> > > > >> > ------------------ Original ------------------
> > > > >> > From: Mohammad Asif Siddiqui <[email protected]>
> > > > >> > Date: Fri,Jul 13,2018 7:55 PM
> > > > >> > To: dev <[email protected]>
> > > > >> > Cc: krishna.m.kumar <[email protected]>, sanil.kumar <
> > > > >> [email protected]>, vinaym <[email protected]>
> > > > >> > Subject: Re: [DISCUSS] Proposal for Re-Design of Service-Center
> > > > Frontend
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > Hi All,
> > > > >> >
> > > > >> > As we have continously put an effort to improve the
> > Service-Center UI
> > > > to
> > > > >> > make it more usable and user friendly, going forwards I would
> > like to
> > > > >> > propose some major changes in the Design of frontend. Some of
> > those
> > > > >> changes
> > > > >> > will include :
> > > > >> >
> > > > >> > 1. Update Dashboard to have a more better snapshot of what
> > > > >> > entities/resources are present in the Service-Center env.
> > > > >> > 2. A place holder in Dashboard to contain the basic User
> > Guide/FAQ for
> > > > >> > ServiceComb.
> > > > >> > 3. Add a new page for showing the list of instances which are
> > > > currently
> > > > >> > running and registered in service-center.
> > > > >> > 4. Add a new page for showing the topology of Microservices,
> this
> > page
> > > > >> will
> > > > >> > describe the relationship between the different microservices
> and
> > some
> > > > >> > metadata of the microservices.
> > > > >> > 5. Advanced search criteria for Service and Instance List.
> > > > >> >
> > > > >> > Here is the Snapshot[1] of the changes we are planning to do.
> > > > >> >
> > > > >> > Most of the features development have been completed and we are
> > > > >> planning to
> > > > >> > put this change in the 1.0.0 release of Service-Center.
> > > > >> >
> > > > >> > Any thought on this?
> > > > >> >
> > > > >> > [1]
> > > > >> > https://github.com/apache/incubator-servicecomb-service-cent
> > > > >> er/wiki/Service-Center-UI-Re-design
> > > > >> >
> > > > >> > Regards
> > > > >> > Asif
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to