The castbars below your UF, is that Quartz? Or the castbars from Pitbull (assuming it is pitbull, which I think it is). I've been trying to get mine set up that way - or similar - but mine keep overlapping (Player is set ok, but the Targets casting bar runs into it). Would you mind sharing your SavedVar on the positions? Or telling me where the anchoring is set etc?
To reply to those feeling different frameworks will lead to bloat, be highly in-efficient:
I've yet to use Ace3, I use Ace2, no Ace, don't think I have Dongle on my machine. I also have Rock. The memory load is practically the same give or take a few kb higher or lower (depending on what I am doing :P aka Raids will make the mem usage go up).
I am an end-user and aspiring developer, I have a lower-end machine nowadays (3 yrs old, yep, low end). So resources matter to me, but even on a high end system it would matter. To be very frank, I don't think I still care about all the frameworks, all I know is - THEY WORK. And using non-frameworked addons that fulfill the roles of my frameworked addons, leads to a much higher resource demand. So all-in-all, despite the confusion - which is subsiding slowly, it's a good change. It'll take some time, as all changes do, but in the end, it will lead to a more streamlined, better resource use UI (UI entailing all addons, personal definition given to avoid confusion on terminology)
Less is better, isn't that the going thought in addon development pertaining to sizes, be that file-size or resource usage size. At first, I too thought this change would be bad. I feared bloat, but after giving it a whirl, it's far from bad. I don't see a negative change in this, the fact is: Developers are constantly trying to improve, they battle without end to cram as much functionality as possible into as little as possible resources and sizes. And some things just reach a limit, so certain features can't be implemented, more addons get written, frameworks get bigger to accommodate more wishes, etc. This "split" was most likely inevitable, but it won't be a bad one. It's a bold gamble, indeed, but I am certain it will prove to be a good move. Though we're all in for a bumpy ride, until all settles down.
PS. I apologize for the slight off-topic, the length and the soap box. I've just been reading so much drama, so much negativity or very technical explanations. I just wanted to voice my opinion calmly and hopefully as unbiased as possible, I solely based my statements on my own experiences. I hope that the devs of all addons and frameworks will find this post at least a bit nice, since most of the devs have gotten a tun of negative criticism spewed at them in the last few days.
So people don't think it's all issues, I've been running the Rockified versions of all Ckknight's addons, and other then an issue in Cart (which might be my own fault) I've yet to get an error, however, I couldn't get the addons to work without disembedded all libs, but running partially embedded and partially disembedded clashes, which was to be expected.
Alright then, for those not wanting to use search.
Ckknight, the creator of PitBull, Cartographer, CowTip, Parrot and Fubar (and a tun more sorry for forgetting some btw), decided to change libraries used in those, he is now using Rock as framework, no longer Ace2. This comes with its own GUI settings panel, Rock Gui, which is what is displaying the icon.
Using any of the now Rock-based addons, will require you to use LibRock (and the other Rock libs forming the framework) just like before when you needed Ace2 for the aforementioned addons.
Wanna use Pitbull and Cart, then you're stuck with Rock - to keep it short.
No icon layout?
Are you planning to do everything with just keys and do them all from memory?
That's hard, especially if you're a pala (which usually has a LOT of buttons)!
Anyway, still trying to find the time to set up an UI of my own, so if I have some questions some time, can I message you? (It's always easier to explain things in our native language.)
Well with no icons I meant.. I don't know what I meant. Probably no icons as portrait, no fubar icons etc.
(And sure, if I can answer it, sure. But I am not too well known with these things yet.)
Alright, Textures and imported them through shared media, works fine.
I was just wondering about borders that one makes customized. I noticed when I opened some borders.tga files, that they all follow a similar layout on the image canvas itself. I've looked around some, but couldn't point the answer to my question.
What are the lay-out rules for borders? Do you always start with Vertical Left, Vertical Right etc? Are there dimension restrictions (eg. a border can't be wider than 10px).
I am asking this because I wanted to try and tinker with EePanels to use my own vector textures, due to the location of my unitframes, it would be nice if they too had a border to match the theme of the UI, which would require me to go outside of the "border" box.
LOL, I like you.
[me=moonwitch]is in IRC already, though mightly lost in the entire thing especially since her background isn't black, which is totally irrelevant.[/me]
0
Indeed, it does, though with Aperture (spelling?) I get errors. And every listing in Rock shows up double. (I'll post it where it should go ;))
0
Peggy's ok still, I think. Nurse Warren doesn't know, she shouldn't know. It would be bad if she did....
0
Uhm Funky?
The castbars below your UF, is that Quartz? Or the castbars from Pitbull (assuming it is pitbull, which I think it is). I've been trying to get mine set up that way - or similar - but mine keep overlapping (Player is set ok, but the Targets casting bar runs into it). Would you mind sharing your SavedVar on the positions? Or telling me where the anchoring is set etc?
0
I've yet to use Ace3, I use Ace2, no Ace, don't think I have Dongle on my machine. I also have Rock. The memory load is practically the same give or take a few kb higher or lower (depending on what I am doing :P aka Raids will make the mem usage go up).
I am an end-user and aspiring developer, I have a lower-end machine nowadays (3 yrs old, yep, low end). So resources matter to me, but even on a high end system it would matter. To be very frank, I don't think I still care about all the frameworks, all I know is - THEY WORK. And using non-frameworked addons that fulfill the roles of my frameworked addons, leads to a much higher resource demand. So all-in-all, despite the confusion - which is subsiding slowly, it's a good change. It'll take some time, as all changes do, but in the end, it will lead to a more streamlined, better resource use UI (UI entailing all addons, personal definition given to avoid confusion on terminology)
Less is better, isn't that the going thought in addon development pertaining to sizes, be that file-size or resource usage size. At first, I too thought this change would be bad. I feared bloat, but after giving it a whirl, it's far from bad. I don't see a negative change in this, the fact is: Developers are constantly trying to improve, they battle without end to cram as much functionality as possible into as little as possible resources and sizes. And some things just reach a limit, so certain features can't be implemented, more addons get written, frameworks get bigger to accommodate more wishes, etc. This "split" was most likely inevitable, but it won't be a bad one. It's a bold gamble, indeed, but I am certain it will prove to be a good move. Though we're all in for a bumpy ride, until all settles down.
PS. I apologize for the slight off-topic, the length and the soap box. I've just been reading so much drama, so much negativity or very technical explanations. I just wanted to voice my opinion calmly and hopefully as unbiased as possible, I solely based my statements on my own experiences. I hope that the devs of all addons and frameworks will find this post at least a bit nice, since most of the devs have gotten a tun of negative criticism spewed at them in the last few days.
0
LOL .. I can just imagine the results, which is why I turned that off as well a long time ago ;)
0
Keep up the good work, Ckk :)
0
Sorry if this is out of line, but maybe this thread should just be locked, there can't be much good coming from this anymore. :(
I hate drama.
0
I love you guys :) Saves me the grief of setting up its position, reloading my UI every 5 seconds etc. Thank you.
0
Ckknight, the creator of PitBull, Cartographer, CowTip, Parrot and Fubar (and a tun more sorry for forgetting some btw), decided to change libraries used in those, he is now using Rock as framework, no longer Ace2. This comes with its own GUI settings panel, Rock Gui, which is what is displaying the icon.
Using any of the now Rock-based addons, will require you to use LibRock (and the other Rock libs forming the framework) just like before when you needed Ace2 for the aforementioned addons.
Wanna use Pitbull and Cart, then you're stuck with Rock - to keep it short.
0
Well with no icons I meant.. I don't know what I meant. Probably no icons as portrait, no fubar icons etc.
(And sure, if I can answer it, sure. But I am not too well known with these things yet.)
0
0
I was just wondering about borders that one makes customized. I noticed when I opened some borders.tga files, that they all follow a similar layout on the image canvas itself. I've looked around some, but couldn't point the answer to my question.
What are the lay-out rules for borders? Do you always start with Vertical Left, Vertical Right etc? Are there dimension restrictions (eg. a border can't be wider than 10px).
I am asking this because I wanted to try and tinker with EePanels to use my own vector textures, due to the location of my unitframes, it would be nice if they too had a border to match the theme of the UI, which would require me to go outside of the "border" box.
0
Working on a custom bordered no icon layout :)
0
[me=moonwitch]is in IRC already, though mightly lost in the entire thing especially since her background isn't black, which is totally irrelevant.[/me]
0
And, for some crazy reason, unknown to me, I was in #acewow and now wowace >.<
Now to not anger the masses, despite the common occurances of stupid moments by me, I am not blonde, nor geriatric.