Hi Chris, great to see you here :)
This the actual page on Royale-docs about that concepts: https://apache.github.io/royale-docs/welcome/features-and-concepts.html That links to this other one (more concrete): https://apache.github.io/royale-docs/welcome/features/payg.html Notice that docs are this days in continuous developement. You can find short examples like (ala flex examples blog) to get you started here: https://royale.apache.org/category/royale-examples/ In the Royale-docs I'm trying this days to document the list of beads that could be used per bead, for example Jewel Button docs is this: https://apache.github.io/royale-docs/component-sets/jewel/jewel-button.html HTH Carlos El sáb., 24 ago. 2019 a las 5:48, Chris Velevitch (< chris.velevi...@gmail.com>) escribió: > As a Flex developer exploring Royale, I've come across the terms "beads", > "strands" and "pay as you go" (PAYG), but I can't find any details, > documentation or tutorials on them. How do these map into existing Flex > concepts? As for PAYG, as far as I can tell, this is just another name for > the concept of "tree-shaking" [1] that other javascript frameworks > have/use. > > So, where can I find more information on these? > > [1] https://en.wikipedia.org/wiki/Tree_shaking > > On Thu, 22 Aug 2019 at 18:35, Carlos Rovira <carlosrov...@apache.org> > wrote: > > > Hi, > > > > while adding yesterday all "Where to go from here" sections in all blog > > examples, I found that Royale docs need a sub menu in the sidebar with > some > > royale important concepts. > > > > So after "*Get Started*" and before "*Component Sets*" I think we need > > something like a "*Fundamental Concepts*" (maybe this title is not the > best > > and others can get other that match better, I'll try to think in other > that > > fits better too. I try to refer to "Core Concepts" or a "Technology > > features" here). > > > > Is what a user should need to know just after finish "Get Started" guide > > and a hello world...know the tools avaialble in the royale arsenal, know > > that they have available things like binding, states, modules... > > > > In this submenu we need to cover the things that are still not covered in > > the docs and others that are covered but seems a bit lost in places > > difficult to find or that are not the best way where a user should find > it, > > or try to search for it. > > > > Options will be all core concepts: > > > > - *Fundamental Concepts * > > - *View States* (just created an empty page yesterday) > > - *Data Binding* (page exists too but is empty now and needs to be > > relocated) > > - *Modules* (This already exist, I think just need to be relocated) > > - *Externs* (this one was created yesterday by Andrew, again the > > problem is still not referenced in menu, and is under "user-interface", > but > > is more a "core concept" or a "technology feature"). > > - *Loading Data* or *Data Access*: This should have a sub menu with > > the main ways to access data : > > - *HTTPService* > > - *JSON* > > - *AMF* > > - ... > > - *Metadata* > > - *Styles and CSS* > > - ... I'm sure there are more to bring here... > > > > For me this is the main missing piece we need to address, and of course > > completing not only that menu but many other pages still to fill. > > > > Just one thing to end: In each page after main title the template expect > > the next line to be a short subtitle. For example, in the new "Externs" > > page y added a new line after title "Use external javascript libraries in > > ActiopnScript" So that line is shown in blue and with a bit more size to > > match the web style. That line should help a user to quickly understand > > what's that page about, since just "Externs" probably will not be of much > > help for a beginner. > > > > many pages are still without subtitle, but as we go over all docs, we > > should add this lines to help users reaching that pages. > > > > Thanks > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > -- > > > Chris > -- > Chris Velevitch > m: 0415 469 095 > -- Carlos Rovira http://about.me/carlosrovira
