Well, this took a bit longer than I expected, but I did finally get what I
think is the foundation of a FlexJS ASDoc app up and running (well,
crawling...). More about this in another thread, but you might be able to
work from the code to get the aggregations you want for your snippets.
HTH,
-Ale
Hi Christian,
The JSON files are intended for a future ASDoc app written in FlexJS. I
expect small JSON files to perform better than one big file of JSON or
XML. It allows for lazy loading of data. Also, the compiler is oriented
towards producing lots of small files because each class is being
Hi Alex,
Thanks for the updated file. After looking over the contents I was
surprised how many classes are involved and how easy it is to get
lost in all that. In order to get a better overview of all this I would
suggest to put all the different JSON files into a single
XML file that can then be
Thanks for looking. I think I've fixed these issues and updated the zip.
There's probably more, so maybe after I get caught up on compiler bugs
I'll write the basis of the AIR app that will display ASDoc which will
then read all of these files and find more problems.
-Alex
On 12/5/16, 2:11 PM, "
One last one:
ToolTipBead.json has TWO trailing commas near the end of the file.
On Dec 6, 2016, at 12:10 AM, Harbs wrote:
> Some more:
>
> CurrencyFormatter.json has the following:
>
> "params": [{ name: "value", type: "Object"}
>
> name and type need to be surrounded by quotes.
>
Some more:
CurrencyFormatter.json has the following:
"params": [{ name: "value", type: "Object"}
name and type need to be surrounded by quotes.
I’m done for the night… ;-)
On Dec 6, 2016, at 12:07 AM, Harbs wrote:
> Accordion.json looks like it has two errors as well:
> 1. The lead
Accordion.json looks like it has two errors as well:
1. The leading comma here:
"members": [
,
2. The trailing comma here:
"namespace": "public”,
On Dec 6, 2016, at 12:04 AM, Harbs wrote:
> That looks good.
>
> I randomly opened some other files and ComboBox has the following error:
>
> par
That looks good.
I randomly opened some other files and ComboBox has the following error:
parse error: invalid object key (must be a string)
he.flex.events.Event", }] }
(right here) --^
The problem looks like a trailing comma near the end of the file.
Thanks for checking. I think I have it as valid JSON now and updated the
zip.
-Alex
On 12/5/16, 12:19 PM, "Harbs" wrote:
>It looks like there’s an error in the JSON. I opened CheckBox.json and I
>got the following error:
>
>parse error: after key and value, inside map, I expect ',' or '}'
>
It looks like there’s an error in the JSON. I opened CheckBox.json and I got
the following error:
parse error: after key and value, inside map, I expect ',' or '}'
"values": ["3.0"]} ] "return": "", "params"
(right here) ———^
It looks like there’s
I just pushed a new set of json files. The accessors should now have
"return" fields.
Looks like default values are supposed to come from @default tags in the
ASDoc, which we haven't written yet. I added one to CheckBox just to see
if it would work and it does appear in the output. We would need
On 12/2/16, 5:07 PM, "Christian Gotschim" wrote:
>
>I guess for something where I can read the most common properties
>and styles from. Let’s take the org.apache.flex.html.Button.json: it lists
>only the constructor and the click event. But I still don’t know how
>to (or if I can) set x and y,
I guess for something where I can read the most common properties
and styles from. Let’s take the org.apache.flex.html.Button.json: it lists
only the constructor and the click event. But I still don’t know how
to (or if I can) set x and y, or if it got left-right-top-bottom, or
width/height to na
On 12/2/16, 2:14 PM, "Christian Gotschim" wrote:
>OK, got the zip and looking at it. At first glance not really what I was
>hoping for, but I’ll see.
What were you hoping for?
-Alex
OK, got the zip and looking at it. At first glance not really what I was
hoping for, but I’ll see.
- Christian
> On Dec 2, 2016, at 6:53 PM, Alex Harui wrote:
>
>
>
> On 12/1/16, 10:41 PM, "Christian Gotschim" wrote:
>
>>
>>> If you know Java, you could write a custom ASDoc emitter. I'
On 12/1/16, 10:41 PM, "Christian Gotschim" wrote:
>
>> If you know Java, you could write a custom ASDoc emitter. I've written
>> one that outputs ASDoc information in JSON format. Or you could write a
>> Flex or FlexJS app to read the JSON files and generate the MXML you
>>want.
>
>I don’t kn
This just goes to show again that we need a dedicated page for each of the
Basic components with simple examples of the component's most common tasks.
Set the text on a button, and listen for some kind of click/tap event.
Populate a list's data provider, listen for a selection change event, and
cha
Hi Alex,
> Thanks for offering to help. We could use all the help we can get.
>
> I don't know what your areas of expertise are and how much time you have,
> and I don't quite know how you want to organize the list, but you might be
> able to write code to build out the list of components.
My e
Hi Christian,
Thanks for offering to help. We could use all the help we can get.
I don't know what your areas of expertise are and how much time you have,
and I don't quite know how you want to organize the list, but you might be
able to write code to build out the list of components.
If you kn
I've been thinking about the complaints I’ve read on this list about the
missing documentation for FlexJS and I’d like to do something to help out. I’ve
used AS3/Flex for many years, and I’m now trying to get a hang of FlexJS.
So I thought it might be a good starting point for FlexJS newbies (li
20 matches
Mail list logo
