I just noticed that my mavanizer generates a new artifact flatspark
... isn't that a theme? Shouldn't this be located in the themes directory?
FlatSpark is not ready to be used as a theme, that's why there is this
distinction. The project is meant to be a port of the FlatUI theme, so
A “deseloper”, actually two of them, joined the project recently. Mahmoud
and Bruno donated the FlatSpark theme. I don’t think it requires designer
skills to make that theme work for FlexJS, so, IMO, any of us developers
is welcome to take on that task.
Also remember that FlatSpark is
Sounds perfect. Are they publicly available anywhere?
Not yet, the example you can find on the old GitHub page is outdated and
shouldn't be used.
How should I proceed? Do you want me to put these examples online so you
can get them or should I add them to TdF myself?
I think it should be skins. FlatSpark is not yet ready to be used as a
complete theme.
A few things I noticed:
The link for the iOS e Android theme support is duplicated.
The Apache Flex SDK is available in source form from the following
download page:
There's a duplicated from in the sentence above.
Other than that, I think it's good.
Oops. Forget about the duplicated from. I just realized it is form from.
*Mental note: never reply emails after just waking up*
- iOS 7+ and Android 4.x+ mobile theme support
https://cwiki.apache.org/confluence/x/7AAIAw
https://cwiki.apache.org/confluence/x/7AAIAw
Both of the links refer to the same wiki page.
The CSS skin Alex cited is called Flat UI [1].
FlatSpark is basically a port from that skin, our main goal was to be as
close to that as possible. That's why FlatSpark has some limitations
regarding customization, we just tried to port the skin, maintaining its
colors and pre-defined sizes.
I'm noticing a strange behavior when I go to the licenses screen.
The first time I enter this screen I only see these licenses:
Apache Flex SDK
Apache Air SDK
Adobe Flash Player playerglobal.swc
Adobe Embedded Font Libraries and Utilities
If I change the language, it doesn't matter which one,
So, we remove the OFL checkbox and add some text to the font jars
license message:
\n\nNote: the use of the FlatSpark skin and components requires
embedded font support.
I like it, but I wonder if we can provide a better way to tell the user who
don't read the installation instructions or
Ah! Is this information in the Wiki article? If not, it should be, so
we can tell people to RTFM ;-)
We just need a confirmation and I'll add it to the wiki.
If it is needed for FlatSpark why it is optional ? :)
I think we were debating this in another email.
I am installing the sdk again right now to confirm the issue.
I think installing FlatSpark but throwing errors that the users will not
understand is not a good idea.
If the license is optional, then FlatSpark's installation should depend on
that license.
Hi Mahmoud,
I think you should commit this fix into develop branch and Erik will
cherry
pick up it if he decide that is valuable for current release. :)
Ok, thanks! :)
Not sure if this has been reported, but I believe there may be a bug in the
flatspark.skins.ButtonIconSkin.mxml as of Flex SDK 4.14 nightly build
#61...
I'll take a look at this tonight.
I think the release branch is closed for regular fixes, so I think I should
commit to the develop branch.
Can someone confirm this?
Which OS are you using? Are you running ant from FlatSpark's folder?
I always build FlatSpark with ant before committing any work, so it should
work...
I see. So everything is fine now?
A lot of people were reporting this error a few days ago, but now it looks
like everything is normal.
Om is right, it looks like if you use FlatSpark and don't select the font
utility you get this error.
On Thu, Dec 25, 2014 at 11:47 PM, OmPrakash Muppirala bigosma...@gmail.com
wrote:
Did you
Don't forget to mention the embedded Font Awesome. I can imagine that
many people will like this ;-)
Will do Olaf.
You should put this link into the README for the new SDK release.
Done. :)
Merry Christmas, everyone :)
I finally wrote the wiki page [1].
I'll be adding more details to it, such as the fixedFontSize property and
other important notes.
[1] https://cwiki.apache.org/confluence/display/FLEX/Using+FlatSpark+skins
It wasn't. Olaf also pointed this could cause some confusion, so I changed
it to fixedFontSize, which describes way better.
Fixed two more issues: FLEX-34693 and FLEX-34695
On Thu, Dec 18, 2014 at 9:09 PM, Mahmoud Ali mudd...@gmail.com wrote:
OK, you should be able to assign issues to yourself now.
Thank you Alex.
I already resolved FLEX-34694 and FLEX-34692, both were reported by Olaf
and were related
I found this link [1] for FlatSpark usage. Can we add this to the
RELEASE_NOTES? Or is Mahmoud planning on a new wiki page?
It would be nice to have a wiki page for the TLF Tables as well. Harbs,
any chance you can get something like that up?
This version is outdated so it can cause
Sure, it is an issue with a new feature. Please commit to
'release4.14', it will be merged into develop after we've released.
Okay :)
I have a JIRA account created (akamud), I can't assign issues to me. but
I'm already resolving FLEX-34692 and FLEX-34682.
Thank you Olaf. I assigned the issue to me.
Olaf, thank you for your help on fixing FLEX-34692. I replicated them to
ButtonIconSkin too.
I just committed changes that fix pretty much everything you reported so
far. Thank you so much for testing!
Erik, I committed them to 'release4.14' branch as you instructed.
OK, you should be able to assign issues to yourself now.
Thank you Alex.
I already resolved FLEX-34694 and FLEX-34692, both were reported by Olaf
and were related to FlatSpark.
I believe he might have an environment issue, since I don't have that issue
with a fresh install of 4.14.
Yeah, probably. The weirdest part, for me, is that it will work if I import
the swc.
I checked all the fonts comparing with the mobile theme and the actual
path, and everything looks
I've copy and paste some code from the WebAppTest.mxml inside the
flatspark git repository:
https://github.com/akamud/FlatSpark/blob/master/samples/WebAppTest/src/WebAppTest.mxml
The examples are outdated, I'll update it once we release the 4.14 SDK.
They only work with the old version of
Anyway: all works fine now and apart from the flatspark theme, I haven't
had any issues in upgrading to the new sdk. All I had to do is modify the
html template file because our projects need a bit of custom code in those.
Thank you for helping Dany.
I'm just wondering if there was any
Actually this skinClass=flatspark.skins.ButtonSkin also should work :)
It should work, last time I checked I used the flatspark.swc from libs
folder directly into FlatSpark's demo and I had no problem.
I'll take a look a this and write the wiki page.
OK, you should have permissions
Thanks
Sorry for the delay to answer this.
I downloaded the 4.14 SDK this morning and I had the same problem Dany is
having.
All the FlatSpark sources are there, but the .swc is not getting generated
in the libs folder.
I downloaded the SDK via the installer.
I'll try to download it again, as Erik
I downloaded the SDK again, FlatSpark is now included in libs folder, but
I'm getting the error Unable to build font for all the fonts FlatSpark
uses.
I did a quick test using the flatspark.swc directly from my local Flex SDK
build (built on release4.14.0 branch) and everything worked fine.
All
All the fonts are added via css, they are declared the same way the
Android mobile theme declares them:
src:url(flatspark/assets/fonts/lato/Lato_Regular.otf);
I forgot to mention, I'm also adding them to the compile-config.xml:
include-file
Thanks, Om.
I just did another test: copied the flatspark.swc from the downloaded Flex
SDK 4.14.0 into my libs project folder and again it worked.
So it looks like it just won't work when referencing the skin from the SDK
itself...
*1.) Specifying skinClass inline:*
Looks like the wiki page has an error
https://github.com/akamud/FlatSpark/wiki/How-to-use-FlatSpark-in-your-project
The wiki was outdated, I changed the namespaces to lowercase just to follow
the convention in the sdk projects. I was planning to update it
the release notes state that FlatSpark is a new theme so that description
should be updated (replace 'theme' with 'skins'?)
I think that would be more appropriate for now.
I can write something in the wiki.
FlatSpark's GitHub had a wiki showing how to use it.
https://github.com/akamud/FlatSpark/wiki/How-to-use-FlatSpark-in-your-project
I just couldn't get the Flex SDK project to build for Flash Builder. Is
there any place I could download the 4.14 SDK to write
I think I just found the binaries in Jenkins.
I'll write something showing how to use it when I get back from work.
On Mon, Dec 15, 2014 at 7:07 AM, Mahmoud Ali mudd...@gmail.com wrote:
I can write something in the wiki.
FlatSpark's GitHub had a wiki showing how to use it.
https
download the 4.14 candidate through the Installer, just follow
the instructions in the thread testing is easy!
Thanks,
EdB
On Mon, Dec 15, 2014 at 11:07 AM, Mahmoud Ali mudd...@gmail.com wrote:
I can write something in the wiki.
FlatSpark's GitHub had a wiki showing how to use
Mahmoud,
Using the GitHub wiki article I've tried to create a new project,
chose 4.14 RC SDK and add one button.
If I try to give this button the FlatSpark look by using the
'skinClass' property directly in MXML, I get 33 compiler errors,
starting with a dozen or so Exception during
Never mind. It turns out it was just me on a Monday morning :-(
Sorry for the waste of time.
EdB
Haha, I know that feel.
Either way, I'll write the wiki article tonight.
Thanks for testing :)
]/frameworks/libs'?
EdB
On Mon, Dec 15, 2014 at 2:52 PM, Dany Dhondt archeme...@mac.com wrote:
What was your mistake? I get the same 33 errors :)
Dany Dhondt
archeme...@mac.com | Mobile +32 496 251 455
Op 15-dec.-2014, om 13:17 heeft Mahmoud Ali mudd...@gmail.com het
volgende
I think I'm a little late, from what I'm seeing this was just a problem
with RAT and not with the licenses, right?
Also, It looks like this is all resolved by now. If I can help with
anything on this, just let me know.
I see. I'll add them to that branch then. If you see something wrong with
the way I'm adding the examples, please let me know.
Oops, my bad.
Just sent a new commit that fixes this.
Thanks for the help.
I think it is now complete. I just tested the .SWC generated with our
FlatSpark demo and everything is working as expected.
I also added the license mentioning the fonts license.
On Wed, Oct 15, 2014 at 11:47 PM, Alex Harui aha...@adobe.com wrote:
On 10/15/14, 7:31 PM, Mahmoud Ali mudd
think we could show examples of the components that are already complete.
On Sun, Oct 12, 2014 at 6:17 PM, Mahmoud Ali mudd...@gmail.com wrote:
What problems did you run into? Ask on the list and you may find someone
who knows the answer + it it helps other people who may of of built the SDK
these components. When I run ant it says it can't find the
specified type.
Does anyone know how to fix this?
On Tue, Oct 7, 2014 at 2:04 AM, Alex Harui aha...@adobe.com wrote:
On 10/6/14, 9:58 PM, Mahmoud Ali mudd...@gmail.com wrote:
It is. I'm actually trying to build the SDK right now
I see Jenkins is failing the build after my commit, I'm not familiar with
it. Can anyone help me on this?
On Wed, Oct 15, 2014 at 9:34 PM, Mahmoud Ali mudd...@gmail.com wrote:
Sorry for the long delay. I added the license files for Font Awesome and
Lato. I also added the build script so
Yes, I'm also interested in making this happen.
I was having some problems building FlatSpark on Windows to complete the
donation, but I must finish this this week.
We could start on the basic components that are already implemented, like
buttons and text inputs.
On Sun, Oct 12, 2014 at 5:34 PM,
What problems did you run into? Ask on the list and you may find someone
who knows the answer + it it helps other people who may of of built the SDK
before.
I had some problems running the constructFlexForIDE.bat that creates the
compatible file for Flash Builder, as described in the readme.
of sparkskins would make sense [1]
So, that would be frameworks/projects/flatspark
Thanks,
Om
[1]
https://github.com/apache/flex-sdk/tree/develop/frameworks/projects/sparks
kins
On Oct 3, 2014 8:55 PM, Mahmoud Ali mudd...@gmail.com wrote:
I don't want to make a mess
Again, thank you very much for all the help getting this done.
It's great to have this as an official part of Apache Flex :)
On Fri, Oct 3, 2014 at 11:49 AM, Alex Harui aha...@adobe.com wrote:
Hi Folks,
I believe Justin has been traveling, but as far as I can tell, the
FlatSpark donation is
at 10:33 PM, Mahmoud Ali mudd...@gmail.com wrote:
Again, thank you very much for all the help getting this done.
It's great to have this as an official part of Apache Flex :)
On Fri, Oct 3, 2014 at 11:49 AM, Alex Harui aha...@adobe.com wrote:
Hi Folks,
I believe Justin has been traveling
I don't want to make a mess, what do you think would be the best folder to
put this?
I could help with that, where is the code from Android skin so I could take
a look? I get the feeling that it won't be as easy as doing a skin based on
pure CSS.
On Wed, Oct 1, 2014 at 6:02 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Continuing in a separate thread:
What does it take for a
-wip-us.apache.org/repos/asf/flex-sdk.git
On Wed, Oct 1, 2014 at 1:06 PM, Mahmoud Ali mudd...@gmail.com wrote:
I could help with that, where is the code from Android skin so I could
take
a look? I get the feeling that it won't be as easy as doing a skin based
on
pure CSS.
On Wed, Oct
Okay, I removed the files needed then zipped the source code and uploaded
to GitHub with its MD5 here
https://github.com/akamud/FlatSpark/releases/tag/v1.0
I'll be sending the signed files today along with that link.
On Mon, Sep 15, 2014 at 7:09 AM, Mahmoud Ali mudd...@gmail.com wrote:
Hi
. They have a board meeting tomorrow.
-Alex
On 9/16/14 4:53 AM, Mahmoud Ali mudd...@gmail.com wrote:
Okay, I removed the files needed then zipped the source code and uploaded
to GitHub with its MD5 here
https://github.com/akamud/FlatSpark/releases/tag/v1.0
I'll be sending the signed files today
to make a few changes to the grant
form. I just want to make sure you got his response. I'll watch for the
Secretary's acceptance email when you file the adjusted form.
Thanks,
-Alex
On 9/16/14 4:32 PM, Mahmoud Ali mudd...@gmail.com wrote:
I just sent the email to the Secretary, thanks
Hi,
On Mon, Sep 15, 2014 at 12:53 AM, Alex Harui aha...@adobe.com wrote:
Good questions, answers inline
OK. At Adobe the employment agreement actually says they own code I write
in my spare time unless I have a previous arrangement with the Adobe. As
long as your company doesn't have an
://www.apache.org/licenses/software-grant.txt
On 9/13/14 12:32 PM, Mahmoud Ali mudd...@gmail.com wrote:
Since FlatSpark is made by two people, should we both sign the forms? If
so, is there a special form for more than one contributor or should I
just
copy-and-paste when necessary?
On Sat
Oops, just to be clear, I meant we will each sign the Software Grant
referencing the same file.
On Sun, Sep 14, 2014 at 10:15 PM, Mahmoud Ali mudd...@gmail.com wrote:
We do work together at the same company, but all the work was done during
our spare time, as two people contributing on GitHub
Since FlatSpark is made by two people, should we both sign the forms? If
so, is there a special form for more than one contributor or should I just
copy-and-paste when necessary?
On Sat, Sep 13, 2014 at 12:09 AM, Justin Mclean jus...@classsoftware.com
wrote:
Hi,
Regarding the other custom
That's great! What would the next steps be?
On Fri, Sep 12, 2014 at 9:37 PM, Justin Mclean jus...@classsoftware.com
wrote:
Hi,
Think we can call a result here :-)
Justin
Okay, I'll be going through the links this weekend.
I also am reading jude's post commenting what he learned from the process
of donation of Radii8. I think it will help me a lot.
On Fri, Sep 12, 2014 at 10:15 PM, Justin Mclean jus...@classsoftware.com
wrote:
Hi,
That's great! What would
I think so. I tried contacting the owner but got no response, so I think
I'll just remove it.
Regarding the other custom components, should I remove them too on the zip
file I'll be sending?
I also have a question, after the project is donated how can I keep
contributing to it? Will it be via
As one of the owners I think the best option is accepting FlatSpark now and
BootFlat later.
About the one file pending license, I'm trying to contact the owner, but if
he doesn't respond, we could just remove the file.
On Wed, Sep 3, 2014 at 2:29 AM, Alex Harui aha...@adobe.com wrote:
On
update?
On Sat, May 24, 2014 at 1:54 AM, Mahmoud Ali [hidden email]
http://user/SendEmail.jtp?type=nodenode=40350i=0 wrote:
That is good news. And no pull requests were accepted?
So far no pull requests were made...
Well, BootFlat is a bit different to Apache Flex. It appears
I would like to donate the entire source code.
It is actually based on FlatUI, which is open-source but under CC 3.0 and
MIT License. While it is not a fork, all the color schemes are based on
this. (https://github.com/designmodo/Flat-UI)
We had planned a version of BootFlat but other things got
FlatUI is written by DesignModo, and I am not affiliated with them.
I wrote new source code to implement their visuals, withouth copying it
from their source code.
FlatSpark does not have any dependency on Bootstrap.
All the code is just ActionScript + some CSS.
Donating just the skins might
ButtonIcon and TextInputIcon were implemented based on Button and
TextInput, no other examples were used, so I think those are fine.
ToogleSwitch was implemented based on the example from this post:
http://yonaskolb.com/blog/2012/1/18/flex-toggle-switch-spark-skin.html
There is a reference to it
Cool, Erik! We are glad you also liked BootFlat. =)
Sure!! Let's talk more about this, I'll be waiting for your contact with
more details.
-
Skype: muddibr
--
View this message in context:
I agree there is a lot of work to be done for Flex/Mobile, but our customers
ask for a better skin in our Flex applications.
We don't think this should replace the current theme for Flex, it should
come as an option, in fact, we are commited to doing this as one of the
guidelines
Good news then, it is created by the two of us, no corporations involved.
The BootFlat we will begin this weekend will follow the same pattern. It
will be owned by the two of us, no corporations involved, so I hope the
donation process will be less bureaucratic, hehe.
-
Skype: muddibr
--
Does the roadmap for the FlatSpark includes providing a way to skin all UI
components of Flex?
Yes, we are designing it with the option to change all the skins at once, if
wanted by the developer.
Regarding the FlexJS + Flex sharing the same theme, I was rather on the
design and artwork level,
That is good news. And no pull requests were accepted?
So far no pull requests were made...
Well, BootFlat is a bit different to Apache Flex. It appears to be owned
by a corporation. You are free to create your own Flex version of
BootFlat because the MIT License allows that, but it will
81 matches
Mail list logo
