Updates from June, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • garyposter 3:52 pm on June 28, 2013 Permalink | Reply
    Tags:   

    frankban: ideas for tracking changes to computed attribute in our databinding

    (1) polling, expensive (angular)

    (2) like ember, you can say that a property depends on other attributes

    See http://eviltrout.com/2013/06/15/ember-vs-angular.html and http://emberjs.com/guides/object-model/computed-properties/

    Ben: sure?

    Jeff: what is use case? Francesco: when UX for one widget is based on two or more values. Example in our UX is the spinner while we are waiting on units to catch up to target.

    Ben: concerned about interactions between triggers

    Discussion: we only need any trigger (OR) causes computed value to render in widget.

    Result: we are all happy.

    ACTION: Gary will make card for Ben to implement databinding feature.

     
  • garyposter 3:41 pm on June 28, 2013 Permalink | Reply
    Tags:   

    Gary: planning poker as conversation starter

    Are we not getting the information we need to start projects? planning poker is of questionable value in my experience and others as an estimation tool but it can give people a better feeling of understanding and ownership.

    Ben: agreed, but there are other tools to do something similar.

    Francesco and others interested in experiment.

    Proposal: we will have a time-constrained planning poker session at first day of bundle sprint. Vote passes.

    ACTION: Gary will prepare planning poker thing for sprint.

     
  • garyposter 10:57 pm on June 27, 2013 Permalink | Reply
    Tags:   

    How can we reuse the Canonical shared CSS?

    Offer to convert class-based CSS to mixin-derived classes. We can use buttons and colors minimally, maybe more. ACTION: Huw will reply to Ant.

     
  • bcsaller 3:31 pm on June 26, 2013 Permalink | Reply
    Tags: HTML5 Javascript   

    Front End web site resouces, lots of good stuff in here.

    https://github.com/dypsilon/frontend-dev-bookmarks

    Having just built a databinding library for our use-cases it seems there were others that we might have been able to make work on that list. That said I’m pretty happy with what we have so far.

    http://simpl.info/

    Is an additional resource and is one of the better places to see newish HTML5 stuff in action with examples.

     
  • bcsaller 4:48 pm on June 24, 2013 Permalink | Reply
    Tags: CSS polyfill   

    We recently had a requirement for sticky headers. This has become a popular UI style for scrolled interactions. Webkit now includes experimental native support for it via a CSS position:sticky. There are polyfills that can be used when its not available.

    For notes and examples:
    http://updates.html5rocks.com/2012/08/Stick-your-landings-position-sticky-lands-in-WebKit
    http://philipwalton.github.io/polyfill/demos/position-sticky/

     
  • garyposter 4:00 pm on June 21, 2013 Permalink | Reply
    Tags:   

    Nicola: The JS linter did not intercept a syntax error, and tests were not being executed

    http://bazaar.launchpad.net/~teknico/juju-gui/loadfixture-no-hashes/revision/743

    A comma went in a bad place.

    Action: Jeff will see if newer version of jshint would have caught the problem

     
  • garyposter 3:58 pm on June 21, 2013 Permalink | Reply
    Tags:   

    Jeff: danger: template partials don’t recompile on change. We can fix this in the script trivially.

    Action:
    Gary will make card to fix this.

     
  • garyposter 3:57 pm on June 21, 2013 Permalink | Reply  

    Juju core meeting attendance. Should we keep doing it?
    Matt suggests no, maybe weekly.
    Mark suggests the Juju cross team meeting would be good.

    Action:
    Gary will remove all juju core attendance meetings except Matt’s, and Matt can move it wherever he wants.
    Gary will start sharing documents produced by the cross team meeting every Thursday.

     
  • garyposter 3:50 pm on June 21, 2013 Permalink | Reply  

    Jeff proposes that we remove the recess css linter.

    Matt introduced linter, and is +1 on removing it. We have it so loose on our restrictions that it is not buying us much. Compiling LESS catches errors anyway.

    Action: Gary will ask Huw’s opinion, sharing data from conversation, proposing that we remove it.

     
  • garyposter 3:46 pm on June 21, 2013 Permalink | Reply  

    Comment-ageddon: benji
    Proposed format:

    /*
    Comment
    */

    Ben: maybe we don’t care?

    Action: Ben will send out an email decribing what his comments look like, and Benji will add it to the style.rst document so we all follow it and then write a linter. As a slack task.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel