igniteui / igniteui-angular Goto Github PK

The navigation bar component should tap into the navigation stack of Angular. It should expose back button upon navigation, and interacting with the back button should pop from the navigation stack and transition the application back a view.

The navigation bar should also hold a title and an icon.

Create a switch component, which will be purely CSS.

The tab should act like a navigation component in Android. It should support loading of different Views.

The syntax should be something of the sort:

<ig-tab-bar alignment="bottom"> 
  <ig-tab label="Home" href="#/Home" src="template_folder/template1.html" icon="home-icon-css-class"> 
  </ig-tab> 
  <ig-tab label="About" href="#/about" src="template_folder/template2.html" icon="about-icon-css-class"> 
  </ig-tab> 
</ig-tab-bar>

We can discuss the src attribute, it could be named something else, or we can create a view component that goes inside the tab and carries the src. This is just a brainstorm, so we can discuss this further.

And add list tests.

Demos should be available through a github.io page for the repo.

Some of the tests or part of them are commented because of the last RC4. They need to be improved so they can work with RC4.

Here's the changelog: https://github.com/angular/angular/blob/master/CHANGELOG.md

Publish new npm package for Zero Blocks on tag build.

Create a search API for the list and a demo which displays how entering symbols in a search box (input), the list is searched by:

1. Text in the DOM elements.
2. Text in a specific DOM element. This should be configurable through the list.
3. Data items the list is bound to. The list should be configurable by what property to search for in the data items.

In addition, this will probably be an enhancement to the nav bar where a search box for the list can be configured.

Create a radio button component. This should be a pure CSS component.

Create a zero blocks label directive.

Create a zero blocks input component, which will be pure CSS component.

There should be npm scripts that produce combined files.
There should be a build setup to run with every commit.

Extend the list to support list-details drill down.

Upon a list item click (tap), the list should be able to transition (drill down) to a new view, which carries details for the specific item.

The transition will happen as a drill down in the case of a phone view.
The details item can be drilled down, or loaded in a separate container in the case of a tablet view.

Create readme.md file in dialog folder

General Naming Guidelines

• Implement 'igx' as a selector prefix (dash separator)
• Naming: follow a pattern that describes the symbol's feature then its type. The recommended pattern is feature.type.ts (badge.component.ts)
• Use dashes to separate words in the descriptive name. (Separate File Names with Dots and Dashes)
• Use upper camel case for class names (export class IgxAvatar)
• Add 'Igx' prefix to class names (export class IgxAvatar)
• Do use consistent names for all pipes, named after their feature
• Do name test specification files the same as the component they test (with a suffix of .spec; Example: badge.component.spec.ts)
• Prefixes for Directives -
  @directive({
  selector: '[igxLabel]'
  })

Coding Conventions:

• use upper camel case when naming classes and interfaces (exceptionService to ExceptionService )
• Do use lower camel case to name properties and methods
• Use underscore for private properties (private _size: string)

Allow badge positioning by providing values for position.
@Property {string} position

Valid positions:
top-left
top-right
bottom-left
bottom-right

Add two action buttons dialog template, so that I can enable the end user make a choice. (dialog)

The README should contain full list of components and directives we provide. Also include theming information together with icon set.

http://stackoverflow.com/questions/38346228/angular2-rc4-testing-uncaught-in-promise-typeerror-testing-1-expect-to/38346646#38346646

Material style alert and dialog types. Related to #127 and #96

The current dependency is on beta 15. Update to RC.

Add info about installing the zero blocks NPM package into the README.MD.

Create a scrollbar for containers.

Currently the component styling is provided inside the component definitions and the styles are provided in a string format. We should provide general theming capabilities for Zero Blocks.

1. Remove style definitions from the components.
2. Implement theming for the components.
3. Setup build to produce combined styles.

Create a proof of concept application for event agenda using Zero Blocks.

Implement styling with the existing theme for the Nav Drawer component.

Coding Guidelines

Create an avatar directive.

Build a POC warehousing application using Angular and Zero Blocks.

Design will be included to the issue.

Implement new avatar component

Zero Blocks should be installable through NPM.

Write unit tests for the nav drawer.

Develop an icon set that will be used by Zero Blocks components, as well as general icons for web.

We will also need an icon component, which should be a CSS component.

• Component
• Icon set

Create a tab component.

• Tab contents within the same view
• Tab contents within separate views
• Unit tests

The list component currently had very basic styling.

Create a theme for zero blocks which is aligned with Angular 2 and follows material design principles.
Have the theme take care of components only with CSS such as:

Create the overall structure of the theme. Look and feel of the default theme may change at a later stage.

Damyan created a separate directory for the list, we should move the List example in there

Create a checkbox component, which should be pure CSS component.

We currently have custom animations which were implemented before the angular animations framework. The current promise callback with our animations is unreliable, so it's time to move our animations to the angular animations framework.

Currently there are custom animations in:

1. Navigation Drawer

Build is failing due to issue with gulp-typescript 2.13.5 package.

Create a new carousel component.

Targeting dev done for sprint 11

Creating a visual identity for Zero Blocks:

1. Create logo
2. Define visual identity style (styleguide):
   A. imagery use (overlays, masking shapes, etc)
   B. fonts (used for websites and promo materials)
   C. colors (define base colors and color scheme)
   D. define iconography styles (round/edgy/mixed/lines/filled)