Hi @quick6black

Just to let you know that a lot of new skins have been implemented on the develop #5 branch! Check it out to see if you can implement something.

Regards

I don't have investigate so far when this error occurs, but sometimes it does:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
at spark.material.components::TextInput/onFocusChange()[C:\local\workspace-ebase-restore\FlexSparkMaterialLib\src\spark\material\components\TextInput.as:77]

A quick and simple fix is to just check if the stage is null:

function onFocusChange(evt:FocusEvent):void
{
if(skin && skin.contains(evt.relatedObject)) return;
if(stage==null) return; // Quick fiX to avoid null pointer errors

var focusPoint:Point = new Point(stage.mouseX, stage.mouseY);
var objectsUnderPoint:Array = stage.getObjectsUnderPoint(focusPoint);
stage.focus = InteractiveObject(objectsUnderPoint.pop().parent);
}

I'll just commit this to the master branch.

it would be cool something shows up on asana...

Hi Rui,
I've started to clean-up the repo and cherry-picked the FloatingActionButton from dev to master.
Would be great if we also could merge the textarea to master.

Thanks,
Olaf

This issue is not a big problem but perhaps somebody stumble over it and could save some time
by reading this:
You shouldn't set the TabBars width="100%" cause:

• Child containers doesn't respect the new width after you minimize the width of the browser window
• The Tab indicator doesn't work properly after resizing

HTH
Olaf

Steps to reproduce:

1. Maximize Browser window
2. Click one item (or mouse over)
3. TabBar/Items displace
4. After scrolling the TabBar is in place again

I can't reproduce it until now but sometimes I've got this error while clicking at the DropDownBox:

I would love to see this two components in your Material theme. I love your work and i really believe that this would be a great addition. Would you consider extending this?

Thanks

I don't investigate why this error occur but sometimes it does:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
at spark.material.components::HSlider/updateSkinDisplayList()[C:\local\workspace-ebase-restore\FlexSparkMaterialLib\src\spark\material\components\HSlider.as:48]

I'll fix it by just checking if the 'inkHolder' and 'thumb' object is not null before it will be accessed.

Olaf

When tabbar is inside form, the creationcomplete bounds are not correct. 919478a

Hi,

Components are growing day-by-day, and at this time the form is not big enough.. I think we need to prototype something new.

I'll create a new branch from #5 to create a new UI. But I think Accordion component is required first.

It would be nice to show a "Clear Icon" next to text on "mouseOver"

By clicking an item it lost its background color ("rollOverColor"):

After clicking an item the "rollOverColor" should still be there.
(Same behaviour like a button)

Great progress! The one especially common component that isn't in here yet is the List component. Adding this Issue as a Feature Request. :)

I'd like to implement the Chips component:
https://www.google.com/design/spec/components/chips.html#
https://material.angularjs.org/latest/demo/chips

I would try to use a List with TileLayout that uses a "Chip" ItemRenderer to display a created Chip.
If it's possible the last item always should use another "NewChip" ItemRenderer for creating new chips.
To avoid wasting time with this approach, I'd ask if this is a proper way.

Thanks,
Olaf

I tried it in DEMO. It happens only on first click:

Would love to see more components (list and grid specifically). Would you be interested in donations or project work on this? @kentonue if you want to talk!

Hi Rui,
I've spend hours trying to solve this issue with no success :-(
I've tried to achive this by using deffered skin parts, but it seems for me that this doesn't work.

The first idea that occurs me, is on updateDisplayList(unscaledWidth:Number,unscaledHeight:Number), assign the skin.scroller or skin.scroller.viewport width/height.. that should

Could you explain this a bit more?

Thanks,
Olaf