You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@royale.apache.org by MARK HARTNETT <m_...@comcast.net> on 2024/05/01 17:21:29 UTC
Almost
Thanks Piotr - I will do that.
Success - its just the login screen with errors but it's up. Nine days from conversion to first screen is good. Working through the JS makes me appreciate the simplicity and organization of Flex.
However, the transcoder is amazing - so much work and co-ordination.
I'm looking forward to upgrading to some Royal components.
Thanks for your help.
> On 05/01/2024 10:14 AM EDT Piotr Zarzycki <pi...@gmail.com> wrote:
>
>
> I'm assuming you are using emulation component - I would move that to variables:
>
> private var services:Services;
>
> And instantiate it inside either creationComplete or initComplete - this is Royale event if available on component.
>
> śr., 1 maj 2024 o 00:15 MARK HARTNETT <m_hartnett@comcast.net mailto:m_hartnett@comcast.net> napisał(a):
>
> > I can kind of see what's going on - the Services in the app (http services) are declared
> > <fx:Declarations>
> > <ns9:Services id="services"/>
> > <ns9:BaseController id="appController"/>
> > </fx:Declarations>
> >
> > When the app initializes it instantiates the services. Each service instantiates and runs the format method that has a null xml parameter. I can delay this but the frontcontroller gets stuck.
> >
> > So I guess the easiest thing to do is to tweek the application based on js errors from the browser debugger.
> >
> > Thanks
> >
> >
> >
> > > On 04/30/2024 4:08 PM EDT MARK HARTNETT <m_hartnett@comcast.net mailto:m_hartnett@comcast.net> wrote:
> > >
> > >
> > > Hi All,
> > > Made some progress after debugging in the browser.
> > >
> > > The error that's killing the browser is
> > >
> > > AbstractOperation.as - public function set resultFormat(value:String):void.
> > >
> > > XML is the parm type. This method retrieves a null resourcebundle () and then throws an error.
> > > I've included images of my call stack and the point when the error is caught.
> > >
> > > Are these some of the bugs I need to fix or is this part of trans-coding,
> > > or maybe this is not the problem.
> > >
> > > Thanks
> > >
> > >
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
Re: Almost
Posted by Yishay Weiss <yi...@hotmail.com>.
Nice milestone, Mark. Good luck and keep us posted.
________________________________
From: MARK HARTNETT <m_...@comcast.net>
Sent: Wednesday, May 1, 2024 8:21 PM
To: users@royale.apache.org <us...@royale.apache.org>
Subject: Almost
Thanks Piotr - I will do that.
Success - its just the login screen with errors but it's up. Nine days from conversion to first screen is good. Working through the JS makes me appreciate the simplicity and organization of Flex.
However, the transcoder is amazing - so much work and co-ordination.
I'm looking forward to upgrading to some Royal components.
Thanks for your help.
On 05/01/2024 10:14 AM EDT Piotr Zarzycki <pi...@gmail.com> wrote:
I'm assuming you are using emulation component - I would move that to variables:
private var services:Services;
And instantiate it inside either creationComplete or initComplete - this is Royale event if available on component.
śr., 1 maj 2024 o 00:15 MARK HARTNETT <m_...@comcast.net>> napisał(a):
I can kind of see what's going on - the Services in the app (http services) are declared
<fx:Declarations>
<ns9:Services id="services"/>
<ns9:BaseController id="appController"/>
</fx:Declarations>
When the app initializes it instantiates the services. Each service instantiates and runs the format method that has a null xml parameter. I can delay this but the frontcontroller gets stuck.
So I guess the easiest thing to do is to tweek the application based on js errors from the browser debugger.
Thanks
On 04/30/2024 4:08 PM EDT MARK HARTNETT <m_...@comcast.net>> wrote:
Hi All,
Made some progress after debugging in the browser.
The error that's killing the browser is
AbstractOperation.as - public function set resultFormat(value:String):void.
XML is the parm type. This method retrieves a null resourcebundle () and then throws an error.
I've included images of my call stack and the point when the error is caught.
Are these some of the bugs I need to fix or is this part of trans-coding,
or maybe this is not the problem.
Thanks
--
Piotr Zarzycki
Re: Almost
Posted by Piotr Zarzycki <pi...@gmail.com>.
This is awesome news!!! Congrats Mark!
Piotr Zarzycki
On Wed, 1 May 2024 at 19:21, MARK HARTNETT <m_...@comcast.net> wrote:
> Thanks Piotr - I will do that.
> *Success* - its just the login screen with errors but it's up. Nine days
> from conversion to first screen is good. Working through the JS makes me
> appreciate the simplicity and organization of Flex.
> However, the transcoder is amazing - so much work and co-ordination.
>
> I'm looking forward to upgrading to some Royal components.
>
> Thanks for your help.
>
>
>
>
>
>
>
> On 05/01/2024 10:14 AM EDT Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
>
> I'm assuming you are using emulation component - I would move that to
> variables:
>
> private var services:Services;
>
> And instantiate it inside either creationComplete or initComplete - this
> is Royale event if available on component.
>
> śr., 1 maj 2024 o 00:15 MARK HARTNETT <m_...@comcast.net>
> napisał(a):
>
> I can kind of see what's going on - the Services in the app (http
> services) are declared
> <fx:Declarations>
> <ns9:Services id="services"/>
> <ns9:BaseController id="appController"/>
> </fx:Declarations>
>
> When the app initializes it instantiates the services. Each service
> instantiates and runs the format method that has a null xml parameter. I
> can delay this but the frontcontroller gets stuck.
>
> So I guess the easiest thing to do is to tweek the application based on js
> errors from the browser debugger.
>
> Thanks
>
>
>
> On 04/30/2024 4:08 PM EDT MARK HARTNETT <m_...@comcast.net> wrote:
>
>
> Hi All,
> Made some progress after debugging in the browser.
>
> The error that's killing the browser is
>
> AbstractOperation.as - public function set
> resultFormat(value:String):void.
>
> XML is the parm type. This method retrieves a null resourcebundle () and
> then throws an error.
> I've included images of my call stack and the point when the error is
> caught.
>
> Are these some of the bugs I need to fix or is this part of trans-coding,
> or maybe this is not the problem.
>
> Thanks
>
>
>
>
>
>
> --
>
> Piotr Zarzycki
>
>