Guys,
The Android table is but weeks away. As I recall VASSAL is JAVA based. What is required to run VASSAL on the Android SDK? Is this something a non tech person could attempt?
I REALLY want to be able to take my VASSAL with me when I travel and I am ready to ditch the mac lead weight.
Failing all that if it is possible would someone help me if I do the ground work?
On 22 September 2010 07:14, hipshot hipshott@gmail.com wrote:
Guys,
The Android table is but weeks away. As I recall VASSAL is JAVA based.
What is required to run VASSAL on the Android SDK?
A major overhaul of how graphics is handled. This is something that might
be possible when we introduce the model/view architecture, but that’s not
happening soon.
Is this something a
non tech person could attempt?
No.
I REALLY want to be able to take my VASSAL with me when I travel and I
am ready to ditch the mac lead weight.
How heavy is your Mac? I think the difficulty in manipulating game pieces
on a tiny screen might largely outweigh the benefits of a smaller device.
Something like this is conceivable on something like an iPad, but iPad
doesn’t support Java. There are other small tablet devices that will work
but the developers don’t have to do anything special in those cases as they
are basically PCs.
I’ve tried playing VASSAL on a netbook, and frankly it’s painful.
Failing all that if it is possible would someone help me if I do the
ground work?
If you have a lot of experience programming Java, you could take a look at
what it will take to implement the model view architecture that’s been
proposed.
On 22 September 2010 07:14, hipshot <hipshott@gmail.com> wrote:
Guys,
The Android table is but weeks away. �As I recall VASSAL is JAVA based.
What is required to run VASSAL on the Android SDK? �
Is this something a
non tech person could attempt?
I REALLY want to be able to take my VASSAL with me when I travel and I
am ready to ditch the mac lead weight.
Failing all that if it is possible would someone help me if I do the
ground work?
I guess I was referring to the 10 inch screened Android tablets like the ADAM or SAMSUNGS new device, not the ph. I realize ph based stuff would be pointless. I 'll take all of the above as a resounding no until told otherwise. Thanks for the quick response.
The 10" screen would actually be worth a try. I don’t have any experience
with such devices, but I’m assuming they are intended to be iPad
competitors.
Some interface stuff might be a problem. I’m not sure how it does
right-clicks, so that’s something to check out.
On 22 September 2010 11:43, hipshot hipshott@gmail.com wrote:
I guess I was referring to the 10 inch screened Android tablets like the
ADAM or SAMSUNGS new device, not the ph. I realize ph based stuff would
be pointless. I 'll take all of the above as a resounding no until told
otherwise. Thanks for the quick response.
The 10" screen would actually be worth a try.� I don’t have any experience with such devices, but I’m assuming they are intended to be iPad competitors.�
Some interface stuff might be a problem.� I’m not sure how it does right-clicks, so that’s something to check out.
- M.
I guess I was referring to the 10 inch screened Android tablets like the
ADAM or SAMSUNGS new device, not the ph. I realize ph based stuff would
be pointless. �I 'll take all of the above as a resounding no until told
otherwise. �Thanks for the quick response.
Thus spake hipshot:
I guess I was referring to the 10 inch screened Android tablets like the
ADAM or SAMSUNGS new device, not the ph. I realize ph based stuff would
be pointless. I 'll take all of the above as a resounding no until told
otherwise. Thanks for the quick response.
It’s also not going to happen unless at least one of the developers has
one of these devices. It’s extremly hard to target a device that you don’t
have access to for testing.
–
J.
Thus spake Michael Kiefte:
Guys,
The Android table is but weeks away. As I recall VASSAL is JAVA based.
What is required to run VASSAL on the Android SDK?A major overhaul of how graphics is handled. This is something that might
be possible when we introduce the model/view architecture, but that’s not
happening soon.
Could you elaborate on what exactly the problem is? The model-view separation
project will do many good things, but I’m not seeing what effect it could have
on whether VASSAL can run on Android.
–
J.
I was going on the assumption that we were talking about small devices.
Maybe we still are.
For alternative-type displays, a different view type could be generated.
Not sure what that would look like.
However, the current, builtin view is unacceptable for small screens.
On 22 September 2010 16:31, Joel Uckelman uckelman@nomic.net wrote:
Thus spake Michael Kiefte:
Guys,
The Android table is but weeks away. As I recall VASSAL is JAVA based.
What is required to run VASSAL on the Android SDK?A major overhaul of how graphics is handled. This is something that
might
be possible when we introduce the model/view architecture, but that’s not
happening soon.Could you elaborate on what exactly the problem is? The model-view
separation
project will do many good things, but I’m not seeing what effect it could
have
on whether VASSAL can run on Android.–
J.
I was going on the assumption that we were talking about small devices. Maybe we still are.
For alternative-type displays, a different view type could be generated.� Not sure what that would look like.
However, the current, builtin view is unacceptable for small screens.
- M.
Thus spake Michael Kiefte:
>Could you elaborate on what exactly the problem is? The model-view separation
> > Guys,
> > The Android table is but weeks away. �As I recall VASSAL is JAVA based.
> > What is required to run VASSAL on the Android SDK?
>
>
> A major overhaul of how graphics is handled. �This is something that might
> be possible when we introduce the model/view architecture, but that's not
> happening soon.
>
project will do many good things, but I'm not seeing what effect it could have
on whether VASSAL can run on Android.
--
J.
_______________________________________________
Thus spake Michael Kiefte:
I was going on the assumption that we were talking about small devices.
Maybe we still are.For alternative-type displays, a different view type could be generated.
Not sure what that would look like.However, the current, builtin view is unacceptable for small screens.
Why? What’s wrong with zooming out?
–
J.
Not enough pixels.
Maybe it depends on the module.
Why? What’s wrong with zooming out?
–
J.
Not enough pixels.
Maybe it depends on the module.�
- M.
Why? What's wrong with zooming out?
--
J.
Thus spake Michael Kiefte:
Not enough pixels.
If screen size is the problem, how will having a different sort of view
help?
–
J.
You could hide the chatter somehow.
On 27 September 2010 06:09, Joel Uckelman uckelman@nomic.net wrote:
Thus spake Michael Kiefte:
Not enough pixels.
If screen size is the problem, how will having a different sort of view
help?–
J.
You could hide the chatter somehow.
- M.
Thus spake Michael Kiefte:
>
> Not enough pixels.
>
If screen size is the problem, how will having a different sort of view
help?
--
J.
Thus spake Michael Kiefte:
You could hide the chatter somehow.
That will be possible once we have docking tabs.
–
J.
Thanks for all the feedback guys. IF I make a bunch of money this year and the new notionink.in/ comes out I’ll buy two! Just promise to return it and make VASSAL work on this format!
For alternative-type displays, a different view type could be generated.� Not sure what that would look like.
I guess I was referring to the 10 inch screened Android tablets like the ADAM or SAMSUNGS new device, not the ph. I realize ph based stuff would be pointless. I 'll take all of the above as a resounding no until told otherwise. Thanks for the quick response.