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: please help. panels UI :( (Read 7637 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

please help. panels UI :(

it's so hard to use, i can't get anything to work.

I've been following/copying/trying to steal what other people have done, but it just leads in stuff that looks like poo/nothing like the original.

Is there a simple PUI i can steal/setup?.

I've reinstalled foobar way to many times now... cause everytime i try someone else's, i end up losing access to prefences, so it becomes hard to use/filled with plugins i dont use.

please help

please help. panels UI :(

Reply #1
it's so hard to use, i can't get anything to work.

I've been following/copying/trying to steal what other people have done, but it just leads in stuff that looks like poo/nothing like the original.

Is there a simple PUI i can steal/setup?.

I've reinstalled foobar way to many times now... cause everytime i try someone else's, i end up losing access to prefences, so it becomes hard to use/filled with plugins i dont use.

please help

Hello.  I just came across this excellent program about 2 weeks ago, myself.  Since that time, I've made it my mission to learn how to code so that I can customize foobar the way I like it.

I would suggest that you do  the following:

Do one more FRESH install of fb.  Then, right away, just copy the entire installation directory to somewhere safe as a backup.  You'll always have that to fall back on when things get messed up, and as you've learned, they WILL get messed up from time to time.

Then, as you go along altering, borrowing, and trying different parts of setups and codes, backup up the same directory several times as you go along, learning and experimenting.  If you have worked on something for a couple of days, and all the sudden it goes wrong, you'll have a recent backup to use.  Just copy the last good working backup right over the installed directory, and you're good to go.

As far as using a good config right out of the box, so to speak, there are many being offered here on the board.  One you might consider is the new version of Elegance.  Not that I prefer it over any of the others being offered here, but it might be easier for you to get set up and working.

Other than that, I can only encourage you to keep doing what you've been doing!  It will all come together before you know it........... at least, that's what I keep telling myself! 

please help. panels UI :(

Reply #2
As a rocket scientist, I can safely say that panels ui is more challenging than most of the stuff I do at work

Moderation: Removed full quote of previous post.

please help. panels UI :(

Reply #3
I recommend to learn and write your own stuff in Assembler, which is easier to learn.

Code: [Select]
xor eax,eax
mov pui,eax

please help. panels UI :(

Reply #4
I've had some luck with PanelsUI, but I didn't start by trying to figure out someone else's complex UI.  I recommend just starting with the default one and adding to it on your own (then coming back here to ask specific questions about the parts you can't figure out).

please help. panels UI :(

Reply #5
If you cant handle it, dont use it (this includes me, who has written the most horrible spaghetti-TAGZ-code in the past - seemed much easier though than panels UI).

- Lyx
I am arrogant and I can afford it because I deliver.

please help. panels UI :(

Reply #6
I think the biggest issue is that the wiki for panels is not exactly a tutorial, but just tells you what certain functions can do... the creative part is up to the person, but that does not help anyone make a pui.

it is akin to an html wiki that just ran down a list of all the <>'s and what they mean/do. it does not indicate anything about how the structure should go or what works in what place.

why can't someone who has coded panelsUI create a simple guide to starting from scratch and adding in a few common features, like albumart, ratings, and how to put together the most basic layout so that anyone could get a handle on it?



I certainly would get into the panelsUI world if I simply had a guide or a walkthrough on how to do something simple. I know everyone around here is all about slugging it out and trial/error learning, which is great. But this isn't something I can learn painfully when I would much rather get to the brass tacks and make something happen.
my 2 cents.
that is our karma...

please help. panels UI :(

Reply #7
I think the biggest issue is that the wiki for panels is not exactly a tutorial, but just tells you what certain functions can do... the creative part is up to the person, but that does not help anyone make a pui.

it is akin to an html wiki that just ran down a list of all the <>'s and what they mean/do. it does not indicate anything about how the structure should go or what works in what place.

why can't someone who has coded panelsUI create a simple guide to starting from scratch and adding in a few common features, like albumart, ratings, and how to put together the most basic layout so that anyone could get a handle on it?



I certainly would get into the panelsUI world if I simply had a guide or a walkthrough on how to do something simple. I know everyone around here is all about slugging it out and trial/error learning, which is great. But this isn't something I can learn painfully when I would much rather get to the brass tacks and make something happen.
my 2 cents.


I might take up a mini-tutorial guide on making a simple layout if someone doesn't beat me to it

please help. panels UI :(

Reply #8
/snipped for space/

I certainly would get into the panelsUI world if I simply had a guide or a walkthrough on how to do something simple. I know everyone around here is all about slugging it out and trial/error learning, which is great. But this isn't something I can learn painfully when I would much rather get to the brass tacks and make something happen.
my 2 cents.


There is a excellent tutorial HERE that will do just what you are looking for!  It is for ColumnsUI, but the syntax and usage is the same for both.  Check it out, and start coding! 

UPDATE:  I just ran across this really good tutorial site, give it a look-see...

Foobar2000 Scripting Tutorial

please help. panels UI :(

Reply #9
I think the biggest issue is that the wiki for panels is not exactly a tutorial, but just tells you what certain functions can do... the creative part is up to the person, but that does not help anyone make a pui.

it is akin to an html wiki that just ran down a list of all the <>'s and what they mean/do. it does not indicate anything about how the structure should go or what works in what place.

why can't someone who has coded panelsUI create a simple guide to starting from scratch and adding in a few common features, like albumart, ratings, and how to put together the most basic layout so that anyone could get a handle on it?



I certainly would get into the panelsUI world if I simply had a guide or a walkthrough on how to do something simple. I know everyone around here is all about slugging it out and trial/error learning, which is great. But this isn't something I can learn painfully when I would much rather get to the brass tacks and make something happen.
my 2 cents.
the basic.pui included in the panels UI download isn't like what you're looking for?
elevatorladylevitateme

please help. panels UI :(

Reply #10
I might take up a mini-tutorial guide on making a simple layout if someone doesn't beat me to it


I imagine there would be MANY lurkers who would appreciate it, and many non-lurkers too! 

please help. panels UI :(

Reply #11
well i think my main problem with stealing other people's configs, is i have no idea how PanelsUI wants to load images, resulting in lovely blank panels.

and i think i ended up putting those images in every folder i have linked to foobar, but it still likes blank over it.

Basic is pretty good (in the newer realeases), but would be cool if someone showed how to make such a thing, and maybe add a few panels / album art.

For now i'm back to columns (though panels has much potential) its just in columns. Creativity > coding knowledge, but it's coding knowlegde > creativity in panels .

Ohh that and trying to get decent versions of the plugins, if i knew how to code my fist idea of a plugin for foobar would be foobar-aptitude lol. No more old websites .

EDIT: also tagz seems to have worked pretty much like i would've thought, and hacking up others PUIs i can see where now playing is coming in etc and changing thats colour i can do fine, however im clueless as to how to change just about anything else .

please help. panels UI :(

Reply #12
I don't mean to offend anyone, but some people are good at and enjoy programing, and others not.  If PanelsUI is too much work or too confusing or complicated, why not just stick with ColumnsUI?  If you think you can and want to learn it, I suggest just starting with a blank slate, and try inserting some commands detailed in the wiki into your layout - maybe start with a SCPL, add a Track Display, etc, just one step at a time.  It's often easier designing something yourself from scratch than picking therough and trying to reverse engineer somebody else's code.  When you think you've gotten the hang of placing what you want where you want, maybe sketch out a scheme on paper that you want to do (or borrow a organization scheme from somebody's screenshot), and set about making it happen in the code.  It's the complete DIY spirit that makes PanelsUI so unique.

please help. panels UI :(

Reply #13
Regards to eboomer's post, I agree that the best approach is to start from scratch and build your own config. - install panels UI, delete the default code, and start with a blank canvas - and if you need to get into preferences, the shortcut key should be set to ctrl+P by default.

I don't actually think you have to be an expert programmer to learn title formatting though, you just have to experiment with code, and checkit against the references on the wiki, until you've got it how you want. If there are questions that cannot be answered by the wikis, then I can't see any problem posting up more specific questions in this forum - that's what it's here for.

to access and delete the default code, and to enter new code, then right click on the background, or the titlebar, and go to 'settings...'.

Once you have deleted it the most important part of code is this:
Code: [Select]
$panel(ID,Name,x,y,width,height,options)

link
..so check the dropdown menu for a list of panels available, and type it in the 'Name' slot exactly how you see it in the menu.

for example:

Code: [Select]
$panel(playlist1,Single Column Playlist,0,0,%_width%,%_height%,)


..will draw a Single column playlist at point 0,0 (top left), occupying the width and height of the window.

use these references too:
Panels UI
Title format reference (general code referenced - logic functions etc..)
Components page
New user guide
Main foobar wiki

I hope that helps a bit, but experimenting and reading is the best way, and ask questions here for things that you can't figure out on your own. 

-mac 

 
SimplePortal 1.0.0 RC1 © 2008-2021