does anyone else get errors like

WARNING: Required namespace not provided for cljs.estimate-work.vectors null

that kind of thing?

I’m trying to google it but not getting much relevant info

that looks like what happens when you (:import [foo.bar Baz]) maybe

would :require have a similar problem?

i've seen something similar i think when using js things via foreign libs

where are you getting the error?

i get it in different places actually

in the compiler or in the browser?

when i run (cljs :optimizations :advanced)

during boot

i pretty much always get it for files that have (page foo) instead of (ns foo)

sometimes, i’m not sure when because it’s not 100% of the time

estimate-work

i get it for things that i’m requiring inside the page

is this a namespace you made?

yes

name of the project

that could be the problem

you want to make your namespaces so they don't conflict with other people's namespaces

the is a bad idea

what am i conflicting with?

oh ok

cljs is owned by clojurescript

well right now i’m trying to get tests running

so this is the third place i’m seeing it

yeah i'd change that

i couldn’t find good examples of how to structure my folders/files/namespaces for testing

the namespace system is devised to help you prevent collisions

like the domain name system

everything i saw just said “oh, assuming you’re using a folder called test add this config…"

yeah but, how do namespaces work for testing?

work?

like suppose i have a namespace adzerk.foop for instance

well, when I use phpunit with PSR I just mirror the namespace of the classes i want to test

but with tests in the namespace or something

i make a second namespace for tests related to that namespace

i will usually name it adzerk.foop-tests

but it doesn't really matter

ok

but don’t namespaces have to match folder structure to get included properly?

yes they do

so if i have a directory in root called src/cljs with .cljs files inside it

so

src/cljs/estimate_work/vectors.cljs

has (ns estimate-work.vectors) in it

so the first thing you want to do is not clobber the cljs namespace

then how do i match up a testing directory/file structure to test thigns in that

?

you can just change the first segment to some other name

then what i usually do is this

that came from the hoplon castra template though

i don’t think i set that up

one second

which template?

i’ll find it

well i can tell you how i do it

usually

i looked for a template specifically to avoid this kind of noob mistakes 😛

like suppose you want to organize your source code in such a way that tests are separate from the working code

and maybe you have different folders for different types of source code

yes well

i did

like scss in one directory and cljs in another or something

want that

yeah

ok yeah

so i would make a directory "src"

and in there "cljs", "test", and "scss"

oh ok

so, test inside src

that’s one thing i did wrong

i mean you don't have to

sometimes i put it at the same level as "src"

that would work also

the key is this though

(set-env! :source-paths #{"src/cljs", "test", "src/scss"})

my gf actually put sass in the top level to make it easier for her to compile into assets

but i don’t think that matters here

i got

:resource-paths #{"assets" "src/clj"}
  :source-paths   #{"src/cljs" "src/hl" "test”}

the idea here is that when you configure the :source-paths and :resource-paths

it will overlay all those directories

and the files in them will be resolved relative to the overlayed directories

so like supose i have my adzerk.foop namespace

ok, i just checked

lein new hoplon-castra foo

run that

you’ll see what i ended up with

you get src/clj src/cljs and src/hl

.
├── sass
│   └── _application.scss
├── src
│   └── cljs
│       └── adzerk
│           └── foop.cljs
└── test
    └── adzerk
        └── foop-test.cljs

this is what i'd make

ok yes

i just installed the template

so i didn’t mean to clobber cljs

if that’s what i did...

if you pull a fresh copy of the template

then do boot show -f in there

that will show you the overlayed files

just x-referencing your nice diagram against my current setup

shuffling a few things around

the diagram was just one possible way

the important thing is to understand this overlaying business

boot show -f is your friend

yeah i know

but i wanted to start with one working example

commit that

then experiment from there

it will show you how boot is assembling the various directories

oooh my tests ran without errors!

the tests failed

but they ran

then when you move things around you can use boot show -f to see how your changes affected the way the tasks see the files

~/zzz/foop
barp $ tree .
.
├── assets
│   └── app.css
├── boot.properties
├── build.boot
├── README.md
└── src
    ├── clj
    │   └── foop
    │       ├── api.clj
    │       ├── core.clj
    │       └── handler.clj
    ├── cljs
    │   └── foop
    │       └── rpc.cljs
    └── hl
        └── foop
            └── index.cljs.hl
8 directories, 9 files
~/zzz/foop
barp $ boot show -f
app.css
foop
├── api.clj
├── core.clj
├── handler.clj
├── index.cljs.hl
└── rpc.cljs

tdm:estimate-work thedavidmeister$ boot show -f
app.css
estimate_work
├── api.clj
├── core.clj
├── elements
│   ├── bucket.cljs.hl
│   ├── estimate
│   │   └── fixed.cljs.hl
│   ├── form
│   │   └── atom
│   │       └── textfield.cljs.hl
│   ├── nav
│   │   └── support.cljs.hl
│   └── outer-dom.cljs.hl
├── handler.clj
├── index.cljs.hl
├── rpc.cljs
├── style-guide.cljs.hl
├── vectors.cljs
└── vectors_test.cljs
ie.css
print.css
screen.css

i see

here i thought you drew me that nice diagram by hand

but it was all the machine

notice how boot is collecting src/clj/foop/, src/cljs/foop/, and src/hl/foop/*

in show -f it appears to be just one directory

foop/*

if i wanted to make some tests i can put them anywhere, as long as i add the correct entry to :source-paths or :resource-paths

yeah sure, so comparing tree against show -f seems like something important to debugging from time to time

yes exactly

so how do i know what goes in source paths and what goes in resource paths?

things in resource paths will end up in the "final artifacts"

i.e. in a jar file or in the target directory

because it was recommended to me to move src/clj from source to resource as part of deploying a war to heroku

yeah

exactly

but i didn’t really get why at the time

well it has to do with the jvm really

boot is a program that's running in the jvm

building a program that will run in a different jvm

actually let me start over

there are files that are source files

that you will be compiling and doing things to

some of those you want to propagate to whatever the final artifact is that you're building

i.e. the war file, or a zip file, or files in the target directory

but some of the source files that will be part of the build process are not supposed to end up on the webserver

like maybe your uncompiled cljs namespace files are not intended to be served from the web server

https://github.com/boot-clj/boot/wiki/Filesets#types-of-tasks

those 50 lines explain the whole thing

good document

so there’s a bit of assumed knowledge about the JVM in there

what does the AOT do? for example

other than stopping a file from being a resource

aot means "ahead of time"

referring to the practice of compiling clojure namespaces into byte code

i mean "into bytecode"

clojure is a dynamic language

it contains its own compiler

and most of the time you run clojure in such a way that it compiles your program as it runs

but sometimes you need to precompile some things into bytecode before the program can run

like if you're compiling things that need to expose Java classes

this doesn’t apply to clojurescript though does it?

you wouldn’t need to aot JS?

clojurescript doesn't have a self hosting compiler really

well it has a very new thing

but historically it hasn't been able to compile itself

so you have no choice but to compile your clojurescript program ahead of time

you can't send cljs source files to the browser and compile them there

yeah i think that’s what i meant

clojure on the other hand can and does do this all the time

you don’t really have a choice

most clojure jar files just contain .clj files

the source

because it always has to be JS before it’s useful

yeah

right, so why would i not want to aot before deploying something?

wouldn’t it be a bit faster to get the byte code as part of making my war?

faster to run the program i mean

well you can't compile dynamic programs ahead of time

there are many things you can't do in cljs because this

things that you can do in clojure

cljs has no eval

which is an important part of lisp

so in general you don't want to AOT

ok

so aot = no eval

is that macros as well?

so when you say exposing java classes, you don’t mean just calling methods on the classes do you?

because that would come up a bunch i assume

i mean like if i make a clojure library that i want to expose to java developers to use in their java programs

and expose it to them in such a way that they don't even know it's not java

ooooh

for going back the other way

i'd have to create concrete java classes then, and interfaces, etc

right

yeah, like, if it wasn’t so crazy i could tell someone i wrote the JS myself that cljs made

and they’d have no way to prove i didn't

does the aot for java actually make code that someone would find legible?

or is that not the point?

no, it doesn't generate java source code

it generates bytecode

it generates the stuff you'd get if you ran javac on a .java file

you get a .class file, which contains binary bytecode

mmmk, i really am not planning to learn much java if possible

so maybe i’ll leave that for now

haha i don't blame you

i don’t love needing to learn about the JVM to get clojure stuff working

it's unavoidable

at least the basics

yeah

this document helped a bunch

i didn’t really know about the classpath or the different types of files

any idea why assets ends up listed as a resource-path instead of asset-path?

also, am i right in saying, because the .cljs files get compiled to JS before being dumped in target/ that is what makes them source-path and not resource-path?

and because the src/clj ends up powering the server backend for castra, and we don’t want to AOT it, to keep all the lispy goodness working, we put it in resource-path?

and because we don’t actually ever want our tests to hit production, because that’s pointless, we leave them in source-path?

yes that's corect

@meeli: micha gave me some really good info about the file structure ^^

you should read over it when you get a chance

when tasks create files they generally create them as resource files

@micha: is there any benefit to using asset-path over resource-path? or is it just easier to use resource-path everywhere you might want something to end up as an artifact

because it's assumed that you're creating them to output them somewhere

it looks like assets are just less flexible versions of resources

asset-path only really exists for completeness

since there are 4 permutations i figured we should give them all names

but i've never found a good use for asset-paths myself

well if you were using something other than boot to generate the assets?

like rake or something?

perhaps

i don't think i have anything like that myself

we do run sassc for example to compile scss

pretty sure we’re still using ruby to do the sass compiling

but we do it from a boot task

haven’t looked at other ways to get sass compiling yet

but i did see there was a lein sass

just haven’t migrated to it yet

one thing at a time

but you know, wouldn’t image files be assets?

boot wouldn’t really be doing anything with the images other than moving them into place

yeah that could be

but at the same time

you just limit yourself by making it an asset not a resource

for what gain?

yeah that's what i was thinking too

is it somehow more efficient under the hood?

or if not now, could it be in the future?

if boot knew it would never need to do certain things with your asset files, maybe it wouldn’t need to load as much into memory, or something...

yeah that's true

it could save some cycles if you have a ton of files

well it would just really need to keep a reference to where the file lives on the file system

and that’s it

then right at the end, just copy and paste from the reference to the target

but yeah...

i wouldn’t bother implementing that unless you’d profiled some real issues on a real project >.<

i've been working on profiling some fileset related things the past few days

oh yeah?

java IO is really pretty fast

they did a good job with it

i did blow up the 4GB memory limit while trying to build pretty much the base template on circle ci

dunno if that’s related to what you’re doing

really?

that's odd

not sure if boot even finished pulling down the dependencies

it freaked out and i couldn’t even download the artifacts containing the memory info

there were some clojars issues

this week

oh, maybe that impacted me

i got my project deploying to heroku

but it’s still manual, wanted merges to master to auto deploy

had to shelve it for now until i learn more about what’s going on

was getting errors about clojars not being git repos or something...

and circle ci maxed out memory before i got very far through seeing if they could help

is circle ci similar to travis?

yeah

actually i’ve used travis more

from what i understand

we do stuff on travis with boot all the time

ci runs your tests, then optionally does a deploy task as well

yeah travis worked for me so far

in theory circle ci is travis + deploy

in practice, it looks like they have pretty different setups/limits on the hardware/environments

so i’m sure for lots of people it’s awesome, didn’t work out for me this time though...

i would hope that boot would use less memory than say leiningen

because it's running in a single JVM

i really don’t know

haha

i’m just throwing shit at the wall to see what sticks

too noob to have an informed opinion about what really should or shouldn’t work

well have a good rest of the night

i'm off to sleep

if you’re curious and profiling things anyway

+dependencies:
+  post:
+    - wget -O boot 
+    - chmod 755 boot
+    - ./boot -V
+    - ./boot checkout
+test:
+  override:
+    - ./boot test

i stuck that in my circle.yml

@micha: see ya, thanks again for helping out!

@micha can you describe how .inc.js used to work in hoplon5? i wonder if a task to do that on h6 would be cool

.inc.js files were added to the top of the compiled js file, in dependency order if they came from dep jars, lexical order for .inc.js files in the fileset

but it required a scan of the jars which can get really slow

i think the problem is now completely solved with cljsjs

i think it's handier for 1-off jq plugins from an vendor/ dir

then if you like them you may cljsjs them

we should make a task that cljsjses them

locally

like generates the deps.cljs file

i was looking into that, can thye be their own externs?

you don't need externs

or yes, they can be their own externs

but that's like only partially successful

just don't do :advanced i would say

unless you are ready to invest your time in a real externs file

yeah

or use a macro lib that gets around the mangling

like transforms interop to the aget/`aset` forms

right

it's nice to have your cljs :advance compiled but then load up the jq libs dynamically

unmunged

it's not the jq that gets munged of course

it's the references in cljs land to them

right