Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_looks 2.0 (RC1) (Read 287430 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_looks 2.0 (RC1)

it's finally here!

[span style='font-size:21pt;line-height:100%']Foo_looks 2.0[/span]

- advanced GUI interface for FB2k with LUA script integration

help us test release candidate 1:

download here

installation guide here (important - you will need the LUA dll's)

---

features list:

- access to 'every' fb2k button & menu command from your 'look'
- use full TagZ code to format your text fields
- amazing LUA scripting support for advanced features and interactivity
- support for the 24-bit PNG graphics format including support for the alpha channel
- custom z-layering of the graphics in your looks
- drag & drop files/folders to append to the playlist

advanced features now possible (using LUA):
- playlist display
- rotational volume control
- sliding drawers (as featured in wa3 skins)
- multiple sizes/layouts at the touch of a button

scripts in development:
- window scroll bars (mainly for playlist display)
- click-sliders (like those that set FM/MW/LW on a radio)

and more....

for information on how to design your own look, see our resource pages

---------------
[span style='font-size:14pt;line-height:100%']Looks:[/span]

so far, there are only three or four 2.0 compatible 'looks'.
after all, we're only a very small dev. team.

these are:

foo_looks default - a showcase of features for designers to see what can be done with the current build
author: danZ
download: included with the plugin



----------------------
[span style='font-size:14pt;line-height:100%']Documentation:[/span]

we are currently in the process of writing extensive tutorials, guides & references.

so far we have some fragmented documention, and an almost complete tutorial on our resource pages

over the next week, we plan to update these pages regularly and build a very comprehensive guide to using & designing your very own 'looks'

---
[span style='font-size:14pt;line-height:100%']Links:[/span]

designer's resource page


-----

we hope you enjoy it!!

plugin developer: danZ
tech support, tutor & webmaster: tk32

if you have any questions/problems/requests/thanks/etc... then you can contact the team

email me:
or join us on ICQ (486325)

foo_looks 2.0 (RC1)

Reply #1 –
looks great, very nice, thanks !

for danz look: would it be easy to add a close button ? to save the currently used size on foobar close ?

and overall, to add a button/menu to change the look with a click somewhere on the look ? without opening the menu/pref/look and setting another primary/secondary look and swap ?

haven't tested tk32's look now...

foo_looks 2.0 (RC1)

Reply #2 –
A bit resource heavy here. Uses 15-100% cpu with std look.  XP1500+.
Looks neat tho 

foo_looks 2.0 (RC1)

Reply #3 –
Quote
A bit resource heavy here. Uses 15-100% cpu with std look.  XP1500+.
Looks neat tho 

Is that on a fresh start?  I've noticed that the resource usage might be creeping up as you switch looks on the fly.

How is the resource usage on the mini layout which doesn't have the spectrum display?

foo_looks 2.0 (RC1)

Reply #4 –
Quote
looks great, very nice, thanks !

for danz look: would it be easy to add a close button ? to save the currently used size on foobar close ?

and overall, to add a button/menu to change the look with a click somewhere on the look ? without opening the menu/pref/look and setting another primary/secondary look and swap ?

haven't tested tk32's look now...

There is no state persistence at the moment and something I'm trying to figure out how to best implement.

For now you could add this to the overrides section in the look prefs.

Code: [Select]
section look_one_presets
int startLayout layouts.standard


The choices are

layout.mini
layout.compact
layout.standard
layout.cover
layout.tv

foo_looks 2.0 (RC1)

Reply #5 –
cpu is high for the default skin - you're right

try my fooAMP skin instead


and  can you please report cpu usage for my fooAMP skin

tell me the % used for big mode & small mode

i'm trying to optimize the code since my cpu is quite old also



also

look inside the ski near the top for handy presets

just remember to save changes

Code: [Select]
// presets section//
section presets
int default_mode  0 // 0 = small, 1 = expanded
int id3_headers  1 //
int smart_tags      1 //
int spectrum      1 // 1 = on
int albumart  0 // 0 = off
int always_on_top  1 //
int small_font  0 //
int minVolume  -40
int albumart_width      70
int albumart_height    this.albumart_width
int time_display      1 // 1 = remaining time, 0 = elapsed time
int use_tracknumber    1 // 1 = use id3 tracknumbers if present, 0 = always use playlistnumber


ehehe, damn tab characters don't show up in the forums.

the layout is nicer in the ski

------
new skin in development

foo_looks 2.0 (RC1)

Reply #6 –
thx for the tip danz. your look seems a little more cpu intensive (10% usual, jumping up to 40% at times. )

tk32, very low cpu usage (0-5% with both looks, xp2600 here...); just couldn't find the expand button without looking the code (my screen is a little bit too dark...)

foo_looks 2.0 (RC1)

Reply #7 –
if you want to free up some cpu using the default look, open the ski and edit the following:


section grips
int layer 2
list rect int {0,0,7,7}
// list transcolor color.red
list srcoff int { 392 0 }


you need to add the // to the transcolor line

if you are too lazy, just download the modified version here: foo_looks.ski

it'll make the grips look strange, but cpu will drop to about 5%


we're looking into the problem now

foo_looks 2.0 (RC1)

Reply #8 –
Quote
thx for the tip danz. your look seems a little more cpu intensive (10% usual, jumping up to 40% at times. )

tk32, very low cpu usage (0-5% with both looks, xp2600 here...); just couldn't find the expand button without looking the code (my screen is a little bit too dark...)

thanks for the report

i'll make the button lighter when i update

foo_looks 2.0 (RC1)

Reply #9 –
Quote
thx for the tip danz. your look seems a little more cpu intensive (10% usual, jumping up to 40% at times. )

tk32, very low cpu usage (0-5% with both looks, xp2600 here...); just couldn't find the expand button without looking the code (my screen is a little bit too dark...)

Grab the beta again, I update the graphics and config file to remove the transparency on the seek grip.  It looks like GDI+ has a pretty big overhead for blitting using a transparent color key.

I'll see what I can do about that if anything.

foo_looks 2.0 (RC1)

Reply #10 –
new build - fixed the cpu drain of the default look


download here


btw designers, don't panic - my skin uses lots of transparency, and still has a low cpu footprint

it's because danZ was using bitmap graphics

foo_looks 2.0 (RC1)

Reply #11 –
Quote
if you want to free up some cpu using the default look, open the ski and edit the following:


section grips
int layer 2
list rect int {0,0,7,7}
// list transcolor color.red
list srcoff int { 392 0 }


you need to add the // to the transcolor line


it works, but looks pretty bad... I'll keep the good looking wasting version until there is a fix (or work out square buttons... oh it's done; man you're fast !)

Thanks and good night !

foo_looks 2.0 (RC1)

Reply #12 –
please don't hesitate to ask about any.....

questions
problems
bugs
suggestions
requests

in this forum

we need to know what you think

both danZ & myself check the forums daily, so you will usually get a quick reply

foo_looks 2.0 (RC1)

Reply #13 –
Hi,

I use the fooAMP skin and have a suggestion.

I like the progress bar in the foobar2000 seek bar since it updates on the fly where you are jumping to, if this same behaviour could be implemented into looks2 (and indeed the fooAMP skin) this would be great.

thanks.
 

foo_looks 2.0 (RC1)

Reply #14 –
Dan, Tom, thanks for your work.
I'll update foobarlooks.tk as soon as I've some spare time.

foo_looks 2.0 (RC1)

Reply #15 –
Quote
Hi,

I use the fooAMP skin and have a suggestion.

I like the progress bar in the foobar2000 seek bar since it updates on the fly where you are jumping to, if this same behaviour could be implemented into looks2 (and indeed the fooAMP skin) this would be great.

thanks.

if i understand you correctly, fooAMP already does this

if you click anywhere on the progress bar it jumps to that time


let me know if you meant something different, i may have misunderstood

EDIT:

after thinking about this some more, i realised you meant 'realtime progress drag'

it can be done, easily, but it makes the sound go all choppy

i never liked it - that's why i programmed my grip to jump to the time when you release the mouse button

but as a special request i can code it for you

custom fooAMP (realtime progress update)

overwrite fooAMP2.ski with the one above

foo_looks 2.0 (RC1)

Reply #16 –
Sorry, i meant the tooltip that comes up that tells you the time currently at the point where you are dragging to, with the current fooAMP design you have to guess where you are dragging to.

also, the albumart isn't transparent as in previous versions, this would be appreciated also.

foo_looks 2.0 (RC1)

Reply #17 –
Quote
Sorry, i meant the tooltip that comes up that tells you the time currently at the point where you are dragging to, with the current fooAMP design you have to guess where you are dragging to.

also, the albumart isn't transparent as in previous versions, this would be appreciated also.

dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

i'll think about where the best place to show it is.

foo_looks 2.0 (RC1)

Reply #18 –
having a foolooks2 control of "status bar" which puts this info in, whilst having user defined text (i.e. the %artist% - %title% display) at other times could be sensible.

foo_looks 2.0 (RC1)

Reply #19 –
Quote
dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

Hey tk32
How about just having it overtake the current time display.


On another note, great update, but there's one feature I'd like to see: a toggle button for the look to pop up instead of the main GUI.  It's just to difficult having to search through a menu for fewer options than the main interface gives.

foo_looks 2.0 (RC1)

Reply #20 –
Quote
Quote
dynamic tooltips aren't possible yet, sorry


however, i am able to display the jump-to time somewhere else in the skin

Hey tk32
How about just having it overtake the current time display.


On another note, great update, but there's one feature I'd like to see: a toggle button for the look to pop up instead of the main GUI.  It's just to difficult having to search through a menu for fewer options than the main interface gives.

sure

i'll add realtime progress time update now i realise people would like it

i'll post the update (with some other polishes) later

as for your other request, i'm not sure i understand what you mean?

can you explain it some more please

foo_looks 2.0 (RC1)

Reply #21 –
Hey Danz!

I tried use new release foo_looks (2.0 rc1), but on start foobar next text displayed in console

INFO (foo_looks) : Sprite 'background' is visible with empty rectangle
INFO (foo_looks) : Sprite 'albumart' is visible with empty rectangle
INFO (foo_looks) : Sprite 'spectrum' is visible with empty rectangle
INFO (foo_looks) : Sprite 'rolltext' is visible with empty rectangle
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 5 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'seekSliderImpl'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'albumartgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 9 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'volumeSliderImpl'
INFO (foo_looks) : AssetManager:Dumping unused image 'H:\Audio\Carpenters\(1971) Carpenters\cover.jpg'
INFO (CORE) : opening file for playback :
INFO (CORE) : location: "file://H:\Audio\Carpenters\(1983) Voice Of The Heart\09 - You're Baby Doesn't Love You A.mp3" (0)

I solve this error in next way:

change 0.0 to 0,  100.0 to 100

in  foo_looks_common.ski

Is it correct?

I have W2k russian, foobar 7.7a.

pIv

foo_looks 2.0 (RC1)

Reply #22 –
I decided to give it a try. No problems
Just one thing - could you change font used in "Overrides" title and section in Preferences to Tahoma?

foo_looks 2.0 (RC1)

Reply #23 –
Quote
I decided to give it a try. No problems
Just one thing - could you change font used in "Overrides" title and section in Preferences to Tahoma?

For the default look it will work to put this in the overrides preferences

Code: [Select]
//Type in skin independent overrides here
section globals
string fontname "Tahoma"

foo_looks 2.0 (RC1)

Reply #24 –
Quote
Hey Danz!

I tried use new release foo_looks (2.0 rc1), but on start foobar next text displayed in console

INFO (foo_looks) : Sprite 'background' is visible with empty rectangle
INFO (foo_looks) : Sprite 'albumart' is visible with empty rectangle
INFO (foo_looks) : Sprite 'spectrum' is visible with empty rectangle
INFO (foo_looks) : Sprite 'rolltext' is visible with empty rectangle
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 5 in string "..."
ERROR (foo_looks) : Sprite 'seekgrip' Error(s) loading script 'seekSliderImpl'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'albumartgrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `0.0' at line 18 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'slider'
ERROR (foo_looks) : malformed number;
  last token read: `100.0' at line 9 in string "..."
ERROR (foo_looks) : Sprite 'volumegrip' Error(s) loading script 'volumeSliderImpl'
INFO (foo_looks) : AssetManager:Dumping unused image 'H:\Audio\Carpenters\(1971) Carpenters\cover.jpg'
INFO (CORE) : opening file for playback :
INFO (CORE) : location: "file://H:\Audio\Carpenters\(1983) Voice Of The Heart\09 - You're Baby Doesn't Love You A.mp3" (0)

I solve this error in next way:

change 0.0 to 0,  100.0 to 100

in  foo_looks_common.ski

Is it correct?

I have W2k russian, foobar 7.7a.

pIv

Hum, I'll have to look into this as it came up before with respect to locale settings.  I'm not sure if lua can be set to respect different locales.