How do I include definitions from another file in my .cljs.hl files?

I created a project with boot-new and I'm trying to include a file from the namespace my-project.library. I created the directory src/my_project and the file library.clj, but it's not being picked up by boot dev

Nevermind, figured it out.

@fiddlerwoaroof can you share what was the problem? I'm writing a tutorial for beginners and would be nice if the problem you had was avoidable.

I mind. It's boiler-plate noise as well as inconvenient for a system that will have a lot of html-as-lisp. It's inelegant and undesirable to have to prefix all the hoplon html element fns in a hoplon file. At that point, might as well not have a hoplon file.

I actually like h/div more than the implicit refer that goes on .hl files. For beginners arriving on Hoplon is hard to know what comes from where and that would not be a problem without doing refer all from hoplon and javelin namespaces. The only reason that I use .hl files on my projects is for prerendered html.

@mynomoto did you try the ^{:hoplon/page "index.html"} namespace metadata approach?

@micha I haven't, is that official in the sense that's not experimental and if it works it will be kept?

i think we should consider it experimental for now, but we can't know if we like it unless people try it out

these are important issues though that would be good to get consensus on

it would be good to develop an API that works well for everyone

without adding extra features that nobody wants

like you mentioned a number of things that you thought could be moved out of hoplon

Is there an example of the metadata for html being used somewhere?

one sec

I think everything that could be moved out should be moved out 😉.

i'm trying to get this terminal slack client working, cause the slack webapp is killing my CPU relentlessly

ridiculous that two slack webpages should be using one full CPU each

they should be using hoplon

lol

Slack is ridiculous in more than cpu usage. FTW!

But I don't have that cpu problem here.

i wish the community had moved to something like telegram

some open, secure platform

For most of what we do here discourse seems a better place for keeping records of solutions.

it gets overwhelming though

especially the overhead of keeping track of async communications

I like gitter better than slack but if everybody is on slack there is no real option.

i'd like an option that isn't owned by any company

At least we have separated contexts there.

something federated

Unfortunately there is no money on that. So we only can pick which megacorp to use.

IRC is almost good enough

but support for code snippets and images is i think necessary

pastebin isn't good enough

rich text, basically

We had irc but there is way more people here than ever on irc. And I like to be able to disconnect and not miss what happened.

yeah

i still pay for irccloud, but i don't check it often

i gues that's where the open solutions fall down

the storage

i wonder what could be done with amazon dev pay

I think ux also is a problem. Slack may use lots of cpu but people enjoy using it, which is more than I heard people saying about irc clients.

i actually really do not enjoy the slack ui at all

like they are constantly doing fancy js bullshit that breaks my browser plugins

like no, i do not want to make a snippet, i just want to paste a link

I don't like slack at all but I think it's better than irc. The way I use it the biggest quirk is that message has a limit and they don't create a snippet automatically when it's to big.

and the textarea is not monospace

and they somehow hack it so you can't easily make it so with a bookmarklet

If people are not responding on discourse maybe we should shut it down? Latest topics have no answers...

hm i should do it once a week maybe

I like the idea of having less places with more content and better responsiveness. We probably should stop sending people to irc from boot and hoplon sites.

Rust is using discourse forum pretty successfully as the main channel of communication

I think Slack works fine for the Hoplon-sized community. The common topics end up as Github Wiki pages

i like that slack is ephemeral

because i can answer questions when i'm able

without stressing about the unanswered ones that will live forever in discourse

that's also because there are ~5-10 people total

or spending time making an answer that will not be read

you also end up answering the same question a few times

🙂

which is not inherently a bad thing

it's difficult for me to write good technical documentation

and that's kind of what you need to do in discourse because of google etc

it's a lot of effort and stress

in slack you can have a more fluid discussion

also the fact that it might take a day for the forum message, response, message cycle

@dm3 I like the idea of having something permanent but if people don't use I would rather that it didn't exist.

there should be an async channel

maybe closing discourse and accepting questions in Github issues could work

We are not that much reposive on github either 😉

But I think that having places where questions goes to die is bad.

yeah, that would leave a single "window"

discourse seems like the best solution there

to pass async questions throuhg

i just need to get on there more 🙂

do you need an account there?

I see a yahoo-login option

i can login and stuff, i am paying for it currently

@dm3 to post you need, only to see what's there no.

i can add anyone to the admins or whatever too if you like

oh lol, i misunderstood your question @dm3

no, I was mainly thinking about barrier to ask a question

which I think is lower with github as pretty much anyone who'd use Hoplon will have an account there already

@dm3 but issues are sort of a bad place for questions doesn't match the flow. Once answered do you close the issue?

yeah, I'd think so.

the problem currently is that discourse forum is pretty much dead

it would be neat if github had a thing where you could promote issues to a FAQ or something

what about stack overflow?

that's a good format because it can adapt to future changes

we have a tag there, or used to anyway

@micha stackoverflow now has documentation

but the #hoplon tag isnt popular enough i think

http://stackoverflow.com/documentation/hoplon/commit

i like that you can vote up/down

and replace out of date answers with new ones

not replace, but augment

yeah i think it's a bit better than a forum

like a living documentation

i get stressed reading long threads

SO has the discussion page too

where you can discuss forum style

for a given question

the moderation might be useful too if the volume increases

like marking things as duplicate, off-topic, etc

link to other sections of SO when appropriate

SO is also easy to track questions and things

cross linking between the wiki and SO would help direct users to find things

but currently all SO questions are old so i guess devs are just coming here?

It would be nice to have "official" places to ask for help. We should deprecate/close unmaintained ones. Also more people need to participate, I can't be only micha and alan.

In the current state SO and here on Slack seems the path of least resistance. The gamification on SO helps to have more people answering questions.

I would like beginners having a good first experience when they have doubts. Today it may be amazing with micha answering here or fall in the limbo and getting no answer.

i am ok with whichever course we decide to take

probably leaning toward moving things to SO maybe

I updated the template hardcoding the versions to avoid breaking it without us knowing as the issue alan opened. Also that should probably live under the hoplon org now. https://github.com/tailrecursion/hoplon-template/pull/10

Something I have been working on: https://mynomoto.github.io/hoplon-tutorial/ hopefully it will be useful to someone starting.