vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   Community Lounge (https://vborg.vbsupport.ru/forumdisplay.php?f=13)
-   -   vb3.5 News (https://vborg.vbsupport.ru/showthread.php?t=81306)

Marco van Herwaarden 05-12-2005 12:52 PM

Quote:

Originally Posted by AN-net
yeah but i know in the long run its better but now im summer is blown because first i have to learn oop then i have to learn the plug-in system and then i have to code. drrr.

You knew this was coming, you could have spend the winter learning. :D

sabret00the 05-12-2005 01:12 PM

i have a question, if you code a hack using OOP, or OOPing the code however the correct reference goes, will it only work with 3.5 or could it be developed on 3.0.7?

Revan 05-12-2005 01:23 PM

Im currently developing RPG v4 in OOP, but (obviously) for .0.7
The difference is that while my $RPG class won't have to change (much), all the $vboptions's etc needs to be changed.

Eagle Creek 05-12-2005 02:59 PM

Quote:

Originally Posted by Xenon
without seeing the code, it will be hard to determine

i already fear upgrading all the vb.org used hacks ^^

lol, poor admin :D

feldon23 05-12-2005 03:28 PM

Quote:

Originally Posted by Paul M
I also don't quite understand the theory of these. It sounds like they will allow you to "insert" code at various points, but many hacks don't just insert code, they actually change existing code, so how will this work ?

The instructions for installing the typical hack will no longer include steps like:

"Open showthread.php and look for:

<<CHUNK OF CODE>>

and replace it with

<<CHUNK OF CODE>>"

and init.php, search.php, etc. ad nauseum.

Instead you will upload a bunch of PHP files which vBulletin talks to in a documented way.

Zero Tolerance 05-12-2005 03:40 PM

Quote:

Originally Posted by sabret00the
i have a question, if you code a hack using OOP, or OOPing the code however the correct reference goes, will it only work with 3.5 or could it be developed on 3.0.7?

Aslong as the class-name and variable given to call the class is 'unique' then no collision will occur.

I am glad to hear about OOP, it was something i always liked about IPB (back when i used it), some may see it as a pain, but from a different perspective it can really neaten codes up, optomize them, and make nice lil library files =)

I'll be looking out for the beta, so i can be prepared what to expect for the Plugins system, i'm also very interested and planning on intergating every single line of the AJAX engine, i have great plans for it.

- Zero Tolerance

filburt1 05-12-2005 03:55 PM

Quote:

Originally Posted by feldon23
The instructions for installing the typical hack will no longer include steps like:

"Open showthread.php and look for:

<<CHUNK OF CODE>>

and replace it with

<<CHUNK OF CODE>>"

and init.php, search.php, etc. ad nauseum.

Instead you will upload a bunch of PHP files which vBulletin talks to in a documented way.

Without seeing the code, one can only speculate on how it will actually work. It was said that "hooks" are used throughout the program now which likely means it will consult a list of installed modifications, see which ones are registered with that hook, and execute code appropriately. Where there's no hook, you won't likely be able to affect the normal code flow, just like now. However, the way they described it, it sounds like they can easily add hooks later.

I would be worried about a hook in a loop. An irresponsible modification author may add a query to their code that registers with that hook and therefore queries in a loop.

feldon23 05-12-2005 04:11 PM

Quote:

Originally Posted by filburt1
Without seeing the code, one can only speculate on how it will actually work. It was said that "hooks" are used throughout the program now which likely means it will consult a list of installed modifications, see which ones are registered with that hook, and execute code appropriately. Where there's no hook, you won't likely be able to affect the normal code flow, just like now. However, the way they described it, it sounds like they can easily add hooks later.

I would be worried about a hook in a loop. An irresponsible modification author may add a query to their code that registers with that hook and therefore queries in a loop.

Hack authors won't need to write queries very often because of the Data Manager and OOP.

Most queries that people add to their hacks search on the post table or add an index or table to supplement users, posts, threads, etc. With vB3.5, all of that should be done with Data Manager and Classes.

AN-net 05-12-2005 04:45 PM

Quote:

Originally Posted by MarcoH64
You knew this was coming, you could have spend the winter learning. :D

well i didnt think it would be so soon and i was busy actually coding the sections of my site. OOP= da evil!!! why cant i just code!!1

Guest190829 05-12-2005 06:05 PM

It's going to be great learning to code 3.5.0 in my opinion, now I have a reason to learn OOP annnd now I have things to do over the summer ^_^


All times are GMT. The time now is 06:35 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01014 seconds
  • Memory Usage 1,743KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (7)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete