Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - minimoo
1
Thanks for the reply - Currently using smf with a mod that allows forum authentication to be checked against game accounts [for eve online] - https://code.google.com/p/temars-eve-api/
The above mod is not the most secure/cleanest/bug-free bit of code, and the original author no longer plays the game. This changes the registration screen to require extra custom data, and validate it. In SMF - IMO one of the hooks is really in the wrong place to be useful, as per it's description.
So I'm pretty sure my end-aim won't be something that will overlap with existing plugins :)
There's obviously been an amount of politics around SMF over last few years, I'm trying to work out whether I would be best basing a plugin for eve around SMF2/2.1 or whether a better gamble would be to look at the public wedge alpha when that gets released shortly, and consider a migration.
The rough idea in any case is:
* customise registration page
* add a few profile pages to store 'api keys'
* add a few pages to view api data
So apart from needing a registration hook in the right sort of places [to allow 3rd party content to be displayed on the page and validate it before creating a user], there's nothing here that I can't code whilst waiting for the alpha release and use either smf/wedge as appropriate.
The above mod is not the most secure/cleanest/bug-free bit of code, and the original author no longer plays the game. This changes the registration screen to require extra custom data, and validate it. In SMF - IMO one of the hooks is really in the wrong place to be useful, as per it's description.
So I'm pretty sure my end-aim won't be something that will overlap with existing plugins :)
There's obviously been an amount of politics around SMF over last few years, I'm trying to work out whether I would be best basing a plugin for eve around SMF2/2.1 or whether a better gamble would be to look at the public wedge alpha when that gets released shortly, and consider a migration.
The rough idea in any case is:
* customise registration page
* add a few profile pages to store 'api keys'
* add a few pages to view api data
So apart from needing a registration hook in the right sort of places [to allow 3rd party content to be displayed on the page and validate it before creating a user], there's nothing here that I can't code whilst waiting for the alpha release and use either smf/wedge as appropriate.
2
[@Mods - Apologies if this is the wrong place to post this - it seemed somewhat appropriate but please move if required]
I've recently put in a pull request against SMF [ https://github.com/SimpleMachines/SMF2.1/pull/242 ] to add some hooks for a plugin that I'm gradually writing to authenticate and add other functionality around a game.
Whilst I've only just signed up, I've been keeping an eye on SMF + forks progress and it seems that despite only two people wedge is currently moving forwards at the fastest rate.
On that basis;
Paul
I've recently put in a pull request against SMF [ https://github.com/SimpleMachines/SMF2.1/pull/242 ] to add some hooks for a plugin that I'm gradually writing to authenticate and add other functionality around a game.
Whilst I've only just signed up, I've been keeping an eye on SMF + forks progress and it seems that despite only two people wedge is currently moving forwards at the fastest rate.
On that basis;
- How similar are the integration hooks between SMF + Wedge at this point in time?
- Is there functionality in the current version of wedge that provides the equivalent to the git pull request for SMF above? If not, let me know and i'll add a post for a feature request if appropriate.
- Between Dragooon's mods on github [https://github.com/Dragooon] and some others, I'm hoping that there's enough example code to be able to work on a mod prior to the public release of wedge. I have however been able to find any 'developer' documentation - I assume that is because it does not exist at this stage - is that correct?
Paul