Log from #neuros IRC channel

and i've got many questions.. like how do we turn off/on the gpu so DSP can show through, etc

should we even be using Davinci, amybe the Open Source supported omap with fast DSP co-cpu is better, etc

aren't we going to first decide for or against GPU and then these questions you just mentioned make any sense ?

i do know however, DMA will not give us anything we actually need.

[01:18]

nerochiaro: sure.. but thats why i'm confused. He gave no rebuttal

[01:18]

Let me prompt for one, we'll see how it gos

[01:18]

goes

[01:34]

allyourrejects: JohnDesigner: post out

[01:35]

i'm starting to think we should hit the ML with this discussion too

[01:36]

i wanted to hold off on that

[01:36]

sure

[01:39]

roger

[01:40]

nerochiaro's replies are always so elegant

[01:40]

i'm just a mass of blah all over the place...

[01:44]

allyourrejects: thanks, i try my best

[01:45]

indeed, a true gentleman and scholar that nero is

[01:46]

except when i use cuss words mistaking them for other words

[01:47]

understandable

[01:48]

i only speak in profanity, which is why I dont go to chuch anymore.

[01:50]

JohnDesigner: fear getting smited by divine wrath if you do enter a church ?

[01:55]

i should clarify that i "I am not welcome" anymore :)

[01:56]

<ljp>

when is 'arizona' scheduled for 'update' release?

[01:56]

which is okay

[01:57]

ljp: what version do you have? There was a new update in the last day or so

3.33-y.2r.upk (2008-02-27)

<ljp>

i thinks it the old style of interface, I havent updated in weeks

ljp: "updater" release, you mean ? in the sense of getting picked up automatically by the network updates from the OSD ?

<ljp>

yes

if you use the 'Dev' setting in Firmware upgrade

<ljp>

is there a manual update?

<ljp>

ah. ok

[01:59]

ljp: the auto-update to arizona is still some weeks off, but you can already manually update to it if you feel like it

[01:59]

ljp: i use the "Dev" and "check now" options

[02:00]

JohnDesigner: you manually updated to AZ once, that's why now you get all AZ updates from the app

[02:00]

JohnDesigner: the people like ljp who are still on old software, will not get them until we release AZ official

[02:00]

ljp: are you not using AZ already?

[02:01]

nerochiaro: i see, I assumed ljp was using Az already

[02:05]

<gremlin[it]>

g'morning all !

[02:30]

nerochiaro: what app or class did we use the QPointer discussion in?

[02:32]

allyourrejects: can't recall. grep

[02:32]

;)

[03:52]

i almost have OSD toolchain compiled for PS3

[03:55]

allyourrejects: dude, you love to waste your time,don't you ? ;)

[03:57]

you tinker. thats how you learn and become the best ;)

<gremlin[it]>

allyourrejects, u'll use PS3 to build software for OSD ?!?!?

yep

allyourrejects: it's actually pretty neat, i was just kidding

i couldn't pass up the ability to compile farm that stuff

its like... a whole extra machine in that black box

I am at a loss here about this barreling menu issue. mainly I didnt know it *was* an issue, is it?

i think it'll be ok

JohnDesigner: it's not. yet

it may or may not be. we don't know until we try

it probably won't be

i wouldn't suggest it for file browser..

to tell the truth, I am not in love with the barreling menu, but some type of animation seeming activity is needed.

allyourrejects: nope, not for file browser.

if just for main menus, it's ok

actually, I am not proposing any change here

probably

JohnDesigner: you are. currently it's not barreling

[04:02]

sorry to interrupt this discussion, i got a question for allyourrejects first

[04:02]

true, so one change to the color of the top and bottom list items on 5 item menus

he's not here

nerochiaro: sure

he.. uhh...

allyourrejects: none of us are here

[04:02]

we are just constructs of senses.

nvrmind.. couldn't think of anywhere useful to be.

allyourrejects: pick up a moment the XIM design. you see the items are of two types, some bold, some not. how do we mark the ones that are bold ?

so that we know that we have to draw them bold ? custom model ?

nerochiaro: set them bold with setFont

[04:04]

allyourrejects: sure, but how do i identify them as "special" when adding them to the menu so that the menu knows that it shall draw them as bold ?

[04:04]

you set the font before you add them

hmm

you know if its bold or not. Context Menu items don't magically appear..

(they aren't read from file, etc)

set the font after you add them..

QAction::setFont(QFont)

ya,i get it

had me though.

what if i need to know if they were special after i activate them ?

i had to go look it up ;)

check the font?

sound a ugly hack

wait wait

you know they are special

how ?

why would you have to look it up?

because you created it

gee, thanks. that's right :)

ok, i'm finished

JohnDesigner: it's ok to try the barreling on the 5-item main-menu menus

should work

oh, thought that might be sarcasm

heh

allyourrejects: nah, it was ok. i was thinking in terms of items loaded from file. it's not the case (for now)

so case closed

shouldn't ever be the case

we'll see

Context menu's are completely context related

just wait

lol

but let's not worry now

I'm going to reject it..

wow... just noticed the irony in that..

said the one with such name

speeking of which

where the hell is crweb..

[04:10]

he was rejected

[04:10]

or got eaten by a PS3

[04:11]

I'd love to chat, but I want to sleep today.. its been a while

[04:12]

going to get in the upgrade boot stuff real quick and finish up work ;)

[04:12]

allyourrejects: sure. get the sleep you need. you're no use dead ;)

[04:12]

not until i finish my necromancy studies, that is

nerochiaro: I dont understand "try". its on latest FW now exactly as is I just found out

JohnDesigner: on the TORFU, you mean ?

the only adjustment needed is to spec a slightly different color.

JohnDesigner: you're talking about TORFU

nope, AZ. its just that...

JohnDesigner: we don't do that color shift on all the 5 items now

the two colors of the non selected items are very close to each other.

but they are different.

JohnDesigner: really ? if they are, then it's absolutely no problem

JohnDesigner: to me, they look the same on video, though

didn't check code

<cr64>

oooo... that was smooth..

[04:16]

ya, Nick told me that there are 3 colors White, 0x66, 0x45

[04:17]

so just altering the 66 and 45 is all that needs to be done

[04:17]

if that's so, we are ok

[04:17]

if he's to be trusted

[04:18]

i mean, if he understood the questions and you understood the answer

[04:19]

i'm looking at the code, and i only see it's painted in a way if it's active item, and in another if it's not active item

[04:19]

there's no provision for two different inactive colors

[04:20]

unless i'm missing something, that is

[04:21]

there is disabled, inactive, and active

[04:22]

normally

[04:22]

allyourrejects: i'm not talking about that

[04:22]

ok

[04:23]

swing and a miss

[04:23]

allyourrejects: i'm looking in the delegate, to see how it paints items. and it just paint the active item in a way, and all the others in another.

[04:23]

s/active/selected/

[04:49]

nerochiaro: I'm quite sure he knew what I was asking.

[04:49]

well, then either i looked wrong, or he looked wrong

[04:49]

in the code

[04:50]

I asked "what is the color of the nonselected text in the main menu"

[04:51]

and he pasted two triplets

[04:51]

the 66 and 45

[04:52]

which initially threw me because I didnt see the 2 non selected colors were close in hue

[04:52]

or that was BS

[04:53]

looking at the menu on-screen right now and the nonselected text in the main menu are one color not two.

[04:54]

anyway, i'll update this spec and we'll go from there.

[04:55]

allyourrejects: BTW, I found out that the P.B list suspected of being squished actually was.

[04:55]

allyourrejects: it will be revised to not be squished and only show 7 items.

[04:55]

JohnDesigner: it may not have been BS, just misunderstanding. it was my first theory

[04:56]

nerochiaro: I'll go with that

[04:56]

although given the two colors of the triplets pasted, it was not a misunderstanding

[04:56]

when I was asking for one.

[04:57]

as usual I'm sure I am not understanding some key tech detail. no matter.

[04:57]

<crweb>

how did it get squished?

<crweb>

something is def. funny then.. cause fonts should clip

crweb: no idea. maybe the listview was forced to fit to a vertical dimension AND forced to show a certain font size.

just wildly guessing tho

<crweb>

but font size should not be squished

<crweb>

i can't be. thats not how they render

JohnDesigner: he probably gave you the two tripets for some other unrelated thing

JohnDesigner: since the didn't understand what you asked for

nerochiaro: could be.

crweb: maybe it's rendered bigger, and then the whole item "image" is squashed

<crweb>

shouldn't. it should clip...

[05:00]

i know, i was just gueesing

[05:01]

JohnDesigner: was the issue solved regarding that email about items being too big in main-menu ?

[05:03]

nerochiaro: AFAIK so far they have. I did not hear any other discussion on the topic.

[05:03]

nerochiaro: I did speak with corlin first to devise the method of adding support for

truncating and name scrolling to the main menu

which will help multi-language translations also

ok then, that was my main concern. if you are ok with them, we're all ok

yep, sounds good to me. thanks for asking

[05:05]

in those main menus, we have enough room for 95% of typical app names, so were good.

[05:07]

let me check someing here..

[05:08]

if a "base color = 255, 255, 255 (white)"

[05:09]

and a related spec is "color = 10% of base"

[05:09]

what color do you think that is light or dark grey?

[05:10]

gah, I'm going to need to list the color # with the %.

[05:16]

<crweb>

you can use # or x,x,x in Qt

[05:16]

<crweb>

i believe i have html color turned on

[05:18]

I have been using # all along, but for certain color schemes like the ribboning text on the main menu,

[05:18]

I agreed to make the color spec read as a % of base

[05:19]

which matches how I design a given screen anyway.

[05:20]

design most of the OSD screens that is. Where the text is mostly shades of a given color.

[05:20]

50% of white is same as 50% of black, no ?

[05:20]

yes

[05:21]

10% of white is almost black.

[05:21]

if 100% white is the base.

[05:21]

this could be a mess, maybe not

[05:22]

we have two functions called "darker" and "lighter" on the QT color class. each take an integer "factor" parameter. doc says "If the factor is greater than 100, this functions returns a lighter color. Setting factor to 150 returns a color that is 50% brighter."

[05:22]

darker does the opposite (which is the same as calling lighter with a value less than 100)

[05:23]

in tech speak that i'm sure you can grok, what it does is "The function converts the current RGB color to HSV, multiplies the value (V) component by factor and converts the color back to RGB."

[05:27]

JohnDesigner: still there ?

[05:27]

or did i scare you away ?

[05:27]

I see for the most part. That explained why nick expressed "lighter" when I described what I would do for a % spec

so if White=base color

exact middle grey

white.lighter(150)

would be specified as 150%

ah, righto

hrmmm

sorry, white.darker(150), or black.lighter(150)

or white.darker(50) but that's confusing

latter one mean 50% LESS dark

but it's better to use lighter than

<crweb>

thats one of those is the cup 1/2 full or 1/2 empty things

wonderful, more variables ;)

<crweb>

i suggest the term "Make it look like this" ;)

JohnDesigner: you just say "i want this 50% lighter" or i want this 50% darker

it will work

alright, I'll just design the colors so they follow the scheme of percentatges of base and spec it the easiest way

[05:31]

nerochiaro: spec like you just stated.

[05:31]

JohnDesigner: ok

[05:32]

if base=white (which is the highlighted item on most screens, white)

[05:32]

90% darker = almost black

[05:38]

from this point forward, every color in the GUI shall be the same shade of Orange.

[05:38]

including the background

all orange ?

everything

;)

a citrus GUI

orange, tangerine, lemon-ish

all Orange all day

easier that way ;)

an orange a day, makes the doctor go away

or was it apples ?

[05:46]

apples

[05:46]

oh well, works with oranges too. they have more C vitamin to boot

[05:46]

with all Orange, we will get a bug stating nothing rhymes with it

[05:48]

nothing rhymes with orange ? that's strange ?

[05:49]

nope

[05:50]

blame my sucky pronounciation, i just looked at the letters

[05:50]

of the near million words in the English language, nothing rhymes with Orange

[05:50]

"strange" does, appearently

[05:51]

as does change, appearenly

[05:51]

nerochiaro: can you verify my above base/% sample spec?

it's ok. if base is white, 90% darker is almost black

or did you mean anyhting else ?

cool thx

nope that was it

[05:53]

and Strange and Change do no rhyme with Orange. similar composition, yes, but the pronunciations are such that one can't even mangle them to be called rhyming.

[05:54]

wow cool, i must have a very crappy pronounciation then, because when i say them they rhyme

[05:54]

you are giften my friend

[05:55]

gifted that is

[05:56]

hello everybody

[05:57]

is thr anyone workin on widgets for neuros

[05:57]

bimzie: what kind of widgets ?

QT4 ones

well i wanna develop some custom widgets having some labels some image

bimzie: you can do that

well yes

bimzie: we already use various widgets like that

[05:59]

ri8

[05:59]

i've seen them

[05:59]

but i wanna ask dat can v inetgrate these widgets with qt4 designer

for now, you can just put qwidgets in designer in their place, and use the "promote" feature of designer. later when it's all more stable, we may integrate them into designer

can u name any widget using multipe widges

bimzie: every screen you see is a QWidget containing multiple widgets

didn't get it....

[06:01]

i mean the designer part

[06:02]

cuz if i open any ui form in designer it doesn't display it properly and dats understandable....

[06:02]

so how cud i integrate them with qt4 designer

as i said, you place QWidgets or QFrame in place of your custom widgets, and then use the "promote" feature of the designer. this is what we do now too

they will not appear like on the OSD, but the size and layout will be the same

ahan

lemme check

[06:04]

check linux-r3-main-app/aplayer/src/forms/naudioplaying.ui for example

[06:05]

k

[06:06]

and sorry if i keep askin stupid questions again and again... as m new to neuros....

[06:07]

ok and whr shud i place it..?

[06:08]

nerochiaro u still thr?

[06:08]

yes

where should you place what ?

your custom widget ? you can place wherevery you want

as soon as you reference it from the .ui files, it's ok

look u didn't get my question let me ask it again.....

i suggest initially to keep it together with the application(s) that are going to use it

[06:10]

no man... :)

[06:10]

listen lets say i wanna integrate naudioplaying.ui with qt4 designer

[06:11]

so wot shud i do...

[06:11]

i don't understand what you mean with "integrate naudioplaying.ui with qt4 designer"

do you want to be able to put naudioplaying widget inside another widget ?

no

ok temme a thing

u guys use designer for widgets development?

and designer i mean qt4 designer

yes, we do

naudioplaying.ui was done in QT designer