A number of people have pointed out that my J2ME version of Pipes doesn’t work properly on some newer phones (especially those with touch screens, such as the Blackberry Storm). It is also lacking in features compared to my iPhone version.
The fact is I simply don’t have the time or resources to maintain the J2ME version. I don’t have a J2ME phone anymore, and since I don’t make any money from the J2ME verison, I can’t justify buying development equipment.
So my question is this: If I were to release the source, would anyone be willing to help out by adding new features?
yes, i’ll try to help…
please share your code to us…
thanks
Yes, please!
I suggest to host the code on github.com or a similar site.
I can do that for you if you wish.
Can I join the choir and say, please do release the code. I also use github.com and would like to help improving the game.
Thanks for the responses – I’m going to make sure the code still compiles in a modern J2ME development environment, and then I’ll post it to either Github or Google Code (Subversion).
I’ve been using Subversion up till now, but I’m interested in learning Git. It sounds like the popular opinion is that Git is better.
\o/
Thanks!
And btw, you won’t regret taking the time to learn git, if you decide to do so.
I understand you have other priorities than fixing old code.
Why not just give the source as it is, and let us fix whatever is needed to compile? Don’t be shy..
I already did
http://www.michaelkerley.net/wp/2010/01/09/pipes-j2me-is-now-open-source/
http://github.com/mkerley/PipesJ2ME
You’ll want to look at the DEVELOPMENT.txt file to see what tools I used to compile. If you (or anyone else) want to get things working with different tools (a different IDE, newer J2ME toolkit, etc), please feel free to share.
yay! thank you.
i already made my fork there, and will take a look as soon as my Real Life(tm) life let’s me.
Awesome! Looking forward to seeing what you’ll do…
BTW thanks for the tip on git. I like it so far
It’s nice being able to just say “I want version control in this directory” and run a few git init/add/commit commands rather than setting up a repository on a central server.
I haven’t tried branching yet, but I watched the Peepcode screencast and they made it look ridiculously easy. I use Perforce most of the time (not my decision) and it makes branching ridiculously hard and tedious. Perforce’s branching is more like Subversion’s in that you essentially make a copy from one path in the repository to another. Except it’s more complicated than that… first you have to create a branch definition to indicate the source/dest paths, then you run an integrate command using that branch spec (which I believe creates a local copy), and then you submit the files in their new location back to the central repository.