Questions about the Sage Full Client Architecture

[dinki]

Originally Posted by jusjoken

Absolutely the touch part is something that needs work and as well some type of added swipe listener would be a good project. I have the guts of a in place menu in the Quick Launch Menu that could be leveraged for that functionality. Unfortunately I do not have a mobile android device so it may be difficult to convince the wife I need one so I can test Gemstone

k

You could try the Andy Android emulator if you have a windows box. http://www.andyroid.net/

[dranockcir]

If I may chime in, I switch my STV to the version 3 one, see the pictures, that's a Nexus 7 2013 sitting on my laptop next to my desktop. It is easier to navigate than the version 7 STV and with the popup menu that Sean dropped in there it makes it pretty darn usable. The version 7 one is nice and all and looks great on the TV but it is a bit much on a small screen.

I absolutely LOVE the placeshifter ability of Sean's Android miniclient. I had been hoping for an Android placeshifter for years and now it's here.

I use the placeshifting everyday practically to connect to my server at home.

There are two types of android devices ones that attach to your TV and stay there, controlled by a remote, keyboard, mouse, etc. and ones that you carry around with you and you use your finger to touch and slide to control. It would be cool if you could detect if you were fixed or portable and load the appropriate STV.

[Fuzzy]

Originally Posted by dranockcir

There are two types of android devices ones that attach to your TV and stay there, controlled by a remote, keyboard, mouse, etc. and ones that you carry around with you and you use your finger to touch and slide to control. It would be cool if you could detect if you were fixed or portable and load the appropriate STV.

Once the STV is configured and set for a given client, it's settings are store on the server tied to that device's MAC address - so you just need to choose your mobile friendly or tv friendly UI once, and any time that device connects, it will use the same settings.

[jusjoken]

Originally Posted by dranockcir

If I may chime in, I switch my STV to the version 3 one, see the pictures, that's a Nexus 7 2013 sitting on my laptop next to my desktop. It is easier to navigate than the version 7 STV and with the popup menu that Sean dropped in there it makes it pretty darn usable. The version 7 one is nice and all and looks great on the TV but it is a bit much on a small screen.

As info....the new windows installer has the V3 STV removed....so you may need to keep a copy somewhere going forward OR create a STV3 plugin so you can install it if that's what you want to use with V9.

[dranockcir]

Originally Posted by Fuzzy

Once the STV is configured and set for a given client, it's settings are store on the server tied to that device's MAC address - so you just need to choose your mobile friendly or tv friendly UI once, and any time that device connects, it will use the same settings.

Hmmm, I thought if I logged in as user XXX I would get the default v7 STV the first time, I change it to v3 STV and all is good. Then, if I log in as user YYY on the same device I get the default v7 STV again. I'll have to test that out so I know what I'm talking about.

[dranockcir]

Originally Posted by jusjoken

As info....the new windows installer has the V3 STV removed....so you may need to keep a copy somewhere going forward OR create a STV3 plugin so you can install it if that's what you want to use with V9.

Ahh, ok, good to know.

[stuckless]

Originally Posted by jusjoken

As info....the new windows installer has the V3 STV removed....so you may need to keep a copy somewhere going forward OR create a STV3 plugin so you can install it if that's what you want to use with V9.

We should probably just repackage the V3 STV as a plugin, that way people can optionally install it if they want. (I see that's pretty much what you already said... I guess I second the thought on making it a plugin )

[Tiki]

Originally Posted by stuckless

We should probably just repackage the V3 STV as a plugin, that way people can optionally install it if they want. (I see that's pretty much what you already said... I guess I second the thought on making it a plugin )

It would probably make sense to have two default UI's (one optimized for TV and one for mobile) as part of the default install package. These could be the v7 and v3 UI's or something new.

Then the configuration wizard that runs on first launch could be updated to select which UI to start with. Since the wizard is actually part of the UI (stv), this would require updating the v3 and v7 UI's.

[Fuzzy]

Originally Posted by stuckless

We should probably just repackage the V3 STV as a plugin, that way people can optionally install it if they want. (I see that's pretty much what you already said... I guess I second the thought on making it a plugin )

That should be pretty easy in the v9 repository (since it would have no purpose in the v7 one).

[stuckless]

Originally Posted by Tiki

It would probably make sense to have two default UI's (one optimized for TV and one for mobile) as part of the default install package. These could be the v7 and v3 UI's or something new.

Then the configuration wizard that runs on first launch could be updated to select which UI to start with. Since the wizard is actually part of the UI (stv), this would require updating the v3 and v7 UI's.

Maybe it would make sense to have the first STV be Wizard.xml, and it goes through the process and then asks the user if they are on a touch device (if we can't figure it out), and if so, it automatically installs the default "touch" enabled UI (which could be STV V3).

I think the goal from my perspective is to allow the mobile STV to evolve at a different pace than the core packages, and at the same time cutting down on the size of the core packages. ie, we probably only need to ship with 1 main STV and then have the other ones installable on the fly.

If something like Wizard.xml was the main STV that only provided configuration, then in theory ALL other UIs even STV7 could actually be a plugin and evolve at a pace separate than the Sage.jar and other components.

[Tiki]

Originally Posted by stuckless

Maybe it would make sense to have the first STV be Wizard.xml, and it goes through the process and then asks the user if they are on a touch device (if we can't figure it out), and if so, it automatically installs the default "touch" enabled UI (which could be STV V3).

I think the goal from my perspective is to allow the mobile STV to evolve at a different pace than the core packages, and at the same time cutting down on the size of the core packages. ie, we probably only need to ship with 1 main STV and then have the other ones installable on the fly.

If something like Wizard.xml was the main STV that only provided configuration, then in theory ALL other UIs even STV7 could actually be a plugin and evolve at a pace separate than the Sage.jar and other components.

Makes sense to me - someone would just need to break out the configuration wizard as a separate UI/STV/XML file.