[WEEK 3] STATUS REPORT

After having the database layout figure out, I managed to get the the basic ‘create ticket’ up an running, it’s also possible for admins to create a ticket for other users. Admins can view the list of users and can easily edit their settings & create tickets this way.

The change gender & country issue from last week is also fixed! Also a lot of other small issues are fixed, like the install.php file is updated to the newest version.

Let’s take a quick look at the DB layout:
The database layout covers most of the future functions, the layout is the following

The classes: ticket, ticket_user, ticket_category, ticket_reply and ticket_content are already made and are used for creating the ticket.
You can also already specify a ticket category from a list loaded from the DB.

A demo version is already running on: http://hexon.neejberhood.be/~daan/ryzom_ams/www/html/index.php you can login with admin/admin

Next week I’ll try to get:
– Read ticket, reply on ticket, show ticketlist based on queues
– Focus also on the different roles: developer, moderator etc
– refine create ticket with add tags etc..
– if time permits, already take a look at the tags.

Note to myself:I have to put more functionality inside the lib, perhaps I need to refactor some parts.

[WEEK2] STATUS REPORT

I just received my scores of my exams, I can say that they were pretty good 😉

Anyhow let’s have a quick peek over what accomplished this week
-Added Language flags with cookie support, so you can easily switch anytime from language.
-Polished Register/Login
-Change Password/Change Email works: admins can also change passwords/emails from other users.
-Fixed the cron job, now it runs smoothly
-Made an install.php file that installs the databases and makes an admin account id:admin/pass:admin
-Made a list preview of all query’s in the libdb’s Query table, and a way to manually start syncing the lib, though I’m not yet sure if I will keep this in the final version.

what is my aim for next week?
-First add the change info form, which is already partially done
-Add a list of all users, where admins can easily modify users data and preview their data. (atm only GET parameters are supported)
-Though my major focus will be: designing the database scheme and the relations. From there, I can start implementing the base of the ticket system.

For those who didn’t know it yet:
you can follow my code-evolution on: https://bitbucket.org/DJanssens/quitta-ryzomcore

And perhaps a quick Screenshot:

Also I wanted to thank Matthew already for all his help in this start-phase of our journey 🙂

-Daan

[Week 1] Status Report

Wow, what a hectic first week..

Combining gsoc and my exams was a lot harder than expected, but I think I managed quite well.
My main focus however was aimed at my exams, because I really didn’t want to fail one of those.
Now that they are over, I can give myself the full 200% for gsoc!

The key features being done this week:
-Added the framework for handling layout for the demo website.
-Reworked the register parts of the drupal module to the account management library.
-Smarty was used for templating, I’ve refined it by adding some smarty inheritance so it can load the template dynamically based on if its a user/guest/admin etc.
-Experimented with the tour feature of charisma. Which has some great potential.

What my aim is for next week:
-Getting all aspects and functionality of the drupal module into the ams_lib.
-Getting the login page/Change Settings page up and running
-Testing the cron job and the ‘if-the-shard-is-offline’ query database table with it.

Probably some other important issues or interesting things pop up, therefor the schedule might change a bit.

I’m glad that my exams are over and that I can focus on 1 thing only!

-Daan

Getting ready to kick some ass!

Me and my Mentor Matthew Lagoe (Botanic) already spend some time on creating the basic framework. Most credits go to Matthew however, I’m still quite busy with my exams for school.
I just wanted to give a sneak peek of the current register page! However, things aren’t permanent at all, so expect changes 🙂 !

The real stuff will start tomorrow!

Let’s kick some ass.

-Daan

Accepted for gsoc 2013

I can proudly pronounce that my proposal ‘Account Management Web Application With Ticketing System And Its Integegration into Ryzom App.’ got accepted by the Ryzom Core(http://www.ryzomcore.org/) community and Google. This means that I’m going to spend my entire summer – coding to save the world (*insert heroic music here*). Well let’s just pretend that it’s for that cause! Still, it’s pretty awesome!

Now you might wonder what is RyzomCore.
Ryzom Core is the open-source project related to the Ryzom Game. Written in C++, Ryzom Core contains the whole code (client, server, tools) used to make the commercial MMORPG Ryzom. Ryzom Core is a toolkit for the development of massively multiplayer online universes. It provides the base technologies and a set of development methodologies for the development of both client and server code.

A screenshot of Ryzom

What’s my part in it?
Since the current way of creating accounts with Ryzom Core doesn’t support any validation or verification techniques even though it’s a rather important aspect these days. We have to come up with some kind of web application that handles this in an efficient way. The results in an ’Account Management System’, with all its related components regarding account registration and maintenance. But also an ’Admin Control Panel’ to perform CRUD operations on player accounts and send out bans and warnings or remove these.

Another important aspect of this account managementsystem is the Ticket system, which could be used for various reasons. This ticketing system allows users to send a query to the CSR
(Customer support representative) or DEV (Developer) team by creating a ticket and to let the CSRs/DEVs respond on these queries.

What’s next?
June the 17th, I will start coding and I will keep posting updates to this blog! So keep an eye on it!

-Daan