Well I've been developing the next version of Mysidia Adoptables for a while now. The release date was initially projected to be in the last week of May, but it seems that it has to be postponed for a week or two. You may wonder why, and this blog will answer your questions and concerns.
Many of you have been informed that Mys v1.3.2 will incorporate some new features such as User System overhaul and Adoptables shop. A complete list is shown below:
Though adoptables shop may seem intimidating, it is actually quite easy to implement, at least for now. The user system overhaul, nonetheless, proves to be more complicated than I had envisioned. Truth is, it is impossible to completely overhaul the User system without touching the other aspects of the script.
In fact, I've created a core class called Mysidia to handle some basic functionalities such as loading required files, retrieving cookies/sessions data, obtaining database/page content and so on. It incorporates lots of OOP(although not yet fully object oriented for now). If you do not understand what I mean, lets see the below example for a comparison of Mys v1.3.1 and v1.3.2's setting page title and adding page content approaches:
Mys v1.3.1:
Mys v1.3.2:
Interesting? Well Mys v1.3.2's approach actually requires more typing, even if you assign the page property of $mysidia object to a variable with a short name. Nonetheless, the power of OOP comes to play when you wish to easily format and reposition the content on a page. Moreover, the OOP style makes extending functionalities more convenient. The current page class/object is not fully developed, but I promise it will be quite useful in not so distant future.
So now you see the story? Converting the script from procedural to OOP is gonna take some time, and the entire process will not be completed until a few more stable releases. The new syntax/code in Mys v1.3.2 may look confusing to some of you, but with time you will get used to it and start to appreciate the new design.
Also another good news, I've pretty much learned intermediate javascript programming and ready to move on to AJAX. It is possible that some basic AJAX effect will be implemented in Mys v1.4.x, and no later than Mys v1.5.0(since battle system surely needs AJAX. XD).
If you have any more questions regarding Mys v1.3.2 and the transition from procedural to OOP style, lemme know and I will try my best to respond to your concerns. Have a great weekend everyone.
Hall of Famer
Many of you have been informed that Mys v1.3.2 will incorporate some new features such as User System overhaul and Adoptables shop. A complete list is shown below:
Though adoptables shop may seem intimidating, it is actually quite easy to implement, at least for now. The user system overhaul, nonetheless, proves to be more complicated than I had envisioned. Truth is, it is impossible to completely overhaul the User system without touching the other aspects of the script.
In fact, I've created a core class called Mysidia to handle some basic functionalities such as loading required files, retrieving cookies/sessions data, obtaining database/page content and so on. It incorporates lots of OOP(although not yet fully object oriented for now). If you do not understand what I mean, lets see the below example for a comparison of Mys v1.3.1 and v1.3.2's setting page title and adding page content approaches:
Mys v1.3.1:
PHP:
$article_title = "This is a title";
$article_content = "Here is my page content";Mys v1.3.2:
PHP:
$mysidia->page->settitle("This is a title");
$mysidia->page->addcontent("Here is my page content");Interesting? Well Mys v1.3.2's approach actually requires more typing, even if you assign the page property of $mysidia object to a variable with a short name. Nonetheless, the power of OOP comes to play when you wish to easily format and reposition the content on a page. Moreover, the OOP style makes extending functionalities more convenient. The current page class/object is not fully developed, but I promise it will be quite useful in not so distant future.
So now you see the story? Converting the script from procedural to OOP is gonna take some time, and the entire process will not be completed until a few more stable releases. The new syntax/code in Mys v1.3.2 may look confusing to some of you, but with time you will get used to it and start to appreciate the new design.
Also another good news, I've pretty much learned intermediate javascript programming and ready to move on to AJAX. It is possible that some basic AJAX effect will be implemented in Mys v1.4.x, and no later than Mys v1.5.0(since battle system surely needs AJAX. XD).
If you have any more questions regarding Mys v1.3.2 and the transition from procedural to OOP style, lemme know and I will try my best to respond to your concerns. Have a great weekend everyone.
Hall of Famer
Forum Contains New Posts
Forum Contains No New Posts
