It's better to have an Application centered view along with the API centered view. I think there are lot of usability improvements that we can do along with that. We can do some mock-up base discussions and do these improvements. I am not sure when and which version we should target.
thanks, Chanaka On Thu, Mar 28, 2013 at 3:58 PM, Afkham Azeez <az...@wso2.com> wrote: > > > On Thu, Mar 28, 2013 at 3:23 PM, Lalaji Sureshika <lal...@wso2.com> wrote: > >> Hi, >> >> On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez <az...@wso2.com> wrote: >> >>> >>> >>> On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez <az...@wso2.com> wrote: >>> >>>> >>>> >>>> On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika <lal...@wso2.com>wrote: >>>> >>>>> Hi, >>>>> >>>>> On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez <az...@wso2.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias <nuw...@wso2.com> wrote: >>>>>> >>>>>>> On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez <az...@wso2.com>wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe < >>>>>>>> sume...@wso2.com> wrote: >>>>>>>> >>>>>>>>> On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez <az...@wso2.com>wrote: >>>>>>>>> >>>>>>>>>> Right now you have to navigate to an API, and then associate it >>>>>>>>>> with an Application. Edit Application only allows you to change the >>>>>>>>>> name & >>>>>>>>>> tier. IMO, it is more natural to create an application, and then add >>>>>>>>>> APIs >>>>>>>>>> to that application, rather than navigating to the API & then adding >>>>>>>>>> it to >>>>>>>>>> the app. >>>>>>>>> >>>>>>>>> >>>>>>>>> Azeez, >>>>>>>>> Your suggesting a UI enhancement. right? >>>>>>>>> This means with in application view, we should provide some means >>>>>>>>> of searching for APIs, then select version. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Yes, UI enhancement. >>>>>>>> >>>>>>> >>>>>>> I'm guessing it would be something like this. >>>>>>> >>>>>>> List My Applications -> Choose an Application and click "Add APIs" >>>>>>> -> Search for APIs and select the ones to be added to the App -> Commit. >>>>>>> >>>>>> >>>>>> Yes, that is correct. My concern is, once you create an Application, >>>>>> you are lost because the flow is broken. You have to start a new flow by >>>>>> going to APIs, and then associate an app with the APIs. >>>>>> >>>>> >>>>> I guess,if there's a link available in Applications page pointing >>>>> to APIs page with some indication similar to to 'select APIs from browse >>>>> APIs page' will be sufficient..As APIs page already providing >>>>> browse/search/subscribe to APIs.. >>>>> >>>> >>>> No it is not sufficient. Once you add an application, it appears on the >>>> list at the bottom part of the page. Add application should be a wizard. >>>> >>>> Step 1: Define application name >>>> Step 2: Select tier - this page needs to contain briefly what each tier >>>> provides, features/limitations etc. >>>> Step 3: Add APIs to Application >>>> Step 4: Generate keys >>>> >>>> The user experience should be smooth & unbroken. This is not just a >>>> problem with API-M UIs, but may of our other UIs as well. We need to make >>>> an effort to improve these aspects, and such small improvements will go a >>>> long way. >>>> >>> >> Should this be added as a work item for a future release/current release? >> >> With the above your suggested way,for Step 3 and Step4,are you suggesting >> to redirect to existing browse API and subscriptions pages or introducing >> new popup UIs. >> > > New UIs. > > >> Please pardon,but still I believe,once an application created,if there's >> a link available in the created application row to redirect into APIs >> page,it'll support your flow from the step 3 and continue.But with that >> way,the current limitation is,you cannot subscribe to multiple APIs at one >> time. >> > > that is not a natural flow because once you are in the API-first view, you > have to select the application again from the dropdown, and you have to > repeat the same for each & every API you want to add to the application > > >> >> Anyhow,if we are going to implement above,I believe it has to be done in >> a future release[ Not the next release 1.4.0],as we have to come up with a >> proper UI design. >> >> Thanks; >> >>> >>> >>>> >>>> >>>>> >>>>> Thanks; >>>>> >>>>> Thanks; >>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> NuwanD. >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Afkham Azeez* >>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>> * <http://www.apache.org/>** >>>>>>>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>>>>>> twitter: >>>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>>>> * >>>>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>>>>>> * >>>>>>>>>> * >>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> /sumedha >>>>>>>>> m: +94 773017743 >>>>>>>>> b : bit.ly/sumedha >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Afkham Azeez* >>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>> * <http://www.apache.org/>** >>>>>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>>>> twitter: >>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>> * >>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>>>> * >>>>>>>> * >>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Nuwan Dias >>>>>>> >>>>>>> Member, Management Committee - Solutions Technology Group >>>>>>> Software Engineer - WSO2, Inc. http://wso2.com >>>>>>> email : nuw...@wso2.com >>>>>>> Phone : +94 777 775 729 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Afkham Azeez* >>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>> * <http://www.apache.org/>** >>>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>> twitter: >>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>> * >>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>> * >>>>>> * >>>>>> *Lean . Enterprise . Middleware* >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lalaji Sureshika >>>>> Software Engineer; Development Technologies Team;WSO2, Inc.; >>>>> http://wso2.com/ >>>>> email: lal...@wso2.com; cell: +94 71 608 6811 >>>>> blog: http://lalajisureshika.blogspot.com >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >> >> >> >> -- >> Lalaji Sureshika >> Software Engineer; Development Technologies Team;WSO2, Inc.; >> http://wso2.com/ >> email: lal...@wso2.com; cell: +94 71 608 6811 >> blog: http://lalajisureshika.blogspot.com >> >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
