What’s new in OneBB forum script?
Creating the framework allowed me to create ready-made modules for managing categories, boards, users and information pages in a short time. Next elements will be more difficult to implement.
I managed to completely solve the problem of loading assets and the default forum directory. All I had to do was to pass that information via TWIG directly to the application template. This approach also allows me to place the appropriate code to configure the modules of the skin itself. Just like in Boards – OneBB Forum will have the ability to dynamically assign modules to particular page types. This gives great possibilities to configure the appearance.
Further development requires creating an endpoint for managing the application configuration. I haven’t decided yet if variables will be available in .env file or in other way. It is important to be able to easily separate individual configuration elements into separate controllers. This solution worked well with the previous forum script. This topic is most urgent when it comes to completing the current stage of the OneBB forum script.
I still haven’t found a good way to solve plugins. I would like them to be loaded dynamically. However I do not know whether they will be JS code that will be added to the VUE or endpoint API from which data will be downloaded and inserted into snippets in the template. Each of these solutions has its pros and cons. The JS version seems to be more optimal and gives more possibilities to define elements and their appearance. On the other hand, working on the server side is more secure and gives the possibility to interfere with the database. It will probably be necessary to create some combination of these elements. Maybe I will create two plugin systems that will be able to communicate with each other.
All in all, the last few days have been very good in terms of OneBB forum script development. Further development unfortunately requires even more work, but I feel that I am 100% ready for it!