I didn't copy code... (if material design was somehow spark based, maybe I
could try to copy something.. :D).
So, a comment after the header sounds great.
Thank you
2016-03-22 19:26 GMT+00:00 Alex Harui [via Apache Flex Users] <
ml-node+s246n1234...@n4.nabble.com>:
> Hi Rui,
>
>
>
> On 3/22
Hi Rui,
On 3/22/16, 12:17 PM, "Rui Cruz" wrote:
>Hi Alex,
>
>The principles behind the skin are the guidelines of material design:
>https://www.google.com/design/spec/material-design/
I am not a lawyer, so I don't know the exact answer, but because the
google code is under CC-BY and not CC-BY
On Tue, Mar 22, 2016 at 12:17 PM, Rui Cruz wrote:
> Hi Alex,
>
> The principles behind the skin are the guidelines of material design:
> https://www.google.com/design/spec/material-design/
>
> also the font embedded is Roboto:
> https://www.google.com/design/spec/resources/roboto-noto-fonts.html
Hi Alex,
The principles behind the skin are the guidelines of material design:
https://www.google.com/design/spec/material-design/
also the font embedded is Roboto:
https://www.google.com/design/spec/resources/roboto-noto-fonts.html
Those are the references, not code just one font and guidelines
Hi Rui,
On 3/22/16, 9:18 AM, "Rui Cruz" wrote:
>Thank you for the clarification Alex,
>
>1) I'll add the the "Licensed to the Apache Software Foundation (ASF)"
>comment block on every files with the google material reference like this:
>
>/
Hi,
> 1) I'll add the the "Licensed to the Apache Software Foundation (ASF)"
> comment block on every files with the google material reference like this:
IMO no need to add the CC-BY to the header it can be added to LICENSE but we
can help you with after after you donate the code.
Thanks,
Justi
Thank you for the clarification Alex,
1) I'll add the the "Licensed to the Apache Software Foundation (ASF)"
comment block on every files with the google material reference like this:
//
// Licensed to the Apache So
On 3/22/16, 3:54 AM, "Rui Cruz" wrote:
>This is just a skin.. and I also have full support from my company :)
Hi Rui,
The key question is whether your company is the true "owner" of these
files. If you are an employee then usually the company owns the work. If
you did this work after hours
Alex Harui wrote
> If not, if you would
> change the licensing to Apache License 2.0, and Olaf agrees in this thread
> to re-license his pull requests as Apache License 2.0, I think it might be
> ok to skip the whole Software Grant process and just have you attach the
> sources to a JIRA issue.
I
This is just a skin.. and I also have full support from my company :)
I think the apache licence on each file would be fine (maybe when I merge
the develop branch is a good time for that).
do I have to reference the material design from google too
(fonts/guidelines/icons)? If yes, can you provide
Hi,
> Did you develop this code on behalf of a company?
Or if you are full time does you employer own the right to that code? Depending
on your contact and where you are in the world this (sadly) may be the case.
> What do other PMC members think? IMO, this could be ruled as just a large
> pat
On 3/21/16, 1:07 PM, "Rui Cruz" wrote:
>Hi Om,
>
>Thanks for asking, Its very kind from you. The code is on github so its
>free and everyone can use it. It would be my pleasure to see this under
>Apache Flex project. Maybe this way gets more people completing it.
>
>A lot of new features are in
Hi Om,
thanks for your request! The origin author is Rui, I've just contribute some
minor things.
>From my point of view it would be great if this great lib will be part of
the SDK.
I'm very unhappy that I've not yet continue to work on it but I definately
will do and anybody is invited to help ;-)
Hi Om,
Thanks for asking, Its very kind from you. The code is on github so its
free and everyone can use it. It would be my pleasure to see this under
Apache Flex project. Maybe this way gets more people completing it.
A lot of new features are in the develop branch and I'm already using them
on
Rui, Olaf,
Any chance we can license this under Apache and bring into the Apache Flex
project (through a donation?) It looks like there is more and more
interest in Spark Material theme.
Thanks,
Om
On Wed, Jan 27, 2016 at 12:03 AM, Angelo Lazzari wrote:
> thanks!
> Angelo
>
> El mié., 27 ene.
thanks!
Angelo
El mié., 27 ene. 2016 a las 7:59, OK () escribió:
> jude wrote
> > Can we choose this as a theme in 4.15?
>
> I don't have any knowledge about themes and I don't now how to create it.
> The origin author Rui Cruz designed the lib as collection of skins and
> inherited components so
jude wrote
> Can we choose this as a theme in 4.15?
I don't have any knowledge about themes and I don't now how to create it.
The origin author Rui Cruz designed the lib as collection of skins and
inherited components so you probably can't create a theme of it.
But I don't know if it makes sense
Can we choose this as a theme in 4.15?
On Tue, Jan 26, 2016 at 1:08 PM, OK wrote:
> >Hi every one, i just wanted to know if there is some news about the
> >material spark design lib you spoke about a few months ago. I see probably
> >we'll have floating button but in the demo i cannot see it
> T
>Hi every one, i just wanted to know if there is some news about the
>material spark design lib you spoke about a few months ago. I see probably
>we'll have floating button but in the demo i cannot see it
The floating button is already there and working, but you're right the demo
is not updated.
I
Hi every one, i just wanted to know if there is some news about the
material spark design lib you spoke about a few months ago. I see probably
we'll have floating button but in the demo i cannot see it
Thank you very much
Angelo
El mar., 6 oct. 2015 a las 15:38, Rui Cruz ()
escribió:
> Hi Olaf,
Hi Olaf,
I replied on github.
Thanks
2015-10-06 14:04 GMT+01:00 OK [via Apache Flex Users] <
ml-node+s246n11274...@n4.nabble.com>:
> I've just finished an implementation of the "FloatingActionButton", but
> I'm not able to attach any kind of text files to the pull request, only
> images are
I've just finished an implementation of the "FloatingActionButton", but I'm
not able to attach any kind of text files to the pull request, only images
are possible:
Here's a screenshot of the circular button:
https://github.com/rui-cruz/Spark-Material/pull/3
@Rui
Is this my fault or is there some
components with Material Design
>I think those are straight forward implementations, just copy the the
buttonskin and remove the label :)
Also the geometrical shape should be circular:
https://www.google.com/design/spec/components/buttons-floating-action-button.html
I'll try to find some t
>I think those are straight forward implementations, just copy the the
buttonskin and remove the label :)
Also the geometrical shape should be circular:
https://www.google.com/design/spec/components/buttons-floating-action-button.html
I'll try to find some time next days to create these component
Hi Olaf,
I think those are straight forward implementations, just copy the the
buttonskin and remove the label :) about the icon I prefer fxg directly on
skin instead of icon.. Thats because icon method converts to bitmap and
then is not sharp as should be.. About textarea is also a copy from
text
Hi Rui,
it would be great to have a "Floating Button" and a "Textarea" component in
your awesome MaterialDesign lib.
So I'd ask you if you've already start to implement one of these components.
If not, I'd try to do this... hope my Flex skills are sufficient ;-)
Are there any known pitfalls?
Thank
On the textinput I've created 3 more states because it was more easy to
handle focus animations on the skin. But of course there's always a way to
handle inside the skin. I have good news regarding mobile too with a
contribution of a or merge with other repository. Next week I'm on
vacations but af
I think we should still be able to fit them into the existing skins somehow.
Can you give an example of the custom states?
Thanks,
Om
On Aug 29, 2015 11:29 AM, "Rui Cruz" wrote:
> Sure I agree. Just not sure how to handle custom skinstates / CSS styles.
> Any suggestions?
> Em 28/08/2015 18:43,
Benefit of having it all in the skins would allow drop in place use for
existing applications.
-Mark
I've never added to much code to the skins, but its indeed a way to do it
without creating new unnecessary components.
The only thing that comes in my mind is the css metadatas.. but we can
always have 4 skins (PrimaryButtonSkin, WarnButtonSkin, etc...)
I've no problems in changing all that if it
Hi Rui,
Happened to look into Button Component and the ButtonSkin within flat
material package.
Main concept within button component was to capture mouseX and mouseY
points on mouseDown and use them to ripple and then destroy the ripple on
mouseUp of the Button component.
Nothing major wrt chang
Hi megharajdeepak,
I did it to handle the ripple effect and override some custom functions.
But you can try to handle that on the skin functions. Let me know you have
success and I'll change the source.
Regards
2015-08-28 7:42 GMT+01:00 megharajdeepak [via Apache Flex Users] <
ml-node+s246n1
I have one question. Why is do we need separate flat material components
like Button, CheckBox etc? Can't we merge all the visual
aspects(colors\fonts\effects) within the skin class of each of those
components?
On Thu, Aug 27, 2015 at 10:06 PM, Rui Cruz wrote:
> You're welcome!
>
> Later tonight
Thank you for bringing the MaterialDesign to Flex, it looks awesome. Im
looking forward to check it out when I'll be back at office next week.
Olaf
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11068.html
Sent fro
You're welcome!
Later tonight I'll add few more components, You're all welcome to
contribute / pull request new features.
@kentonue already joined the github project and I'm really happy with the
feedback from the community, I'll keep the mailing list updated with new
releases.
Regards,
Rui
201
Thanks for sharing!
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11053.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Hi Rui,
Out of curiosity, I tried it out on iPad. It works great! No lags of any
kind(only thing got missed was the font. It picked up system font instead
of embedded one(not a big concern though)). It worked just fine as it did
for web. Looks excellent and the ripple effect is awesome! Just goes t
I just have checked your github repository out. It looks really great and
promissing. Thank you for your commitment.
Regards.
2015-08-26 7:14 GMT+09:00 Rui Cruz :
> Thanks Om :) I've forgotten to place the url on the first post and edited
> later ^^
>
> I'll add new components in the upcoming da
Just see it on Google+ publication and I think it looks so cool
I just tweeted it!
Thanks for sharing Om, and great work on iOS-Android mobile skins! :)
2015-08-26 0:02 GMT+02:00 OmPrakash Muppirala :
> For some reason, your link did not show in the email (but shows up on
> nabble)
>
> Here it
Thanks Om :) I've forgotten to place the url on the first post and edited
later ^^
I'll add new components in the upcoming days, sliders / dialogs / etc.. But
right now I'm not happy the way I handle the remove of the ink drops /
ripples and also the maximum size of them, at this time I'm using th
For some reason, your link did not show in the email (but shows up on
nabble)
Here it is again: https://github.com/rui-cruz/Spark-Material
Thanks for sharing this with the community. There is definitely a lot of
interest in Spark skins - including mobile. In the last couple of
releases, we push
41 matches
Mail list logo
