Page 2 of 2
Re: First campaign javascript dissected
Posted: 17 Oct 2014, 07:45
by NoQ
Hmm, on lvl2 the timer is set to 4 hours too, even though it's wzscript and timer value is different
Re: First campaign javascript dissected
Posted: 18 Oct 2014, 18:21
by NoQ
Per: i'm ready to commit the first level, more or less refactored to my liking, with docstrings for libcampaign, could you hang around in -dev some time today or tomorrow (or next weekend) to investigate any buildbot problems that i may accidentally cause, on the server side?
I should be available for pinging most of the time. And i think it shouldn't be hard; i added the relevant line to Makefile.am and to javascript.tex, and i guess it's enough. And then i guess i'd proceed on my own. And i guess i'd have to push it to master to get the docs used?
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 17:06
by NoQ
I mean, the server may fail to run autogen.sh properly, or something like that.
Compiling the documentation locally works well for me, to both pdf and html.
Or maybe i just push in a new branch and you merge it when ready to ...
Second level almost ready.
Edit: pushed
d480fd0 and
9d6203e, into a separate branch.
Will make a new thread now, and probably a wiki page, for further discussion.
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 19:14
by Goth Zagog-Thou
I'll get started on Mission 2 then.
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 19:32
by NoQ
Mission 2 is already done in the second commit, next step is the power module and the away mission. I'm preparing a wiki page now.
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 19:35
by Goth Zagog-Thou
Hehe, nice, beat me to it. Very well, Mission 3 then.
[EDIT] Are we using any elements from the prototype Libcampaign yet, or are we sticking to the items in the .pdf file?
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 20:10
by NoQ
Are we using any elements from the prototype Libcampaign yet?
We are using a *lot* of them. Actually, most likely *all* of them. And the PDF i posted is already outdated. Try to learn-by-example or see the code of the library for up-to-date documentation (or run
Code: Select all
make javascript-doc
make javascript-doc-html
), before buildbot is set up.
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 20:26
by NoQ
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 20:33
by Goth Zagog-Thou
Yep, I was looking at your Cam1.js Refactor and I saw the include. I'll hop over to the new thread in a sec. That's the new Wiki entry. heh.
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 20:57
by Per
NoQ wrote:Per: i'm ready to commit the first level, more or less refactored to my liking, with docstrings for libcampaign, could you hang around in -dev some time today or tomorrow (or next weekend) to investigate any buildbot problems that i may accidentally cause, on the server side?
I should be available for pinging most of the time. And i think it shouldn't be hard; i added the relevant line to Makefile.am and to javascript.tex, and i guess it's enough. And then i guess i'd proceed on my own. And i guess i'd have to push it to master to get the docs used?
Sorry, I was off mountain hiking this weekend. I just had a look at your commits, and they look fine to me. Feel free to push to master.
(Not sure if campaign documentation should be in the same document as the js API, but that we can sort out later once we see the big picture clearer.)
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 21:07
by NoQ
Feel free to push to master.
Oh well, here goes nothing (:
Re: First campaign javascript dissected
Posted: 19 Oct 2014, 21:25
by Goth Zagog-Thou
Okee dokey. I'll wait for Buildbot to do the fresh build and I'll grab it.