@pitaya-components/top-bar v0.0.44

Description

Topbars are a container for items such as application title, navigation icon, and action items.

Pitaya-framework template component.

This documentation assumes you are at least slightly familiar with aurelia and its usage. If not, we highly suggest you take a look at its Quick Start section first to get a better understanding of the approaches that are presented it here.

Screenshot

Demo

MDC Design & API Documentation

• Material Design guidelines: Buttons
• MDC Top-App-Bar

Installation

npm install @pitaya-components/topbar --save

Basic Usage

Via plugin (main.js)

Simple registration

You can register this component as an aurelia plugin. In that case you don´t have to do anything else.

export function configure( aurelia: Aurelia )
{
	aurelia.use.standardConfiguration()
		   .plugin( "@pitaya-components/topbar" )
		   .feature( "resources" );

	aurelia.start().then( () => aurelia.setRoot( "app/app", document.body ) );
}

With plugin configuration

You can optionally specify which sub components you will need and thus want to define to globally available.

import { PitayaTopbarConfiguration } from "@pitaya-components/topbar";

export function configure( aurelia: Aurelia )
{
	aurelia.use.standardConfiguration()
		   .plugin( "@pitaya-components/topbar", ( pluginConfig: PitayaTopbarConfiguration ) =>
		   {
			   pluginConfig.use(
				   "pitaya-topbar-row.html",
				   "pitaya-topbar-navigation.html",
				   "pitaya-topbar-actions.html",
				   "pitaya-topbar-action-icon.html"
			   );
		   } )
		   .feature( "resources" );

	aurelia.start().then( () => aurelia.setRoot( "app/app", document.body ) );
}

Import

If you don´t want this component to be handled as a plugin you have a few other options when importing a component into your layout:

Template

<template>
	<require from="@pitaya-components/topbar/dist/native-modules/pitaya-topbar"></require>
	<require from="@pitaya-components/topbar/dist/native-modules/pitaya-topbar-row.html"></require>
	<require from="@pitaya-components/topbar/dist/native-modules/pitaya-topbar-navigation.html"></require>
	<require from="@pitaya-components/topbar/dist/native-modules/pitaya-topbar-actions.html"></require>
	<require from="@pitaya-components/topbar/dist/native-modules/pitaya-topbar-action-icon.html"></require>
    ...
</template>

View model

@viewResources( 
	"@pitaya-components/topbar/dist/native-modules/pitaya-topbar",
	"@pitaya-components/topbar/dist/native-modules/pitaya-topbar-row.html", 
	"@pitaya-components/topbar/dist/native-modules/pitaya-topbar-navigation.html", 
	"@pitaya-components/topbar/dist/native-modules/pitaya-topbar-actions.html", 
	"@pitaya-components/topbar/dist/native-modules/pitaya-topbar-action-icon.html"
)
export class MyView
{
	...
}

Global resources

export function configure( config: FrameworkConfiguration )
{
	config.globalResources( [
		PLATFORM.moduleName( "@pitaya-components/master-component/dist/native-modules/master-component" )
	] );
}

Initialization

Our components are usually initialized by defining them in your views HTML. And can be accessed afterwards in the corresponding view model.

Template

<template>
	<pitaya-topbar
		view-model.ref="topbar"
		on-attached.call="doSomething(component)"
	></pitaya-topbar>
	...
</template>

View model

import {PiTopBar} from "@pitaya-components/topbar";

export class MyView
{
	public topbar: PiTopBar;

	public doSomething(component: PiTopBar)
	{
		this.topbar.type = "short";
	}
}

Variants

Default setup

<pitaya-topbar>
	<pitaya-topbar-row>
		<pitaya-topbar-navigation
			icon="manu"
			on-icon-click.call="openDrawer()"
			title="My Topbar Title"
		></pitaya-topbar-navigation>
		<pitaya-topbar-actions>
			<pitaya-topbar-action-icon
				icon="event"
				on-click.call="openCalendar()"
			></pitaya-topbar-action-icon>
			<pitaya-topbar-action-icon
				icon="more_vert"
				on-click.call="openMenu()"
			></pitaya-topbar-action-icon>
		</pitaya-topbar-actions>
	</pitaya-topbar-row>
</pitaya-topbar>

Event handlers

Attaching an event handler is as simple as adding on-<event>.call="<function>(<parameters>)".

NOTE: The function that you specify has to be defined as a method on the view model class, so that aurelias template engine can use it.

Template

<pitaya-topbar	
	on-navigation.call="topbarNavigated(event, component)"
	on-attached.call="topbarHasBeenAttached(component)"
>
	...
</pitaya-topbar>

View model

export class MyView
{
    public topbarNavigated(event: CustomEvent, component: PiTopBar)
    {
	    ...
    }

    public topbarHasBeenAttached(component: PiTopBar)
    {
	    ...
    }
}

You also can pass any parameter you like. Specifying event just tells the component that you wish to receive the event object, but if you define something else, it will be passed down to your function just like one would expect.

Template

<pitaya-topbar	
	on-attached.call="topbarHasBeenAttached('my custom message')"
>
	...
</pitaya-topbar>

View model

export class MyView
{
	public topbarHasBeenAttached(message: string)
	{
		...
	}
}

Bindables

A bindable is part of a core functionality of aurelia which basically allows you to configure a component from within your HTML code. They can be set/accessed via HTML attribute and also programmatically.

Template

<pitaya-topbar	
	type="dense"
>
...
</pitaya-topbar>

View model

import {PiTopBar} from "@pitaya-components/topbar";

export class MyView
{
	public topbar: PiTopBar;
	
	public someMethod()
	{
		this.topbar.type    = "prominent";
	}
}

Bindable properties

<pitaya-topbar>

<pitaya-topbar-navigation>

<pitaya-topbar-action-icon>

Methods and properties

PiTopBar

Style Customization

SASS mixins

With this component we are relying on the Top-App-Bar component of MDC. Check out the documentation to learn how to use their SASS mixins.

Note: SASS mixins are always applied on the main component <pitaya-topbar> by using the .pitaya-topbar selector.

Changes

The main repository uses tagged Releases to communicate changes between versions.

FAQ

Q: Why another JavaScript framework? \ A: Read this article for a detailed overview of ours goals.

Reach Out!

Find us on Twitter for the latest news, and please consider giving us a ?? star on GitHub!

Support

For contributions in the form of bug fixes and changes, feel free to use Pull Requests or send us a DM on Twitter to discuss how best to approach your issue.

License

The Master component source code is licensed under the MIT license.