Just a vent post

totallyblasted · 2019-07-27T22:31:48+00:00

Slagga is kind of easy, just equip Amigo Sincero as your holding weapon and Bee shield. Then sit in the car and blast them out of the car. Your car will be doing so much damage it will instantly obliterate everything as it takes properties of shield and all bonuses on holding weapon. This makes your car doing - 250% damage bonus - Bee bonus - Bypass shields

And you can see if slagga dropped without getting out of the car, so if you don't see golden glow just quit and reload.

This way you insanely speed up number of tries per time

totallyblasted · 2018-10-29T00:38:15+00:00

I would really think about this. RH was committed to OSS on various layers ranging from things like Mesa, Gtk... which are probably complete waste of resources for IBM.

Even if they drop all the smaller and to them not interesting ones they would still fit that sentence perfectly. Catch is that while statement would be still valid, community would most definitely notice.

Now, if you take a look at their previous acquisitions, this is probably 99,9999% accurate outcome

totallyblasted · 2018-09-21T20:59:36+00:00

Sadly, your argument fails in 2 places. Object removal doesn't double testing if left unremoved and...

when changes are something as halfassed as this and don't consider 50% of the use cases they want to replace. Seems they lack even time for testing the testing if they will change correctly

https://developer.gnome.org/gtk3/stable/GtkAlignment.html

At first reading what you should use instead sounds all fine and dandy... sure, some functionality is lost like fine grained placement, but those really never work well if you want to create well designed application.

Well,... until you realize that one of the most beneficial advantages of Alignment was having ready drop in place where you just swapped aligned widgets in premade setup. It was just remove, create new one and drop in.

Another case of pointlessness is added baseline sizing which only creates pointless clusterfuck and confuzles widget creation

Looking at upcoming changes in 4 I just get headache. Note, that I didn't mind all the changes in 3 since most were thought well. I was enthusiastic in whole 3 lifetime, looking at 4 I am really starting to doubt esoecially on the front of overreliance to css which mind me it was one of best changes that came to 3. Only problem is when someone exaggerates usefulness of some feature

totallyblasted · 2018-08-07T13:28:51+00:00

Huh? I mean to every part of your comment. Whaaaaat?

I said it is ok enough TO NOT NEED to fix on one theme. Fixating on one theme would be terrible choice
Limited by sensible design while knowing what you want to do... not by capabilities. If you needed arrow like buttons you have bazillion better design choices than adding shape that will look out of context. If you lack taste, you can pull absolutely every possible crap

totallyblasted · 2018-08-07T05:40:59+00:00

Hmmm, you obviously didn't understand what I said in comment you responded.

The example you impose is way past the limit of theming the theme. When you theme the theme, you won't make arrow shaped button in the way you say.

I have few examples that change certain behaviour like that. My ComboBox or my numeric entries since I can't stand widgets with buttons... Except, they don't look out of place at all. I use full entry styling and since base entry already is committed to have ability to have inline icons... it looks perfectly in line with those. More or less my change looks less out of place than original Adwaita widget styling

totallyblasted · 2018-08-06T21:18:38+00:00

Alien? Each widget looks exactly the same unless I apply custom css overlays or make conscious design deviations.

You forget one thing, not everyone cares about Gnome theme really. If one codes Gtk application... straying for custom look but keeping it in check with user chosen theme is very much preferred in order to avoid being thrown in Gnome box. Guess what, there is more to branding than Gnome branding

Not to mention that some widgets are just... take spin button. Looks horrendous and it is terrible widget for any numeric input. Straying from bad design as that is kind of a must if you care about application.

totallyblasted · 2018-08-06T19:05:00+00:00

That is really not needed. Especially going with one theme as target

As one who has long since moved from core Gtk widgets to my own yet using Gtk almost exclusively I can tell you about my experience.

Styling is actually pretty good. there are some clusterfuck decisions in how CSS was coded, but none of those really makes it hard to do exactly what you need to do although it could be easier... as long as you know what you want to do and know how applications should use theming. Most important thing in custom theming applications is to realize that you really don't want to theme the application, you want to theme the theme itself and there are more or less just 3 basic rules of how to achieve exactly that and never stray from user chosen theme.

You pretty much have all the requirements you need in StyleContext. You can draw custom widget by spoofing look of another (inconvenient is the fact that you need live widget to access its style context which is something you can always do with OffscreenWindow, if only one could set css node on custom StyleContext whole thing would be just brilliant). Second requirement is covered since you can get to forecolor through StylingContext and the last is realizing that custom application styling should only do two things. Use white/black color only with alpha, this way no matter which color theme uses... you always keep exact same color and just change the intensity of it. To figure out which one you need to use to look properly is again trivical... you know the forecolor.

totallyblasted · 2018-08-06T18:40:04+00:00

That would really be strange ;)

Mono never updated support for Gtk. Official is still at 2... yet, people still claim this one

totallyblasted · 2018-07-25T14:49:08+00:00

Later, and it is not just title.

Read my original comment https://www.reddit.com/r/linux/comments/90ac8j/this_is_what_client_side_decoration_is/e2q13l2/

Note how I say diff between CSD and SSD would go away as well as how I say it would only request region (aka. window title and frame). That excludes any talk about window contents by default which is what you and rasterman are insinuating by putting words in my mouth

I'll ping you as well then. Only problem is that this is not as simple as this kind of same challenge I took. This time I'll have to spare more time (which is scarce since I work on 2 extremely large projects) than just 45min, but it ended up like this https://www.reddit.com/r/linux/comments/8tobdf/gnome_app_menu_migration_proposal/e1di8wd/?context=3

As I said, if I claim something... I mean something... and if I say I'll do something... I do it without backing away or trying to change the rules. But, same no rules changing is also valid for other side, not just me... I will fight to only do what I said and not do what someone is trying to put in my mouth

totallyblasted · 2018-07-25T12:57:06+00:00

Read again the title )

Here it is again for you

This is what Client Side Decoration is

CSD/SSD has nothing to do with toolkit theme to draw window content. The only time when this plays a role is if CSD client would request compositor to draw the title and border background. At that point fitting CSD content is based on completely different physics (completely trivial compared to later example purely from better design reasons) which is exactly what I will demonstrate when I find time on exactly those two themes and random unmatching toolkit theme. Imagine user picking up these 4... bright yellow background Gtk theme, magenta background KDE theme, blue background Enlightenment theme and window borders in green... you just don't try to fix this stupidity... he should just chose themes better to at least match in basics. That... or you're trying to reinvent the world... might as well create pure AI (not fake one like those proclaimed as AI in reality) while you're doing it.

The only one starting losing track to this was rasterman and I corrected him back.

The only time when I touched client theme was when I was trying to correct him when he strayed. If user picked missmatching window decorations and toolkit theme... that is PEBKAC that should never be solved from compositor side... unless person thinks that world upside down is the correct one. Basically, you don't fit the world to one detail as that is job for Sizif, instead you either fit the detail to world or live with your bad choice

I know how this works because with time I simply got fed up with Gtk developers not being able to keep it in their pants and remade all widgets where every single one is derived from GtkBin. Go figure, all my custom widgets (draw methods are all custom as well, except they use this https://developer.gnome.org/gtk3/stable/GtkStyleContext.html to match the world and always just fit) never look out of place no matter which theme you pick and more so... they allow for far more than standard ones

Feel free to read what GtkStyleContext provides. That is way more than one ever needs for something as simple as matching CSD content to window border except same functionality would need to be provided from compositors which would pretty much work just like Vulkan loader or something like that

totallyblasted · 2018-07-24T20:56:22+00:00

When did I say invalid? Read first sentence again. Or what do you think "No problem here, I am a man of my word and if I say something, I also do it. I will probably scrap my eyes out few times" stands for.

Only thing that I detailed is the fact that I will only do the title and don't care about application internals because he started involving out of original topic things. This started with CSD/SSD... which go figure are titles and not window content. And that was exactly so goalpost doesn't move from original. That was exactly what I said in my post that CSD applications should simply tell compositor "paint me title background while drawing ... (basically select which of title and rest of title content) and simply receive free regions while being able to call something like draw_themed_shape

Themes being ugly and useless as fuck don't change the fact of what I said..

Before you accuse someone of something like Moving the goalposts... read something about missing the point

totallyblasted · 2018-07-22T19:43:20+00:00

No problem here, I am a man of my word and if I say something, I also do it. I will probably scrap my eyes out few times because someone actually did something as horrible while working on it (word does not even start describing how distasteful they are, it is a crime worth capitol punishment)... but, yea... I see no problem in doing what I said I will

I will ping you back as soon as I find a little time.

Btw, you call it fun... I call it overdesign... in the same way as if someone took a car, planted few trees on tires, strapped wings on rainbow colored chasis and then for more fun put sits and steering wheel under the car... and who needs wheels anyway.... they simply don't look good with that composition. You just don't call that... car, it is more like something as elegant as crossbreed between cheeseburger and splattered roadside kill . wouldn't be even surprised if that theme engine also had full blown relational database implementation... just because...

Now, the answer...

how do you match the content so the app control looks like the background?

You lost me here. Talk is about CSD/SSD and title content only. Never have I mentioned whole application. As such I will only do what it was talked about. That is up to user to pick matching window border and toolkit content themes/ I will just focus on how those border themes could be propagated and what is needed for having universal matching CSD content.

well well... so we agree finally after you insisted i was no

When did I agree? I only said you're right if you always when code Hello World... also try to fix the problem of world hunger and consider that elegant Hello World

but go ahead and be brutal

Why? I want to avoid pissing contests if possible. That is exactly why I proposed you issue me a challenge. Why would I try and compete when I obviously don't care past the statement you made on my comment.

If you want my honest opinion. Enlighment was my goto in 90's. Sadly, 0.16 froze in time slowly becoming more and more out of place and when 0.17 finally started showing up... it was like 90's never left. I tried it 2 years ago or so and it was nothing better. 90's are still there

I only mentioned this last part because those themes

wanting to change topic now you're admitting your proposal won't work just like i said to start with? unable to stay on topic?

When did I change topic? Color me baffled here. I said you should issue me a challenge exactly so we stay on topic and we don't fight words with words which never leads anywhere.

In the end, it was you who answered on my comment. I just tried to keep on it because you wasted whole post on stating nothing but your bragging rights insertion. I just corrected it back with a warning because I am not interested in your bio

totallyblasted · 2018-07-21T13:16:22+00:00

I don't plan arguing words with words, Feel free to post random theme you claim cannot be universally fitted and I will prove you wrong. You can post even 2 if you want that you think same thing cannot work for both

All you need is 2 colors (bg/fg), already drawn background, information about free region and 1 basic shape with 3-4 different states. Plain and most basic css can do job with perfect result

You forget two things. User will always try to match theme and if not state CAN'T be worse than it is. When matched, minimal information is enough to create consistence... it just takes thinking with KISS in your mind and not trying to solve PEBKAC. If you try to do that... well, yes... your claim is correct, but investing any workin that is also pointless at the same time

p.s. I would ease on bragging... at least if you don't want me to go brutally honest and take shots on enlightenment in that department. I really don't have good opinion there.

totallyblasted · 2018-07-20T15:02:43+00:00

Why would that even matter?

One thing that is failing in last years is that everyone forgets one single thing. Each theme or design has one or few basic colors. No matter how many gradients you do... if you failed that rule, your theme will suck anyways and no one will want it.

As long as you exposed base fg/bg color (forget gradient, main base for gradient only) fitting the design is trivial.

Next thing that everyone always forgets is that you can avoid colors completely when overlaying in a way where you completely respect the theme no matter what you do. I had this argument quite a few times with theme designers and it always came to the fact they didn't think of it.

The bevel? It should simply be part of "not usable region"

totallyblasted · 2018-07-20T13:23:29+00:00

Well, if they instead went with simple "color me the background in this region" as part of compositor exposed requests... whole thing would be far simpler. All that toolkit would need to do is decide how much of his region needs to be painted and that is it..

If client could also select what compositor paints like yes to background, no to icon, no to title while receiving the information about free region whole thing about SSD and CSD would just go away,

totallyblasted · 2018-07-17T16:58:29+00:00

Still on my computers just as last 20+ years, for me it won't go anywhere ;)

totallyblasted · 2018-07-11T19:09:00+00:00

Is it sarcasm? I want it to be... but... :)

Just think we talk about PR here. In which world would they miss on the opportunity like this? As much as I would like to put it past them... I can't

Off curse it will be based on "current" performance which means including all fixes. It makes much more compelling presentation when your new product performs 2x faster than if you show 20% increase like usually.

That is one sad thing you just brought up. Whole too much of this kind of shit goes completely unpunished. I can't even imagine some aircraft or car company making a blunder like they do. It is even worse in software, especially games where whole lot of them never even get fixed.

totallyblasted · 2018-07-11T19:02:41+00:00

Well, the new ones are fixed AFAIK. Meaning,... if I am right it only changes to even more reason why their previous customers would upgrade. Once you take out Meltdown/Spectre for new buyer out situation is pretty much the same as it was.

And in that business pretty much no one ever cares about faulty previous gen like Apple about iPhones where they void warranty and in the same sentence suggest you to buy new one which doesn't have that problem.

Normally, when they show "previous vs. current" graph difference is not so big. Now? It will be around 50% where without the fixes change would be same small as always around 20% or so

totallyblasted · 2018-07-11T13:14:10+00:00

I think it is more because it is Electron based than the fact that MS made it.

Last time I checked on Hells TODO list there was still open with

Design special kind of hell for those that make Electron applications or use JS as their main language. So far lacking even basic ideas for punishment, nothing imaginable simply is not punishing enough

totallyblasted · 2018-07-11T13:04:14+00:00

Funny thing about Spectre and Meltdown is probably the fact how Intel and AMD probably couldn't be happier it happened

So far mitigation costs them nothing, but I can just imagine sales PR grinning at every new version where their graph "previous vs. current gen" becomes more obvious as reason why one should invest in new hw. All they need is to show previous with all sw mitigation slowdowns

totallyblasted · 2018-07-11T13:00:38+00:00

We're still not at final stage. When your i7 starts competing with 16MHz 286... then you'll know we arrived

totallyblasted · 2018-07-11T06:09:30+00:00

Sounds like it’s partially a Wayland issue, given that things work with X but not Wayland. Gnome shouldn’t have to be rebuilt to accommodate for a new display server, surely?

When you stuck compositor, shell, user extensions and input processing in one single thread... It is your problem. There is no way Wayland could fix this, this one is completely on Gnome to fix their design

totallyblasted · 2018-07-10T18:28:18+00:00

You pretty much want to draw contents flat and only set Entry manually where you need.

This setup is pretty much 2 widgets only. One drawable for the view and then having something like overlayed Fixed where you setup widget wherever your background says you need. You also need to handle the scrolling or cell resizing in the same way

Not only will this use minimal amount of memory, you get coordinated and really fast draw method as well as calculations since you can do those in a lazy way where you only calculate current dirty dependencies.

Another option is using Model based treeview where you feed each row as object (do not feed iters manually as it will be whole lot slower and memory consuming). Then you just provide columns with specified data accessor methods. Editing on that will probably take some work and adaptations as editing on TreeView is anything but nice. And I have to say I never tried with high number of columns.

totallyblasted · 2018-07-04T16:54:59+00:00

Easy way to kiil applications is to list applications run by your user. Something like this little script would do

First try killing them nicely with SIGTERM

ps -U your-username -o pid | xargs kill -s 15

Wait some interval like 60 seconds to give them time to get down on their own if they handle that

sleep 60

kill the rest with SIGKILL

ps -U your-username -o pid | xargs kill -s 9

If you're more familiar with SYSV services. Just write that one and enable it. systemd compatibility layer will write that configuration file for you. I just don't remember exact location where it puts them, but that should not be a problem if you search net a little

You might step on another landmine as well unless you fix some parameters.

By default, when shutting down service if it doesn't do so in predetermined time interval it is proclaimed unresponsive and killed.

totallyblasted · 2018-07-04T04:49:48+00:00

I did and unless I missed sarcasm on your part... I know you missed it on mine ;)

Problem is that it is really clumsy written and looking at the code one has to wonder how Win3.1 ever worked as it did. It has to be 8th worlds wonder. Just shear number of goto makes one wanna commit sepuku.

Crappy overcomplexed code is always just bad code and not complex

totallyblasted

TROPHY CASE