Android port

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Android port

stonysmith
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.


Reply | Threaded
Open this post in threaded view
|

Re: Android port

Brad Pitcher
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.

On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad

Reply | Threaded
Open this post in threaded view
|

Re: Android port

tjhowse
How about a hovering translucent code window that fades out mostly (10-20%) when you compile, allowing a full-on look at your model, and fades back in (80-90%) when you start typing again?

On 20 January 2012 09:03, Brad Pitcher <[hidden email]> wrote:
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.


On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


Reply | Threaded
Open this post in threaded view
|

Re: Android port

Whosawhatsis
Considering that on most devices, "start typing again" involves an onscreen keyboard, that might not work very well.

On Thursday, January 19, 2012 at 4:42 PM, tjhowse wrote:

How about a hovering translucent code window that fades out mostly (10-20%) when you compile, allowing a full-on look at your model, and fades back in (80-90%) when you start typing again?

On 20 January 2012 09:03, Brad Pitcher <[hidden email]> wrote:
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.


On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list

Reply | Threaded
Open this post in threaded view
|

Re: Android port

Brad Pitcher
I'm thinking in terms of the easiest-to-get-out-the-door-but-usable interface right now. I haven't even got that damn thing to compile yet. ;) The bells and whistles can come later.


On Thu, Jan 19, 2012 at 4:45 PM, Whosawhatsis <[hidden email]> wrote:
Considering that on most devices, "start typing again" involves an onscreen keyboard, that might not work very well.

On Thursday, January 19, 2012 at 4:42 PM, tjhowse wrote:

How about a hovering translucent code window that fades out mostly (10-20%) when you compile, allowing a full-on look at your model, and fades back in (80-90%) when you start typing again?

On 20 January 2012 09:03, Brad Pitcher <[hidden email]> wrote:
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.


On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


Reply | Threaded
Open this post in threaded view
|

Re: Android port

tjhowse
I haven't used an android tablet, does the on-screen keyboard occupy the entire screen in landscape mode by default?

On 20 January 2012 10:49, Brad Pitcher <[hidden email]> wrote:
I'm thinking in terms of the easiest-to-get-out-the-door-but-usable interface right now. I haven't even got that damn thing to compile yet. ;) The bells and whistles can come later.



On Thu, Jan 19, 2012 at 4:45 PM, Whosawhatsis <[hidden email]> wrote:
Considering that on most devices, "start typing again" involves an onscreen keyboard, that might not work very well.

On Thursday, January 19, 2012 at 4:42 PM, tjhowse wrote:

How about a hovering translucent code window that fades out mostly (10-20%) when you compile, allowing a full-on look at your model, and fades back in (80-90%) when you start typing again?

On 20 January 2012 09:03, Brad Pitcher <[hidden email]> wrote:
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.


On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad



_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


Reply | Threaded
Open this post in threaded view
|

Re: Android port

Whosawhatsis
Depending on the aspect ratio, it can be up to about half the screen on a tablet. On an android phone, it can be more than half.

On Thursday, January 19, 2012 at 4:50 PM, tjhowse wrote:

I haven't used an android tablet, does the on-screen keyboard occupy the entire screen in landscape mode by default?

On 20 January 2012 10:49, Brad Pitcher <[hidden email]> wrote:
I'm thinking in terms of the easiest-to-get-out-the-door-but-usable interface right now. I haven't even got that damn thing to compile yet. ;) The bells and whistles can come later.



On Thu, Jan 19, 2012 at 4:45 PM, Whosawhatsis <[hidden email]> wrote:
Considering that on most devices, "start typing again" involves an onscreen keyboard, that might not work very well.

On Thursday, January 19, 2012 at 4:42 PM, tjhowse wrote:

How about a hovering translucent code window that fades out mostly (10-20%) when you compile, allowing a full-on look at your model, and fades back in (80-90%) when you start typing again?

On 20 January 2012 09:03, Brad Pitcher <[hidden email]> wrote:
I agree. At first I was thinking it made sense to keep everything the same as much as possible for the first release just to make things easier. It really would be completely unusable as is on a phone though.
I think it should go beyond the changes you suggest though. There should be 2-3 sections as there are now (code, view, console) but they should each fill up the whole screen and be swipeable between panels. So you code in a full screen and swipe right and compile to see the result. This is more of a handheld/touchscreen device type of interface and is about as usable as can be in my opinion.


On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith <[hidden email]> wrote:
I am not sure what is being considered for the User Interface on Android,
but may I make a suggestion?

Especially on some of the smaller-screen devices, it would be helpful if the
three main panels of Openscad were setup as three separate tabs, rather than
sections of a single screen.

Especially for the text panel, if you slice the screen in half to present it
beside the model view, then that text area is going to be very difficult to
type in.

The text panel and the model view have entirely different keyboard/mouse
controls.. it might be simpler if only one of them was on the screen at any
one time.

Just my two cents.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad



_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad


_______________________________________________
OpenSCAD mailing list

Reply | Threaded
Open this post in threaded view
|

Re: Android port

kintel
Administrator
Hi,

I just want to mention that since most of the backend is no longer dependent on Qt, it should be totally doable to write a front-end using a more suitable GUI framework. It might turn out to be less work than trying to cram the existing interface into a pad device.
Some refactoring is still needed I guess - I just fix stuff whenever I come across it (or need a low-brain task). One key test would be to get the test suite to build without Qt.

 -Marius


Reply | Threaded
Open this post in threaded view
|

Re: Android port

Brad Pitcher
That's great to hear Marius. Yeah, I was thinking it would make more sense to use the native Android interface and use the rest of OpenSCAD more like a library.

On Thu, Jan 19, 2012 at 5:18 PM, Marius Kintel <[hidden email]> wrote:
Hi,

I just want to mention that since most of the backend is no longer dependent on Qt, it should be totally doable to write a front-end using a more suitable GUI framework. It might turn out to be less work than trying to cram the existing interface into a pad device.
Some refactoring is still needed I guess - I just fix stuff whenever I come across it (or need a low-brain task). One key test would be to get the test suite to build without Qt.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad

Reply | Threaded
Open this post in threaded view
|

Re: Android port

Marius Kintel
Yeah, that would also provide more motivation to further refactor and librarify the backend :)

 ~/= Marius


On Jan 20, 2012, at 18:51, Brad Pitcher <[hidden email]> wrote:

That's great to hear Marius. Yeah, I was thinking it would make more sense to use the native Android interface and use the rest of OpenSCAD more like a library.

On Thu, Jan 19, 2012 at 5:18 PM, Marius Kintel <[hidden email]> wrote:
Hi,

I just want to mention that since most of the backend is no longer dependent on Qt, it should be totally doable to write a front-end using a more suitable GUI framework. It might turn out to be less work than trying to cram the existing interface into a pad device.
Some refactoring is still needed I guess - I just fix stuff whenever I come across it (or need a low-brain task). One key test would be to get the test suite to build without Qt.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
Reply | Threaded
Open this post in threaded view
|

Re: Android port

Torsten Wagner
In reply to this post by Brad Pitcher
Hi,

just my two cents...

if you want a quick port and stick to QT check out
    http://sourceforge.net/p/necessitas/home/necessitas/
A QT-port for Android which also takes care of dependencies.

Swiping between different panels sounds reasonable and a very good idea
to get more real estate screen space.
However, often, just glimpsing at the image at the moment of refreshing
helps me a lot to get an idea if the new code it is right or not...
That is, you might want to change something at the upper left corner of
an object but accidentally change the lower right. Only looking at the
new image, you might miss the wrong changing due to focusing at the
wrong part of the object. Debugging can become ugly and a headbanging task.

Seeing the refresh from old to new helps to spot wrong changes.

This would get lost if you have to switch between code panel...
compile... and switch back to the image panel. However, it might be
easily solved by allowing to refresh the image panel manually. Compile,
switch over to the image panel, check the old image and press refresh to
see how it changes..

Totti





On 01/20/2012 08:03 AM, Brad Pitcher wrote:

> I agree. At first I was thinking it made sense to keep everything the same
> as much as possible for the first release just to make things easier. It
> really would be completely unusable as is on a phone though.
> I think it should go beyond the changes you suggest though. There should be
> 2-3 sections as there are now (code, view, console) but they should each
> fill up the whole screen and be swipeable between panels. So you code in a
> full screen and swipe right and compile to see the result. This is more of
> a handheld/touchscreen device type of interface and is about as usable as
> can be in my opinion.
>
> On Wed, Jan 18, 2012 at 9:47 PM, Stony Smith<[hidden email]>  wrote:
>
>> I am not sure what is being considered for the User Interface on Android,
>> but may I make a suggestion?
>>
>> Especially on some of the smaller-screen devices, it would be helpful if
>> the
>> three main panels of Openscad were setup as three separate tabs, rather
>> than
>> sections of a single screen.
>>
>> Especially for the text panel, if you slice the screen in half to present
>> it
>> beside the model view, then that text area is going to be very difficult to
>> type in.
>>
>> The text panel and the model view have entirely different keyboard/mouse
>> controls.. it might be simpler if only one of them was on the screen at any
>> one time.
>>
>> Just my two cents.
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> [hidden email]
>> http://rocklinux.net/mailman/listinfo/openscad
>>
>
>
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad


Reply | Threaded
Open this post in threaded view
|

Re: Android port

Michael Ambrus
In reply to this post by stonysmith

Love the idea, thanks for the hint. There was some fuss about Qt for Android on the Android platform forum a while back. Happy to see Google didn't follow through their threat on invalidating this via the runtime linker. 

Got an Android tab yesterday for the purpose. Will play around to see how far I get next weekend. Anyone interested in joining, I'll be on IRC.

Den 30 jan 2012 06:41 skrev "Torsten Wagner" <[hidden email]>: