Let's use the existing wiki page [1] as a sort of status-update page, if that works for you.
1. https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale On Sun, Dec 5, 2021 at 9:23 AM Harbs <harbs.li...@gmail.com> wrote: > OK. I’ll hopefully start on this sometime this week. > > Once I make some progress I’ll probably try and coordinate with you on how > to best document it. > > If anyone has further thoughts, please let me know. > > Harbs > > > On Dec 5, 2021, at 2:57 PM, Andrew Wetmore <cottag...@gmail.com> wrote: > > > > Excellent. We will need both maintenance and user-facing documentation, > but > > once we have this in place Royale will be much stronger and more suitable > > to many more uses. > > > > On Sun, Dec 5, 2021 at 8:54 AM Harbs <harbs.li...@gmail.com <mailto: > harbs.li...@gmail.com>> wrote: > > > >> Great. > >> > >> After spending some time looking at existing implementations, I think > I’m > >> going to port the parsing code from > >> https://github.com/jonschlinkert/remarkable < > https://github.com/jonschlinkert/remarkable> < > >> https://github.com/jonschlinkert/remarkable < > https://github.com/jonschlinkert/remarkable>> > >> > >> It’s well organized and the performance is very good. > >> > >> > >> > https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block > < > https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block > > > >> < > >> > https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block > < > https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block > > > >>> > >> > >> Only Snarkdown is faster, but that implementation seems very bare-bones > >> and outputs directly to html. > >> > >> Here’s the approach that I’m considering: > >> > >> 1. Markdown gets parsed into nodes. > >> 2. We have a mapper class which maps nodes to corresponding > IParentUIBase > >> components. This map will be customizable. > >> 3. We walk down the node tree and create and populate the components. > >> 4. I’d like to hook this into a Router for navigation. > >> > >> I’m probably going to do this with my daughter who is in school to serve > >> as a practice lesson in generating and using document trees. B-) > >> > >>> On Dec 5, 2021, at 1:17 AM, Andrew Wetmore <cottag...@gmail.com> > wrote: > >>> > >>> I would be happy to help with this. I started to build such a parser > >> myself > >>> a few months back, but got swamped with work. It would be an excellent > >>> demonstration of how adaptable Royale is. > >>> > >>> On Sat, Dec 4, 2021 at 7:07 PM Harbs <harbs.li...@gmail.com> wrote: > >>> > >>>> I’ve been thinking about the website and I had an idea. > >>>> > >>>> The problems we have with the website currently: > >>>> > >>>> 1. You need to loging to Wordpress to make changes. > >>>> 2. It relies on external resources. > >>>> 3. There’s no way to make pull requests to improve the website. > >>>> 4. It doesn’t showcase Royale. If we could "eat our own dogfood”, that > >>>> would be great. > >>>> > >>>> Royale *can* be used to generate a website, but it’s not really great > >> for > >>>> writing or updating content. > >>>> > >>>> The best way (IMO) to write content is using markdown. We can create a > >>>> Royale app which loads markdown files to populate content. We can > route > >>>> based on the URL to specific markdown files to determine which content > >> to > >>>> load. > >>>> > >>>> The content can be formatted by mapping markdown nodes to Royale > >>>> components. You could have multiple mappings in a single document so > >>>> multiple markdown files can be used to populate content in different > >> areas > >>>> (i.e. sidebar, footer, main content, etc.) > >>>> > >>>> I’m willing to volunteer to write the parser and mapper if others like > >> the > >>>> idea and are willing to participate in other aspects. There’s a couple > >> of > >>>> appropriately licensed projects that I can borrow code from for the > >> parsing > >>>> logic. https://github.com/markdown-it/markdown-it > >>>> https://github.com/showdownjs/showdown > >>>> > >>>> Thoughts? > >>>> > >>>>> On Apr 18, 2021, at 2:52 PM, Andrew Wetmore <cottag...@gmail.com> > >> wrote: > >>>>> > >>>>> Hi, all: > >>>>> > >>>>> I have created a wiki page [1] where we can scope out developing the > >>>> Royale > >>>>> website as built using Royale. I have suggested some requirements, > some > >>>>> "nice to have" things and some things that are not required; however > >>>> these > >>>>> are just my ideas. Input from others until we reach consensus would > be > >>>>> useful. > >>>>> > >>>>> Here is one specific point: there are a couple of abandoned efforts > to > >>>>> build the Royale site using Royale. Do we use these repositories, or > >>>> create > >>>>> a new one for this effort? > >>>>> > >>>>> a > >>>>> > >>>>> 1. > >>>>> > >>>> > >> > https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale > >>>>> > >>>>> On Fri, Apr 16, 2021 at 12:29 PM Alina Kazi <alinakazi1...@gmail.com > > > >>>> wrote: > >>>>> > >>>>>> Congrats Andrew. > >>>>>> > >>>>>> Yes we can add viewstates (includeIn), phone/tablet/desktop > Numerator > >>>>>> denominator to adjust the view on different devices, common header > and > >>>>>> footer and much more. > >>>>>> We'll be waiting for the wiki page tomorrow to get started. > >>>>>> > >>>>>> Thanks, > >>>>>> Alina Kazi > >>>>>> > >>>>>> On Fri, 16 Apr 2021, 7:29 PM Piotr Zarzycki, < > >> piotrzarzyck...@gmail.com > >>>>> > >>>>>> wrote: > >>>>>> > >>>>>>> Congrats Andrew! > >>>>>>> > >>>>>>> pt., 16 kwi 2021 o 13:31 Andrew Wetmore <cottag...@gmail.com> > >>>>>> napisał(a): > >>>>>>> > >>>>>>>> Today my wife and I have appointments, a long drive from home, to > >> get > >>>>>> our > >>>>>>>> first COVID-19 injections. This will probably use up most of the > >> day, > >>>>>>>> leaving aside possible side-effects, so I likely will not have the > >>>> wiki > >>>>>>>> page about the web site ready to receive ideas and concerns until > >>>>>>> tomorrow > >>>>>>>> at the earliest. > >>>>>>>> > >>>>>>>> a > >>>>>>>> > >>>>>>>> On Thu, Apr 15, 2021 at 8:33 PM Maria Jose Esteve < > >> mjest...@iest.com> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> What dizziness! jajajaja > >>>>>>>>> > >>>>>>>>> Hiedra > >>>>>>>>> > >>>>>>>>> -----Mensaje original----- > >>>>>>>>> De: Andrew Wetmore <cottag...@gmail.com> > >>>>>>>>> Enviado el: viernes, 16 de abril de 2021 1:29 > >>>>>>>>> Para: Apache Royale Development <dev@royale.apache.org> > >>>>>>>>> Asunto: Re: Use Royale to build the Royale website? > >>>>>>>>> > >>>>>>>>> This is great. > >>>>>>>>> > >>>>>>>>> To start, I think I will create a wiki page so we can capture > what > >> we > >>>>>>>> must > >>>>>>>>> have and what we would like to have in the website. For me, our > >>>>>> website > >>>>>>>>> must communicate useful and engaging information about our > project > >>>>>> and > >>>>>>>> what > >>>>>>>>> one can do with Royale. I would also like to include some > features > >> to > >>>>>>>>> demonstrate a little bit of what Royale can do--maybe viewstates > to > >>>>>>>> manage > >>>>>>>>> what displays when, localization (at least some of the site), > >>>>>>> responsive > >>>>>>>> so > >>>>>>>>> it appears well on laptops and mobile devices, use of CSS, and > >> other > >>>>>>>>> stuff...and then we can use the website itself as a demonstration > >> of > >>>>>>>>> Royale's versatility. > >>>>>>>>> > >>>>>>>>> The Infra guidelines say a project's site should not be dynamic, > in > >>>>>> the > >>>>>>>>> sense of using HTTP calls to get data that it then displays: the > >> site > >>>>>>>>> should be "flat". But we may find that Royale code compiled to > >>>>>>>> JavaScript > >>>>>>>>> can do lots of interestng things wiithout breaking the Infra > rules. > >>>>>>>>> > >>>>>>>>> I will set up the wiki page tomorrow and let you all know that it > >> is > >>>>>>>>> available for adding ideas. > >>>>>>>>> > >>>>>>>>> Andrew > >>>>>>>>> > >>>>>>>>> On Thu, Apr 15, 2021 at 5:42 PM Alina Kazi < > >> alinakazi1...@gmail.com> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> Hi, > >>>>>>>>>> Great Maria and really its very good to show it in ApacheCon > 2021. > >>>>>>>>>> > >>>>>>>>>> Great Idea Andrew, I would also love to contribute in any way I > >>>>>> can. > >>>>>>>>>> Also, If you have some design in mind. Share with us. > >>>>>>>>>> Create a source repository,so we can start with jewel basic flat > >>>>>>> theme > >>>>>>>>>> or any other option that community suggests. We start migrating > >>>>>>>>>> wordpress website step by step. Until we have virtual machine or > >>>>>>> other > >>>>>>>>> stuff ready. > >>>>>>>>>> > >>>>>>>>>> Alina Kazi > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Thu, 15 Apr 2021, 10:03 PM Maria Jose Esteve, < > >>>>>> mjest...@iest.com> > >>>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> Hi guys, > >>>>>>>>>>> > >>>>>>>>>>> Andrew, I can help, I think the community has to make an effort > >>>>>> if > >>>>>>>>>>> we > >>>>>>>>>> want > >>>>>>>>>>> to get to ApacheCon 2021 😝 > >>>>>>>>>>> > >>>>>>>>>>> Have you thought about a redesign of the website or a > >>>>>>> "translation"? > >>>>>>>>>>> > >>>>>>>>>>> How could I contribute? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Hiedra > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -----Mensaje original----- > >>>>>>>>>>> De: Andrew Wetmore <cottag...@gmail.com> Enviado el: jueves, > 15 > >>>>>> de > >>>>>>>>>>> abril de 2021 1:51 > >>>>>>>>>>> Para: Apache Royale Development <dev@royale.apache.org> > >>>>>>>>>>> Asunto: Use Royale to build the Royale website? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Hi: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> At the moment the Royale website depends on a private server > >>>>>>> running > >>>>>>>>>>> WordPress. I wonder if it is time to build and deploy it using > >>>>>>>>>>> Royale itself. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> We don't need the great strengths of Royale--dynamic display, > >>>>>>> subtle > >>>>>>>>>>> data-processing, and so on--to support the site. It is (as all > >>>>>>>>>>> projects sites are intended to be) a flat, relatively static > >>>>>>>>>>> website. That should mean that running our own website with the > >>>>>> aid > >>>>>>>>>>> of our own tool should be far from impossible. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> What is required? If I understand correctly, we would need > Infra > >>>>>> to > >>>>>>>>>>> provide a virtual machine on which we could install and run a > >>>>>>> stable > >>>>>>>>>>> instance of Royale, and a repository of the site's source code > in > >>>>>>>>>>> MXML > >>>>>>>>>> and > >>>>>>>>>>> AS files, just like a real Royale application.. Each time we > >>>>>>> updated > >>>>>>>>>>> a > >>>>>>>>>> page > >>>>>>>>>>> or a file in the website repository, Infra's automated tools > >>>>>> would > >>>>>>>>>>> set > >>>>>>>>>> off > >>>>>>>>>>> a build and deployment of the updated site. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Some time ago a proof-of-concept was partly built to do this > very > >>>>>>>>>>> thing, so we have some resources to start from. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Benefits: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -- Since it is a simple website, it should probably be an > >>>>>> exercise > >>>>>>>>>>> contributors and committers at many skill levels could help > work > >>>>>>> on. > >>>>>>>>>>> > >>>>>>>>>>> -- It would give us a "brag" to point to. > >>>>>>>>>>> > >>>>>>>>>>> -- We would move over to open-source resources, rather than > those > >>>>>>> of > >>>>>>>>>>> WordPress.. > >>>>>>>>>>> > >>>>>>>>>>> -- Infra has an efficient and stable CI process in place that > can > >>>>>>>>>>> work with Royale's command-line to trigger builds and > deployment. > >>>>>>>>>>> > >>>>>>>>>>> -- Other???? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Costs: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -- Time to migrate the existing site into Royale assets. > >>>>>>>>>>> > >>>>>>>>>>> -- Other????? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> What do you all think of such a proposal? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> a > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -- > >>>>>>>>>>> > >>>>>>>>>>> Andrew Wetmore > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> Andrew Wetmore > >>>>>>>>> > >>>>>>>>> http://cottage14.blogspot.com/ > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Andrew Wetmore > >>>>>>>> > >>>>>>>> http://cottage14.blogspot.com/ > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> > >>>>>>> Piotr Zarzycki > >>>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Andrew Wetmore > >>>>> > >>>>> http://cottage14.blogspot.com/ > >>>> > >>>> > >>> > >>> -- > >>> Andrew Wetmore > >>> > >>> Editor, Moose House Publications <https://moosehousepress.com/> > >>> Editor-Writer, The Apache Software Foundation <https://apache.org/> > >> > >> > > > > -- > > Andrew Wetmore > > > > Editor, Moose House Publications <https://moosehousepress.com/ < > https://moosehousepress.com/>> > > Editor-Writer, The Apache Software Foundation <https://apache.org/ < > https://apache.org/>> > > -- Andrew Wetmore Editor, Moose House Publications <https://moosehousepress.com/> Editor-Writer, The Apache Software Foundation <https://apache.org/>
