Git Product home page Git Product logo

photonui's Introduction

PhotonUI - A javascript framework to create user interfaces

Build Status NPM Version License Dependencies Dev Dependencies Greenkeeper badge

PhotonUI javascript framework to create rich web user interfaces without having to manipulate any HTML nor CSS.

Screenshot

Getting Started

Standalone Version

All the files you need are in the dist folder. You just have to import

  • photonui-base.css (must be imported first),
  • photonui-theme-particle.css,
  • andphotonui.js (or photonui.min.js)

in your page:

<!DOCTYPE html>
<html>
    <head>
        <meta charset="UTF-8" />
        <title>Boilerplate</title>
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />

        <link type="text/css" rel="stylesheet" href="dist/photonui-base.css" />
        <link type="text/css" rel="stylesheet" href="dist/photonui-theme-particle.css" />
        <script src="dist/photonui.js"></script>
    </head>

    <body>
    </body>
</html>

NPM and Browserify

If you are using Browserify in your project, a NPM package is available. To install it, juste type:

npm install --save photonui

then, to use it in your project you just have to import PhotonUI:

var photonui = require("photonui");

NOTE: do not forget to import CSS files in your HTML page:

<link rel="stylesheet" href="./node_modules/photonui/dist/photonui-base.css" />
<link rel="stylesheet" href="./node_modules/photonui/dist/photonui-theme-particle.css" />

Hacking

PhotonUI is built using Grunt, Less and Browserify. If you want to hack it, you will have to install few tools.

Installing Dependencies

To build PhotonUI, you will first have to install Node.js (or io.js).

NOTE: If you are on Ubuntu / Debian Linux you must install the nodejs-legacy package.

Next, install globally the grunt-cli npm package:

npm install -g grunt-cli

Then install the PhotonUI's dependencies:

npm install

Building PhotonUI

Once the build stuff and dependencies installed, you just have to run the grunt command to build PhotonUI:

grunt

All generated files are in the dist folder.

NOTE: during the development, it can be annoying to run the grunt command every time you make a change. You can instead run the following command to automatically rebuild what changed each time you modify a file:

grunt watch

Coding Style

PhotonUI follows the Yandex Javascript CodeStyle EXCEPT for the quote marks where we use double quotes (").

You can automatically check that your code follows the conventions by using this command:

grunt jscs

Testing

To run the PhotonUI tests, you can use the following commands (you should have chromium and firefox installed):

npm test

You can also run manually the tests in your browser:

  1. Check that the javascript is well formed and that it follows the coding style: grunt jshint jscs
  2. Build PhotonUI: grunt
  3. Run the tests: open test/index.html in your browser.

Git Hooks

To avoid committing bad stuff, you can install a git pre-commit hook that will abort the commit if the code contains errors. To install the hooks you just have to run the following command:

grunt githooks

Creating Your Own widgets

If you want to create you own PhotonUI widgets, first read this:

The documentation above explain how to create a custom widget outside of the PhotonUI project.

Once you feel comfortable with the custom widget creation, you can create widgets inside the PhotonUI project. We created a Yeoman generator that creates all required files for you:

Related projects:

Changelog:

  • 1.7.2:

    • New event on ColorPicker: value-changed-final called when the value is no more modified after continuous changes
  • 1.7.1:

    • Dependencies updated (uuid 2.0.3 → 3.0.0)
  • 1.7.0:

    • photonui.Color improved: it can now import/export colors from/to many format
    • Dependencies updated
  • 1.6.4:

    • Fields new event: value-changed-final called when the value is no more modified after continuous changes
  • 1.6.3:

    • Fixes an issue when unregistering a callback in photonui.AccelManager (#73)
    • Fixes translation not updated on selected elements of photonui.Select widget (#71)
    • Fixes absolute widget calculation (partially fixes #70)
  • 1.6.2:

    • Fixes regression in the photonui.ColorPicker widget (#68)
  • 1.6.1:

    • Fixes wrong import path of fontawesome files when importing photonui less files from the module.
  • 1.6.0:

    • New widget: photonui.Expander (thx @Breush),
    • Base.prototype._updateProperties() is now deprecated: the @photonui-update annotation replaces it (#55),
    • Various fixes (issue #51, issue #58, issue #60, PR #53,...).
  • 1.5.1:

    • Fixes an issue with FileManager,
    • cleanup build / test dependencies
  • 1.5.0:

    • New widget: photonui.KeyboardManager (thx @Breush)
  • 1.4.1:

    • various fixes
  • 1.4.0:

    • New widgets: Template, IconButton,
    • All widgets have now a data property that can contain anything you want,
    • Font Awesome updated to 4.5
  • 1.3.0:

    • Fixes vertical sizing issue in GridLayout with latest Gecko versions...
    • Better split of Less files
  • 1.2.1:

    • Fixes minor display issues
  • 1.2.0:

    • TabItem can now have icons
    • Touch support on Window and Slider
    • Window: fullscreen option added
    • Fixes "click" wEvent triggered twice on ToggleButton (issue #17)
    • Translation abstraction added to MouseManager
    • FluidLayout: re-implemented using CSS flexbox, new properties and layoutOptions available,
    • Stone.js updated
  • 1.1.0:

    • Classy replaced by Abitbol
    • Scaling support added to MouseManager
    • "click" wEvent added to TabItem
  • 1.0.1:

    • Fixes (GridLayout exception on some edge cases, flat ToggleButton theme)
    • Optimizations (destroying a layout widget)
  • 1.0.0:

    • First release

photonui's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

photonui's Issues

An in-range update of grunt-contrib-uglify is breaking the build 🚨

Version 3.2.1 of grunt-contrib-uglify was just published.

Branch Build failing 🚨
Dependency grunt-contrib-uglify
Current Version 3.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-uglify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits ahead by 4, behind by 1.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Slider + AccelManager conflict

The slider element blocks all keyboard inputs if it's focused, even with the safe argument passed to false in the addAccel method, like in the following code :

var slider = new photonui.Slider({
    fieldVisible: true,
    min: 0, max: 100,
    step: 10,
    value: 50
});
photonui.domInsert(slider, "demo");

var label = new photonui.Label({text: ""});
photonui.domInsert(label, "demo");

var accel = new photonui.AccelManager();

accel.addAccel("accel3", "ctrl + q", function() {
    label.text += "'Ctrl + Q' accelerator\n";
}, false);

Fluid Layout : End line too much spacing

When we have a FluidLayout with severals items and we are on the edge of placing the last widget of a line to the next one, the spacing here is too wide.

It's should be like on the left side.

Here is a screen with the problem shown:
2016-04-25_1708

An in-range update of karma-jasmine is breaking the build 🚨

Version 1.1.1 of karma-jasmine was just published.

Branch Build failing 🚨
Dependency karma-jasmine
Current Version 1.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

karma-jasmine is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 10 commits.

  • f48a731 chore: release v1.1.1
  • 00b97de chore: update contributors
  • 4c3221a Merge pull request #187 from maksimr/patch-fix-travis-npm
  • 4411737 Merge pull request #140 from tehvgg/master
  • 23ef6b3 chore: fix problem with npm on travis for old nodejs
  • 372adb9 Merge pull request #162 from TheModMaker/feat-afterAllErrors
  • f3fa264 feat: Propagate errors thrown in afterAll blocks
  • 9879a94 Revert "Allow lib adapter through so it can be used when pointing to this repo as a dev dependency."
  • 6ae78a1 Allow lib adapter through so it can be used when pointing to this repo as a dev dependency.
  • 7373f2e Check that a message is a string before calling .indexOf() when building the relevant stack.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Color alpha channel

Everything is in the title, none of the widgets allows to set the alpha field of the color class

An in-range update of jasmine-core is breaking the build 🚨

Version 2.9.0 of jasmine-core was just published.

Branch Build failing 🚨
Dependency jasmine-core
Current Version 2.8.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

jasmine-core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 2.9.0

Please see the release notes

Commits

The new version differs by 61 commits.

There are 61 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

TabItem: Could add IconButton support

Actually in a TabItem, we can only put classes herited of BaseIcon: see here

It's could be a good Idea to enable the IconButton too. This will simplify the process to handle a click on the Icon.

Here is an example code to add an IconButton to a TabItem.

var tabs = new photonui.TabLayout({
    tabsPosition: "top", // "top", "bottom", "left" or "right"
    children: [
        new photonui.TabItem({
            title: "Tab 1",
            child: new photonui.Label("Widget inside the first tab")
        }),
        new photonui.TabItem({
            title: "Tab 2",
            child: new photonui.Button()
        }),
        new photonui.TabItem({
            title: "Tab 3",
            rightIcon: new photonui.IconButton({
                icon: new photonui.FAIcon("fa-send"),
                    width: 32,
                    height: 32,
                    callbacks: {
                        click: function(widget, event) {
                            alert("clicked!");
                    }
                }
            })
        })
    ]
});

photonui.domInsert(tabs, "demo");

An in-range update of grunt-contrib-less is breaking the build 🚨

Version 2.0.0 of grunt-contrib-less was just published.

Branch Build failing 🚨
Dependency grunt-contrib-less
Current Version 1.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-less is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 7 commits.

  • 815cef9 v2.0.0 with dep updates (#342)
  • 5b04ca0 Update less to 3.0.0 (#340)
  • d8231dc Add node 8, remove node 0.10 (#337)
  • 0353e53 accept a function for sourceMapFilename (#306)
  • c81d284 accept a function for sourceMapURL (#307)
  • e0c3722 Update AppVeyor project.
  • 459ca0b Update less-options.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Remove `_updateProperties`

Behavior of _updateProperties can be replaced using abitbol meta-data.

  • Deprecate _updateProperties
  • During $super, call the setters of all not-previously-set properties

An in-range update of abitbol is breaking the build 🚨

Version 1.2.0 of abitbol was just published.

Branch Build failing 🚨
Dependency abitbol
Current Version 1.1.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

abitbol is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 16 commits.

  • 2e2324c 1.2.0
  • 576ec03 Merge pull request #14 from wanadev/13-bugfix-mixin-classvars
  • 4f56db7 Fixes for jscs and refactored code
  • e3f81ad Merging classvars
  • eaa1573 Added failing test
  • 2fcba52 Merge pull request #12 from wanadev/greenkeeper/mocha-4.0.0
  • 76bc83e chore(package): update mocha to version 4.0.0
  • e108a9c Merge pull request #11 from wanadev/greenkeeper/initial
  • 853c15a Update README.md
  • 858a01a keep old version of jscs because the yandex coding style is no more in the module
  • 954886d docs(readme): add Greenkeeper badge
  • c2846b7 chore(package): update dependencies
  • 04674a0 Merge pull request #8 from wanadev/perriern-patch-1
  • e2f2f87 Update index.md
  • fc3af4f Update class-api.md

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of lodash is breaking the build 🚨

Version 4.17.5 of lodash was just published.

Branch Build failing 🚨
Dependency lodash
Current Version 4.17.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Disabling widgets

One nice feature would be to allow disabling widgets (greyish look + no event).

An in-range update of uuid is breaking the build 🚨

Version 3.2.0 of uuid was just published.

Branch Build failing 🚨
Dependency uuid
Current Version 3.1.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

uuid is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 14 commits.

  • c0d44fd Publish v3.2.0 (#240)
  • eaa9f4e Use standard-version for release (#246)
  • 67d697c Fix #248 (#251)
  • 1fef18b fix: use msCrypto if available. Fixes #241 (#247)
  • 815daa3 eslint (#224)
  • bba9402 eslint (#219)
  • 0ea33e6 use typeof to check for crypto rather than global. Fixes #185 (#221)
  • c1f720d Defer random initialization of node and clockseq. Fixes #189 (#220)
  • dc02a76 UUID v3 Support (#217)
  • 72fbabb Corrected version from v4->v5 in README_js.md (#215)
  • 962c80a Use runmd to build README (#204)
  • e2389b3 Fix parentheses typo in README.md (#203)
  • 880d24e Update README.md (#208)
  • 8e23981 Fix buffer not being modified (uuid v5) (#201)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of grunt-contrib-yuidoc is breaking the build 🚨

Version 1.0.0 of grunt-contrib-yuidoc was just published.

Branch Build failing 🚨
Dependency grunt-contrib-yuidoc
Current Version 0.10.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-yuidoc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 12 commits.

  • 81426ee v1.0.0
  • 9573212 Merge branch 'master' of github.com:gruntjs/grunt-contrib-yuidoc
  • 8d87c5a Point main to task
  • 87a6881 Remove peerDeps. Ref gruntjs/grunt#1116
  • a0a20fc Merge pull request #34 from okuryu/yuidoc-v0.10.0
  • 8b40fa0 Bump yuidocjs version to v0.10.0
  • 72582c1 Minor lint tweaks.
  • 76772d3 Update copyright to 2016
  • 6778a97 CI: remove node.js 0.12 and add "5".
  • 8b2756d Update appveyor.yml.
  • 3290e65 CI: test node.js 4.0.
  • 46b7f39 fix changelog date

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Nested TabLayout inherit parent style

When nesting TabLayout the child inherit parent CSS.

It's annoying when you want to nest a TabLayout with tabsPosition to top in a TabLayout with tabsPosition to left, it result in the second TabLayout to not draw title and to display them to the left.
capture-bug-photon

Code sample:

new photonui.TabLayout({
    tabsPosition: "left",
    children: [
        new photonui.TabItem({
            title: room.label,
            child: new photonui.GridLayout({
                horizontalSpacing: 5,
                verticalSpacing: 5,
                children: [
                    new photonui.Text({
                        rawHtml: "<strong>" + _("Superficie") + "</strong>",
                        layoutOptions: {
                            x: 0, y: 0,
                            cols: 1, rows: 1
                        }
                    }),
                    new photonui.Label({
                        text:  (room.area / 10000).toFixed(2) + "m²",
                        layoutOptions: {
                            x: 1, y: 0,
                            cols: 1, rows: 1
                        }
                    }),
                    new photonui.TabLayout({
                        tabsPosition: "top",
                        children: [
                            new photonui.TabItem({
                                title: _("Menuiserie"),
                                child: new photonui.Label({text: "Test"})
                            })
                        ],
                        layoutOptions: {
                            x: 0, y: 1,
                            cols: 1, rows: 2
                        }
                    })
                ]
            })
        })
    ]
})

photonui.Slider: the visible property has no effect

Nothing happen when setting the visible property of the photonui.Sliderto false. This is caused by a display: flex !important; in the CSS...

Example code to reproduce:

var slider = new photonui.Slider({
    fieldVisible: true,
    min: 0, max: 100,
    step: 10,
    value: 50,
    visible: false
 });

Expected: Slider should not be displayed.
Current Result: The slider is visible.

An in-range update of grunt-contrib-watch is breaking the build 🚨

Version 1.0.1 of grunt-contrib-watch was just published.

Branch Build failing 🚨
Dependency grunt-contrib-watch
Current Version 1.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-watch is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 16 commits.

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of keyboardjs is breaking the build 🚨

Version 2.3.4 of keyboardjs just got published.

Branch Build failing 🚨
Dependency keyboardjs
Current Version 2.3.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

keyboardjs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 11 commits.

  • d8fb78a 2.3.4
  • 81bfa29 update dist
  • fa778c8 Merge pull request #125 from cwill/master
  • 2cf55a2 Merge pull request #127 from daniel-wer/master
  • 76e1d61 fix #96 by forcing a keyup on Mac when command is kept pressed
  • 641a63f Fix infinite recursion when calling setContext from a key release handler
  • fb155f5 Merge pull request #120 from McPo/reduce-fix
  • 30446bb updated dist
  • b611562 Fix reduce on any key
  • 804b249 Merge pull request #116 from weltonrodrigo/master
  • a3ec9f7 Minimal bower file with main

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Expander strange behavior when inside a Window

I took the same code as from Photonui expander's doc and put it inside a window.

The behavior is strange because the expander are not stacked together and split the space at 33% each.

screenshot from 2016-11-20 21-53-58

Here is my code:

JavaScript:

var photonui = require('photonui');

var win = new photonui.Window({
	visible: true,
	fullscreen: true,
	closeButtonVisible: false,
	child: new photonui.BoxLayout({
		orientation: "horizontal",
		children: [
			new photonui.BoxLayout({
			    horizontalPadding: 10,
			    verticalPadding: 10,
			    spacing: 10,

			    children: [
			        new photonui.Expander({
			            title: "Expander 1",
			            child: new photonui.Label({
			                text: "Never gonna..."
			            })
			        }),
			        new photonui.Expander({
			            title: "Expander 2",
			            folded: true,
			            child: new photonui.Label({
			                text: "... give you..."
			            })

			        }),
			        new photonui.Expander({
			            title: "Expander 3",
			            folded: true,
			            child: new photonui.Label({
			                text: "... up!"
			            })
			        })
			    ]
			})
		]
	})
});

My CSS: (should not interfere)

html, body {
    margin: 0;
    width: 100%;
    height: 100%;
}

Possible solutions:

Here are the css rules that I find controlling this behavior:

  • Disable: height: 100%; from top BoxLayout element.
  • Disable: flex-grow: 1; from .photonui-boxlayout > .photonui-boxlayout-item

I just give this possible solutions like that but I didn't think about their usage.

Removing accels remove more than expected

In the following example, "accel2" should still be active, but is not:

var label = new photonui.Label({text: ""});
photonui.domInsert(label, "demo");

var accel = new photonui.AccelManager();
accel.addAccel("accel1", "ctrl + a", function() {
    label.text += "1\n";
});
accel.addAccel("accel2", "ctrl + a", function() {
    label.text += "2\n";
});

accel.removeAccel("accel1");

An in-range update of keyboardjs is breaking the build 🚨

Version 2.4.0 of keyboardjs was just published.

Branch Build failing 🚨
Dependency keyboardjs
Current Version 2.3.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

keyboardjs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of grunt-browserify is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.3.0 of grunt-browserify was just published.

Branch Build failing 🚨
Dependency grunt-browserify
Current Version 5.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • f20e21c Version bump.
  • 30ad90d Merge pull request #401 from zkochan/master
  • 6cb1429 fix(deps): update browserify to version 16
  • 4e8eb1f Merge pull request #399 from ChuanyuWang/master
  • 4899438 Add example to use plulgin with options

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of grunt is breaking the build 🚨

Version 1.0.2 of grunt was just published.

Branch Build failing 🚨
Dependency grunt
Current Version 1.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 27 commits.

  • ccc3163 v1.0.2
  • e7795dc Remove iojs from test matrix (#1622)
  • a6a133b Remove deprecation warning for coffeescript (#1621) r=@vladikoff
  • 06b377e https links to webchat.freenode.net and gruntjs.com (#1610)
  • 7c5242f Use node executable for local grunt bin for Windows support
  • f6cbb63 Oh right, Windows isnt bash
  • a9a20da Try and debug why appveyor is failing on npm
  • 48bba6c Move to the test script to avoid npm was unexpected at this time.
  • 6b97ac0 Try to fix appveyor script
  • 19003ba For appveyor, check node version to decide whether to install npm@3
  • 3fcf921 Install npm@3 if npm version is npm 1 or 2
  • 77fc157 Use the local version of grunt to run tests
  • 400601a Updating devDependencies
  • 6592ad1 Update travis/appveyor to node versions we support
  • b63aeec Dont manually install npm, use the version each node version corresponds with

There are 27 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

What is type : kzd.Color

Hello guys, I am working on a definition library for PhotonUI.

And I just encounter something strange.

All the Color widget:

  • ColorPalette
  • ColorButton
  • ColorPickerDialog
  • ColorPicker

Have a property _color of type kzd.Color. I don't really understand this type. For example : Here

I was thinking that this widgets should use the type photonui.Color = require("./nonvisual/color.js");

An in-range update of browserify-licenses is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.4.6 of browserify-licenses was just published.

Branch Build failing 🚨
Dependency browserify-licenses
Current Version 1.4.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

browserify-licenses is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • ac1a382 v1.4.6
  • 557a271 handles namespaced packages
  • d010d2b update dependencies
  • 512de37 Merge pull request #24 from wanadev/greenkeeper/mocha-4.0.0
  • 65bfc9e chore(package): update mocha to version 4.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of karma-firefox-launcher is breaking the build 🚨

Version 1.1.0 of karma-firefox-launcher was just published.

Branch Build failing 🚨
Dependency karma-firefox-launcher
Current Version 1.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

karma-firefox-launcher is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 8 commits.

  • cf20be3 chore(release): 1.1.0
  • 66812f1 chore: update dev dependencies
  • 98a4ada fix: safe handling of missing env variables
  • fe9d442 Merge pull request #77 from keithamus/patch-2
  • 66cd7ed chore(ci): remove depracted Node versions from Travis.yml
  • ede7023 Merge pull request #79 from mgol/mailmap
  • 5f352c4 chore: add a Git .mailmap with my new name
  • a1fc1c8 feat: support Firefox headless

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

AccelManager Mac

Sur ton AccelManager, tu as oublié de remplacer le ctrl par cmd 😉

Callback of tab item activate when close parent window.

Code sample to reproduce issue (just click on close button)

var pos = photonui.Helpers.getAbsolutePosition("demo");
var tabs = new photonui.TabLayout({
    tabsPosition: "top",  // "top", "bottom", "left" or "right"
    children: [
        new photonui.TabItem({
            title: "Tab 1",
            child: new photonui.Label("Widget inside the first tab"),
                    callbacks: {
                        show: function(tab) {
                            console.log(tab.visible)
                        }
                    },
        }),
        new photonui.TabItem({
            title: "Tab 2",
            child: new photonui.Button(),
                    callbacks: {
                        show: function(tab) {
                            console.log(tab.visible)
                        }
                    },
        }),
        new photonui.TabItem({
            title: "Tab 3",
                    callbacks: {
                        show: function(tab) {
                            console.log(tab.visible)
                        }
                    },
        })
    ]
});

new photonui.Window({
    title: "My Window",
    visible: true,
   child: tabs,
    x: pos.x, y: pos.y,
    width: 300, height: 100,
    callbacks: {
        "close-button-clicked": function(widget) {
            widget.destroy();
        },
        "position-changed": function(widget, x, y) {
            widget.title = "My Window (x: " + x + ", y: " + y + ")";
        }
    }
});

An in-range update of grunt-contrib-uglify is breaking the build 🚨

Version 3.1.0 of grunt-contrib-uglify just got published.

Branch Build failing 🚨
Dependency grunt-contrib-uglify
Current Version 3.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As grunt-contrib-uglify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 1 commits.

  • 5aefbce Update uglify-js to v3.1.0.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Wrongly rounded value when creating a Slider

var slider = new photonui.Slider({
    value: 0.5,
    min: 0, max: 10,
    step: 0.5,          
    decimalDigits: 2,
});

photonui.domInsert(slider, "demo");

Expected result

A new slider with current value set to 0.5.

Result

A new slider with current value set to 1.0.

Note

Moving the value parameter to the end of the object make it work.

Is this project still active?

I'd like to know if this repository is still actively developed. I love the work you've done so far and it looks amazing and well done.

I've made some serious changes over on my fork, mainly related to modernizing and standardizing the build system, and it introduces significant incompatibilities between this repository and my own. Any changes to that fork will likely be incompatible with this one.

I'd simply like to know if it would be worth it to take the effort to maintain a separate branch which more closely mirrors to this one, so that any improvements can be contributed back to this repository.

Keep up the good work!
-Tribex

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.