javascript - AngularJS directive design patterns for a sidebar menu -


i working angularjs create simple side menu. have following 2 options directive design cannot decide 1 better:

option 1

the html markup:

<sidebar title="sidebar heading">   <sidebar-element name="heading">description</sidebar-element>   ... </sidebar>

option 2

the html markup:

<sidebar>sidebar heading</sidebar>

and, data coming directly controller: 

$scope.sidebarelements=[{name:'head 1', description:'description 1', isactive:true}];


consider data coming me server in json.

if go option 2, can pass data directly controller.

if go option 1, have <sidebar-element ng-repeat='element in elements' ...> in it, , pass on data it. option 1 seems 'better designed' somehow don't know if should build layer of abstraction way when not required.

which 1 of 2 better , why?

i have started work angularjs , trying find right way 'think in angularjs'

it depends on how extensible need make design. if want make design work option1 in future, should go it, because going consume more time put piece of code.

if want go highly extensible approach should create directive , directive create collection using controller data. this (option1) allow user use combination of both directives menu static or dynamic data. if decide go option1, link useful [link] : http://sporto.github.io/blog/2013/06/24/nested-recursive-directives-in-angular/ [it has live example] : http://jsbin.com/acibiv/3/edit

if data coming json (controller data) , there never need add html (static ) go option2.

i think starting, should go option2 (less reusable easier compared).

about directive naming think sidebar may contain other elements (other menu). naming should tell menu.


Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more