ubuntu-phone team mailing list archive

[Joseph Mills <josephjamesmills@xxxxxxxxxx>]

Ok SO I thought about it some more on my day off from work and this is what
I came up with,
http://www.youtube.com/watch?v=38w0XWHuFcA

I am sure that Each one of the things that are plugged /qDebuged() out
could be used and or read across dbus with ease.  It is just a matter of
how Canonical want to do It. I think and I think wrong on things that I
think about a lot.....  At any rate.  I implemented that code into my app
in under 4 hours.  And Have never touched that class till today. Seems Like
that would be a lot faster also then dealing with layouts.


Joseph




On Sun, Jul 14, 2013 at 2:05 PM, Dinko Osmankovic
<dinko.metalac@xxxxxxxxx>wrote:

> I think the best thing for desktop is to put everything from toolbars to
> the global menu. It's quite visible there.
>  On 14 Jul 2013 20:03, "Zisu Andrei" <matzipan@xxxxxxxxx> wrote:
>
>> That is why I think that it is best to look at options that just look at
>>> the screen. But I am sure that there is flaws in my ideas there always is :
>>> )
>>
>> I can't remember if it was a vUDS or here on the mailing lists, but there
>> was a discussion about that. The "options" method was preffered.
>>
>> Zisu Andrei
>>
>>
>> On 14 July 2013 18:45, Joseph Mills <josephjamesmills@xxxxxxxxxx> wrote:
>>
>>> Sorry I did not read this before the last message that I posted.  The
>>> only thing that I see wrong with what you are talking about is the Mouse
>>> stuff.  What If I have a mouse attached to a phone ? That is why I think
>>> that it is best to look at options that just look at the screen. But I am
>>> sure that there is flaws in my ideas there always is : ) . at any rate
>>> something needs to be done about the form-factor thingy.  have a good one.
>>>
>>> Joseph
>>>
>>>
>>> On Sun, Jul 14, 2013 at 1:11 PM, Martin Kaistra <admin@xxxxxxxx> wrote:
>>>
>>>> Am 14.07.2013 18:57, schrieb Joseph Mills:
>>>> >
>>>> > Yeah that is what I meant swipe is not ideal for desktops or anything
>>>> > that uses a mouse. As far as things having labels on them ie phone
>>>> > core apps. I don't think that that should matter the programmer should
>>>> > have a way to say if desktop use this else do this. It down not matter
>>>> > what the platform what matters is it does what the end user wants it
>>>> > to do. Not my personal feelings and again they don't matter. But a
>>>> > simple thing like
>>>> > If (Qt.platform ==== "Linux") do this or some sorta bool option that a
>>>> > Dev can use. Maybe a c++ dbus plugin that says what kinda device it
>>>> > is. There are many options. The import part of all this IMHO (again
>>>> > does not matter) is that nothing gets locked into one thing. What if I
>>>> > want to run this on desktop TV toaster oven that is my choice as a end
>>>> > user.
>>>> >
>>>> >
>>>> My understanding was that as part of the convergence you can choose your
>>>> layout based not only on screen size but also depending on the input
>>>> devices available. The toolbar and other SDK components though should
>>>> behave differently automatically when there is a mouse available.
>>>>
>>>> martin
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~ubuntu-phone
>>>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~ubuntu-phone
>>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
>>