I just hope it's really polished and at least 99% percent of the work is done before it's even released as a beta.
I only say that because I don't want Nao & Arantor to get frustrated with us asking about crap all the time.
I feel bad for Nao at times because at one point he got hammered with nonsense support questions over avea at SMF.
I remember one fella asked how to do something and the answer was in a post directly above his. I was like WTF?
It's good that you guys keep this under-wraps for awhile. Just plan a good support team and documention for when it's released(officially).
Truth is I'm just afraid to see this project fail. I know Nao and Arantor are tough and hardest to break, but I'm been somewhat involved in several SMF projects over the past 5 years and I don't think a single one made it at 100% intented.
I'm edger to see what you guys do with it, and just want to make sure you guys have room to breathe. People can be like locusts at times...
Keep it safe, keep it secret.
Truth is I'm just afraid to see this project fail. I know Nao and Arantor are tough and hardest to break, but I'm been somewhat involved in several SMF projects over the past 5 years and I don't think a single one made it at 100% intented. I'm edger to see what you guys do with it, and just want to make sure you guys have room to breathe.
Netscape's inability to compete was evident from the moment it arrived being a paid package, when IE was free and bundled.
I saw the last couple of major versions of Netscape before it failed entirely and it was getting more and more sluggish as time went on - it was slower then (relatively) than FF is now, and FF is sluggish these days.
One thing that would be interesting is a list of coding features. I mean, not the core features, but the things that allow you to (as a themer o modder) make your work even easier and clean as possible.
Not many (I know any) that list that kind of things, even less document it...
I think one of the best things that will make this a success is that while Nao and Arantor are keeping the future community in mind for this project, it's first and for most for their own purposes. The have said elsewhere, if no one else ever uses it they'd be fine with that. I think that gives it an edge over most other projects out there.
All to often projects like these get bogged down by community and committees (a big part of whats slowing SMF down at the moment IMHO). This isnt about what does everyone else want, its about what I, err I mean, they (Nao and Arantor) want out of it. Incidentally what they want out of it is what many of us in the SMF community have been looking for, for a long time.
One thing that would be interesting is a list of coding features. I mean, not the core features, but the things that allow you to (as a themer o modder) make your work even easier and clean as possible.
I went to crazy lengths to avoid edit conflicts in SimpleDesk, obscene in some cases, and got the opportunity to point out how bad SMF's structure is for extending things. Rest assured the knowledge I'm gaining from working on SimpleDesk (for my own ends as much as anything else) will come to play a direct part in what I do with Wedge.
I know at least one change implemented in Wedge that I made specifically came about because of something I had to do in SimpleDesk (the register-replacements thing in the DB layer) to avoid edits.
Makes me think I have a reply to finish posting over at the topic where we discuss edit-less templates
Yeah... That change was damn cool, Pete.
Do you realize that you actually made me *like* OO programming? Well, at least not hate it anymore. And I've been pestering at OO for something like 15 years