Help description in admin CP on VB3
 

I'm doing my first hack for VB3 :banana:

Well, vb3 coding is really different of the v2 :hurt:
It's not really easy at the begining ...

I think it shouldn't be too hard too finish, but I'd like to add next to my field (so, it adds a box where you can enter datas in the image.php) an image bubble to show some informations about this new feature, but I don't know how to ....


I've looked at the adminhelp.xml, the adminhelp table, have add what I think should be correct, but I don't know where I can add a description for this new feature ...

Can someone help me ?

Tell me if you didn't understand what I want to do ;)

Thx

You are absolutely INSANE to be coding now. Hell, the base code doesn't all work yet and you are going to try to debug hacks?

Have fun.

We don't support hack discussion for vB3 here yet, sorry. Amy's point is correct: the whole point of a beta is to get a final stable version to then modify. By hacking you're completely destroying it.

I don't destroy it, I'm just learning how VB3 is working ... ;)

It's not a shame if I have to remake it for the final RC, at least I would have learned how it's working ... :p

As long as you realise you are excluded from bug reporting. You can modify code for yourself.

It's ok, I've found ...

I may have an other question ... but ... I don't will ask it :p

My primary concern isn't that people will tinker with their own boards. My main worry is that people will release their tinkerings in the mad dash to be first to release a VB3 hack.

Then, people who should barely be installing the beta due to lack of skills will try to use those posted hacks, and utterly screw up their boards.

Amy

But the Final version will be only in two months?! It's insane, that what it is. It should be done in two weeks, tons of coders ... brrr, and no vB3 hack discussions. :rambo:

@ amy : I don't want to be the first to release a VB3 hack ... but I'm now learning how it works, and this will be good bases for future hacks ...

Of course the code used for the RC will be (a little) different, but major functions will be conserved ;)

I just want to take a good new start with VB3 ;)

You guys don't understand. You're working with an unstable codebase, and you have no idea what'll change. Just look how many bugs were posted the first day of the beta testing.

The whole point of a beta test is to get a good final stable version. By hacking, you're making it even more unstable to the point where god-knows-what'll-happen.

I agree with filburt;)

I am making a few hacks and testing them, but I am not setting them in stone, and removing them after testing...

I am merely familiarising myself with basic code, knowing that things will change...

You need to detatch yourself from major code-changing hacks, and study vB3 and iron out the bugs - I know I am doing small hacks, but I am also finding potential bugs at the same time;)

Satan