greyrook / gown.js Goto Github PK

I have not idea what is feathers-ui, but I have very strong background in HTML5+CSS3 (also HTML APPS). In this HTML world new fresh projects try to stay as much as possible away from defining element styles with images (sprite-sheets etc.). This is due new advanced CSS settings, that let you define, for example, a complete custom button (with round borders, gradient, opacity, etc.). This is a very obvious tendency, because it solves retina issues & saves assets loading size (especially when there are a lot of different styles) / Also doe's not require Photoshop :)) / . So what is with Gown? Can we hope for some features to define, at least, button styles with settings (and no image required)? I think PIXI makes this really easy?...

What do they do? Why is labelFont, labelColor and textStyle used in buttons for the label? Does seem a bit redundant and error prone, since labelFont and labelColor are used to set updateLabel, but textStyle is used to update the style.

Support for component and state dependent text-styles defined in a theme. If none are given use global text-styles.

Scrollbar.js line 14
Uncaught TypeError: Cannot read property 'thumbSkin' of undefined

...with an API like the one in feathers, see
https://github.com/BowlerHatLLC/feathers/blob/master/source/feathers/controls/ScrollContainer.as

set overflow:hidden or something so you do not see the scrollbars

Like feathers-ui, but customizable where the suggestions are shown (below, above, both), and how the suggestions are generated (fixed list, function that generates suggestions) with the option to not allow setting of invalid options.

Any hopes of some updates, fixes, etc? Project being still since APR 18.

new Button label flash at position 0:0 before they get positioned at the right position (scroll the buttons in example 4 to see this)

Been a while now :)

use EventEmitter3

• make a first release 0.1.0 based on current master
• release 0.1.x branch to npm
• merge dev back into master
• make a second release, 0.2.0
• finalize API strcture
• npm release
• coverage test
• inch-ci
• code climate
• CI (travis)
• API docs & examples online
• fancy website

Default horizontal sliders and scrollbars seem to have a theming problem on the thumb

they should at least show the label

Click events are passed by

Check is always displayed as not selected. Just use the following theme for check in aeontheme, add width and height to the aeon-checks in the checkbox example and see for yourself. In not selected state it shows a white rect with black border, in selected state it should show a black rect.

"check": { "up": { "type": "rect", "radius": 0, "border": 3, "color": "0xffffff", "borderColor": "0x000000" }, "down": { "type": "rect", "radius": 0, "border": 3, "color": "0xffffff", "borderColor": "0x000000" }, "hover": { "type": "rect", "radius": 0, "border": 3, "color": "0xffffff", "borderColor": "0x000000" }, "selected_up": { "type": "rect", "radius": 0, "border": 3, "color": "0x000000", "borderColor": "0x000000" }, "selected_down": { "type": "rect", "radius": 0, "border": 3, "color": "0x000000", "borderColor": "0x000000" }, "selected_hover": { "type": "rect", "radius": 0, "border": 3, "color": "0x000000", "borderColor": "0x000000" } },

see "example 7 - slider" not working

overwrite destroy-function and remove all listeners, destroy skins, help gc to free memory.

Add example for PickerList / Drop Down functionality

The pixi loader wants to use XHR to load image files, but that is not available in e.g. testem

When the user just moves the content in the scroll area without klicking on the thumb the thumb does not move.

Is very confusing as the password seems to be one character longer than the userinput although it is not. Also the trailing space is always behind the pipe (**|).

I am thinking about merging the three projects back together into one.

Reasoning:

1. less to maintain (one bug tracker instead of three)
2. make it simpler for newcomers to find there way around and actually built gown successfully
3. claim: they are not in use separately from gown anyway

in Slider: Scrollable.call(this, thumb, theme)

but

function Scrollable(theme) {...}

The example works because the theme is the only argument, and since the first argument is thumb it works, but does not look like its intendet this way?

Might just be because of deprecated use of the "font" attribute.

A way to add new types to the ThemeParser that then can be used in the theme itself.

recalculate the layout when the width/height of a child changes (update using EventEmitter3)

When I'm loading a Texture into a GOWN.utils.ScaleContainer and then scale it, it looks like this:

Seems good so far but, when I set the width and the height of the container it looks like this:

Any ideas why thats happening?

Hi,

I followed the steps explained in the CONTRIBUTING.md file to setup dependencies. But I do not figure out how to build gown.js?

Is there a document explaining this simple step.

Regards,

As of now the virtual keyboard does not open on focus of a InputControl.

keep store position of thumb and recalculate it when the scrollbar gets resized

InputControls are only on the text itself clickable, not the element.

Like the one in feathers

https://feathersui.com/api-reference/feathers/controls/ToggleSwitch.html

hi.

example 5 - scrollbar

i can click button of invisible area like 'button7' into LayoutGroup.

LayoutGroup has mask. so button can't show except button on layoutgroup

We need more documentation.

• Auto-generated documentation form API
• merge/fix examples and update gown-examples
• create basic tutorials for building example applications::
• one app that has every ui like the Feathers Components Explorer
• business-application with fake-login and show some data
• game ui-dialogs

The build scripts in gown are just copied over from an older pixi version (with some minor modifications). There is a lot going on that is not needed and complicates the build process unnecessarily.
So we should clean up and create some new scripts that only do what is needed. It can be based on the current PIXI-build scripts but should not be just a copy

My primary goal is to create cascading lists (Miller columns) right now. But I'd also like touchpad two finger scroll to work with ScrollArea. I'll probably add this myself but please consider it a feature request. Thanks!