Biggest coding project ever

[filburt1]

ANYWAY , you would not believe how complex this installation script is compared to the standard script I used for all of my vB2 hacks (including vBMS 1 and all the late hacks here). The vast majority of the time trying to code it was trying to figure out how the hell vB's own functions work. Speaking independently from my moderator position, the documentation is terrible within the code. Not only do nearly all of the functions lack any documentation, but the ones that have it have incorrect function names and don't document any of their arguments or the return value. Even the variable names don't help much.

I would pay a significant extra for a developer edition of a vB license that included proper PHPDoc-formatted (similar to PHPDoc) comments for each function. It would have cut my development time for vBMS and for future projects in half.

[Dean C]

Originally Posted by filburt1

Speaking independently from my moderator position, the documentation is terrible within the code. Not only do nearly all of the functions lack any documentation, but the ones that have it have incorrect function names and don't document any of their arguments or the return value. Even the variable names don't help much.

I would pay a significant extra for a developer edition of a vB license that included proper PHPDoc-formatted (similar to PHPDoc) comments for each function. It would have cut my development time for vBMS and for future projects in half.

I couldn't agree more, the documentation within the code is terrible as it is.

[Brad]

Originally Posted by Dean C

I couldn't agree more, the documentation within the code is terrible as it is.

I agree aswell, and would pay extra for said 'developer edition'

[Dean C]

Oh I wouldn't pay extra, it's just common sense and useful to document your code well

[Craigr]

Originally Posted by filburt1

ANYWAY , you would not believe how complex this installation script is compared to the standard script I used for all of my vB2 hacks (including vBMS 1 and all the late hacks here). The vast majority of the time trying to code it was trying to figure out how the hell vB's own functions work. Speaking independently from my moderator position, the documentation is terrible within the code. Not only do nearly all of the functions lack any documentation, but the ones that have it have incorrect function names and don't document any of their arguments or the return value. Even the variable names don't help much.

I would pay a significant extra for a developer edition of a vB license that included proper PHPDoc-formatted (similar to PHPDoc) comments for each function. It would have cut my development time for vBMS and for future projects in half.

Codename Sunset looks good too. Have you started work on it?

Will you do a convertor from Photopost to Sunset?

[filburt1]

Given I don't own a license for Photopost, that's not likely. I'm also spending the vast majority of my time finalizing vBMS rather than working on new projects.

[DrkFusion]

I have just started the biggest of coding projects I will have ever done. Incorporates alot of modulizing, and has heavy reliance on security. Let's see what I have learned in the past few years will bring to me now in this big project.

[filburt1]

To those who asked about Sunset, I updated its product page with a list of planned features, although please don't ask for a release date because it is far too early in the development to even guess.