Invision Board 3.0 Discussion

[Keith J. Kacin]

We are planning on not making any changes to the posts table, unless absolutely positively necessary, for the very reason that you state.

Yeah, believe me, that was one of our main concerns too.

[henke37]

More of the core parts implemented as modules/plugins/hooks/whatever, should make things easier to toy around with and encourage the interfaces given to be done with at least the same quality the main developers want and need to use.
Oh, yeah, as I asked before, maybe us, the community, getting a chance to comment on the wip application structure design? Yes, it is a big thing where some people just "don't get it". I realize that it will be an additional burden, but I also see the benefits. Yes, you do have some of the best thinkers. But even the worst thinker can come up with a valuable observation, perhaps because he/she is less skilled.
Of course, I do not think that everybody need to know this, so I should be the first one to suggest to make it opt in and only for existing customers.

[Dark55mage]

omg I can't wait till 3.0 comes out! Keep up the great work.

[Carl M]

Not happy about the rep system but otherwise throughly impressed a new major release might be released in 2008.

I do really think IPS should look at creating a much better mod community, i would say for me that is the only plus point vB's got over IPB otherwise keep up the fantastic work guys (and girls!)

[Jaggi]

i've seen this over at phpbb and think its very good, they have a template for creating mods using xml this includes everything including the documentation itself. They also have a community project which develops a program to help make doing documentation easier. maybe ipb should think of something similar for 3.0 to make the mods more reliable by sticking to one standard.

[TestingSomething]

Well when they say they are making "no effort" to have anything for 2.1 work on it, I see no reason for them to make it easy to modify things in 3.0 itself. Why care about developers there, but say there is no concern at all with everythign for 2.1 breaking for 3.0?

Honestly everyone who wants particular features in the software, keep in mind that the more things that re in it by default, the less you can have on your site that others don't have so all of the sites will blend together more where basically an admin can put in zero effort and get the member base that someone who puts in hard work is getting. Thus I would rather many things stay as modifications anyway because I know I put in more effort than most and it would be annoying if even default sites would all have the same things in them where there is no such thing as an active admin modification-wise.

[kirov]

I hope that there will be other changes in the skin, not only css colors and some gif's

[Charles]

Well when they say they are making "no effort" to have anything for 2.1 work on it, I see no reason for them to make it easy to modify things in 3.0 itself. Why care about developers there, but say there is no concern at all with everythign for 2.1 breaking for 3.0?

Honestly everyone who wants particular features in the software, keep in mind that the more things that re in it by default, the less you can have on your site that others don't have so all of the sites will blend together more where basically an admin can put in zero effort and get the member base that someone who puts in hard work is getting. Thus I would rather many things stay as modifications anyway because I know I put in more effort than most and it would be annoying if even default sites would all have the same things in them where there is no such thing as an active admin modification-wise.

We are going to be making 3.0 easier for modification authors to work with in many different ways. When we say we're making "no effort" for 2.x mods to work in 3.x simply means that while we're not going out of our way to break things if we feel changing something will have a beneficial impact but may break some mods then we will make those changes. In the past we had usually tried not to do that.

[Charles]

I hope that there will be other changes in the skin, not only css colors and some gif's

There will be a whole new set of skin templates.

[FrostedPopTart]

There will be a whole new set of skin templates.

Please be sure to add a skin_charles, skin_lindy, and skin_keith template ASAP to IPB 3.0. :)

[Charles]

Please be sure to add a skin_charles, skin_lindy, and skin_keith template ASAP to IPB 3.0. :)

Um... will do?

[FrostedPopTart]

Um... will do?

I thought the small :lol: smiley would have given it away. :(

[zigs]

What would be nice is the ability to pm members if you delete a post, then they know why it was deleted, like the warn system...

[Josh]

I thought the small :lol: smiley would have given it away. :(

Wait, that was a joke? Now I have to go redo all those templates :huh:

[TestingSomething]

We are going to be making 3.0 easier for modification authors to work with in many different ways. When we say we're making "no effort" for 2.x mods to work in 3.x simply means that while we're not going out of our way to break things if we feel changing something will have a beneficial impact but may break some mods then we will make those changes. In the past we had usually tried not to do that.

ok, thanks for clarifying. I was really just saying even if it's easier for developers with 3.0, since it won't necessarily support 2.2 mods then whenever 3.1 comes out maybe things made for 3.0 won't work also. I'm probably just exaggerating it. Mods "in general" didn't need much changing between 2.0 and 2.3, it seems. Although I never used 1.x.x mods, so I have no clue how much modders needed to change between 1 and 2.

[TestingSomething]

What would be nice is the ability to pm members if you delete a post, then they know why it was deleted, like the warn system...

Oh that reminds me of something I suggested long ago. reason for suspend/ban really needs to be shown in a board message when that person goes to the board becuase they can't even read a private message or the warn logs anymore. I noticed vb started using that after I mentioned it too. Maybe they spied on me. (or maybe others had that idea also, hmm)

As far as your idea, I guess I like it although if someone deleted a lot of posts it would be a lot of PMs being deleted. But I don't know a better way to do it than you suggest either. And frankly I myself have wondered why a post was deleted on other sites in the past and could find nobody to tell me.

[FrostedPopTart]

Wait, that was a joke? Now I have to go redo all those templates :huh:

No, I do want those in there. Make sure to put a skin_linda template inside Lindy's template; just to confuse people even more about his name. Put a skin_chuck for Charles, and a skin_boxcar to rag on Keith for his undying love of Toyota Scions. :D

[IBTheme]

I am constantly amazed at how far Invision software is progressing. It has far surpassed all other community based software in my honest opinion. It has been a pleasure to recommend this software to my clients on both of my designing sites. I have never been disappointed and I'm sure I will be just as pleased with 3.0 as we have all anxiously awaited it's arrival for quite some time now. As a designer, of course I have to comment on how pleased I am to know there will be a new skin with 3.0. A little clich

[Charles]

Well we do have some pretty nice ideas for a social networking solution but that is a bit later... :)

The new skin is also being designed with designers in mind. The biggest problem with our current skin, and particularly its CSS, is that is it an updated version of a 6 year old skin. So a new skin will clean up all that old HTML and CSS to make things easier to edit. Details on that I will of course leave to Rikki's forthcoming blog post.

[Axel Wers]

For IPB 3 Development team:

SEO will be really good decision, but please don't forget on boards where is diacritics used in words.

For example topic with name ľ

[Charles]

The SEO features will be configurable so they can be tweaked to specific needs.

[bfarber]

Just a note regarding modifications and upgrades...

In making the jump to PHP5 only support we have a host of new options. interfaces, abstract classes, new functions and new coding conventions. I would venture to say 99% of all 2.3 and older modifications simply won't work.

For instance, there is no longer an $ipsclass. This object steered off course from it's original intentions and became quite bloated. We've redesigned the entire process of fulfilling a request to make it more streamlined. Long story short, pretty much all existing modifications won't be compatible.

Moving forward, however, we won't have such a drastic jump for quite some time I'd guess. Of course there's always the risk of breaking an old modification during an upgrade, but we're making huge jumps with 3.0, whereas we generally make much smaller jumps between point releases.

[MindTooth]

I really hope that you go PHP 5.2.x. Since from what I know, 2.5.x has some nice features.

Birger :)

[TestingSomething]

Just a note regarding modifications and upgrades...

In making the jump to PHP5 only support we have a host of new options. interfaces, abstract classes, new functions and new coding conventions. I would venture to say 99% of all 2.3 and older modifications simply won't work.

For instance, there is no longer an $ipsclass. This object steered off course from it's original intentions and became quite bloated. We've redesigned the entire process of fulfilling a request to make it more streamlined. Long story short, pretty much all existing modifications won't be compatible.

Moving forward, however, we won't have such a drastic jump for quite some time I'd guess. Of course there's always the risk of breaking an old modification during an upgrade, but we're making huge jumps with 3.0, whereas we generally make much smaller jumps between point releases.

I just wish there will be some attempt at providing documentation to help understand the new set up. I'm sure the programmers who have been using IPB for a long time will quite easily figure it out, but me personally... since I am just starting to learn even the current setup and don't exactly understand what is going on in the current IPB functions, I probably will be very confused.

Just would be helpful if it is explained somewhat in the future, even though obviously it's not something "promised" to customers. Although I thought it was said that components would keep working even with 3.0. Maybe I misunderstood. It's been a while, but I sure thought that was said.

[BryanH]

I kinda agree. At least... I'm not a PHP whiz or anything. I don't understand the greater inner-workings of IPB. But since it seems 3.0 will be a big re-write, I plan to learn through this new version.