tooley1chris wrote:Thread rolls system shock for resurrection... success!
I'd personally pay hmmm, say $50 for a version of maptools (even JUST the map making capabilities ) for my android Kindle Fire. Java emultator?
I may have rolled successfully on resurrection
but I'll have to make additional rolls before we can call it full reanimation (normaly I'm in the necro class for RP'ing)
@tooley1chris & Other readers of this thread
I believe the Kindle Fire may be one of the devices that can be rooted and have the above method (in my previous post) work to have maptools run on your device. Some tags to make your searching easier would be:
once you've read up on rooting and you thing you're ready to take the dive if you've not done so already in the past, use the following Google searches just like the above ones (copy/paste into Google search bar)
those quarries will preemptively educate you as a user on how to fix your device and the files to download to do so (look for stock recovery files and stock update.zip(s)) because eventually you may run into the dreaded "boot loop" or "soft brick" and having all the steps to recover and the related files to do so will keep you as a, new or experienced, user of Android root from getting to frustrated when that happens. I can say after hacking and modding and rooting android and Symbian phones (yes that may be a blast from the past for some that know what the Symbian OS for phones was, but I've been hacking on mobile hardware sense those days
) I have yet to "super brick" or "full brick" any of my devices, yes, it may take me a day or more to restore the hardware, but so long as I've access to it and the rest of the world I can always solve my issue with search queries constructed similar to the above examples.
As far as coast goes the current method should be relativity "coast free" aside from time and more time the money shouldn't have to change hands... That being said I am working on a developer donate button though Google Wallet that will be placed on my Google+ and other development sites I frequent, this will not be for Maptools development specifically but instead for the development project that I'm working on as a whole (android mobile super cloud computer) however, there will be a place for people to put in a request on what their "tip" should be used for (you all can always email me or message me for free to state what you want me working on for free too, I'm helpfull as much of the time as I can be throughout the day) with in that project and I will base my attention heavily on those topics within the guide that get the most attention from other users. In other words I'll be working on this among other things but I can be "peer-pressured" into faster development or my time can be "bought".
Update to status of running Maptools Natively on Android With Debian Kit?
I have split the "Main Guide" that I've been working on into a smaller "clone guide" specifically for running Maptools on Android.
It is still what I would call "pre-alpha" or "very rough" because I just copy pasted the core directions from the main guide into this clone (link right bellow)
Guide to Running Maptools On Androidhttps://docs.google.com/document/d/1W0H ... sp=sharing
I will be getting onto fixing this today at some point and get it to a readable state for you all here, by the end of the day. I hope to get it to "beta" level of readability. And have something that I can submit in the form of a new thread here on the rptools forums by the end of the week; I'll add links into this post and my previous post in this thread to direct you where to go when that is set up. Likely the full guide that will, step by step, take you from a rooted android phone (or tablet) all the way to hosting or joining a Maptools is still a little ways off (few weeks at the most) this is because I'm only one guy with only my lifetime to spend on this, however, I've a lot of pressure from my "other half" to not only finish this project for Maptools specifically but also (and you all should nerd sequel with me if you can) I will be writing scripts (script pack app) for the android side of things that will (at first) at the push of one button; download and install all the necessary components of Linux to your Android device, then at the push of a second button; download and install all the dependencies that allow Maptools to run, then at the push of a third button; download and install Maptools, from there we should be ready to rock and role with a simple app or script pack and then only need the guide for technical support and reference (this is a stretch goal but one of the things that I'm currently starting on)
Yesterday before my previous post was approved by a mod or admin (yes I am that new to this forum as far as my account will show) I worked on a parallel project "Installing jMonkey SDK to Android" I tell you all this because it is going to look very similar to the guide that I'm writing for Maptools as well, find the link bellow
jMonkey Specific Guidehttps://docs.google.com/document/d/1_Nn ... sp=sharing
This will only be relovent to those of you that wished to have a 3D experience to game making/development/hosting and not have to learn something other than Java. jMonkey is very powerful and has many similarities to Maptools in that it allows it's users to build and develop games for others and then publish them for free onto many devices (Android included) it just has a much steeper learning curve and a much longer development time coast when working on a project as an individual.
For both of these side projects that I'm doing and the Main Guide project one thing that will come to pass between all of them will be syncing of files between all networked devices, this will allow you all to have your game project files move effortlessly between your mobile development device (android phone or tablet) to any other device in your house hold (computers and laptops and such) at the push of as few buttons as possible.
I realize this is a long post but I will always try to supply the best and most current information and doing so requires that I use many words (this is because I've yet to figure out the Vulcan mind meld thing
) I will be keeping you all up to date on how this guide for installing Maptools for Android as best as I can, but it takes a day or two for post to get approved before I'm out of the probation period for these forums here. This is not a complaint as I fully understands what happens when there is not a system like that in place to protect against spam, just the truth, you all are reading this after I wrote it and after it's been approved. So if you are feeling impatient, or have to know what is currently being done, you can fallow the work as it's being done at one of the, many, Google Doc's links that I've posted up here and in my signature. Commenting within the Guide has been turned on and once I get it to a state that it can be posted up on these forums I will be making the Guide on Google "publicly" editable, this means that when I do that, any of you will be able to make additions and modifications to the guide too.
Thanks all for your time and I hope to hear from ya all about this.
... oh and I've email notifications turned on on this thread for right now so I'll see ya if any posts back a question or comment here, it'll just be a day (or more) for the response from me...
EDIT: 05242013 (yes I prefer to edit my posts instead of spamming the page with new posts, it means less pages for all readers to read though in order to find new information on this topic)
So the guide's that are referenced in the above links (jMonkey and Maptools)"should" be usable now, they'll look very similar for a little wile aside from the very end where java dependencies and installation of the actual program is concerned this is because the methods of set up are almost Identical. The reason that such similar things should be separated is that the dependencies for Java are different for these two programs and mixing them up caused me some errors recently and now I'm down to re-installing Linux onto my phone (again) no worries though this happens to me a lot because I'm contently testing things and breaking things in order to notate what should be done and what should be avoided, this is to keep people from falling into easy mistakes that would have happened without the author making them for you
I'll be back up and running with a new install a few hours after I begin the process.
If you are going to attempt to install Maptools on your Android device with the guide that I've linked here, then one suggestion; try the install to '.img' file instead of a partition for the Debian Kit method and make a copy of that file once you've a Linux system that you are happy with and that boots without anything extra installed to it (aside from what is explicitly stated to install with the set up section of the guide) , this will allow you to delete the original one, if you mess up like I did and, then just copy the back up to where the original was and retry, this will avoid you having to go though the installation part of the guide multiple times until you've a working method to fallowing the instructions (which are nearly complete now) Hope this helps you all from repeating my errors and with debugging errors you run into along the way because having this up and running has been a dream for many for what seems to be a long time now. Once we do have a working and nearly fool proofed way of doing this then I'm sure that installing to a partition on the SD card will evidably be the preferred method as this will offer more space within the system to run Maptools services off of.
... ha, the links looked similar because the links where identical (yep, I always try to ensure I check that at some point) fixed it now though, links now go to their properly titled guides.