Hi Matteo, This is a nice idea!
I just created a community there: https://www.reddit.com/r/nuttx/ Please share it with your friends and people that could be interested in embedded systems. BR, Alan On Wed, Jul 10, 2024 at 5:47 PM Matteo Golin <matteo.go...@gmail.com> wrote: > Maybe we could consider creating a Reddit community? It's a nice forum for > discussion and very easily searchable on Google. That would help in > accumulating solutions to common difficulties people encounter. > > On Tue, Jul 9, 2024, 4:20 PM Alan C. Assis <acas...@gmail.com> wrote: > > > I used a "tutorial" / documentation last month to include a PNG image in > > the LVGL and the code was mainly done. > > > > The only issue I faced was that the converted PNG to C file page > generated > > a code with LVGL v8 information about RGB format. > > > > After fixing that everything worked like a charm. > > > > BR, > > > > Alan > > > > On Tue, Jul 9, 2024 at 5:05 PM Gábor Kiss-Vámosi <kisvega...@gmail.com> > > wrote: > > > > > Actually at LVGL I don't think that we have too many tutorials. What we > > > have are > > > - ready to use projects for many IDEs and several dev boards to easily > > get > > > started > > > - many simple, short and targeted examples that can be tested by > calling > > > functions like lv_example_chart_7() > > > - some complex demos to have good looking UIs too > > > - documentation, but it should be used only for specific, in depth > > > knowledge about a module or widget. In most of the cases the API docs > in > > > the header files are enough too. > > > > > > If we need to create a tutorial it means that something is so > complicated > > > that we need to explain it in great detail. I know it's not always > > > possible, but in an ideal world we could have only demo videos with > just > > a > > > little bit of info about how to do it. Based on that hint people should > > see > > > themselves how it was done. > > > > > > It's somewhat similar with the docs too. The details should be for > power > > > users, but I'd like to get started on an okay level by reading one-two > > > paragraphs. 🙂 > > > > > > Gabor > > > > > > On Tue, Jul 9, 2024, 21:36 Alan C. Assis <acas...@gmail.com> wrote: > > > > > > > Thank you very much Gábor, I think having some nice tutorials like > you > > > have > > > > for LVGL will help many people! > > > > > > > > Something that people always asked me to do in the NuttX Channel > videos > > > was > > > > create some real file application examples. > > > > > > > > I was more focused on showing NuttX features, but after getting the > > > > peripheral working people got lost. > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On Tue, Jul 9, 2024 at 3:21 PM Gábor Kiss-Vámosi < > kisvega...@gmail.com > > > > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > There are two more points that I'd add: > > > > > 1. Easy to get started: have example projects that can be set up by > > > > reading > > > > > a few lines from the README. > > > > > 2. Easy to move forward: by reading a few extra sentences the user > > > should > > > > > know how to customize the project by adding new files, trying new > > > > features, > > > > > changing config, or changing target. It also means they need to > > > > understand > > > > > what is what. (Tools, project structure, etc. The less magic is > > better) > > > > > > > > > > These are just my cents about what I'd love as a developer. Besides > > > that > > > > I > > > > > feel like these worked at LVGL. Obviously, NuttX is way more > complex > > > than > > > > > LVGL, however trying to make things simpler and more intuitive is > > > always > > > > a > > > > > plus. > > > > > > > > > > > > > > > I'm not an experienced NuttX user, so I might be a good example new > > > user. > > > > > If it helps I can try setting up a project for unix and collect > > where I > > > > > felt puzzled about what to do next. > > > > > > > > > > > > > > > Regards, > > > > > > > > > > Gabor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jul 9, 2024, 19:55 Alan C. Assis <acas...@gmail.com> > wrote: > > > > > > > > > > > Another important thing the AI didn't say: YouTube!!! > > > > > > > > > > > > YouTube is another great way to let more people discover about > > NuttX. > > > > > > > > > > > > There is a nice YouTube channel called Robots5 using NuttX and > > > > > PySimCoder, > > > > > > please subscribe and help to share it: > > > > > > > > > > > > https://www.youtube.com/watch?v=xFeQVtbyKyQ > > > > > > > > > > > > BR, > > > > > > > > > > > > Alan > > > > > > > > > > > > https://www.youtube.com/watch?v=xFeQVtbyKyQ > > > > > > > > > > > > On Tue, Jul 9, 2024 at 2:28 PM Alan C. Assis <acas...@gmail.com> > > > > wrote: > > > > > > > > > > > > > Hi Everyone, > > > > > > > > > > > > > > Let's get help from AI to improve the situation: > > > > > > > > > > > > > > To increase visibility and adoption of NuttX RTOS, here are > some > > > > > planned > > > > > > > strategies that can be renewed: > > > > > > > 1. Content Creation and Promotion > > > > > > > Blog posts and technical articles > > > > > > > > > > > > > > Step 1: Create an official NuttX blog with detailed technical > > > > articles > > > > > > on > > > > > > > use cases, tutorials, comparisons with other RTOS, and > > explanations > > > > of > > > > > > > unique features. > > > > > > > Step 2: Publish articles on recognized technology platforms > and > > > > > > > e-magazines (e.g. IEEE Spectrum, Hackster.io). > > > > > > > > > > > > > > Webinars and Workshops > > > > > > > > > > > > > > Step 1: Organize webinars and online workshops to demonstrate > > the > > > > > > > functionality and benefits of NuttX. > > > > > > > Step 2: Attend technology conferences and events, presenting > > talks > > > > and > > > > > > > tutorials. > > > > > > > > > > > > > > 2. Community Engagement > > > > > > > Forums and Social Media > > > > > > > > > > > > > > Step 1: Participate in discussion forums like Stack Overflow, > > > > Reddit, > > > > > > and > > > > > > > LinkedIn groups, answering questions and helping other > > developers. > > > > > > > Step 2: Create and update official NuttX profiles on social > > media > > > > > > > (Twitter, LinkedIn, Facebook) to share updates and relevant > > > content. > > > > > > > > > > > > > > Hackathons and Competitions > > > > > > > > > > > > > > Step 1: Organize hackathons and convention competitions > > > encouraging > > > > > the > > > > > > > use of NuttX. > > > > > > > Step 2: Offer awards and recognition for the best projects and > > > > > solutions > > > > > > > developed with NuttX. > > > > > > > > > > > > > > 3. Partnerships and Collaborations > > > > > > > Universities and Research Institutions > > > > > > > > > > > > > > Step 1: Establish partnerships with universities and research > > > > > institutes > > > > > > > to include NuttX in academic curricula and research projects. > > > > > > > Step 2: Offer scholarships and support to students and > > researchers > > > > > using > > > > > > > NuttX. > > > > > > > > > > > > > > Companies and Startups > > > > > > > > > > > > > > Step 1: Collaborate with companies and startups to integrate > > NuttX > > > > > into > > > > > > > their products and solutions. > > > > > > > Step 2: Provide technical support and resources to help with > the > > > > > > adoption > > > > > > > of NuttX in commercial environments. > > > > > > > > > > > > > > 4. Continuous Improvement and Support > > > > > > > Documentation and Educational Resources > > > > > > > > > > > > > > Step 1: Continuously improve the official NuttX documentation, > > > > > including > > > > > > > user guides, tutorials, and FAQs. > > > > > > > Step 2: Create and maintain a repository of examples and > > reference > > > > > > > projects to make learning and adopting NuttX easier. > > > > > > > > > > > > > > Technical Support and Community > > > > > > > > > > > > > > Step 1: Offer technical support through dedicated channels > such > > as > > > > > > > official forums, discussion groups and ticket systems. > > > > > > > Step 2: Encouraging community participation in development and > > > > problem > > > > > > > solving, creating a collaborative and welcoming environment. > > > > > > > > > > > > > > 5. Comparisons and Benchmarks > > > > > > > Case Studies and Technical Comparisons > > > > > > > > > > > > > > Step 1: Conduct case studies that demonstrate the superiority > of > > > > NuttX > > > > > > in > > > > > > > terms of performance, security, and usability. > > > > > > > Step 2: Detailed public comparative benchmarks between NuttX > and > > > > other > > > > > > > RTOS, such as FreeRTOS, Zephyr, RT-Thread, highlighting NuttX's > > > > > > strengths. > > > > > > > > > > > > > > Certifications and Audits > > > > > > > > > > > > > > Step 1: Obtain relevant certifications for NuttX in critical > > areas > > > > > such > > > > > > > as security and reliability. > > > > > > > Step 2: Conduct independent security audits and publish the > > > results > > > > to > > > > > > > increase trust in the platform. > > > > > > > > > > > > > > 6. Incentives and Loyalty Programs > > > > > > > Certification Programs > > > > > > > > > > > > > > Step 1: Develop certification programs for developers and > > > engineers > > > > > > using > > > > > > > NuttX. > > > > > > > Step 2: Offer training and study materials to prepare > > > professionals > > > > > for > > > > > > > certifications. > > > > > > > > > > > > > > Loyalty Programs > > > > > > > > > > > > > > Step 1: Create loyalty programs to reward NuttX's most active > > and > > > > > > > contributing users. > > > > > > > Step 2: Offer exclusive benefits, such as early access to new > > > > > versions, > > > > > > > priority support, and invitations to special events. > > > > > > > > > > > > > > Conclusion > > > > > > > > > > > > > > These combined strategies can significantly increase the > > visibility > > > > and > > > > > > > adoption of NuttX RTOS, highlighting its advantages and > building > > a > > > > > > strong, > > > > > > > engaged community. > > > > > > > > > > > > > > BR, > > > > > > > > > > > > > > Alan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
