![]() |
for the elite? You watch the elections too much LOL
|
The mod was pretty easy to use i thought, and i am the average joe coder.
In the SVN sources, i had to add a vbb plugin to the product so that you could export templates to the proper directory. I think i might have spent maybe 30 minutes looking through the source to figure out what and how to do anything i needed. I do agree though that there is a pretty big importance on documentation, but it's also obvious that the original author posted more of a proof of concept product rather than a complete tool that can be used with little understanding as to why it works. I have thought of taking the SVN code and building upon it to complete his work, but my skill in object languages isnt up to the task at this time. |
A tool that does this for plugins would be a god send. *drools* just thinking about it, and phrases too! Not having to deal with the phrase manager one at a time...*drools more*
|
I've been trying to find resources to teach myself php's object programming ways so i can figure out what the original author has done and apply a similar method to the plugin system but i end up playing world of warcraft or watching Chef Gordon Ramsay on hulu.com or something :|
Although, who ever creates a working system to edit plugins via text file v.s. the plugin editor will hold the mod of the month spot for quite some time :) |
Quote:
PHP Code:
1) I can use my regular PHP editor on the code itself. 2) I can use xdebug (i.e. step through the code, enable breakpoints, etc), which you can't do with directly eval'ed code. Once the code is ready for release, I just paste it into the plugin and get rid of the require. -- hugh |
Quote:
|
Hugh / Anthony,
You are welcome to take it over and extend it to plugins and phrase. I think phrases is already done though, just kinda slow with this method. |
So how do we go about getting access to this mod thread? I'd rather keep it in place than create a new one.
-- hugh |
Quote:
Andreas method is to create a folder, /addondev/pluginname/plugins or /addondev/pluginname/template and for the plugins, your filename is simply the hook that it belongs to. the name of the template is just that (with .tpl at the end). When you refresh/visit your site, it loads up the data thats stored on the disk. When you export your product for distribution it reads all of the data from the disk and adds it to the xml file. I created a plugin w/the name of my domain that i've placed extra templates such as custom templates for vbadvanced pages and modified style templates and it all works as expected. |
There is a wealth of developer's tools over there
|
All times are GMT. The time now is 10:54 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|