Notices by muesli (fribbledom@mastodon.social), page 40

@loke

Please, someone figure this out, it's giving me headaches 😆

@Gargron

Nice!

One thing I noticed: on high-res monitors it only fills half the gallery's height with items, then showing a "Load More" button. Would be nice to have it fill up the entire pane and proceed with lazy-loading more on scroll events, like it does after I click the button once.

@lunduke

Welcome to the fediverse, Bryan! Glad to have you on board.

Now we just need to convince you to also give peertube a chance 😉

@chucker

...and that may be the difference to Twitter, really. Here it's the exception, over there it's just how people seem to behave these days.

I'm still baffled by how many nice, friendly and intelligent people I meet here, every single day.

@chucker

To be honest, I think that's just fine, and as long as it doesn't happen in a patronizing or condescending manner, I always give benefit of the doubt.

I'm sure just like you and others I've done this myself many times before with no bad intentions whatsoever 😆

@Cedara

Musste das mal kurz für dich aus dem Schrank holen :blobaww:

https://mastodon.social/media/T5dvxKFW5l3_NmxnS3k

https://mastodon.social/media/MuM4Ne0hoZqRC9HL_UU

https://mastodon.social/media/E3voobBdvxrQM5CMWdQ

@Cedara

Lynx <3

@katana_steel

I strictly separate UI and the backend. There's probably about 15 lines of JavaScript in my QML, and all it does is toggle the state/label of buttons.

Everything else is written in Go.

@brainblasted

Wouldn't be opposed, even though I don't have any immediate plans for packaging just yet.

@zalandocalrissian

Nope.

@Wolf480pl

An import "repoA/foo/bar" will be searched for in $GOPATH/src/repoA/foo/bar - So the "src" part is enforced when using GOPATH.

Other than that: yes, absolutely common and valid layout.

Unless you meant to mix or combine package bar together from two different directories? That doesn't work. You can have and use two "bar" packages, but they would live independently from each other.

@minus

@Wolf480pl

Actually it kind of does: each package is restricted to exactly one directory.

In other words:

github.com/foo/bar is an entirely different package than github.com/foo/bar/abc (abc is not included by its parent).

Yes, this is convention: Your GOPATH will contain your project(s) in the directory structure I laid out in the previous toot.

@minus

@Wolf480pl

No, you're overthinking this. It really doesn't work like the Java CLASSPATH: it merely defines your import search path for the compiler at build-time.

@minus

@Wolf480pl

The GOPATH env-var is a build-time setting. It tells Go where to find (and store) your imports. It has no effect at runtime. So it's more like the -I and -L parameters for gcc than a Java CLASSPATH.

@minus

@Cedara

Wie ich im Toot bereits andeutete ist das momentan noch eher etwas umstaendlich fuer Leute die sich nicht gleich ne Entwicklungsumgebung aufsetzen wollen 😆

Ich wuerde dir empfehlen einfach noch ein paar Tage zu warten, dann hab ich mit etwas Glueck einfach ein Ubuntu Package fuer dich bereit liegen.

@Wolf480pl

GOPATH is the root of your workspace. Within it you'll find a directory structure that resembles something like this:

src/github.com/username/project

This helps Go to (automatically) resolve imports with full canonical paths. For example you can do

import "github.com/foo/bar"

in your code. Go would import that package (and potentially git clone from GitHub first) from $GOPATH/src/github.com/foo/bar

@minus

@carbontwelve

If you're interested in learning a bit of #golang, I streamed a live coding Go Crash Course the other day:

https://www.youtube.com/watch?v=uMA8wJ6xA_g

@er1n

@nx

Not yet, but I'll hopefully get to a first release this weekend. Stay tuned 😊

@Cedara

Ja,sollte auf allen gaengigen Platformen laufen.