Omnimaga
General Discussion => Other Discussions => Miscellaneous => Topic started by: ben_g on August 16, 2014, 07:35:15 pm
-
Introduction
As most of you will probably know, many projects here tend to die, especially the bigger or more complex ones.
Well, I had an idea that might be able to decrease the number of death projects: We'll team up with some people here on this site (everyone is free to join, regardless of programming skills), and decide on a project to pick up (As long as we have the author's permission to do this). Then, we'll divide the uncompleted part of the project in bite-sized chunks and distribute those chunks to the members of our team that are willing to cooperate in this project. Because everyone will now only have to do a small part of a project, it's far easier to bring it to completion, and it won't take nearly as much time as finishing a complete project, which should decrease the chance of people getting bored with it and putting it asside.
Off course, I nead people to join this team, or else this idea will certainly fail. And I'll be honest: community project don't have a very big chance of success on calculator forums. I just hope that it'll go better with this one because it's lost of small projects instead of one big one.
Guidelines
Please be aware of these guidelines when you join this team:
- Programming knoledge is advised when you want to joint his team, however, it isn't required. For some projects, we will probably need spriters as well.
- The author of the project being worked on will act as the team leader (to improve consistency in the project), unless:
- The author doesn't want to work on his project anymore, or
- The author will work with us, but doesn't want to be the leader
In those cases, a democratically chosen volounteer will become the leader.
- When you decide to join the team, be aware that we may not start by reviving your project first.
- Anything you create for the team belongs to the whole team. If you decide to quit the team for a certain reason, you shouldn't be able to force the rest of the team to redo your work by suddenly dissalowing them from using your part.
- Please don't join just to get only your project completed. When you join, do it because you want to revive projects of this community
Proposed project flow (may change in the future)
We won't start with a project right away, because I first want to see if there's enough intrest to actually pull this off. If the team is big enough, we'll start by shoosing a project in the way described below, but to not abuse this, the first project we'll work on will not be one of mine.
1) We'll shose a project amongst the dead projects owned by our team members.
2) If we feel like an other project should be finished before those of our team, we'll try to contact the author asking for the source code and the permission to complete their projects. We'll also try to ask the author as much as we need to know to finish the project in the way he intended it to be.
3) Once the project is selected, we'll check what parts are already fully functional, which parts have to be fixed and which parts are not written yet or have to be entirely rewritten.
4) All those parts get divided into 'modules' based on their function (so they can be put together more easily), and divided amongst the team, based on both what certain people like to do and based on skill (mainly so that speed-sensitive parts can be written by people that write more optimized code).
5) Everyone will be regularly asked to upload the source files and resources they have created to a cloud storage*, so that everyone can see how the whole project is coming along. We may also need a place to discus the code.
6) Hopefully, we manage to complete the project. Then we'll make sure we put the names of our team in the credits, among with the original author and everyone who was in the original credits.
7) Choose the next project (Goto 1)
Conclusion
So, if you are interested in joining this team and performing some CPR on some neat projects that just died too soon, please say so in a reply, and also include your GitHub name. (EDIT: poll added. Please vote in it so we can all easily see how many are willing to participate)
Also if you want to change something about the guidelines or project flow, or just want to add something to this discussion, please do so in a reply.
*For the cloud storage, princetonlion.tibd has created a github that you can access here (https://github.com/princetonlion-tibd/OPRT-projects).
-
Hmmm... Sounds interesting. I might join, assuming my schedule doesn't kill me now that school has started.
-
I'm in, as stated in IRC, PM, and here :)
I'm going to try and learn new languages as we do this (or if)
Some of my opinions:
The cloud idea: If I can't upload them to the cloud, I'm either going to PM them or post them here
The communication idea: We could use this thread, or email (if willing).
Poll idea: I think there's an option to do that. Try editing.
-
Apparently, you have the option to add a poll after you post a topic. Poll added.
-
Sounds fun.
-
The cloud idea: If I can't upload them to the cloud, I'm either going to PM them or post them here
How about using GitHub? We all have access to some form of a calculator IDE or tokenizer. (TokenIDE, ORG and IES, SC3, and various others).
-
One issue with team projects is that they have to be organized properly, so that everyone has access to the entire work in real time. GitHub is definitively gonna help. Also one reason why solo projects sometimes die is that the user gets stuck at one part of the programming or even pixel art. It could just be someone who helps other people projects whenever possible.
-
Does this mean Continuity will get finished? O.O
-
Apparently, you have the option to add a poll after you post a topic. Poll added.
Last I recall it was also there when you post a topic, but whatever, we have a poll now :P The cloud idea: If I can't upload them to the cloud, I'm either going to PM them or post them here
How about using GitHub? We all have access to some form of a calculator IDE or tokenizer. (TokenIDE, ORG and IES, SC3, and various others).
I never thought of that! Yeah, that would work for me.
ben_g: So how many people do we need until we start?
EDIT: I'm starting ASM. MIPS. Something simpler to get me started.
(hey, it's (supposed to be) college level and I'm barely in middle school, give me time :P)
I'm going to try my best to contribute when/if we get this started, even if it means coding in school (which I always do)
-
ben_g: So how many people do we need until we start?
Well, it's hard to put a number on it. According to the poll, we already have 3 people, that might already be enough to pick up a smaller project or one that's nearly completed.
Does anyone have a suggestion for a project to pick up?
Does this mean Continuity will get finished? O.O
Let's hope so :)
-
I think we should start with something simple.... so...
(not my projects, they're too small and simple :P)
-
I'm in. I won't start before quite some time though, since I already have unfinished projects myself.
-
Which we could help finish if this gets going
And is there a way to see who voted in a poll so we can see who votes "yes"?
-
I'm in. I won't start before quite some time though, since I already have unfinished projects myself.
Which we could help finish if this gets going
Indeed, that's the goal of this project.
And is there a way to see who voted in a poll so we can see who votes "yes"?
Not as far as I know, but I trust everyone yere to only vote "yes" when they are actually interested in helping, and not just voting for it to get our hopes up.
BTW: for the first project, I think it's best to start with a Ti-83+ series project, since most of us are familiar with that series. I guess a computer project could work as well, but they are usually much larger than calc projects.
-
I doubt anyone would vote just to get our hopes up...
But some might.
-
They wouldn't do it in order to get your hopes up, but they might vote yes as in "yeah, that sounds so much of a good idea that I vote yes", but then laziness comes and as a result, it only got your hopes up.
I voted "no because I don't have enough time" because I have a project that I'd like to "finish" before school starts over, and I am not sure I'll manage. Maybe it will become one of the projects you'll finish :P
-
As long as we have permission :P
Anyways, github idea? or bitbucket.
Okay, it's at https://github.com/princetonlion-tibd/OPRT-projects
I'll need usernames.
-
They wouldn't do it in order to get your hopes up, but they might vote yes as in "yeah, that sounds so much of a good idea that I vote yes", but then laziness comes and as a result, it only got your hopes up.
I voted "no because I don't have enough time" because I have a project that I'd like to "finish" before school starts over, and I am not sure I'll manage. Maybe it will become one of the projects you'll finish :P
Pokémon Opal? :trollface:
-
As long as we have permission :P
Anyways, github idea? or bitbucket.
Okay, it's at https://github.com/princetonlion-tibd/OPRT-projects
I'll need usernames.
Why not create a github organization? That way you can have multiple repos ;)
-
hm... I thought it cost money...
and should I add you soru ;D
-
Would projects started the same way Escheron: Shadow Over Rangaroth (formerly Lost Legends II) be allowed? Basically, the author plans everything, makes the entire storyline, create all maps, enemies stats+sprites, names and chronology of events+scripts, but leave the whole programming task to somebody else?
If so, then I might be interested in entering Terranigma 2 for the CSE in a certain future. :P The Reign of Legends 4 2007 would be a possibility as well if it wasn't for the fact that only the intro and final event ever got planned much.
-
As long as we have permission :P
Of course you'll have permission for that game. In fact, it is impossible that I really finish it myself so I'll try to finish the engine but it is sure that there will be a call for contributors ;)
Pokémon Opal? :trollface:
Nope :P
But actually, part of the name I thought about for that project is "Open", not so far from "Opal" O.O
-
Actually, about "Open", if somebody was to make a new game similar to Pokémon but entirely stripped from any Nintendo material and with some tweaks so that the game becomes original, it could be called Open Monsters instead of Pocket Monsters/Pokémon. :P Maybe such game could allow the user to create his own monsters too (with obviously stat limits) including an in-game editor and the ability to load external monsters into your game.
-
Lol, my game is not a Pokemon game but it will allow users to create their own external characters and load them into the game :P
-
hm... I thought it cost money...
and should I add you soru ;D
Sorry, I'm afraid I'm too busy already.
-
ok.
And I created the organization "OPRT" on github
and added it to my site.
-
Alright so here are my thoughts on how we should handle GitHub.
First, have an organisation with all members granted free access and write privileges. OPRT/ indeed works.
Second, create a repo in this organisation for every picked back up project. That way, commits for several projects won't mix up and keeping track of history for eventual rebase (that's pretty much why versioning exists) will be much easier.
Before actually starting anything, everyone should agree on a way of editing Basic, Axe and ASM programs on a PC. All source code should be kept in text form ; no calc files should be allowed in the git repo. That means we'll have to agree on a way (and maybe write a script) for easy conversion/compilation of text-formatted sources into executables. Having never used a PC for other z80 coding than ASM, I can't give any suggestion.
Thoughts ?
-
why no calc files in the git repo? the script idea is good. I need to do the extra repos with ben_g.
those are my thoughts
-
I agree on the text-based source files only, and the editor I'd reccomend is Cemetech's SourceCoder3. I've tried many editors, but SourceCoder seemed to be the best one that I could get to work in Linux.
For the GitHub stuff: As long as it's easy to find things, I'm happy. This is the first time I work with GitHub so I don't know how it all works yet.
-
I like the sourcecoder idea.
It is getting a bit hard to find things IMO. I don't know how github worksyet either, I created an account for the sake of it but now it's come in use :P
-
I agree on the text-based source files only, and the editor I'd reccomend is Cemetech's SourceCoder3. I've tried many editors, but SourceCoder seemed to be the best one that I could get to work in Linux.
Why not TokenIDE? An online editor doesn't really mesh well with this. You'd have to constantly be uploading and downloading your sources. As far as I know, TokenIDE should be multi-platform via mono and/or wine.
-
As Runer said, I disagree for SC3. It can't export text and you keep downloading and uploading things. An offline solution would be best-suited.
-
I can't install things on my computer so I'm going to use sourcecode until I can install wine
-
Yeah the issue too with SC3 is that for massive projects it lags a lot. And obviously having to upload everytime will be annoying for such project. I guess we could use both TokenIDE and SC3 though in case some people can't use the former or latter for any reason.
-
Well apparently they both use the same text format, so it should be good.
-
Yeah the issue too with SC3 is that for massive projects it lags a lot. And obviously having to upload everytime will be annoying for such project. I guess we could use both TokenIDE and SC3 though in case some people can't use the former or latter for any reason.
Users don't have to upload every time, but then again, I'm banned and don't really want to go back...
.tiprogram is like a text file IMO, but windows users cannot run them.
-
Yes they have to, because how do you retrieve the latest source from GitHub and edit with SC3 without uploading it ?
Also, never heard of .tiprogram, only .8xp and the like. And if you're speaking about that, I don't want to pull 8xps to GitHub, send files to my calc to edit then, get then back on PC, push them to GitHub and repeat. That's why calc files should be banned from repos.
-
.tiprogram is what the Mac TI editor generates. not accepted on ticalc.
I wish github had an emulator for calc programmers like source coder
-
I indeed managed to get TokenIDE to work with mono. I just tried to open a file, not edit it nor saving it, but at least it doesn't crash right away.
At worst, there is tok8x that you can use too. Just make tok8x's tokens.c look like TokenIDE's tokens.xml and you'll have compatible files.
(Beware though if you use Axioms, tok8x lacks some tokens starting with Z and crashes at conversion if you use them).
-
I know its a bit unorthodox, but I might be able to write a module for a non-calculator IDE with built-in git support (probably netbeans) that can detokenize and retokenize, so the source on github is plaintext of some sort. Good idea? Bad idea? I'm doing this anyway for my own projects, but if it's useful here, I'd like to be able to help.
-
That would be very cool indeed. Also if someone knows how to work with the COM interface of Wabbitemu, a quick compilation of Axe programs would be doable via script.
-
I have now have a page/section dedicated to OPRT on my site. link in my sig
tell me if you want to edit, it's a google site.
-
Will someone please add me to the Github group? Thank you.
-
Are you Philip N on GitHub?
-
eyup. https://github.com/pimathbrainiac
-
I sent an invite.
-
Thanks! I'll put my module up on GitHub when it's dev-ready!
-
We're getting some progress setting things up :D
-
Well apparently they both use the same text format, so it should be good.
Unless it's been changed, I don't think the two use the same syntax for most special tokens (L1 for TokenIDE and {L1} for SC3 for example). <shamelessplug>But IES (http://clrhome.org/ies/) uses TokenIDE syntax out of the box for consistency, and comes with inline sprite editor and stuff</shamelessplug>
Also, this is a nice idea. Something that might be relevant: the Our Projects board is now a bit reorganized with a subboard called Discontinued Projects, which may come in handy (?)
-
SourceCoder does use just L1 for list variables, and I think it even uses the same token definition file as TokenIDE, though it won't be entirely compatible with TokenIDE's preprocessor.
But anyway, I'll see if I can get TokenIDE to work now on my Ubuntu computer.
-
I'd be interested for helping with any computer projects. I still don't know enough about calc programming to assist for calc projects, but I can definitely help for projects written in C/C++, Java, or Python.
My Github: https://github.com/Scipi (https://github.com/Scipi)
-
That'll work when we get to a computer project!
(I'm adding you)
-
I got bored today, so I tried out a different algorithm for moving the snowflakes around in Dodge (our current project).
The main upsides of this new algorithm are that it seems to be faster, all snowflakes move at the same time (which looks neater/more organized), and that it seems to slow down a lot less when the number of snowflakes increases (when handling a lot of them, it 'laggs' a bit when rendering the bottom line, but the movement happens at the same speed).
But the algorithm also has a major downside though: it only works when moving the snowflakes up, not down. It's also a lot slower on a MathPrint OS in MathPrint mode, though it works fine in Classic mode.
Here's a comparization of the new algorithm (left) and the old algorithm (right):
(http://img.ourl.ca/screenshot000-4.gif) (http://img.ourl.ca/1408406197.gif)
So, should I update the code on GitHub to use this new 'engine'? Or is the change just too big?
For those interested, the source file of the test program using the new algorithm is currently 203 bytes.
-
Well apparently they both use the same text format, so it should be good.
Unless it's been changed, I don't think the two use the same syntax for most special tokens (L1 for TokenIDE and {L1} for SC3 for example). <shamelessplug>But IES (http://clrhome.org/ies/) uses TokenIDE syntax out of the box for consistency, and comes with inline sprite editor and stuff</shamelessplug>
Also, this is a nice idea. Something that might be relevant: the Our Projects board is now a bit reorganized with a subboard called Discontinued Projects, which may come in handy (?)
Actually, if it were possible, could you make a standalone IES thingymabob? Netbeans modules are a pain to program, as I have come to realize D:
-
I got bored today, so I tried out a different algorithm for moving the snowflakes around in Dodge (our current project).
The main upsides of this new algorithm are that it seems to be faster, all snowflakes move at the same time (which looks neater/more organized), and that it seems to slow down a lot less when the number of snowflakes increases (when handling a lot of them, it 'laggs' a bit when rendering the bottom line, but the movement happens at the same speed).
But the algorithm also has a major downside though: it only works when moving the snowflakes up, not down. It's also a lot slower on a MathPrint OS in MathPrint mode, though it works fine in Classic mode.
Here's a comparization of the new algorithm (left) and the old algorithm (right):
(http://img.ourl.ca/screenshot000-4.gif) (http://img.ourl.ca/1408406197.gif)
So, should I update the code on GitHub to use this new 'engine'? Or is the change just too big?
For those interested, the source file of the test program using the new algorithm is currently 203 bytes.
Looks a lot nicer! I think we might use a separate file, I'm copying the old one down.
I think it deserves the change!
(though I personally like the different-falling because of confusion :P
I'm telling T.Wang (the other original author) about the changes
-
I would like to join! I'm always available, unless I'm working very hard on a project of my own or am away from my computer/calculator.
-
Do you have a GitHub account?
-
Do you have a GitHub account?
Yes, it's "Outerme" (for some reason, 123outerme was taken ??? )
Edit: Apparently I already had one under 123outerme, I just forgot about it.
-
I sent an invite.
Welcome to the team.
-
I sent an invite.
Welcome to the team.
Thanks! I just saw that I did register some time ago under "123outerme". If you don't want to, you don't have to send an invite to that username as well, but I'd thought I'd let you know.
-
I sent an invite to 123Outerme as well.
-
I sent an invite to 123Outerme as well.
Thanks! To keep it simple, I am deleting "Outerme" and will use 123outerme when working with you all.
-
I think we should start splitting jobs.
We could do it in the issues part of github because that has an assign job function.
-
I have some time available to commit to a computer project, if we are interested in finding one.
-
Since I can't work much on any dead project that is incompatible with the CSE (since I have no way to test it), should I have my own branch/folder for CSE projects revived?
I still can work on monochrome projects by contributing code, but I would need someone else to test my edits.
-
Well there's no reason for you to have a specific branch or directory. You just have to participate only in CSE-based projects.
-
I have some time available to commit to a computer project, if we are interested in finding one.
We might do that next, (if anyone has a dead computer project) because github is meant for that.
Since I can't work much on any dead project that is incompatible with the CSE (since I have no way to test it), should I have my own branch/folder for CSE projects revived?
I still can work on monochrome projects by contributing code, but I would need someone else to test my edits.
We have separate repositories for separate projects, and you don't have to join in on every single one.
-
I have an old project, wxWabbitemu, which is basically a Linux port of Wabbitemu via wxWidgets. Would anybody like to help pick that up? I'd be happy to help with setup and such! :)
https://code.google.com/p/wxwabbitemu/
-
Ouch, I don't have Linux and never heard of wxWidget. I would like to help but I can't :/
-
I have a mac. I think it counts.
-
Ouch, I don't have Linux and never heard of wxWidget. I would like to help but I can't :/
Linux is very easy to set up on a virtual machine.
I have an old project, wxWabbitemu, which is basically a Linux port of Wabbitemu via wxWidgets. Would anybody like to help pick that up? I'd be happy to help with setup and such! :)
https://code.google.com/p/wxwabbitemu/
It sounds like an interesting project to pick up, though I have absolutely no experience with programming in C nor with programming emulators.
Though if everyone agrees on this project, I have no problems with learning C for it.
-
I have an old project, wxWabbitemu, which is basically a Linux port of Wabbitemu via wxWidgets. Would anybody like to help pick that up? I'd be happy to help with setup and such! :)
https://code.google.com/p/wxwabbitemu/
The only reservations I have is that I do not know wxWidgets nor linux programming, and my C is rather rusty (since I'm so used to C++). But I am willing to give it a go if we have people working on it that do know those things.
-
I'm rather good at C. I was told my C++ looked very C-ish. But I don't know Linux-specific programming nor wxWidgets.
-
I just started at programming so I only know some TI BASIC, some Python, and currently I'm learning MIPS.
-
bump (so the project revival team doesn't die)
We should start giving jobs for dodge. We might have to explain to each other what we changed/how it works.
/me waits for ben's cue
Let's post jobs here or on github.
-
I think we need more projects. Because right now there's only one project, it's Basic, and not everyone does Basic. There are many dead projects, it shouldn't be too hard to find some more.
-
I agree. Any ideas?
This way we could choose our favorite project to work on.
-
/me looks back a few posts
I have an old project, wxWabbitemu, which is basically a Linux port of Wabbitemu via wxWidgets. Would anybody like to help pick that up? I'd be happy to help with setup and such! :)
https://code.google.com/p/wxwabbitemu/
I guess I should start learning C
And I'll try to divide the doge project into jobs which I'll post as issues. Then everyone can assign one to himself when he wants to do one of them. (Or at least that's my plan. I hope I understood GitHub's systems correctly to get this to work)
Also I don't mind having multiple active projects on out GitHub, but please always check for interest before simply adding it to the GitHub and keep it down to a reasonable number so we won't drown in projects.
-
I also should learn C.
A reasonable number is about 3?
-
I also should learn C.
A reasonable number is about 3?
It's hard to put a number on it. It also depends on how big the team is at the moment when those projects are submited. When there are multiple people on the team that don't have a project, I guess they are free to add an other one, if enough of them can agree on that project (enough meaning enough people to finish the project)
-
yeah.
And the project discussion is in the github issues, right?
-
Yeah, I think it's easiest like that.
-
And there's the fact that it doubles as an email conversation (at least for me)
-
Wow, lots of interest for wxWabbitemu!
So basically, if this were to become a OPRT project, these are the following things that need to get done...
Tasks:
- Update wxWabbitemu's core code to the latest, excluding any files that have NOT been created inside wxWabbitemu.
- Bring GUI interface up to date with wxWidgets 3.0.
- Bring GUI functionality up to date with the original Wabbitemu, WITHOUT adding new files from Wabbitemu. (Especially the debugger!)
- Add new features from Wabbitemu to wxWabbitemu.
These tasks will be explained in MUCH more detail if this project does get picked up with active team members.
Requirements to being a GREAT team member:
- You MUST have a good command of C to work on core code. You need to know a good amount of C overall. You definitely need to know pointers, memory management, and C structs. (If you don't know C, that's fine - go read and do a C tutorial! We recommend a thorough lesson on EVERYTHING!)
- You MUST have a good command of C++ and C to work on GUI code. Object-oriented programming knowledge in C++ is a MUST. (Again, the above applies - if you don't know, go learn it!)
- Good familiarity with wxWidgets is a MUST to work on GUI code - familiarity with tools like wxGlade a major plus. Same as above - wxWidgets doesn't always have the greatest docs, but either way, check this (https://www.wxwidgets.org/docs/tutorials/) out first, then go to this tutorial (http://zetcode.com/gui/wxwidgets/) to get into things.
- Good coding conventions - always a MUST! :D You can code dirty, but the final result must be code that is readable and understandable.
- Any OS is allowed, but at least 1 team member per OS, especially Linux. Although wxWabbitemu is geared towards Linux users, generally, it should be compilable and runnable on all platforms! That said, there should be at least 1 team member on Linux (et. al.), so that compatibility is ensured.
- CLI (command-line interface) knowledge. Even on Windows! wxWabbitemu's main building tool is run via CLI, and often you may want to run programs via CLI as well.
- Knowledge of Git. (Duh.)
- OPTIONAL - strong knowledge of calculator hardware. No, we're not talking about the number of buttons your TI-83 has - we're talking about the z80 microchip, its commands and features, and the TI calculator's low-level hardware features. (A good benchmark - if you're writing z80 ASM, you probably have some idea!) Again, this is totally optional.
Note that you can join regardless of experience, but knowing the above allows you to contribute the most to the project.
The main repository will still remain on my GitHub (alberthrocks/wxwabbitemu (https://github.com/alberthrocks/wxwabbitemu)), but development can definitely occur on OPRT's side of things! Basically, the development process is like this:
- As a team, decide on the task. (You probably should do them in order - they're ordered by difficulty!)
- Work on it locally (OPRT repo).
- Fix bugs.
- Submit a pull request to my repo.
- If approved, yay! If not, fix the issues that I mentioned, and then resubmit. Repeat #3-5 until approved!
- Pull the latest changes from my repo. (This may need to be done during the dev process, before anything is even done.)
- Go back to step 1 and start the process over again!
...whew... lots of stuff. Yeah, it's a hard project. But if you aren't deterred by the challenges ahead, hop aboard - it's gonna be a great ride! :D
Who's in?
-
Requirements to be a team member should be Requirements to efficiently work on this project
-
Is knowing how to go to a folder, list all files in a folder, and running and building programs seen as enough CLI knowledge?
Anyway, it looks like I have a lot to learn to be able to start on it, but it looks like a great challenge, and I'd love wxWabbitemu to be more up to date.
Though can I ask you, alberthrocks, to then please either join our team or at least look at our GitHub regularly to give advice and feedback? This project is quite different from other projects I've done in the past, and I think this is the case with more people from the team.
BTW: my main OS is Linux (Ubuntu), but I have Windows 7 on a virtual machine, so I can test on both.
Oh, and I have programmed in ASM in the past, so I know the basics of how the hardware works. I'd need documentation for the details though.
-
Requirements to be a team member should be Requirements to efficiently work on this project
Changed it to "Requirements to being a GREAT team member" and added this little blurb:
Note that you can join regardless of experience, but knowing the above allows you to contribute the most to the project.
Is knowing how to go to a folder, list all files in a folder, and running and building programs seen as enough CLI knowledge?
Pretty much! Really, it's just the ability to find/get CLI help (cmd /? or cmd --help), and from the help, run the necessary tools in CLI. The tool in question is our build tool, Premake. A quick start guide for it can be found here (http://industriousone.com/premake-quick-start).
Anyway, it looks like I have a lot to learn to be able to start on it, but it looks like a great challenge, and I'd love wxWabbitemu to be more up to date - m.
Though can I ask you, alberthrocks, to then please either join our team or at least look at our GitHub regularly to give advice and feedback? This project is quite different from other projects I've done in the past, and I think this is the case with more people from the team.
Awesome!
And definitely - the whole goal is to mentor those working on the code so that it isn't too much of an undertaking! (I might be busy, but at the very least, I'd like to help get things going, and try to answer any questions people may have.) The only thing is that the final code will be at our repo, alberthrocks/wxwabbitemu, for QA and centralization of efforts. (No worries, we'll give credit where credit is due!)
BTW: my main OS is Linux (Ubuntu), but I have Windows 7 on a virtual machine, so I can test on both.
Oh, and I have programmed in ASM in the past, so I know the basics of how the hardware works. I'd need documentation for the details though.
I'm dual booting Windows 7 and Linux Mint (LM is the OS I tend to use more).
To be honest, I don't have much hardware knowledge, so I tend to trust BuckeyeDude's implementation and work to integrate his code from there. However, knowing the HW is a big plus and can help when debugging wxWabbitemu and adding the Wabbitemu debugger later!
-
Or first project, Dodge (https://github.com/OPRT/Dodge), seems to be nearly completed.
Could anyone who is working on it / is interested to still work on it please check if there are any major bugs or features we forgot about?
And now that one project is nearing completion, maybe we should start looking for an other calculator project to work on.
I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.
Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).
-
Nope, nothing missed. Congrats on first project finished!
I'm starting C too.
-
Or first project, Dodge (https://github.com/OPRT/Dodge), seems to be nearly completed.
Could anyone who is working on it / is interested to still work on it please check if there are any major bugs or features we forgot about?
And now that one project is nearing completion, maybe we should start looking for an other calculator project to work on.
I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.
Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).
This is cool to hear. However, I would have suggestions for future OPRT products:
-Cross-post progress and updates over Omni, so that non-Github users are aware that they are being worked on or exist at all. For example, I didn't know about that Dodge game until I checked this thread tonight. It would also help increasing Omnimaga forum activity. Yesterday there were only 10 posts on Omnimaga and 14 Saturday.
-Those who really can't help on projects could simply post suggestions or feedback on other people's projects (at least the non-quadratic solver ones), to give encouragement and criticism for improvements.
-
Can I have an invite to the organisation too?
I'm https://github.com/Vijfhoek (https://github.com/Vijfhoek).
-
I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.
Awesome! I'll start filing relevant issues as starting points for things to work on. :)
Do you want the issues to be filed on the original repository or the OPRT? (Either way is fine.)
Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).
I'll join! (Just to watch over, of course. ;) )
-
This is cool to hear. However, I would have suggestions for future OPRT products:
-Cross-post progress and updates over Omni, so that non-Github users are aware that they are being worked on or exist at all. For example, I didn't know about that Dodge game until I checked this thread tonight. It would also help increasing Omnimaga forum activity. Yesterday there were only 10 posts on Omnimaga and 14 Saturday.
-Those who really can't help on projects could simply post suggestions or feedback on other people's projects (at least the non-quadratic solver ones), to give encouragement and criticism for improvements.
- Ok, I'll try to post more updates here. I agree that it's getting a little bit quiet here, and I'd love to see more activity.
- I like your 2nd point as well. It would make it more clear for the programmers on what they should focus, and more feetback may also increase motivation. And as a reminder (to everyone): everyone can suggest any projects to finish, even if you are not in the team, and even if it's not your project you want to suggest.
Can I have an invite to the organisation too?
I'm https://github.com/Vijfhoek (https://github.com/Vijfhoek).
Off course. I sent you an invite.
I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.
Awesome! I'll start filing relevant issues as starting points for things to work on. :)
Do you want the issues to be filed on the original repository or the OPRT? (Either way is fine.)
Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).
I'll join! (Just to watch over, of course. ;) )
I'd prefer it if you add the issues in the OPRT repository, to keep all of it mostly in one place.
And I've sent you an invite.
-
Also to add on my 2nd point, although I know Omni is supposed to be free of hostility and that overly simple projects that were already done many times before just get ignored by most members rather than bashed, I think at one point if the user doesn't elvolve it's generally a good idea to encourage him to learn more programming tricks and even ask for help if tutorials won't help out, so that he moves on from quadratic solvers and work on more interesting or original stuff. There are many ways to do it constructively and politely.
On the other hand, we have to be careful in case newer programmers start projects that are way beyond their programming skills. Of course, OPRT can come to the rescue but I see OPRT more as a project revival or for E:SoR-style projects (where pretty much the entire game, other than code, is designed in advance within the platform/language limits) rather than a crutch for newbie programmers, so I guess OPRT would just have to do some filtering in such case (to prevent being overwhelmed by projects that are still in the planning stages).
Now, talking about E:SoR-like projects, are those actually allowed for submission? What I mean is for example, if I decided to make another Illusiat game, made all sprites, coded/drew animations, designed every dungeon/town/overworld map, monsters and their data, character names, the title screen and the entire storyline including side-quests and dungeon locations, but left the entire coding process (excluding animations, for example) to somebody else, kinda like Zera/Grendel did with Lost Legends, Escheron: Shadow Over Rangaroth and a few other projects.
-
Now, talking about E:SoR-like projects, are those actually allowed for submission? What I mean is for example, if I decided to make another Illusiat game, made all sprites, coded/drew animations, designed every dungeon/town/overworld map, monsters and their data, character names, the title screen and the entire storyline including side-quests and dungeon locations, but left the entire coding process (excluding animations, for example) to somebody else, kinda like Zera/Grendel did with Lost Legends, Escheron: Shadow Over Rangaroth and a few other projects.
It depends on how much of the engine is planned, and on how 'special' or hard to code it is. I think we should allow tilemappers with all or most of their artwork already created, while we probably won't accept a 3D portal game with all it's artwork done but with not a single line of code.
I don't mind entirely different projects (in fact, wxWabbitemu is completely different from what I usually do), but they should at least have a working prototype engine to make it clear if the calculator can handle it well enough. Though in the end it all comes down to who wants to work on the suggested projects, so it's hard to know which projects will be accepted. But if anyone wants to start a project for which he only wants to create art, I'd suggest first asking for interest either here or in a project topic.
-
Ok thanks for the info. I was mainly thinking about RPGs, for example, which usually don't require any action element, so speed/performance is usually not an issue.
-
Also to add on my 2nd point, although I know Omni is supposed to be free of hostility and that overly simple projects that were already done many times before just get ignored by most members rather than bashed, I think at one point if the user doesn't elvolve it's generally a good idea to encourage him to learn more programming tricks and even ask for help if tutorials won't help out, so that he moves on from quadratic solvers and work on more interesting or original stuff. There are many ways to do it constructively and politely.
That's sort of the goal with wxWabbitemu - give people some hands-on experience for C/C++, and then hopefully they can turn "Hello, world!" into something more complicated, like wxWabbitemu! I'll be helping with mentoring OPRT on this project as much as I possibly can... though it's really dependent on my schedule. I'll try to help as much as I can within my means.
On the other hand, we have to be careful in case newer programmers start projects that are way beyond their programming skills. Of course, OPRT can come to the rescue but I see OPRT more as a project revival or for E:SoR-style projects (where pretty much the entire game, other than code, is designed in advance within the platform/language limits) rather than a crutch for newbie programmers, so I guess OPRT would just have to do some filtering in such case (to prevent being overwhelmed by projects that are still in the planning stages).
That what I'm sorta worried about - whether the project would be too complicated. For one, you have to learn C/C++, and learn it well. Then you have to learn wxWidgets, and then you have to learn the code, and then potentially low-level TI-8x hardware design... but hopefully, it won't be THAT bad! For most, they will only have to learn C/C++ really well and then learn the code... which is tough, but I'm willing to help out! :D
I'd prefer it if you add the issues in the OPRT repository, to keep all of it mostly in one place.
And I've sent you an invite.
Thanks - joined! And yeah, let's do it in the OPRT repo - couldn't figure out how to link issues from the main and assign them to OPRT, so it's better there. (Not to mention it's better there due to keep it all in one place.)
I'll start adding the issues in OPRT when I get a chance.
-
Also, I suggest writing a file with what the author of the project wants with it. For example, with Dodge, I'd love to help, but I have no clue how.
-
Also, I suggest writing a file with what the author of the project wants with it. For example, with Dodge, I'd love to help, but I have no clue how.
Speaking of that, I've posted the first two issues!
https://github.com/OPRT/wxwabbitemu/issues/1
https://github.com/OPRT/wxwabbitemu/issues/2
Issue #2 (cross-platform) should go first before #1 (update code)!
If you intend to work on a task, assign yourself to the issue!
If you need more help/details, let me know!
-
Also, I suggest writing a file with what the author of the project wants with it. For example, with Dodge, I'd love to help, but I have no clue how.
We did do that, it was in the commented code.
-
Also to add on my 2nd point, although I know Omni is supposed to be free of hostility and that overly simple projects that were already done many times before just get ignored by most members rather than bashed, I think at one point if the user doesn't elvolve it's generally a good idea to encourage him to learn more programming tricks and even ask for help if tutorials won't help out, so that he moves on from quadratic solvers and work on more interesting or original stuff. There are many ways to do it constructively and politely.
That's sort of the goal with wxWabbitemu - give people some hands-on experience for C/C++, and then hopefully they can turn "Hello, world!" into something more complicated, like wxWabbitemu! I'll be helping with mentoring OPRT on this project as much as I possibly can... though it's really dependent on my schedule. I'll try to help as much as I can within my means.
On the other hand, we have to be careful in case newer programmers start projects that are way beyond their programming skills. Of course, OPRT can come to the rescue but I see OPRT more as a project revival or for E:SoR-style projects (where pretty much the entire game, other than code, is designed in advance within the platform/language limits) rather than a crutch for newbie programmers, so I guess OPRT would just have to do some filtering in such case (to prevent being overwhelmed by projects that are still in the planning stages).
That what I'm sorta worried about - whether the project would be too complicated. For one, you have to learn C/C++, and learn it well. Then you have to learn wxWidgets, and then you have to learn the code, and then potentially low-level TI-8x hardware design... but hopefully, it won't be THAT bad! For most, they will only have to learn C/C++ really well and then learn the code... which is tough, but I'm willing to help out! :D
I'd prefer it if you add the issues in the OPRT repository, to keep all of it mostly in one place.
And I've sent you an invite.
Thanks - joined! And yeah, let's do it in the OPRT repo - couldn't figure out how to link issues from the main and assign them to OPRT, so it's better there. (Not to mention it's better there due to keep it all in one place.)
I'll start adding the issues in OPRT when I get a chance.
Yeah basically what I meant is that it would be a good idea if members, not necessarily from OPRT, keep a certain balance, eg not devoting their entire three years at Omni just in useless and mega-simple programs, but not starting a Zelda project after only 1 month of experience in programming either. Of course that would detract from the main OPRT goal, but I guess it might be a good idea to look about that to ensure that Omni doesn't get flooded by guessing games and that the OPRT project list doesn't get flooded by failed Crysis/Mario Kart 8 calculator ports by newbies. :P
-
Or first project, Dodge (https://github.com/OPRT/Dodge), seems to be nearly completed.
Could anyone who is working on it / is interested to still work on it please check if there are any major bugs or features we forgot about?
And now that one project is nearing completion, maybe we should start looking for an other calculator project to work on.
I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.
Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).
This is cool to hear. However, I would have suggestions for future OPRT products:
-Cross-post progress and updates over Omni, so that non-Github users are aware that they are being worked on or exist at all. For example, I didn't know about that Dodge game until I checked this thread tonight. It would also help increasing Omnimaga forum activity. Yesterday there were only 10 posts on Omnimaga and 14 Saturday.
-Those who really can't help on projects could simply post suggestions or feedback on other people's projects (at least the non-quadratic solver ones), to give encouragement and criticism for improvements.
Just wanted to say I agree. I think it would be helpful to post about these projects here as well. This *is* in the interest of reviving Omnimaga projects after all right? :) Most of them should already have topics, so they can just be updated as they progress. A download can also be added when the project is complete, or as it progresses if you guys want to do betas or demos. Finally, you may attract people who are interested in helping who may not have known otherwise.
-
What about adding AxIDE to OPRT?
-
I would work on AxIDE.
-
Hey everyone!
If you're following the project, you may have noticed something interesting - big update!
I fixed 2 bugs and changed the history to provide credit to those who have worked on the project in the past.
Unfortunately, this means that the commit IDs have changed, and if you try to update, it will likely fail. You will have to redownload (re-clone) the repository again to resume work. Sorry about that!
If you were working on anything, copy the files you were working on out of the repository, delete and redownload the repository, and then copy it in. Note that hardware/83psehw.c and README.txt were updated since the fork, so if you are working on these files, make sure to merge the changes!
(See: https://github.com/alberthrocks/wxwabbitemu/commits/master)
Again, sorry for the inconvenience, and looking forward to seeing what you guys come up with!
-
Well, it seems that I won't be able to work on wxWabbitemu. Sorry about that.
-
Bump
Did this idea die?
-
We actually need to revive the project revival team O.O
-
We actually need to revive the project revival team O.O
Knew this was coming
-
*sighs*
This is the future of programming (ish)! :P
Revive the revive that was designed to revive the reviver of the reviver of the reviving team! (Well, that's what might happen in the future)
-
I would just let WXwabbit emu die. I have some plans for wabbitemu that will make wxwabbit pointless ;) (alberthro knows)
-
I would just let WXwabbit emu die. I have some plans for wabbitemu that will make wxwabbit pointless ;) (alberthro knows)
WHAT? ??? YOU WANT TO KILL OFF wxWabbitemu?!?! ARRRRGGGHHHH!!!! :mad:
....just kidding. He's right - he has some magnificent plans, and I'll probably be helping him out with those plans when he gets the ball rolling! ;)
In the meantime, SirCmpwn reported an interesting bug, and I sorta fixed it:
https://github.com/alberthrocks/wxwabbitemu/issues/1 (https://github.com/alberthrocks/wxwabbitemu/issues/1)
(Yay progress!)
OPRT should track this bug and be prepared to merge, as this may be pushed to master within a week or so. (Of course, that's if OPRT is still alive, of course! :P)
EDIT: I should also mention that while fixing this bug, I found 2-3 other bugs, including (but not limited to):
- Not saving the save state... at all! This is a significant regression...
- Adding a CLI argument to load a specific ROM causes a SIGABRT on exit...
- The CLI argument isn't read at ALL unless the configuration ~/.Wabbitemu does not exist.
-
Well, I'm sorry, Alberthrocks, but I've taken a look at the project and did some thesting, and then I found out that my C skills are way to poor to be of any use in this project, and it doesn't seem like anyone else had both the skills and the interest either...
If someone submits a project in an easier language or one I'm already familiar with, then I'll deffinately try to help.
-
What about f zero :P
/me runs
-
Since there's not much activity, could I remove the project from OPRT? The code there is getting somewhat stale, and it might be confusing to others who are looking for wxwabbitemu.
If you guys are still interested, no problem - but just note that I will have to remove and re-fork the repository due to major changes.
Let me know what you guys think!
-
I think we're pretty much dead now...
So I think you can remove the code.
-
If anyone wants to revive this with my help, feel free to do so...
https://github.com/juju2143/supersonicball
-
If anyone wants to revive this with my help, feel free to do so...
https://github.com/juju2143/supersonicball
Sigh...I guess I'll try re-doing what I was working on with abstractions before my HD crash. :)