Blog Documentation Book a Demo
Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

Naming Conventions for Vanilla 2?

2»

Comments

  • squirrelsquirrel
    Agree with mattucf. Just pick one and stick to it. That will put you ahead of PHP's own schizophrenic blend of C-style and perl-style naming.
  • MySchizoBuddyMySchizoBuddy
    this would be a good time to create some demo themes for vanilla 2. one less work for mark i like the theme of beast forum engine http://beast.caboo.se/ no i'm not saying to copy it. but something as simple as beast
  • klipklip New
    I like the convention as it is. But if you have to adjust lot of different codes you got used to everything, so I personally don't care.

    I like timfire's suggestion to have extension's name as a prefix for extensions identifiers.

    I think any framework is better than nothing.

    PHP4 vs. PHP5: I guess when the day comes and Vanilla 2 is ready and stable, PHP5 would be much much more supported then now.
    There is no reason for hosting companies to not support PHP5 but lazyness. Shame on them!

    http://www.php.net/ sais:
    PHP 4 end of life announcement
    [13-Jul-2007]

    Today it is exactly three years ago since PHP 5 has been released. In those three years it has seen many improvements over PHP 4. PHP 5 is fast, stable & production-ready and as PHP 6 is on the way, PHP 4 will be discontinued.

    The PHP development team hereby announces that support for PHP 4 will continue until the end of this year only. After 2007-12-31 there will be no more releases of PHP 4.4. We will continue to make critical security fixes available on a case-by-case basis until 2008-08-08. Please use the rest of this year to make your application suitable to run on PHP 5.
    What else to say?
  • FyorlFyorl
    I think any framework is better than nothing.
    Why?
  • MySchizoBuddyMySchizoBuddy
    edited February 2008
    @Dinoboff *smacks myself* whats stopping us from using zend anyway. i like the new Zend_Form, i hate creating forms for extensions. such a tedious work. http://devzone.zend.com/article/3030-Lifting-the-Skirt-on-Zend-Framework-1.5---Zend_Form
  • FyorlFyorl
    i hate creating forms for extensions. such a tedious work.
    I'd like to second that, writing the configuration forms usually take longer than the actual functionality in my experience.
  • klipklip New
    @Fyorl: because frameworks make things faster to make and still it's easier to understand the code.
    True is that to learn a framework you have to pass some learning curve, but after that everything is so fast ane easy to do.
    Actually I don't see any reason not to use a framework.

    that's my opinion :)
  • FyorlFyorl
    There are plenty of reasons to not use frameworks. To quote myself earlier:
    It adds a lot of code overhead that is a problem for things like forums which require fast page loads. Also, as projects get bigger, frameworks become more of a hindrance than a help - you find yourself bending your code around the framework to perform otherwise simpler tasks.
  • gerry22gerry22
    I vote for Zend Framework.

    And as far as naming conventions goes, i vote camelCase.
  • timfiretimfire
    edited February 2008
    Re: Using a Framework

    I have no strong opinion right now, but wasn't one of Mark's goals for V2 to shrink the core program? It seems that cutting out the framework would further that goal...

    PS---I do like ThisTypeOfNamingConvention, now that I gotten used to it. It saves a few keystrokes over writing_with_underscores. But it's not a big deal. I am ambivalent towards camelCase. Pick one and go for it.
  • sirlancelotsirlancelot New
    edited February 2008
    Whatever is chosen, it's less important that there be one and more so that there only be one. I loved the Lussumo Framework because there was only one naming convention (to my knowledge).

    I don't remember if the naming convention was stated in the documentation but that would also be equally as important as having only one. Naming conventions should not be an obstacle for veteran programmers, but an aid to programmers new to a team.

    Keep the current naming scheme. PHP5 is now case-sensitive when retrieving function/class/method names via get_class() or other related functions. PHP4 is no longer supported (or will no longer be soon).

    I for one however, still need to upgrade my servers to PHP5 :-/ The reason I haven't is because so far I've had no reason to upgrade... Vanilla 2 will hopefully change my mindset :)hopefully soon too!
This discussion has been closed.