Re: Skinning FlexJS

2013-06-26 Thread Igor Costa 
Why not creating a basic approach but give total freedom for developers
apply metro style, twitter bootstrap, pure css, topcoat.

Like, re-using existing code and apply directly to our framework.

This week I started working on a model that could work with Apache Flex UI
Builder that outputs some sort of it, but I'm using topcoat with purecss
from yahoo.

I'm getting lucky until now and guess I will publish to whiteboard later
this summer.


Regards


Igor Costa
www.igorcosta.com
www.igorcosta.org


On Fri, Jun 21, 2013 at 7:52 AM, jude  wrote:

> Hi Om,
>
> I have been trying to think of a way to be able to reuse the skin you
> create in Flex with HTML 5 as well. I think it may require a new Flex
> component or MXML Skins with certain constraints (such as no ActionScript
> in the skin).
>
> Off the top of my head I have listed some ways we can create the visual UI
> of a button in Flex:
>
> - Button - button class draws the skin itself using graphics commands
> - Button with Programmatic Skin - programmatic skin of a button draws the
> graphics
> - BitmapImage Button -  button draws the up, over, down states from
> provided bitmaps (png, gif, jpg)
> - MXML Skin - the button skin draws the visuals from inline FXG and AS3
> (what Flex 4 uses)
> - FXG only MXML Skin - the button skin has only inline FXG. no AS3 used in
> skin
> - FXG external MXML Skin - the button skin references external FXG files
> for up, down, over states. no AS3 used in skin
> - MXML Bitmap Skin - the button skin references external images
> - FXG Button - the button references FXG for up, over, down states. no AS3
> in FXG obviously
> - AS3 Skin - the button skin written in AS3 draws the graphics
> - more?
>
> To create visuals of a button in HTML:
>
> - Button - the browser(s) draws the graphics (default size, position,
> padding, margins, etc)
> - Styled Button - the browser(s) draws the graphics use CSS to override the
> size, position, padding, margins, etc
> - BitmapImage Button - use CSS to draw the up, over, down states using
> external bitmaps
> - SVG Button - use CSS to draw the up, over, down states using external SVG
> files
> - SVG Inline Button - draws the up, over, down states using inline SVG
> (requires JS?)
> - BitmapImage Inline Button - draw to draw the up, over, down states using
> inline bitmap data (requires JS?)
>
>
>
> On Thu, Jun 20, 2013 at 3:47 PM, OmPrakash Muppirala
> wrote:
>
> > On Wed, Jun 19, 2013 at 7:09 AM, Erick Ghaumez  wrote:
> >
> > > hi,
> > >
> > > yes Om i'm in !
> > >
> > > I'll start with some skinning tests for the stockQuote sample.
> > > I think I can send a first proposal next week.
> > >
> >
> > Sounds good!
> >
> >
> > >
> > > Just to be sure : the goal is to create a default skin which you can
> use
> > > with SWF and html/js export ?
> > >
> >
> > Yes.  An AI or Fireworks file should be good.  We can export that to
> > .png/.fxg/.svg as needed.
> >
> >
> > > Does the skinning system for SWF Flex will be the same as today ( Skin
> > > class with MXMLG & FXG ) ?
> > >
> > >
> > I am trying to figure out what the best options would be.  I think I will
> > start out with skinning the Flash version with bitmaps and HTML5 version
> > with SVG to start out with.
> >
> > In the long run, I want to figure out how to bring back FXG to the Flash
> > version.
> >
>
>
>
> >
> > Thanks,
> > Om
> >
> >
> >
> > > Erick
> > >
> > >
> > > Le 19 juin 2013 à 02:21, OmPrakash Muppirala  a
> > > écrit :
> > >
> > > >>
> > >  What kind of beautification are you taking about?
> > > >>> I'm don't think it looks as good as Spark or MX right now.  Colors,
> > > >>> styles, spacing might make it look more like it is worth trying to
> > use
> > > >>> this stuff.
> > > >>>
> > > >> Perhaps the designers in this list could help us design the next gen
> > > >> default look and feel for Flex?  Any takers?
> > > >> Thanks,
> > > >> Om
> > > >
> > > >
> > > > Designers in the list,
> > > >
> > > > How about we try to put together a new visual look and feel for
> FlexJS?
> > > >
> > > > I am thinking that we can use the traditional approach of creating
> > assets
> > > > in AI or Fireworks and export them to formats we want.  This will
> also
> > > give
> > > > me a chance to figure out the various approaches and tooling
> > > requirements.
> > > >
> > > > We have a lot of different options to do this, CSS3, FXG/MXML, SVG,
> > etc.
> > > > To get an idea of the first set of components we want skinned, here
> are
> > > > the links to some samples Alex had put out a while ago [1,2]
> > > >
> > > > P.S.  Erick, you had pinged me on Twitter about wanting to help.  I
> > hope
> > > > you are in this list now :-)
> > > >
> > > > [1] http://people.apache.org/~aharui/FlexJS/
> > > > [2] http://people.apache.org/~aharui/FlexJS/StatesTest/
> > >
> > >
> >
>

Build failed in Jenkins: flex-sdk_mustella-air #4

2013-06-26 Thread flex . mustella 
See 

--
Started by upstream project "flex-sdk_mustella" build number 186
originally caused by:
 Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on WindowsSlave in workspace 

Checkout:flex-sdk_mustella-air / 
 - 
hudson.remoting.Channel@189a0ca:WindowsSlave
Using strategy: Default
Last Built Revision: Revision 541083ce147e511d62d053e8c4aa8d6097df0d28 
(origin/develop)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision 643dc5bade5292e95321809f6ca1829a15c6db3d 
(origin/develop)
Checking out Revision 643dc5bade5292e95321809f6ca1829a15c6db3d (origin/develop)
FATAL: Could not checkout null with start point 
643dc5bade5292e95321809f6ca1829a15c6db3d
hudson.plugins.git.GitException: Could not checkout null with start point 
643dc5bade5292e95321809f6ca1829a15c6db3d
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:878)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1229)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1205)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Thread.java:619)
Caused by: hudson.plugins.git.GitException: Command "C:\Program Files 
(x86)\Git\bin\git.exe checkout -f 643dc5bade5292e95321809f6ca1829a15c6db3d" 
returned status code 128:
stdout: 
stderr: fatal: Unable to create 
'c:/jenkins_slave/workspace/flex-sdk_mustella-air/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:740)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:750)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkout(CliGitAPIImpl.java:855)
at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:865)
... 13 more

Build failed in Jenkins: flex-sdk_asdoc #47

2013-06-26 Thread Apache Jenkins Server 
See 

Changes:

[KesslerConsulting] Adding to "SDK Changes" section in Release notes.

[KesslerConsulting] FLEX-14522:  Added enabledField and support during button 
creation. Minor logic changes.

[KesslerConsulting] Added an addition issue and updated the sdk changes.

[KesslerConsulting] FLEX-14522: Made boolean comparison more consistent.

--
[...truncated 1711 lines...]
automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

automation_agent_bundles-clean:

clean:

compile:
 [echo] Compiling frameworks/libs/automation/automation_agent.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation_agent\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\automation_agent.swc
 (75055 bytes)

bundles_en_US:

automation_agent_bundles:
 [echo] Compiling dmv_automation/locale/en_US/automation_agent_rb.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation_agent\bundle-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\locale\en_US\automation_agent_rb.swc
 (10192 bytes)

main:

automation_dmv:

clean:

compile:
 [echo] Compiling frameworks/libs/automation/automation_dmv.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation_dmv\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\automation_dmv.swc
 (48496 bytes)

main:

tool:

clean:

compile:
 [echo] Compiling tool.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\tool\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\tool.swc
 (48589 bytes)

main:

automation:

bundles-clean:

clean:

compile:
 [echo] Compiling frameworks/libs/automation/automation.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\automation.swc
 (86322 bytes)

main:
 [echo] Compiling frameworks/locale/en_US/automation_rb.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation\bundle-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\locale\en_US\automation_rb.swc
 (2139 bytes)

tool_air:

bundles-clean:
 [echo] IN bundles clean

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

tool_air_bundles-clean:

clean:

compile:
 [echo] Compiling tool_air.swc
 [echo] Using 
 
Integration Kit/frameworks/libs/air/airglobal.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\tool_air\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\tool_air.swc
 (67273 bytes)

main:

automation_spark:

clean:

compile:
 [echo] Compiling frameworks/libs/automation/automation_spark.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation_spark\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\automation_spark.swc
 (87221 bytes)

main:

automation_flashflexkit:

clean:

compile:
 [echo] Compiling frameworks/libs/automation/automation_flashflexkit.swc
[compc] Loading configuration file 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\projects\automation_flashflexkit\compile-config.xml
[compc] 
F:\hudson\hudson-slave\workspace\flex-sdk_asdoc\frameworks\libs\automation\automation_flashflexkit.swc
 (7359 bytes)

ma

Re: [FlexJS][FalconJX] The Beginnings of Databinding

2013-06-26 Thread Alex Harui 
Sorry, forgot to mention that the FlexJSOverlay is updated on [1]
and examples are at [2] with view source enabled for the Flash versions.

[1] http://people.apache.org/~aharui/FlexJS/
[2] http://people.apache.org/~aharui/FlexJS/DataBindingTest/

On 6/26/13 3:50 AM, "Carlos Rovira"  wrote:

>Very cool :)
>
>for your mail I thought that examples had this update but I can't see
>modified examples in the commits? maybe I'm missing something?
>
>
>
>2013/6/26 Alex Harui 
>
>> Hi,
>>
>> I just checked in the beginnings of {} databinding in FlexJS.  If you
>>look
>> at the source code, the SimpleBinding and ConstantBinding beads that
>>were
>> in the earlier examples are replaced by {} expressions.  The compiler
>> generates a data structure describing the bindings, and a bead
>>interprets
>> the data structure and sets up the bindings as needed.  In this early
>> version, the binding bead is looking for a specific pattern that can
>> resolve to what should be faster ConstantBinding and SimpleBinding
>> expressions.  The rest of this week I'll be working on more and more
>> general and complex cases.
>>
>> The reason binding is applied by a bead is because it allows you to
>> optimize by replacing general databinding beads with beads that know
>> something about the binding context.  For example, in this prototype,
>>the
>> ViewBaseDataBinding bead knows that it is setting up bindings for a
>> ViewBase which means that it can make assumptions that, for instance,
>>the
>> applicationModel structure itself will not be changing (its properties
>> will, but not the reference to the model).  And that means you can use
>>one
>> less watcher and you can apply initial values at initComplete and not
>> necessarily at the instantiation of each widget.
>>
>> -Alex
>>
>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>M: +34 607 22 60 05
>F:  +34 912 94 80 80
>http://www.codeoscopic.com
>http://www.directwriter.es
>http://www.avant2.es

Re: [FlexJS][FalconJX] The Beginnings of Databinding

2013-06-26 Thread Carlos Rovira 
Very cool :)

for your mail I thought that examples had this update but I can't see
modified examples in the commits? maybe I'm missing something?



2013/6/26 Alex Harui 

> Hi,
>
> I just checked in the beginnings of {} databinding in FlexJS.  If you look
> at the source code, the SimpleBinding and ConstantBinding beads that were
> in the earlier examples are replaced by {} expressions.  The compiler
> generates a data structure describing the bindings, and a bead interprets
> the data structure and sets up the bindings as needed.  In this early
> version, the binding bead is looking for a specific pattern that can
> resolve to what should be faster ConstantBinding and SimpleBinding
> expressions.  The rest of this week I'll be working on more and more
> general and complex cases.
>
> The reason binding is applied by a bead is because it allows you to
> optimize by replacing general databinding beads with beads that know
> something about the binding context.  For example, in this prototype, the
> ViewBaseDataBinding bead knows that it is setting up bindings for a
> ViewBase which means that it can make assumptions that, for instance, the
> applicationModel structure itself will not be changing (its properties
> will, but not the reference to the model).  And that means you can use one
> less watcher and you can apply initial values at initComplete and not
> necessarily at the instantiation of each widget.
>
> -Alex
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Build failed in Jenkins: flex-sdk_mustella-air #3

2013-06-26 Thread flex . mustella 
See 

--
Started by upstream project "flex-sdk_mustella" build number 185
originally caused by:
 Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on WindowsSlave in workspace 

Checkout:flex-sdk_mustella-air / 
 - 
hudson.remoting.Channel@189a0ca:WindowsSlave
Using strategy: Default
Last Built Revision: Revision 541083ce147e511d62d053e8c4aa8d6097df0d28 
(origin/develop)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision 643dc5bade5292e95321809f6ca1829a15c6db3d 
(origin/develop)
Checking out Revision 643dc5bade5292e95321809f6ca1829a15c6db3d (origin/develop)
FATAL: Could not checkout null with start point 
643dc5bade5292e95321809f6ca1829a15c6db3d
hudson.plugins.git.GitException: Could not checkout null with start point 
643dc5bade5292e95321809f6ca1829a15c6db3d
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:878)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1229)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1205)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Thread.java:619)
Caused by: hudson.plugins.git.GitException: Command "C:\Program Files 
(x86)\Git\bin\git.exe checkout -f 643dc5bade5292e95321809f6ca1829a15c6db3d" 
returned status code 128:
stdout: 
stderr: fatal: Unable to create 
'c:/jenkins_slave/workspace/flex-sdk_mustella-air/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:740)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:750)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkout(CliGitAPIImpl.java:855)
at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:865)
... 13 more

Jenkins build is back to normal : flex-sdk_mustella #185

2013-06-26 Thread flex . mustella 
See