The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#31
12-09-2013, 03:16 AM
|
||||
|
||||
I don't understand why vb org doesn't use vB 6 as it could help with the testing of the vB 6 software which they will bring out next year
|
| Благодарность от: | ||
| Max Taxable | ||
|
#33
12-09-2013, 04:09 AM
|
||||
|
||||
|
Quote:
Keep in mind that mobile devices is, indeed, phones, and tablets going up to 10 inches or more. The site doesn't look or navigate as good as it could were it optimized. What percentage do any of us spend downloading modifications here? The vast majority of our time is spent asking questions, answering them, providing support and all that stuff inherent to any discussion forum. And the reason I can say all that is because I spend a lot of time on the site via different mobile devices. I've become super proficient with the Swype keyboard. And I'm an old guy. This is a very different generation. They're not daunted by touch screens or because the monitor is small. If they're going to be able to do something online while not at home, while in bed or simply not near the computer, they are. (And for the record, I've done bit of template editing via mobile, and the single reason I haven't done more is because the Admin CP isn't optimized for it. If it were, I would do it far more frequently. ) |
|
#34
12-09-2013, 09:13 AM
|
||||
|
||||
|
Quote:
It just looks old and stale imo. In comparison a board like http://theadminzone.com (which is on 3.7.x) looks incredible. IDK - I just think the .org deserves an upgrade. Quote:
Anyway = Gasping at vB.com - the Yugo... Touche about vB.org keeping the '90 Caddy -- but it's a classic now and seemingly in spectacular shape. We should place it in a museum so that all can glory at how marvelous it looked in 1990. Time for an upgrade. No compelling reason - but the clock is tickin :P Quote:
----- ----- Anyway - excellent points all. I truly do understand the 'if it ain't broke - don't fix it' thing. But you can only lie in bed saying such a thing for say 7-8 years before you really want to ((here comes another treacherous analogy lol)) change the bedroom sheets.  Ah... Yeah - and then there's the entire mobile friendly conversation... |
|
#35
12-09-2013, 10:07 AM
|
|||
|
|||
|
There are many of these "Why don't you upgrade vb org" that if any one had bothered to do a search, they would see why they don't.
In one of them it is clearly stated the main reason is there are so many custom mods and tweaks for vb org that if they did upgrade, the mods would have to be written all over from scratch. That's the bases for my comment "If it ain't broke, don't fix it. Your voices aren't falling on deaf ears, I'm sure. But on ones who's hands are tied in some form or fashion. Be it IB protocol or the amount of work to upgrade, either is enough to put the kibosh on a large project as that. In the end I'm happy to just have a place to come to where I can ask questions and get friendly answers. Maybe help some one out where I can. I don't care how old the software is or what it looks like. I'm just glad it's here. |
|
#36
12-09-2013, 01:13 PM
|
||||
|
||||
|
Quote:
|
|
#37
12-09-2013, 01:51 PM
|
||||
|
||||
|
Quote:
Quote:
Using them for constant communication is not the best choice, that would be far better done via e-mail A mobile style would be nice, but you cannot just plug one in, many features here would break (we have 80+ customised templates). Upgrading is not just a case of uploading a few files and running the upgrader. Despite the fact we have also repeated this many times, I'll cover it again. Any upgrade is a huge effort - even going from just 3.6 to 3.8 is major work - as above, we have 80+ template edits to check or redo (or modify). Over 120 plugins to check, rewrite (or remove in some cases). Things like thread prefixes are a custom mod in 3.6, but a standard feture in 3.8. All our custom javascript would all need redoing (3.8 uses YUI, 3.6 did not). All out custom functions (contained in a number of custom files) would need to be checked. Its a lot of work, so its not going to be done until there is a very good reason to do so. Despite what most people think, the thing most likely to drive an eventual upgrade is the servers we run on. vBulletin 3.6 does not play well with php5.3, even less so php5.4. Eventually we are going to have to do something to move off the old Jelsoft servers we use onto newer servers, and they wont be running php 5.2. |
|
#38
12-09-2013, 02:39 PM
|
||||
|
||||
|
Quote:
|
|
#39
12-10-2013, 01:03 AM
|
||||
|
||||
|
Quote:
You probably know better than most on here how Jacquii can't let a dead horse go unbeaten. ha. I just think vB.org should be a showcase. It's the official vB modification site. If the tagline in the header is any indication - vB.org IS a showcase site whether we want to admit it or not. Anyway - No biggy. A question was asked and I thought I'd peak my head in on the conversation and speak my peace yet again. 
|
|
#40
12-10-2013, 01:25 AM
|
||||
|
||||
|
Quote:
|
 |
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT. The time now is 07:17 PM.