Windows come with a GUI front end, but I never use it. I did not even install the GUI for git on my linux box. I'm pretty sure the MAC as a GUI as well, as the official build now has a GUI.
Good on ya mate. It will change your world on how easy it is compared to SVN. Once you remember over the command line that is.
I merged vic's pth branch. I think I did it in a dirty way so it might not look like that in the tree. But that's besides the point. Cargame, if you can try that out, let me know what's working and what's not on a populated server.
Yep, we love it here! I tried using SVN back in 2004, but like Linus said, it did things to my source code, and I found that unacceptable.
Last edited by Dygear, .
PHP migrates to Git
I'd like to welcome PHP to the party! PRISM was using git before it was cool tho
.Using the Button class should be a better option. By the way, I'm at work, so I've not tested this code, and from my understanding that Button class is not working in the current version of PRISM, so it would be better to test with version 0.4.2.
<?php
class flame_test extends Plugins
{
const URL = 'http://www.lfsforum.net/showthread.php?t=78721';
const NAME = 'Flame Test';
const AUTHOR = 'Martin Kapal';
const VERSION = '0.0.1';
const DESCRIPTION = 'Button Test Phase';
public function __construct()
{
$this->registerPacket('onState', ISP_STA);
}
public function onState(IS_STA $STA)
{
$BTN = new Button(0, 'Test', 'Flame');
$BTN->T(50)->L(50)->W(30)->H(10)->BStyle(ISB_DARK + ISB_LEFT + 1);
$BTN->Text('Test button')->registerOnClick($this, 'onBtnClick')->Send();
}
public function onBtnClick(IS_BTC $BTC)
{
IS_MSX()->Msg('Clicked a button!')->Send();
}
}
?>
Yeah, I'm gonna make an API so that programmers can do that, using this plugin as a template.
Had not really considered that.
(BTW, my girlfriend is here, so I can't even program because she wakes up when ever I type.) <- Slowest typed sentence of my life.
Last edited by Dygear, .
Yeah, I'll fix that.
Yeah, that was my intention.
I was under the impression that STA packets are only sent when the track is loaded, I did not know it happens when some one leaves and joins too ... So I'll have to change that to something else. Actually, it should not reparse the file if the track is the same.
Glad to hear that! I feel the same way.
From my understanding he has been MIA for about 2 months now, but it's not every day that you get a message from a dev so ... who knows!
He 'licensed' it to Victor, I don't want to take someone else's work without permission.
That edit made me giggle.
So I guess we could fix that ... The SMX file should have the correct track markings, we could use that and convert it over to the PTH.
As long as you caused no damage, as long as you did not go outside of the permission level for your account, then you should be fine. Email him, let him know there is a problem. Some thing along the lines of "Hey, I noticed there was a problem with your site, it let me do this, and I don't think that's what you intended."
I'll finger the commit in my branch and revert the changes.
That's awesome, never really thought about that.
No, that's just because I tested in a local server on my client, I do not normally test for single player type accounts. But yes, PRISM should support all modes that LFS supports. It was just me in the programming of that LVS plugin using the MTC packets that made it not work as well as it should off.
Yeah, that's why I did it. I also don't have the chance to test PRISM on an active host because I don't have a server to test on. Just the servers that I make for myself with my LFS client. The only clients I have on besides my self is the AI that I put on the track.
Thank you, I'll look into this!
I'm pretty sure I read that these should be unsigned, not signed.
It seems to happen when you get to the end of the pth array, something that I thought I had fixed in this version. I'll take a look at it. Thanks for the report.
LVS and PTH parser now works on the repo. Please do take a look at it, and report back.
Then we are on the same page. I'll do this if I don't come up with something that I think it better. But if I did, I'll ask the community first if they think it's better.
Yeah, I saw it. I just don't know if I want to break that compatibly in this branch.
I'll look into fixing both the timers and the buttons in the next release, as that's a pretty huge over sight on my part. :sorry: 
I'll also ask around for how to do the pth parsing correctly on getting the size of the node, because, I'm really getting something wrong for sure on the size of the nodes. I hope I can get in contact with scawen, and maybe he could explain how he does the calculations.
I'll also ask around for how to do the pth parsing correctly on getting the size of the node, because, I'm really getting something wrong for sure on the size of the nodes. I hope I can get in contact with scawen, and maybe he could explain how he does the calculations.
Show me how you want it to work.
Ya know, I don't know. I don't think I did any testing with buttons, I really did not expect them to stop working. I'd be pissed if I did something silly and it caused a huge bug like that. Can you post some example code that was working in 0.4.2, but is not working in 0.4.3?
But you have no formal education on the subject?
Just by playing with it. For me it was, AMX Mod, and SmallC, they have a bunch of plugins that you could compile with the tools they gave you, and they also had a bunch of people making plugins for these Counter - Strike servers that would add things like jetpacks and crap like that. I was like, that's awesome, I want to be able to do that! So I found the source code of the plugins, as AMX Mod was under the GPL everyone had to give out their source code for their plugins if they gave out the binary on the forums. From there, I started playing on the servers with the plugin devs, helping them test their plugins, they would give me the code, and say, I'm having a problem in this area of the plugin, from Line X to Line Y, and that's what I need you to test. Just by doing things like that you learn alot about how to program because you see how the engine and how your actions with the engine and there by your actions effect the plugin. It was a pretty easy way of learning for me. This is what I'm trying to get at with PRISM, people that don't know how to program, learning PHP from the fun side, games! Learning about event based programming with it.
Right now, PRISM 0.4.3 it compatible with both PHP 5.3.x and 5.4.x, simultaneously. The next update to PRISM, 0.5.0 will require everyone to PHP 5.4.x. There is a pretty substantial advantages to running even 0.4.3 with PHP 5.4.x over PHP 5.3.x right now as it offers a 20% memory reduction, and speed increase. I will continue to support PRISM 0.4.x and release a couple of releases to ensure that they are no major bugs in it, but you can consider it to be deprecated around the time 0.5.0 is released.
FGED GREDG RDFGDR GSFDG