I had to close #25, which doesn't mean that there's no need to implement all the things mentioned in there.
Quite the opposite, but we need to push all those features to 0.4.0 and release a slimmer 0.3.0 now.

• Angular 1.2.0(rc) compat (esp. animations)
• Convert tests to Protractor
• Update and consolidate all dependencies front(aka bower) & back(aka npm)
• Use generator-angular based build process #36
• Convert existing demos to new demo app
• migrate tabbar, detail disclosure and other fixes/features from old 0.3.0 branch to new bp structure
• deprecate old iOS or at least 0.3.0 should be the last release that supports it (talking styles only here)

The idea of the up state detection simply using the second to last url parameter as the identifier of the up state name seems to break or at least get very awkward when using parameters in the route URL.

For example:
When on a state called "selectAccount" with the url /clientList/:id/selectAccount, bp-navbar directive will try to look up the state with name ":id".

I don't have a conceptual fix in mind right now, but will think about it. My current workaround is to just define an up state on the data object of the state for these cases.

package.json contains caret symbols prefixing version numbers, this syntax cannot be found here: https://www.npmjs.org/doc/files/package.json.html and appears to be causing errors. Is this an OS or encoding problem?

Make this badge a green 100.

Inspiration: https://github.com/daniellmb/angular-test-patterns/

Build a page with few bp-tables (table-grouped).
If I want to scroll and put my scrolling-finger on a cell of a table which is "bp-tapable", it seems that the scroll isnt smooth anymore. The device thinks that i want to tap that cell.
Same with bp-button.

Textareas seem not to be styled yet.

Hi i have a problem with the iscroll directive. I have the following view code:

<div class='bp-content-custom bp-content' bp-iscroll>
  <input ng-model="email" type="email" placeholder="E-Mail"/>
  <input ng-model="password" type="password" placeholder="Ihr Passwort"/><br/>
  <div class="button" ng-click="login()">Einloggen</div>
</div>

And the following in the controller:

$scope.login = function() {
      authentication.login($scope.email, $scope.password).then(function() {
        $state.go('home');
      }, function(result) {
        $window.alert(result.error);
      });
    };

Unfortunately $scope.email and $scope.password are undefined. However if i remove the bp-iscroll directive in the view, $scope.email and $scope.password are correctly defined. Whats going on here?

Error after installing the phoneGap-Emulator. Even if the Emulator is disabled.

Consequence is a white screen.
If you comment the 4 involved lines out, it seems to work normally.

Cell

• @boennemann text is elipsed after one or two characters (value 1)
• @boennemann reenable transclude, so text is always wrapped

iScroll

• @boennemann background visibility and compositing layers broken during flip
• @boennemann delay iscroll initalisation
• hide scrollbar unless scrolling postponed
• @boennemann don't enable sticky headers on android

Navbar

• @boennemann text cut off due to incorrect height
• @boennemann android icon invisible due to missing overflow visible
• @boennemann don't center text on android
• @boennemann place all the buttons on the right on android

Search

• @boennemann misplaced search icon on mobile (vs. Chrome)
• @boennemann misplaced cancel button on focus (android only)

Tap

• @davidpfahler expose event (maybe: click fallback)

Tests

• @boennemann bpConfig
• ViewService
• @boennemann define number of assertions expect

Chore

• don't commit dist on every commit
• release tasks: dist builds, tag, bower and npm bump, changelog

It seems that the GUI-Elements do not resize correct.
I took the photo with android as platform. Same with ios.
I used a 10 cent-coin for comparison.

Sorry for the bad picture-quality.

The slide animation appears broken in Chrome.
If we update to Angular 1.2.14 it would break in Safari, too.

• investigate
• fix

• test current navbar code #57
• introduce a way to use icons in the ios navbar #60
• implement toolbar/action overflow #61
• automatically create toolbar/action overflow from within the navbar #64
• make slide transition independent from navbar #59
• make navbar state-aware #68
• transition correctly #69

To save memory the bp-iscroll directive automatically destroys the iScroll instance.
This shouldn't happen until the transition has ended, as its causing serious flickering.

• cell elements e.g. (detail) disclosure indicator
• table, e.g. grouped, headers, footers

6c14c0a#commitcomment-3784513

• Don't rely on scope or options.
• Expose unbinding method.
• Write Provider, rather than using bpConfig.
• reconsider use of factory/ rename to bpTap

Feat:

• click fallback

I have discovered a problem with the bp-iscroll directive. I have a list rendered into a scrollable area. But when the length of the list changes, the iscroll container is not adapted to the new height of the list. Is there any way i can trigger a refresh on the iscroll-wrapper?

expand ngmin task

These lines aren't reusable at all, they should be moved to bpApp completely.
https://github.com/excellenteasy/bradypodion/blob/master/modules/scripts/services/view.js#L2-L10

I have a div with the bp-scroll directive. As long as there is enough content in it so that you actually have to scroll, no scrollbars are shown. This is fine. But when there is not enough content, vertical and horizontal scrollbars show up. This applies to the android and the ios skin.

the refresh event should wait or use another mechanism to wait for the DOM / angular to do its magic.

For some reason, the iOS web view breaks jQuery in a way that makes it impossible to look up attributes using .attr(...). This screws up the logic when trying to detect whether the user has set a type attribute on the input in bp-search. Although this technically seems to be a jQuery bug, we need to fix it.

fixes

• do not use delay on iscroll instantiation when no transition is happening (e.g. on app start)
• back button detection for paramtarized URLs

features

• tabbar
• loading indicators
• button groups (segmented navbar)
• ng-swipe
• swipe back and forth gestures
• horizontal snapping swipe views
• detail disclosure
• image gallerys
• bp-navigation
• calender view

for sencha touch 2 feature parity

UI

Table / iScroll

• pull to refresh
• load more (when scrolling to the end of a list)
• ABC navigation

Forms

• sliders
• checkmark

overlays

• action sheet
  others?

tooling

• generator-bp-app
• phonegap build grunt tasks

Should we implement a triaging system similar to Hoodie?

I'm +1. @boennemann Is it feasible for us to use the same system (with dotfiles repo etc.) that you have done at hoodie? I would do it if you give ok.

On Android, bpAction displays nothing or weird unicode symbols when not icon class is defined. To void this mistakes, developers should be notified when they forget to add an icon class to bpAction.

https://github.com/excellenteasy/bradypodion/blob/master/src/scripts/directives/navbar.js#L250

When .after($toolbar) is executed on a spawned toolbar the navbar isn't yet in the DOM and therefore the toolbar bar won't appear.

Hi the android navbar shows that submenu as soon as the navbar contains more then 3 action-icons.
This results in 2 icons beeing displayed and the dropdown with only one item in it. I think it would be better if the submenu would only appear for >= 4 icons. Why do I need a submenu if there is only one option in it? It would be better to just display the icon instead. Unfortunately this is hardcoded into the source of bradypodion so there is no chance to change it

When group a table everything seems right.
But... if i change the last-cells display css-value to 'hidden', it just hides the last cell. It does not adjust the corners.

There would be a quite easy way to fix this bug, in js. (case-specific -> i mean outside the framework)
Maybe you already want to fix it directly in your framework.

Generate all the module.less and class.less files to remove boilerplate code and ease the development.

hi i have two tabs in my app and in every tab view i have a bp-navbar-config element.

When i click on a tab the navbar changes correctly, but if i switch to the other tab the configs seems to be not used anymore. however if i switch between the two tabs a few times the missing actions in the navbar reappear and also stay regardless which tab i click.

any hints what could be wrong? Both tabs use the same view template and controller

The text ('Größe', 'Alter') disappears.

How it looks like:

How it should look like: