General > Developers

Need help!

(1/4) > >>

golgoj4:
Ok, so after QOrbiter has hit the general user populace, a huge glaring problem has shown its face. location that it actually exists in.

As it stands now
*Rooms that one not might want set to manual, are set to manual, with new ea's added for the new media targets.
This presents a problem of both clutter in the old ui (EA's are treated as rooms, thus every device shows up as an additional room) Its really bad and I dont know how to fix it.

*When I play media on an android tablet, I get lights dimming and such. This is more likely not the desired action in this _new_ context. So its something else to be considered.

I have made changes to the qorbiter DT to allow for specifying what form factor it is (workstation, tablet, phone, md, god knows what else will be invented. watches you say?)

Now, the 'solution' i have for the moment is that they should all exist in a room called 'Mobile Orbiters' or something.
This would let them operate independent of a location they may or may not be tied to re: the automation options.
Users could still choose other rooms as normal, but this one would be specific to mobile devices.

It doesn't do much for the longer list of 'Rooms' on the old orbiter. they assume a 1 to one mapping and it doesn't seem i can change that.

And finally, I need seriously help writing the mysql queries to
*Make the 'Mobile Orbiters' Room show up when people add a QOrbiter, then add the subsequent new EA in that room
*Look at how we branch to do this as well OrbiterGen. Right now its done in php, which is fine with me for prototyping, but I feel like it would be messy to leave orbitergen spread over two places.

Thanks

Dap-P:
Langston,

in my opinion, all mobile devices can be added to multiple ea's in 1 room. But i would like to see this room 'hidden' in all other orbiters, and on the mobile device you can only select your own device.

I have no idea is this is possible, and what would be needed. just want to share my opinion.

At the moment i have very little spare time, but i would like to volunteer. I dont know much about mysql, but i know i can learn about it.

Anton

golgoj4:

--- Quote from: Dap-P on November 10, 2013, 07:54:24 pm ---Langston,

in my opinion, all mobile devices can be added to multiple ea's in 1 room. But i would like to see this room 'hidden' in all other orbiters, and on the mobile device you can only select your own device.

I have no idea is this is possible, and what would be needed. just want to share my opinion.

At the moment i have very little spare time, but i would like to volunteer. I dont know much about mysql, but i know i can learn about it.

Anton

--- End quote ---

The UI part isnt so difficult as deciding architecturally how we want to deal with devices than travel around the home (world?!) that still are part of linuxmce.

Help will be appreciated, first and foremost for creating scenarios based on device data.
Android gets x media scenarios
iOs gets y media scenarios

desktop get normal ones, etc

-Langston

Dap-P:
You made me think about that "world" comment...
Should there be a VPN client in qorbiter, well perhaps)))

Is there already a feedback of the device type (android, ios, phone, tablet) when first connecting? or should there be an option in the web admin for creating these different scenarios?

In my opinion, the scenarios should be more based on device type, instead of brand. ie: phone, tablet, full blown md
The more i think about this, i think there are only 2 different types, mobile, and full blown md.

What about bluetooth? The md can detect the bluetooth mobile device, and automaticly place it in the correct room.

Just thinking out loud,
Anton

WhateverFits:

--- Quote from: golgoj4 on November 10, 2013, 04:08:41 pm ---And finally, I need seriously help writing the mysql queries to
*Make the 'Mobile Orbiters' Room show up when people add a QOrbiter, then add the subsequent new EA in that room
*Look at how we branch to do this as well OrbiterGen. Right now its done in php, which is fine with me for prototyping, but I feel like it would be messy to leave orbitergen spread over two places.

--- End quote ---
I'm pretty good with SQL. What areas are concerned here? Is this all in the orbitergen?

Navigation

[0] Message Index

[#] Next page

Sitemap 
Go to full version