Hi Malintha, please refer [1] instead of details_layout.
[1] http://wso2-dev-ux.github.io/theme-wso2/layout.html Regards, *Dakshika Jayathilaka* PMC Member & Committer of Apache Stratos Senior Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Thu, Mar 17, 2016 at 10:30 AM, Malintha Fernando <malinth...@wso2.com> wrote: > Hi, > > +1 for using WSO2 tree view layout. Btw, it seems like there is an issue > with loading CSS in [1]. > > [1] http://wso2-dev-ux.github.io/theme-wso2/details_layout.html > > BR > > On Thu, Mar 17, 2016 at 10:07 AM, Lahiru J Ekanayake <lahi...@wso2.com> > wrote: > >> Hi Dakshika, >> >> Thank you for design layouts. >> >> Regards >> >> >> On Thu, Mar 17, 2016 at 9:44 AM, Dakshika Jayathilaka <daksh...@wso2.com> >> wrote: >> >>> Hi, >>> >>> AFAIK we don't need to have tree view on store side, this can be useful >>> for publisher view. >>> >>> You can use tree view available within WSO2 theme. [1] Also We can help >>> you to tweak to >>> match with current theme. >>> >>> [1] http://wso2-dev-ux.github.io/theme-wso2/layout.html >>> >>> Regards, >>> >>> *Dakshika Jayathilaka* >>> PMC Member & Committer of Apache Stratos >>> Senior Software Engineer >>> WSO2, Inc. >>> lean.enterprise.middleware >>> 0771100911 >>> >>> On Fri, Mar 11, 2016 at 9:59 PM, Lahiru J Ekanayake <lahi...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> I'm currently implementing taxonomy feature [1] . Here we have to >>>> render a tree structure in store view .I have tried with several tree >>>> structures while implementing taxonomy UI for store side. If we implement >>>> horizontal or vertical tree structures [2] with more nodes , >>>> >>>> - we will have a usability issue. That is , If we have more nodes >>>> to render, user interface will not have enough space to render those >>>> nodes. >>>> Even we reduce the size dynamically, user will not able to see nodes >>>> clearly. >>>> - Another problem is , assets are rendering bellow to tree >>>> structure. So when tree becomes larger, we will not able to see the >>>> assets >>>> results until we scroll down. >>>> >>>> So my suggestion is if we render this kind of tree structure as drop >>>> down tree [3] , It will more user friendly. As well as if we have more >>>> nodes we can handle it by only scrolling drop down menu. >>>> >>>> [1] - >>>> https://docs.google.com/a/wso2.com/document/d/1gU0KCCb595kJ0-B9ERMYmIbducZO3-4OCAGf0coZCs4/edit?usp=sharing >>>> [2] - http://bl.ocks.org/mbostock/4339184 >>>> [3] - >>>> >>>> http://www.jqueryscript.net/demo/Animated-Vertical-Accordion-Menu-with-jQuery-CSS3-mtree-js/ >>>> <http://www.jqueryscript.net/demo/Animated-Vertical-Accordion-Menu-with-jQuery-CSS3-mtree-js/> >>>> >>>> -- >>>> >>>> >>>> >>>> *Lahiru J Ekanayake**Software Engineer* >>>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547 >>>> Email : lahi...@wso2.com >>>> WSO2, Inc.; http://wso2.com/ >>>> lean . enterprise . middleware. >>>> >>>> >>> >> >> >> -- >> >> >> >> *Lahiru J Ekanayake**Software Engineer* >> Mobile : +94 (0) 77 8812629 / +94(0) 778509547 >> Email : lahi...@wso2.com >> WSO2, Inc.; http://wso2.com/ >> lean . enterprise . middleware. >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Malintha Fernando > Software Engineer > WSO2 Inc. | http://wso2.com > Mobile : +94 718874922 > Blog : http://blog.malintha.org > > Lean . Enterprise . Middleware > > > > > > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
