- Joined
- Sep 2, 2011
- Messages
- 2,171
- Reaction score
- 916
Yes, finally Chocolatey it's turning out to the BETA version. (basically two months of alpha!)
Finally, we're going to the BETA version that will include.:
* Fully Class Documentation
* Fully Changelog
* Full In-Code Documentation
* Variables/Code Normalization
* Installer
* +Give Suggestion
* Plugin System
* Analytics System
Also, I'm thinking of separating the API from the HabboWEB part into two separated modules.
Basically, the Frontend thing would be on Laravel and the API thing in a microservice provider (aka Lumen). (But IDK if it's good for dummies, newbies or if it's good doing it..)
-----
Anyways, now it's the time for the PLUGIN system + Installer.
I want a suggestion of how you want to the Plugin System would be.
You can suggest PHP Libraries that are Plugin Engines, features for the Plugin System, Technical tips, etc.
Remember.: Composer Plugins:
As an example, It's good the plugin system being like each plugin it's a composer package?
Or in a folder called Plugins?
Do the plugins can add or edit the API Paths? (Like custom paths + ability to overwrite other paths?)
Is it good the plugin system with the ability to create/adding more views? pages? Habbo-web pages?
----
It's good I make a script that changes the Angular Content to something that includes your view? How would custom pages be? Like Staff Page? Something easy?
It's good I create a system that allows Angular automatically route to dynamic pages?
Give'me your suggestions!!
------
For the Installer, what yours want to the Installer be? Something that allows configuring MySQL? Chocolatey Config File things, like HotelName? TELL ME!
Thanks!!!
Finally, we're going to the BETA version that will include.:
* Fully Class Documentation
* Fully Changelog
* Full In-Code Documentation
* Variables/Code Normalization
* Installer
* +Give Suggestion
* Plugin System
* Analytics System
Also, I'm thinking of separating the API from the HabboWEB part into two separated modules.
Basically, the Frontend thing would be on Laravel and the API thing in a microservice provider (aka Lumen). (But IDK if it's good for dummies, newbies or if it's good doing it..)
-----
Anyways, now it's the time for the PLUGIN system + Installer.
I want a suggestion of how you want to the Plugin System would be.
You can suggest PHP Libraries that are Plugin Engines, features for the Plugin System, Technical tips, etc.
Remember.: Composer Plugins:
You must be registered to see links
As an example, It's good the plugin system being like each plugin it's a composer package?
Or in a folder called Plugins?
Do the plugins can add or edit the API Paths? (Like custom paths + ability to overwrite other paths?)
Is it good the plugin system with the ability to create/adding more views? pages? Habbo-web pages?
----
It's good I make a script that changes the Angular Content to something that includes your view? How would custom pages be? Like Staff Page? Something easy?
It's good I create a system that allows Angular automatically route to dynamic pages?
Give'me your suggestions!!
------
For the Installer, what yours want to the Installer be? Something that allows configuring MySQL? Chocolatey Config File things, like HotelName? TELL ME!
Thanks!!!
Last edited by a moderator: