Loading ...vBSed development is in a state where you can check back see what you did good or bad or really really bad. I have so many ideas to implement and to start seriously thinking about a release. Don’t ask if it will be a paid product or a free mod. It’s true when I started the project I didn’t give a shit about that but now i regret it and I see how a few mistakes will keep me behind some time schedules.
Firstly the name. vBSed it sounded cool that time but now people think i just ripped seditio, they are terrible wrong on that but i can’t prove it yet. So i am on a name hunt to replace vbsed. I want something without any prefixes cause i don’t want to brand this project as a vbulletin product only. Who knows maybe on some point with only a few changes it will be available for so many other bb forum software out there. I don’t want any fancy things or something meaningless F.C.G.T.H.J.Y lol. It must be unique of course and attractive.
My biggest problem is the structure of the current vbsed which comes with various section but they all interact with each other. The categories/pages, the SFS site file space, Terminology, Portal Page and a few other less important to mention. What i have to do it break these sections apart and make them work independently from the other apps. It sounds easy but it’s not, they all share some common functions, they all share some common phrases even templates, don’t metion the configuration options. It’s not hard to do it after you think some unique product ids, it’s mostly search and replace, move this and copy that. I kinda hate these things. I wish i had some new, young underling for that, but hey in my work i am the underling so no luck with that.
If you get over with these “minor” problems we have the portal page problem which everything is hardcoded with no option to change things. I have big plans for this and it will be proved really enjoyable as it will be something new. Widgetize everything, custom layouts for each section with a million options, show this for lists but only for a few categories and only if the user is logged in or not. If i get over this i will try to convert or build new addons/widgets from the vbadvanced. People often mistake it for a cms but it’s not. The truth is that it’s a simple portal page, with a few nice options like adding some custom pages or adding sidebars to specific sections, and it has hundreds of addons for almost every single content addon of vbulletin. It’s funny cause 2/3 people i know hate it bad really bad but they can’t live without it cause of the 3rd party modules.
Before the early stages behind a release, i will have to re-examine the weak points of vbsed. The very few permission rules. eg for pages 1. can view, 2. can submit, 3. can admin. Pretty much ridiculous if you ask me, as i write this i can think at least 6-7 more permissions. I don’t think vbsed has other so important weak points. People will always find some but the as it is now vbsed is working as it’s made to be. Of course all parts of the project need to be revisited, don’t forget vbsed it was still is supposed to be a custom cms for my 3dacc.net
I also need to come up or ask help from professionals for some serious logo work, have you noticed how empty this post is?
Feed for this Entry Trackback Address The permalink
One Response to “vBSed mistakes and what the future holds”
Chris T Says:
May 16th, 2008 at 4:23 pm
The operation of separating the conjoined scripts will be proved a tough job, i kinda found a formula for this but will all the name changes and the common functions it’s like rewriting the whole thing.
Recent Comments