Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 5905690" data-attributes="member: 8835">the system will be stuck with whatever vBulletin expects for code or modules to be done as.&nbsp; Mostly PHP, using whatever libraries vBulletin demands.the actual Parser can be mostly detached from the vBulletin.&nbsp; Anybody could code it in PHP as a class library or set of functions the other code can call.&nbsp; The one caveat to that is that Assets are likely to come from vBulletin's DB and that'll require whatever architecture constraints to access it.&nbsp; A developer could get clever with his code and ini files to make it so an Asset could come from different sources (text file, simple MySQL DB or vBulletin DB) and the rest of the code would be clueless when it uses the Asset object.thus, a developer could work on the Console and Parser to get it working, then somebody more knowledgeable in vBulletin coding could hook up the rest.</blockquote>

[QUOTE="Janx, post: 5905690, member: 8835"] the system will be stuck with whatever vBulletin expects for code or modules to be done as. Mostly PHP, using whatever libraries vBulletin demands. the actual Parser can be mostly detached from the vBulletin. Anybody could code it in PHP as a class library or set of functions the other code can call. The one caveat to that is that Assets are likely to come from vBulletin's DB and that'll require whatever architecture constraints to access it. A developer could get clever with his code and ini files to make it so an Asset could come from different sources (text file, simple MySQL DB or vBulletin DB) and the rest of the code would be clueless when it uses the Asset object. thus, a developer could work on the Console and Parser to get it working, then somebody more knowledgeable in vBulletin coding could hook up the rest. [/QUOTE]

Verification