Re: 0.9.3 Release

[Alex Harui]

In case folks are wondering, I deleted the release/0.9.3 branches from all 3 
repos.  There have been changes made in each of the branches since the branches 
were cut and there were also issues with the royale-compiler and 
royale-typedefs branches not having synced version numbers to their develop 
branches.

I see a vote thread opened today on Maven's lists for the SCM plug in.

AIUI, we are on hold for a release unless we get general consensus to what 
commit hash to release from for royale-asjs.

-Alex

On 5/17/18, 3:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
 wrote:

The minimun change is to see package names change.
Take into account that all is building and working ok. Only we have
problems in jsonly build since is only depends on ANT (what I think is not
good, since is missing maven build), in "/mustella/tests/basicTests/".
Looking at what's happening in that part will solve the build.

2018-05-17 11:40 GMT+02:00 Harbs :

> You are right. I missed this.
>
> What is the minimum change necessary to get this to work?
>
> > On May 17, 2018, at 12:24 PM, Carlos Rovira 
> wrote:
> >
> >  I think you missed one important point I
> > posted in other email: All blog post samples posted that are using the
> > actual names, packages and namespaces. If you release 0.9.3 without all
> > that, we can destroy out credibility since in all posts we have:
> >
> > "The example uses the new Jewel UI set that supports themes. Jewel will
> be
> > available in the forthcoming 0.9.3 release of Royale. In the meanwhile
> you
> > can find it in the develop branch."
> >
> > and the code is tailored with the actual api.
> >
> > For that reason, I think is important to hold 0.9.3 until it can ship
> with
> > all that we are promising in website and social networks for the latest 
2
> > months. I think this is crucial.
>
>


-- 
Carlos Rovira

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C9a61c338f4554b04aa9008d5bbdd5762%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636621481721528268=6FoSfupJoaFpfsqJcJ7HtHNpRoQluGUzh6hlM21AH20%3D=0

Jenkins build is back to normal : royale-compiler #264

[apacheroyaleci]

See 

Build failed in Jenkins: royale-compiler #263

[apacheroyaleci]

See 


--
[...truncated 4.07 KB...]
 [echo] Cloned fresh copy of Google Closure Library

check-env:

env-properties:

main:

BUILD SUCCESSFUL
Total time: 27 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
'"-Denv.ASJS_HOME=C:\Program Files (x86)\Jenkins\workspace\royale-asjs"' main 
&& exit %%ERRORLEVEL%%"
Buildfile: 


sdk:

annotate.class:

unknown.tree.pattern.input.output:

main:

compiler.downloads.cache:

compiler.downloads:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is 


prepare:
 [echo] Making lib directory 


all:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:

Build failed in Jenkins: royale-compiler #262

[apacheroyaleci]

See 


Changes:

[aharui] handle excluding functions as well

--
[...truncated 3.91 KB...]

env-properties:

main:

BUILD SUCCESSFUL
Total time: 25 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
'"-Denv.ASJS_HOME=C:\Program Files (x86)\Jenkins\workspace\royale-asjs"' main 
&& exit %%ERRORLEVEL%%"
Buildfile: 


sdk:

annotate.class:

unknown.tree.pattern.input.output:

main:

compiler.downloads.cache:

compiler.downloads:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is 


prepare:
 [echo] Making lib directory 


all:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:
 [echo] checking for 


download-dependency:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is 

 [echo] ROYALE_COMPILER_HOME is 


check-dependency:

Re: Should Jewel default to Express Beads? (was Re: [Discussion] Package change names (was Re: 0.9.3 Release))

[Alex Harui]

Hi Carlos,

Express is not an attempt to emulate Flex APIs.  The Emulation Components are.  
Express is merely designed to pre-compose more beads with less strong-typing in 
the data handling, in response to user feedback we received.  That's why I 
think Jewel should compose Express beads, in order to respond to our users.

Hopefully we will hear from others.

Thanks,
-Alex

On 5/24/18, 3:43 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
 wrote:

Hi Alex,

I think Jewel born from Basic and started doing the same as Basic do in
order to develop the view, CSS, etc... then is evolving to something that
is usable directly. For example: in the beginning there was Button and
TextButton like in Basic, then I find that only Button (with text property)
was needed since is what we already use it 99% of the time. In the other
hand, things like "Disabled" is already written as a bead since is a
behavior that is needed sometimes. I'm trying to balance so maybe the
response is that is not white, but is not back. So I think is not exactly a
Express set when all is preconfigured. I must say that I'm still learning
from developing Jewel and I'm testing things and sometimes I refactor to
what seems a better solution. In the end I use to think in how the code
finaly looks, and if is usable, flexible and how simple is to write it. So
like in many other fields, iteration over an idea and decision based on
empiric testing use to end in the best solution.

I think Express use to tend mostly to what Flex was, and I think not all in
flex was good, so I hope Jewel could get some things equal, but be better
in other fields. For example, I never liked Validation in Flex, I think is
too tied to the view controls, while Validation should validate date, so be
tied to models instead. As well loved the way this was implemented in
GraniteDS with Metadata, maybe this could be bring to Jewel in bead form,
we'll see when we come to that point.

Other case I'm finding now is for example how to deal with incoming
collections from a Server. In Basic List controls manage ICollectionView,
so we can do what we did in Flex storing data in ArrayLists or instead,
store in simple Array and then making a SingleSelectionArrayListModel,
since normaly that would be what people will use. So people can plug
directly their Array to list.dataprovider, and the control will knows how
to consume the Array. In this case Jewel can give a preselected bead
configuration that should be the use in mostly all cases, since the actual
SingleSelectionCollectionViewModel in Basic is not usable unless
application developers store make a conversion of the incoming Array to
ArrayList to feed the control.

So, in resume I think Jewel is right now in a middle step between Basic and
Express in terms of low-high configuration



2018-05-24 21:48 GMT+02:00 Alex Harui :

> Changing subject in case people have stopped reading.
>
> I think the question in the subject should be decided before we continue
> the package name discussion.  After thinking about it more, I really do
> think that Jewel should default to using Express beads (which might also
> mean that we need to create a few more Express beads).My reasoning is
> that we've already heard from users that a "high-configuration" component
> set like Basic was a pain to work with, which is why started creating a
> "low-configuration" set with Express.  It doesn't make sense to go back to
> "high-configuration" in Jewel.  Jewel should be the one component set 
folks
> use to get to know Royale and it should have both a good default
> look-and-feel (which Carlos has done) but also be "low-configuration".
>  Jewel has enough CSS and complex Views that we shouldn't be worried about
> trying to make Jewel lighter by not using Express beads.  Folks can
> optimize by swapping out beads as needed.
>
> Thoughts?
> -Alex
>
> On 5/22/18, 3:59 PM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira" 
> wrote:
>
> Hi Alex,
>
> I think we are saying the same in essence.
>
> I want to reuse beads. So lets take "TextPrompt" bead and have only
> one in
> all Royale (always that make the same of course), think that is in a
> library called "Foundation" that depends from Core but is not core.
> Seems
> "Foundation" is a name less confusing than Basic. All UI sets, link
> this
> foundation library and take what they want from it. Normally all UI
> sets
> will borrow "TextPrompt" bead. The same with the pieces in you 
DataGrid
>