Remote object is here
https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Network/src/main/royale/org/apache/royale/net
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Peter,
Many thanks for your clear explanation about the difference between
sub-components and beads. I hadn't understood that at all before.
headerColors - I'm only interested in HTML for this project so the
background-image solution is the simplest and most reliable. CSS gradients
are very
Hey Justin,
That's fantastic. Big thank-you from me.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Carlos,
Take a look at this
https://github.com/apache/royale-asjs/tree/develop/examples/royale/ModuleExample
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
I have a DateChooser that looks like this
Taking the attributes one by one
headerColours - Do I set the CSS background-color style on the
DateChooserHeader bead? Is there now any easy way to set a color gradient or
do I have to create and set a background-image?
showToday - Presumably this
Thanks Peter, that's very helpful.
I do think Basic is the thing to put the most effort into whilst maintaining
the PAYG approach. If this were to be deeply integrated into Moonshine then
this could show users what beads are available for each strand.
Whilst FlexJS users can use other IDEs and
Hi Alex,
In the children of Main (the Views), Declarations are not instantiated
before the rest of the page, so they are all undefined when required. (The
problem is fixed in Main itself - the items in its Declarations are all
defined correctly.)
In the meantime I have been clearing up all the
If you mean the setting in wwwroot/WEBINF/flex/services-config.xml --
Sadly it is already set to false -
false
But thanks for pointing out that there is a setting for this.
Doug
--
Sent from:
My RemoteObject returns a complex Object in part of which CF has specified
what looks to me like a simple array as an ArrayCollection in the returned
AMF Data. (Works ok in the old SWF project.)
Stepping through the code in the browser debugger, when the reader reaches
the n of ArrayCollection in
Hi Alex,
I have finally found out what is really wrong in my code causing all these
undefined errors.
In old Flex, setting visible and includeInLayout to false prevents the
object from appearing or having space allocated for it in the layout.
In JS you only need to set visible to false to
Hi Piotr,
I can't change it. This is something CF does inside its serializer before
sending the data. The original data are just fields in a database converted
to a query by CF and then serialized by its internal converter.
The writer of AMFBinaryData was obviously aware of the problem as the
Hi Carlos,
Sure, I can take a look at this. Leave it with me.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Sorry, you misunderstand me.
All I have done is allow AMFBinaryData to read ArrayCollection from CF
correctly.
I don't think there is any need for ArrayCollection in Royale. ArrayList is
perfectly adequate.
So all this is is a small change to AMFBinaryData.
Doug
--
Sent from:
Hi Carlos,
I now have ArrayCollection working properly. I suspect the same change will
also allow ObjectProxy to work properly as well, but at the moment I can't
test that.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Alex,
Just got back to this.
This is what I think is happening, please correct me if I'm wrong.
"-The top tag is instantiated.
-Attributes in the top tag are applied by MXMLDataInterpreter during
constructor time.
-fx:Script variables are initialized.
-top tag is added to
Hi Alex,
Okay thanks for that. Then since it should appear let me study my code for a
bit longer and compare it with ProductSupport in RoyaleStore example. I'll
come back if I can't find a solution.
Thanks,
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
In our Spark project we defined in fx:Declarations some DisplayObjects,
Effects, Images and Formatters that were not going to be displayed or used
immediately.
Some further settings were then applied after initComplete.
But in Royale JS only, these declarations are still not defined after
Running (in Moonshine 1.11) Build as JavaScript on RoyaleStore results in
this error:
SEVERE:
~/Moonshine/RoyaleStore/bin/js-debug/productsView/ProductCatalogPanelTitleBarView.js:18:
ERROR - required "productsView.CatalogTitleButtons" namespace not provided
yet
:
Hi Alex,
Yes that solved the problem.
So now I can see that the items in the Declarations of ProductSupport are
properly defined.
The only difference I can see between this and my project is that in
RoyaleStore this effect is not used until the user clicks a button whereas
mine have to be
Hi Alex,
I think I see what the problem is now. It's happening because of the way
I've replaced FlexGlobals.
I have done this by creating a static class with all the global variables,
but this means that instead of the AlertPopup pointing directly to a public
var set by the mxml in Main before
Hi Alex,
I was just about to ask how the fx: objects get added. I can't find it in
the Royale code.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Alex,
You are right. I need all the stuff in Main.xml : public vars, Declarations
etc. built before the Views start to build otherwise it can't work.
So I'll do as you say and try to devise a top-down bead.
If I have any success I'll let you know and of course I can submit it to the
project.
The old Flex project used a ViewStack (and Spark Navigator) for the Body
Views. I have changed this to use visible = false in the mxml and then
switch visible on and off whenever the user wants to change the View.
The call stack is creating the items in the order of the mxml in Main - so
it goes
Hi Alex,
The as class is a kind of pop-up Alert. In the early parts of the
actionscript code the first thing that happens is a RemoteObject gets called
and the as class pops up a "Getting data" message. This happens in
Main.init() and View2.init().
For some reason the first bit of actionScript
Hi Alex,
I am still trying to work out what is happening, but I'm almost certain the
problem is nothing to do with any problem with fx:Declarations.
Instead the problem occurs because the order in which JS builds things is
totally different than Flex Spark/MX.
I have not changed the basic
Hi Alex,
OK I've tried the new build and as far as I can see, Main now gets built
first.
But that doesn't solve the problem that for each mxml file being built, the
mxml and the script still build before the Declarations which causes
undefined errors in the file's script.
If there's a way to
I used the Apache Flex SDK Installer. Is there an update for this or is this
not working any more for Dev builds?
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
OK got it. Thanks to you both.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Okay I see what you mean. I'll find a way to do that.
Many thanks for your help.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
This is a JS only project. All of the mouse events available in
org.apache.flex.events.MouseEvent seem to work in the js:Button component,
so as ImageButton extends Button I assumed they would all be available in
this component as well. They seem to work in TextButton for example.
Doug
--
Hi Piotr,
I hope I can do that but I think I'm still some way from finishing. Although
I've been testing snippets as I've gone along, I'm pretty sure there will
still be lots of problems once it all has to work together. But I can't test
that till I can get the whole thing to compile.
But having
I'll certainly give that a try. Thanks very much Justin.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Yes found the bad line.
When correct variable added, build continues until 20 files are built.
Then I get a new internal error.
Internal error: java.lang.NullPointerException
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitFactoryMXMLRoyaleEmitter.java:2537)
The new Global Search is brilliant.
Fantastic stuff.
Big thank-you to everyone who helped to make this happen.
Moonshine just took a giant step forward !!
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
It would help so much if the compiler could output the line in the user's
code that it was working on at the time of or just prior to the error
occurring.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Piotr,
Problem for me is I don't know where to look and there are still about 80
files not built. So the problem is somewhere in that lot, I guess.
It's probably something trivial like the other two errors, but I need some
guidance on what sort of faulty code could cause a
Hi Piotr,
Yes I did and it all worked perfectly. Quick and simple update to new
version.
It was great!
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Oh yes of course, silly me. I've actually used this method to replace missing
parameters like 'data' in lots of other places in the app.
Many thanks for all your help.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Re Converting my project from Spark browser project to Royale JS only.
I have done some initial testing of my modules by making them into
individual Views, but can't get very far with this as I need to pass data
from one to the next. However they are built correctly and will run to some
extent.
Hi Alex,
Main.mxml contains initialView/View and a bunch of getters and setters.
Inside this View is a header group, a body group that contains the modules
and a footer group. Originally the modules were contained in a ViewStack,
but I've written something I hope will replace this, but I can't
Hi Alex,
I built it with Moonshine. I don't doubt that it works with Ant, but I don't
want to have to build my whole project with Ant.
Shall I report the problem to the Moonshine guys or is it something outside
Moonshine's control?
Doug
--
Sent from:
Hi Alex,
Before doing the first Build JavaScript, I ensured that there were no errors
or warnings from the Flex compiler. All the things the js compiler is
finding were passed by the Flex compiler.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Hi Alex,
Now that is fantastic!
The error it was failing on was in a .as file that was unchanged from the
old Flex project where it worked.
The problem is that when a Number expression of the form
myObj[myArr[i].name] is on the right-hand side of = or == it needs to be
explicitly cast to
Hi Alex,
Oh that will be a great help. The other error was something I was playing
around with and forgot to remove.
Removed the empty itemRenderer to solve the problem.
Doug
--
Sent from:
Maybe that's not right, I'm just downloading from
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/apache-royale-0.9.3-bin-js.zip
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
I think I'm using Nightly Build 0.9.3 #489.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Yes that solved the problem.
No errors now but a few more warnings which I will take a look at now.
Doug
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
47 matches
Mail list logo