You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by Angelo Lazzari <an...@redtulp.com> on 2016/01/26 19:54:05 UTC
Re: Spark components with Material Design
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 (<in...@gmail.com>)
escribió:
> Hi Olaf,
>
> I replied on github.
>
> Thanks
>
> 2015-10-06 14:04 GMT+01:00 OK [via Apache Flex Users] <
> ml-node+s2333346n11274h68@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 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 customizing needed to be able upload
> > textfiles?
> >
> > @Mark
> > From my point of view examples are welcome :-)
> >
> > Olaf
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11274.html
> > To unsubscribe from Spark components with Material Design, click here
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=
> >
> > .
> > NAML
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11275.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
Re: Spark components with Material Design
Posted by Rui Cruz <in...@gmail.com>.
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+s2333346n12343h7@n4.nabble.com>:
> Hi Rui,
>
>
>
> On 3/22/16, 12:17 PM, "Rui Cruz" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12343&i=0>> 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-SA, unless this was a port of
> existing code, your work can be under the Apache License, and thus the
> licensing of Material isn't a factor in these files (unless you did copy
> something from their repo).
>
> But you could just add "The principles behind the skin are the guidelines
> of material design:
> https://www.google.com/design/spec/material-design/" or something like
> that as a comment after the header.
>
> HTH,
> -Alex
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12343.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12347.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Mar 22, 2016 at 12:17 PM, Rui Cruz <in...@gmail.com> 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
>
> Those are the references, not code just one font and guidelines.
>
> The email for sending the clas is hidden.
>
> Regards
>
The Roboto fonts are already mentioned in our Apache Flex SDK License[1]
We use it for the Android 4.x+ skins. So no need to add another note
about them.
Thanks,
Om
[1] https://github.com/apache/flex-sdk/blob/develop/LICENSE#L252
>
>
> 2016-03-22 19:04 GMT+00:00 Alex Harui [via Apache Flex Users] <
> ml-node+s2333346n12339h83@n4.nabble.com>:
>
> > Hi Rui,
> >
> > On 3/22/16, 9:18 AM, "Rui Cruz" <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=12339&i=0>> 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:
> > >
> >
> >//////////////////////////////////////////////////////////////////////////
> >
> > >//////
> > >//
> > >// Licensed to the Apache Software Foundation (ASF) under one or more
> > >// contributor license agreements. See the NOTICE file distributed
> with
> > >// this work for additional information regarding copyright ownership.
> > >// The ASF licenses this file to You under the Apache License, Version
> > >2.0
> > >// (the "License"); you may not use this file except in compliance with
> > >// the License. You may obtain a copy of the License at
> > >//
> > >// http://www.apache.org/licenses/LICENSE-2.0
> > >//
> > >// Unless required by applicable law or agreed to in writing, software
> > >// distributed under the License is distributed on an "AS IS" BASIS,
> > >// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > >implied.
> > >// See the License for the specific language governing permissions and
> > >// limitations under the License.
> > >//
> > >//
> > >// This product bundles Google Material fonts and icons available under
> > a
> > >// CC-BY-4.0 license.
> > >// For details, see <src\spark\material\assets\fonts\Roboto.swf>.
> > Source
> > >// for these fonts and icons are available at:
> > >// https://github.com/google/material-design-icons
> > >//
> >
> >//////////////////////////////////////////////////////////////////////////
> >
> > >//////
> > >
> >
> > What is a "reference"? If it is just a link back to the original, then I
> > would say that Google's license doesn't need to be mentioned. AIUI, a
> > source header is meant to describe the licensing of the actual contents
> of
> > the file. If there are no lines in the file copied from Google, then
> > there is no requirement to provide attribution in the header.
> >
> > IMO, the top-level LICENSE file is the place to put the above. It
> > provides a summary of what licenses affect the various files in a set of
> > files.
> >
> > >
> > >2) I'll provide the signed ccla[2] and ccla[3]. But where do I submit
> the
> > >ccla?
> > >
> >
> > All clas get sent to [hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=12339&i=1>.
> >
> > Thanks,
> > -Alex
> >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12339.html
> > To unsubscribe from Spark components with Material Design, click here
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=
> >
> > .
> > NAML
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12340.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
Re: Spark components with Material Design
Posted by Alex Harui <ah...@adobe.com>.
Hi Rui,
On 3/22/16, 12:17 PM, "Rui Cruz" <in...@gmail.com> 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-SA, unless this was a port of
existing code, your work can be under the Apache License, and thus the
licensing of Material isn't a factor in these files (unless you did copy
something from their repo).
But you could just add "The principles behind the skin are the guidelines
of material design:
https://www.google.com/design/spec/material-design/" or something like
that as a comment after the header.
HTH,
-Alex
Re: Spark components with Material Design
Posted by Rui Cruz <in...@gmail.com>.
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.
The email for sending the clas is hidden.
Regards
2016-03-22 19:04 GMT+00:00 Alex Harui [via Apache Flex Users] <
ml-node+s2333346n12339h83@n4.nabble.com>:
> Hi Rui,
>
> On 3/22/16, 9:18 AM, "Rui Cruz" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12339&i=0>> 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:
> >
> >//////////////////////////////////////////////////////////////////////////
>
> >//////
> >//
> >// Licensed to the Apache Software Foundation (ASF) under one or more
> >// contributor license agreements. See the NOTICE file distributed with
> >// this work for additional information regarding copyright ownership.
> >// The ASF licenses this file to You under the Apache License, Version
> >2.0
> >// (the "License"); you may not use this file except in compliance with
> >// the License. You may obtain a copy of the License at
> >//
> >// http://www.apache.org/licenses/LICENSE-2.0
> >//
> >// Unless required by applicable law or agreed to in writing, software
> >// distributed under the License is distributed on an "AS IS" BASIS,
> >// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >implied.
> >// See the License for the specific language governing permissions and
> >// limitations under the License.
> >//
> >//
> >// This product bundles Google Material fonts and icons available under
> a
> >// CC-BY-4.0 license.
> >// For details, see <src\spark\material\assets\fonts\Roboto.swf>.
> Source
> >// for these fonts and icons are available at:
> >// https://github.com/google/material-design-icons
> >//
> >//////////////////////////////////////////////////////////////////////////
>
> >//////
> >
>
> What is a "reference"? If it is just a link back to the original, then I
> would say that Google's license doesn't need to be mentioned. AIUI, a
> source header is meant to describe the licensing of the actual contents of
> the file. If there are no lines in the file copied from Google, then
> there is no requirement to provide attribution in the header.
>
> IMO, the top-level LICENSE file is the place to put the above. It
> provides a summary of what licenses affect the various files in a set of
> files.
>
> >
> >2) I'll provide the signed ccla[2] and ccla[3]. But where do I submit the
> >ccla?
> >
>
> All clas get sent to [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12339&i=1>.
>
> Thanks,
> -Alex
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12339.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12340.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by Justin Mclean <ju...@classsoftware.com>.
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,
Justin
Re: Spark components with Material Design
Posted by Alex Harui <ah...@adobe.com>.
Hi Rui,
On 3/22/16, 9:18 AM, "Rui Cruz" <in...@gmail.com> 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:
>
>//////////////////////////////////////////////////////////////////////////
>//////
>//
>// Licensed to the Apache Software Foundation (ASF) under one or more
>// contributor license agreements. See the NOTICE file distributed with
>// this work for additional information regarding copyright ownership.
>// The ASF licenses this file to You under the Apache License, Version
>2.0
>// (the "License"); you may not use this file except in compliance with
>// the License. You may obtain a copy of the License at
>//
>// http://www.apache.org/licenses/LICENSE-2.0
>//
>// Unless required by applicable law or agreed to in writing, software
>// distributed under the License is distributed on an "AS IS" BASIS,
>// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>implied.
>// See the License for the specific language governing permissions and
>// limitations under the License.
>//
>//
>// This product bundles Google Material fonts and icons available under a
>// CC-BY-4.0 license.
>// For details, see <src\spark\material\assets\fonts\Roboto.swf>. Source
>// for these fonts and icons are available at:
>// https://github.com/google/material-design-icons
>//
>//////////////////////////////////////////////////////////////////////////
>//////
>
What is a "reference"? If it is just a link back to the original, then I
would say that Google's license doesn't need to be mentioned. AIUI, a
source header is meant to describe the licensing of the actual contents of
the file. If there are no lines in the file copied from Google, then
there is no requirement to provide attribution in the header.
IMO, the top-level LICENSE file is the place to put the above. It
provides a summary of what licenses affect the various files in a set of
files.
>
>2) I'll provide the signed ccla[2] and ccla[3]. But where do I submit the
>ccla?
>
All clas get sent to secretary@apache.org.
Thanks,
-Alex
Re: Spark components with Material Design
Posted by Rui Cruz <in...@gmail.com>.
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 Software Foundation (ASF) under one or more
// contributor license agreements. See the NOTICE file distributed with
// this work for additional information regarding copyright ownership.
// The ASF licenses this file to You under the Apache License, Version 2.0
// (the "License"); you may not use this file except in compliance with
// the License. You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
//
// This product bundles Google Material fonts and icons available under a
// CC-BY-4.0 license.
// For details, see <src\spark\material\assets\fonts\Roboto.swf>. Source
// for these fonts and icons are available at:
// https://github.com/google/material-design-icons
//
////////////////////////////////////////////////////////////////////////////////
2) I'll provide the signed ccla[2] and ccla[3]. But where do I submit the
ccla?
Thanks,
Rui
2016-03-22 14:41 GMT+00:00 Alex Harui [via Apache Flex Users] <
ml-node+s2333346n12334h28@n4.nabble.com>:
>
>
> On 3/22/16, 3:54 AM, "Rui Cruz" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12334&i=0>> 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 without any company resources, then it
> depends on your employee agreement. For me, my employer even owns after
> hours work.
>
> Assuming the company owns these files, because it is an existing code
> base, the normal process is to fill out a Software Grant [1] and have it
> signed by someone in the company who is authorized to sign contracts.
>
> However, I think that because this is "just a skin", it would be ok to
> have someone who is authorized to sign the much simpler CCLA [2] and
> authorize you to sign an ICLA [3] which are needed anyway so you can make
> changes in the future to these files in an Apache repo.
>
> [1] https://www.apache.org/licenses/software-grant.txt
> [2] https://www.apache.org/licenses/cla-corporate.txt
> [3] http://www.apache.org/licenses/icla.pdf
>
> The reason for all of this paperwork is so that users of your code can
> trust that Apache has checked the files truly can be used under the Apache
> License. It is sort of like knowing the food you eat has been inspected.
> Otherwise some potential users and contributors might shy away from using
> and contributing.
>
> >
> >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 me the text/example
> >please? (I think its all creative commons)
>
> It depends on if you have included these fonts and icons in the set of
> files. If you have, assuming there isn't any "source code" for the
> fonts/guidelines/icons involved, you would add to the LICENSE some text
> like:
>
> This product bundles Google Material fonts and icons available under a
> CC-BY-4.0 license.
> For details, see <path to folder(s) containing fonts and icons>. Source
> for these fonts and icons are available at:
> https://github.com/google/material-design-icons
>
> Thanks,
> -Alex
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12334.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12337.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by Alex Harui <ah...@adobe.com>.
On 3/22/16, 3:54 AM, "Rui Cruz" <in...@gmail.com> 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 without any company resources, then it
depends on your employee agreement. For me, my employer even owns after
hours work.
Assuming the company owns these files, because it is an existing code
base, the normal process is to fill out a Software Grant [1] and have it
signed by someone in the company who is authorized to sign contracts.
However, I think that because this is "just a skin", it would be ok to
have someone who is authorized to sign the much simpler CCLA [2] and
authorize you to sign an ICLA [3] which are needed anyway so you can make
changes in the future to these files in an Apache repo.
[1] https://www.apache.org/licenses/software-grant.txt
[2] https://www.apache.org/licenses/cla-corporate.txt
[3] http://www.apache.org/licenses/icla.pdf
The reason for all of this paperwork is so that users of your code can
trust that Apache has checked the files truly can be used under the Apache
License. It is sort of like knowing the food you eat has been inspected.
Otherwise some potential users and contributors might shy away from using
and contributing.
>
>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 me the text/example
>please? (I think its all creative commons)
It depends on if you have included these fonts and icons in the set of
files. If you have, assuming there isn't any "source code" for the
fonts/guidelines/icons involved, you would add to the LICENSE some text
like:
This product bundles Google Material fonts and icons available under a
CC-BY-4.0 license.
For details, see <path to folder(s) containing fonts and icons>. Source
for these fonts and icons are available at:
https://github.com/google/material-design-icons
Thanks,
-Alex
Re: Spark components with Material Design
Posted by Rui Cruz <in...@gmail.com>.
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 me the text/example
please? (I think its all creative commons)
Kind regards,
Rui
2016-03-22 0:34 GMT+00:00 jmclean [via Apache Flex Users] <
ml-node+s2333346n12329h73@n4.nabble.com>:
> 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
> > patch.
>
> As long as both contributors sign and submit an ICLA s[1] (or have already
> done so) all good from me.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/licenses/#clas
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12329.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12330.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by OK <OK...@edscha.com>.
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 agree with licensing my contributions under Apache License 2.0.
Olaf
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12333.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by Justin Mclean <ju...@classsoftware.com>.
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
> patch.
As long as both contributors sign and submit an ICLA s[1] (or have already done so) all good from me.
Thanks,
Justin
1. http://www.apache.org/licenses/#clas
Re: Spark components with Material Design
Posted by Alex Harui <ah...@adobe.com>.
On 3/21/16, 1:07 PM, "Rui Cruz" <in...@gmail.com> 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 the develop branch and I'm already using them
>on a company project.
>
>
>So for me is a GO and I believe Olaf will love this move too :)
Hi Rui,
Did you develop this code on behalf of a company? 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.
What do other PMC members think? IMO, this could be ruled as just a large
patch.
-Alex
Re: Spark components with Material Design
Posted by Rui Cruz <in...@gmail.com>.
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 a company project.
So for me is a GO and I believe Olaf will love this move too :)
P.S - This is far from complete / production ready, my plans was to make a
swc version of the skin, and also a side-project (or branch) where the
logic was coded inside the skin (personally I don't like, but is the only
way to use spark default components, then submit for voting and keep/drop
the swc version). Also mobile components missing.
If there is anything I can do, just say it and I'll try to provide it.
Kind regards,
Rui
2016-03-21 19:35 GMT+00:00 OmPrakash Muppirala [via Apache Flex Users] <
ml-node+s2333346n12319h63@n4.nabble.com>:
> 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 <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12319&i=0>
> > wrote:
>
> > thanks!
> > Angelo
> >
> > El mié., 27 ene. 2016 a las 7:59, OK (<[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12319&i=1>>) 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 you probably can't create a theme of it.
> > >
> > > But I don't know if it makes sense to provide a material theme cause
> IMO
> > > the
> > > material idea is not only to have fancy UI components. If you've
> > > implemented
> > > your app using a kind of material design you probably would never
> switch
> > > back to a standard theme. E.g. you would not like to place a standard
> > > button
> > > on top of your app layers instead of a floating action button.
> > >
> > > Olaf
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11831.html
> > > Sent from the Apache Flex Users mailing list archive at Nabble.com.
> > >
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12319.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12322.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by OK <OK...@edscha.com>.
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 ;-)
Currently I've started to create a simple material demo UI with the goal to
show how the material design could make a flex app much more fancy.
Btw from my point of view we'll need the same for FlexJS ;-)
Thanks,
Olaf
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12323.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by OmPrakash Muppirala <bi...@gmail.com>.
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 <angelo.lazzari@redtulp.com
> wrote:
> thanks!
> Angelo
>
> El mié., 27 ene. 2016 a las 7:59, OK (<OK...@edscha.com>) 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 you probably can't create a theme of it.
> >
> > But I don't know if it makes sense to provide a material theme cause IMO
> > the
> > material idea is not only to have fancy UI components. If you've
> > implemented
> > your app using a kind of material design you probably would never switch
> > back to a standard theme. E.g. you would not like to place a standard
> > button
> > on top of your app layers instead of a floating action button.
> >
> > Olaf
> >
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11831.html
> > Sent from the Apache Flex Users mailing list archive at Nabble.com.
> >
>
Re: Spark components with Material Design
Posted by Angelo Lazzari <an...@redtulp.com>.
thanks!
Angelo
El mié., 27 ene. 2016 a las 7:59, OK (<OK...@edscha.com>) 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 you probably can't create a theme of it.
>
> But I don't know if it makes sense to provide a material theme cause IMO
> the
> material idea is not only to have fancy UI components. If you've
> implemented
> your app using a kind of material design you probably would never switch
> back to a standard theme. E.g. you would not like to place a standard
> button
> on top of your app layers instead of a floating action button.
>
> Olaf
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11831.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
Re: Spark components with Material Design
Posted by OK <OK...@edscha.com>.
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 to provide a material theme cause IMO the
material idea is not only to have fancy UI components. If you've implemented
your app using a kind of material design you probably would never switch
back to a standard theme. E.g. you would not like to place a standard button
on top of your app layers instead of a floating action button.
Olaf
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11831.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Spark components with Material Design
Posted by jude <fl...@gmail.com>.
Can we choose this as a theme in 4.15?
On Tue, Jan 26, 2016 at 1:08 PM, OK <OK...@edscha.com> 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
> The floating button is already there and working, but you're right the demo
> is not updated.
> I've started working on the Chips component a few weeks ago and will
> continue it soon.
> I'd also like to create a litte material design demo app.
> Checkout the develop branch and also the other branches to get an idea of
> the progress.
>
> Thanks,
> Olaf
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11823.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
Re: Spark components with Material Design
Posted by OK <OK...@edscha.com>.
>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've started working on the Chips component a few weeks ago and will
continue it soon.
I'd also like to create a litte material design demo app.
Checkout the develop branch and also the other branches to get an idea of
the progress.
Thanks,
Olaf
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p11823.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.