nice, but at that stage, it’s a just 3d viewer. Nice looking, but just a 3d on a dead map like i saw so many on youtube.
Interesting case, because it’s what i was talking about. People learn to do the fancy stuff with some logic bricks, then realise that making a game is a bit more than just parenting a gun and a camera on 2 empties. Most of the time, the project stops at that point. I’m not critising the guy, im just pointing out that it’s a pitty that so many people are re-inventing the wheel each time.
Edit : i was wrong on him, i checked his youtube channel and he’s doing very good stuff
I made a few changes to your document as well as adding a few annotes. I got the following message tho.
I’ve tried to learn how to use GitHub on a few occasions, and failed badly, each time. They seem to preasume participants will have either prior knowledge or direct mentoring. I think it may be unreasonable to expect people without formal training to participate on this platform. Either that or I’m just an idiot.
Actual no, thats not really what I want. Its possible that I would make tutorials for parts of that project, but It was designed for a very particular game and I am currently thinking of code that is more general and preferably better encapsulated. I feel like were talking past each other tho, so let me be more clear.
I’m getting online right now because I posted something to another forum. I don’t check my email unless I’m actively expecting a message. You see, I’m unreliable. I wont maintain my own code.
Think of the times you watched a tutorial only to have it not work. Then you check the comments section, and some body explains that the api changed. You should then be able to change the tutorial it self, rather then relying on comments.
Take TutorialsForBlender3d. It was a great resource. I believe it claimed it would take submissions, but didn’t explain how to submit. No body participated and the site became outdated and inadequate. Eventually it disappeared.
These aren’t problem to be avoided, there to be expected and planed for. None of these problems exist for a wiki that any one can edit. So long as the site is still hosted and some one wants it to continue, it will.
There are predominately two things that I want, in order for me to write tutorials. The ability for the tutorials to be found using an index, and the ability for any random yahoo to edit them. Without those two things, it’s unlikely that I will participate.
I think I might understand what you mean about brainstorming. Theres got to be like a hundred different first person templates on this forum. Whats the point of all that? If we had like all of the disparate code people have done sort of sitting in a row, then we could look at and be like, “This worked but that didn’t, lets see if we can combine it into something cohesive?” I mean at very least people should knew that it’s there.
is now open and editable by ALL, no subscriptions !
To create the page ‘whatever’ , just enter http://upbge.wikidot.com/whatever and you will have the possibility to create that page. I will secure a back-up.
Of course you would have to understand how to use Git, but it is a pain I don’t mind people taking.
If you are using the BGE your are already hands deep in technical stuff, you may be a beginner or a more advanced user, but using Git is just yet another tool that is useful to know about.
I agree that there might be easier-to-contribute solutions, but right now that should do the trick in my opinion, since reading requires almost no effort, while writing requires some commitment.
In the long run, I would prefer to drag people closer to GitHub, since UPBGE is managed there as well.
The wikidot solution seems to be a nice compromise as well
edit: @Cortu I would say that GitHub+Git is like Blender, you cannot really expect to learn how to use it instinctively, you have to learn via articles/tutorials. Regarding pull requests, I think I had added a link to some resources explaining how to properly use them. In any case I can tell you here that it is possible to leave comments directly from the website, see this. You can annotate lines with review comments.
@wkk , since you seem familiar and have affinity with GitHub you will be the one who gonna supervise all the content and manage the input. Since already very few people are showing interests (for the moment) to contribute to a wiki, don’t you think that GitHub complexity will just keep them away even more ?
What about letting everybody freely edit upbge.wikidot.com and start thinking to port (copy-paste) the content to GitHub after reaching a critical mass ? I say that because, for the moment people seem not really reacting as they don’t see the point to help. Maybe , after i port the old tutorialforblender3d maybe people will start to show signs of life . I’m just feeling that nobody really wants to go into Github for the moment (and probably not even create an account)
My point of view here: I don’t expect people to move a finger. I want to have something on GitHub to get the few that will go through closer to the sources. If someone wants to interact with the repository I’ll indeed welcome them. Please do as you wish, as the wikidot site seems nice. Until we notice movement on either side, we can think about how to proceed later.
Ok, copy that. Feel free to add content on wikidot too It will be a pleasure to have an article of your wkk.py . For the moment, one can simply flat list all the contributions on the main page
Its possible I might have commented on that link, I’m not really sure.
Theres certon aspects of my code that could possibly benefit from something like this, some that probably wouldn’t. I’ve tried to learn how to use GitHub on more then one occasion, including reading multiple articles/tutorials. For instance, in all the tutorials I’ve read, I’ve never seen something like the page you just linked. I was basically just clicking on stuff. Maybe the tutorials I’ve read are just no good. If so, then theres a lot of bad ones out there. At any rate, I really appreciate that your willing to help people with this stuff, but I’ve already tried, it hasn’t worked, and I don’t want you to waste your time. Also you should be aware that I’ve sworn off programing in C, so its unlikely I will ever directly contribute to UpBge. I don’t know that theres much of a reason for me to keep banging my head on the keyboard for this.
I’v added a tutorial to the wiki. It is just something that I thought would be easy to write. I was wanting to create a place to put stuff, so I needed something to put. This is the first time I’v edited a wiki but it seems pretty ease. I haven’t used markup much, but I have used it a few times, so I wasn’t completely in the dark. http://upbge.wikidot.com/error-logger-tutorial
First tutorial on UpBge wiki! We’ll see if this goes anywere
let me remind you that the purpose of upbge.wikidot.com is to be like a documentation garage. One have to put everything in the same place before figuring how to order things and easily deport everything on github after.
Cortu made already many tutorials, im still progressing to put in form the old documentation upbge.wikidot.com/logics
And 1 game has already it’s own page.
Please, create pages and drop your stuff on that wiki. We need to centralize documentation once for all .
im going to create page for TBW tomorrow then just give me time should it be for showcases as well or just documentation cuz rn i cannot provide any documentation since alot of things aren’t yet finalized yet!
It will be a pleasure to have an article of your wkk.py . For the moment, one can simply flat list all the contributions on the main page
