I've had many problems in the past on Firefox (latest), where it just
never finishes loading (just says "Loading..." in big letters under the
class name, for example).
Seems to happen on some pages but not others. It's so bad that I
basically don't look at the API docs anymore.
On 4/20/2021 11
Good stuff. Should I start a Jira ticket and dump all this information into
it, so we don't lose our minds trying to find it again?
On Tue, Apr 20, 2021 at 4:40 PM GAbe Barbosa wrote:
> Apologies for posting images. Console dump. url:
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDa
drew Wetmore
Date: Tuesday, April 20, 2021 at 11:08 AM
To: Apache Royale Development , Alex Harui
Subject: Re: Getting to 1.0
I have not done any work on the ASDocs section. We would be glad of any help we
can get to make it more useful. Does it need a color guide at the top to
indicate what blu
This is very helpful.
a
On Tue, Apr 20, 2021 at 4:40 PM GAbe Barbosa wrote:
> Apologies for posting images. Console dump. url:
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
>
> Mixed Content: The page at 'https://royale.apache.org/asdoc/' was
Apologies for posting images. Console dump. url:
https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded
over HTTPS, but requested an insecure stylesheet '
http://maxcdn.bootstrapcdn.com/
>> > > >
>> > > > > On Apr 19, 2021, at 11:23 AM, Yishay Weiss <
>> yishayj...@hotmail.com>
>> > > > wrote:
>> > > > >
>> > > > > There are already some Royale apps in production so I think we are
>
some Royale apps in production so I think we are
> > > ready
> > > > for 1.0 in terms of code. Whether to call it 1.0 is probably a
> > marketing
> > > > decision at this stage. There will be announcements and (hopefully)
> > > > feedback to take care
e
> > ready
> > > for 1.0 in terms of code. Whether to call it 1.0 is probably a
> marketing
> > > decision at this stage. There will be announcements and (hopefully)
> > > feedback to take care of.
> > > >
> > > > At least that’s how I think
lly)
> > feedback to take care of.
> > >
> > > At least that’s how I think of it.
> > >
> > >
> > >
> > > From: Andrew Wetmore<mailto:cottag...@gmail.com>
> > > Sent: Sunday, April 18, 2021 3:42 PM
> > > To: Apache Royale Develo
ay, April 18, 2021 3:42 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Getting to 1.0
> >
> > I know it is not in the nature of Apache projects to have timelines,
> since
> > each volunteer chooses to work on the task that attracts
; From: Andrew Wetmore<mailto:cottag...@gmail.com>
> Sent: Sunday, April 18, 2021 3:42 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Getting to 1.0
>
> I know it is not in the nature of Apache projects to have timelines, since
> each volu
releasing that.
From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, April 19, 2021 11:23 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: Getting to 1.0
There are already some Royale apps in production so I think we are ready for
1.0 in terms of code
Wetmore<mailto:cottag...@gmail.com>
Sent: Sunday, April 18, 2021 3:42 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Getting to 1.0
I know it is not in the nature of Apache projects to have timelines, since
each volunteer chooses to work on the task that attracts t
I know it is not in the nature of Apache projects to have timelines, since
each volunteer chooses to work on the task that attracts them. However...do
we know what we need to do to get from now (almost 0.9.8) to a 1.0 release?
What critical elements are lacking?
For me, there are big gaps in docum
14 matches
Mail list logo
