Hello everyone, Could we have a conversation on call to finalize the design framework? It would be great as we'll have more clarity on the mentioned points. As soon as it is possible and feasible for everyone, anytime today or over the weekend would be great as it will give us some time to explore and work at a better pace.
Thanks Abhay On Fri, Jun 15, 2018 at 7:35 PM Anwesh Krishna Nayak <anweshkna...@gmail.com> wrote: > Hi Gaurav, > > I understand your point. We are using https://bootswatch.com/materia/ for > overriding the common bootstrap.css properties. In our case it shouldn't be > of much difference. It is just a material wrapper over common bootstrap.css > . > > As about the point of using Angular Material. It is just to give material > look to components like tables,tabs which comes with its own materialize > css properties. As we already have material look by bootswatch it doesn't > add much to the material effect. Using https://bootswatch.com/materia/ > will help maintaining the overall material look of the web app while using > only angular-material won't give that look. > > We can use angular-material for use cases if necessary but the UI we wrote > is less dependent on angular material library as we are using simple > material bootstrap components for it. > I will host the link with updated pages today itself. > > Thanks > > On Fri, Jun 15, 2018 at 7:19 PM, Gaurav Saini <gauravsain...@gmail.com> > wrote: > >> Hello Anwesh, >> >> I would say we should use Angular Material library for consistency and >> below reasons: >> >> - We already have our self-service app last year built on angular >> material itself so we should follow. >> - Another reason is its official Angular library and there can be >> chances in future that bootswatch or ng-bootstrap might discontinue >> support >> or don't add further modules. >> - I don't see angular material support mentioned on both bootswatch >> <https://bootswatch.com/> and ng-bootstrap >> <https://github.com/ng-bootstrap/ng-bootstrap> github repos. Might be >> there is some add-on package which i am not aware of. >> >> I saw the initial hosted project and have some feedback to speed-up the >> development: >> >> - Define the wire-frames or some sample mock-up ideas how we want our >> new web-app to look like. >> - Also, wire-frames for some important pages like Client Page, >> Dashboard etc >> - Use of Data-table as in our current application we have a lot many >> views using data-tables. @Ed Cable <edca...@mifos.org> If you can >> give some feedback improvement we needed from the current look we have so >> we in-corporate from start and maintain same data-table in entire project. >> - Make sure you re-use as much code as possible by making proper >> modules. >> - Go through each page on current community-app to find what all >> pages are sharing same modules like I mentioned of data-table. This will >> help you re-use code and fasten the development cycle. >> >> @Mohit Bajoria <mohitbaj...@gmail.com> @Pranjal Goswami >> <pranjal.b.gosw...@gmail.com> Please add more suggestions you have from >> your experience or something I might not be right here. Let's try to help >> out both Anwesh and Abhay as much possible from our available time, as I >> can see they have a big task in front of them, which I am positive that >> they can take over :) >> >> Thanks >> Gaurav >> >> On Sat, Jun 9, 2018 at 11:41 PM Anwesh Krishna Nayak < >> anweshkna...@gmail.com> wrote: >> >>> Raunak, >>> >>> Infact we are using material based design for Angular that is bootswatch >>> and ng-bootstrap. We are already following the UI/UX guidelines for >>> consistency. >>> >>> Thanks >>> >>> On Sat, Jun 9, 2018 at 11:50 AM, Raunak Sett <sett.rau...@gmail.com> >>> wrote: >>> >>>> We should use Angular Material. We should have consistent experience >>>> across all platforms and given that we are already following material >>>> design guidelines on a lot of our android clients as well as web. So it >>>> would be easier if we just have a common UI/UX guidelines for the >>>> consistency. >>>> >>>> On Fri, Jun 8, 2018 at 10:13 PM Abhay Chawla <abhay.chawl...@gmail.com> >>>> wrote: >>>> >>>>> Hello everyone, >>>>> >>>>> After some discussion, Anwesh and I have a come up with the following >>>>> points regarding the decision to use Angular Material or bootswatch and >>>>> ng-bootstrap for the new MifosX Web App (Angular 6): >>>>> >>>>> 1) ng-bootstrap is a wrapper over bootstrap.js which contains a set of >>>>> Angular Directives that can be implemented without any dependencies on >>>>> jQuery or popper.js https://ng-bootstrap.github.io/#/home >>>>> 2) Bootswatch provides a collection of themes(21 + 1 default) for >>>>> Bootstrap https://github.com/thomaspark/bootswatch/ >>>>> 3) Bootswatch provides with an API which can be integrated with the >>>>> platform for theme configuration easily and provide the organizations with >>>>> a choice from these 21 themes https://bootswatch.com/api/4.json >>>>> 4) We are currently using the bootswatch material theme to compete and >>>>> provide with a similar kind of look as by angular-material >>>>> 5) New themes if required can be configured easily using bootstrap, as >>>>> a simple example I have created a demonstration here: >>>>> https://abhaychawla.github.io/angular-theme/ >>>>> 6) We can also provide instructions so that the organizations will be >>>>> able to clone the project, create their own custom theme, build the app >>>>> and >>>>> use that theme. >>>>> 7) Overall, ng-bootstrap and bootswatch built on top of bootstrap are >>>>> easy to implement and could be modified and used to suit our needs >>>>> >>>>> 8) On the other hand, angular-material provides with 4 inbuilt >>>>> material themes to chose from https://material.angular.io/ >>>>> 9) More custom themes can be configured according to organizations >>>>> needs using angular-material as well but it will be a bit more complex >>>>> 10) Overall, angular-material will be more time consuming and a little >>>>> difficult to implement >>>>> >>>>> We would like to share this with the community and get their opinion >>>>> regarding our choice of design framework so that we can finalize the same >>>>> as soon as possible in the initial stage of the project. >>>>> >>>>> Looking forward to your responses. >>>>> >>>>> Thanks >>>>> Abhay. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Mifos Google Summer of Code 2018" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to gsoc-2018+unsubscr...@mifos.org. >>>>> >>>> >>>> >>>> -- >>>> Raunak Sett >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Mifos Google Summer of Code 2018" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to gsoc-2018+unsubscr...@mifos.org. >>> >> >> >> -- >> Regards, >> *Gaurav Saini* >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mifos Google Summer of Code 2018" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gsoc-2018+unsubscr...@mifos.org. >> > > -- > You received this message because you are subscribed to the Google Groups > "Mifos Google Summer of Code 2018" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gsoc-2018+unsubscr...@mifos.org. >