Hi Peter, as Harbs said, is better to introduce all info we need and use the organization you think is better. Then as we start to set up all website and documentation we can make a "reorganization" work so we focus on getting the info as easy as possible for new comers.
Thanks 2017-11-08 23:33 GMT+01:00 Harbs <[email protected]>: > Changing wiki structure is pretty easy after the fact, so don’t worry > about that. Do whatever you think makes sense. > > Let’s just get as much content as we can in the wiki and we can reorganize > as it fills out. > > Harbs > > > On Nov 9, 2017, at 12:29 AM, Peter Ent <[email protected]> wrote: > > > > I seem to be having trouble getting mail sent out. Apologies if this > appears as a duplicate, but I didn't see this appear earlier. > > > > I just finished modifying the Panel component in Basic and deleted its > use of removeBead() in favor of transferring beads from the outer Panel > strand to the Panel's inner Container, contentArea, child. The removeBead > process has some issues so Alex and I thought it best to just avoid the > situation. > > > > I'd like to document this on the new Apache Royale Github Wiki. What I > thought I would do is create new section called "User Manual" and under > that a chapter for "Tips" and put this information about transferring beads > into there. > > > > What I do not want to do is make things more complex or more work for > us. Let me know if you think this structure is going to be a problem. > > > > Regards, > > peter > > > > -- Carlos Rovira http://about.me/carlosrovira
