Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 24 07:36
    scala-steward opened #224
  • May 15 10:37
    scala-steward opened #223
  • Apr 12 23:03
    scala-steward closed #218
  • Apr 12 23:03
    scala-steward commented #218
  • Apr 12 23:03
    scala-steward opened #222
  • Apr 04 23:09
    scala-steward closed #219
  • Apr 04 23:09
    scala-steward commented #219
  • Apr 04 23:09
    scala-steward opened #221
  • Mar 22 20:11
    scala-steward opened #220
  • Feb 28 12:18
    sake92 commented #55
  • Feb 14 14:19
    scala-steward closed #216
  • Feb 14 14:19
    scala-steward commented #216
  • Feb 14 14:19
    scala-steward opened #219
  • Feb 02 01:30
    scala-steward opened #218
  • Jan 19 22:37
    scala-steward opened #217
  • Dec 11 2021 02:32
    scala-steward opened #216
  • Dec 07 2021 16:20

    sake92 on master

    Derive JsonRW for jsonable clas… (compare)

  • Dec 07 2021 16:18
    scala-steward opened #215
  • Dec 07 2021 15:55

    sake92 on master

    Fix MimeTypes (compare)

  • Dec 07 2021 15:52

    sake92 on master

    Fix literals bug.. cannot deriv… (compare)

Sakib Hadžiavdić
@sake92
See link I pasted, I override it in hepekDocs project
nice :smile:
Soren
@srnb_gitlab
Well, then you get myBuild/../docs/my/sub/package/index.html
Sakib Hadžiavdić
@sake92
Do you mean that sbt-plugin should render only classes under specified package?
Then someone would complain why it doesn't render all.. xD
Soren
@srnb_gitlab
So what you're suggesting is (making table)
Sakib Hadžiavdić
@sake92
These 2 are separate things, just to make clear
Soren
@srnb_gitlab
No package set (Default) Package set
Page under package $package/$sub/$page $sub/$page
Page not under package $sub/$page No Render
Sakib Hadžiavdić
@sake92
hepekTarget is just the root folder where all will be written
Soren
@srnb_gitlab
Yeah
Sakib Hadžiavdić
@sake92
that's already configurable
Soren
@srnb_gitlab
hepekPackage := None would be the default, which is what is the current behavior
Sakib Hadžiavdić
@sake92
Yup, something like that could work
but I don't like it :smile:
Soren
@srnb_gitlab
But hepekPackage := Some("my.package") would turn what would be my/package/subpackage/thing.html into subpackage/thing.html
Sakib Hadžiavdić
@sake92
what's the problem with current solution?
worse thing is that you get a deeply nested structure
Soren
@srnb_gitlab
I have to do some funky stuff with ghpages-sbt to get it to take stuff from a deeper level than target
Sakib Hadžiavdić
@sake92
e.g. if you have package a.b.c.. doesn't matter
Soren
@srnb_gitlab
Having an object in package a.b.c will give you target/a/b/c
Currently
How about if I wrote a non-breaking pr to add it? I.e. any current build (that doesn't use the key hepekPackage which I don't see why would be used) will still behave exactly the same after the pr
Sakib Hadžiavdić
@sake92
just said siteSourceDirectory := target.value / "web" / "public" / "main" / "examples"
Soren
@srnb_gitlab
image.png
A-Frame Hepek?
Sakib Hadžiavdić
@sake92
first time I see it, looks very interesting
although it is more like a dynamic thing, probably more suited for ScalaJS
DOM manipulation etc
Sakib Hadžiavdić
@sake92

An almost trivial but useful thing would be Fontawesome helpers
e.g. with a definition like: def syncAlt(mods: Seq[FaModifier] = Seq.empty, styles: Seq[StylePair] = Seq.empty)
Sakib Hadžiavdić
@sake92
FA.syncAlt(mods = Seq(FaSpin))
should render <i class="fas fa-sync-alt fa-spin"></i>
Sakib Hadžiavdić
@sake92

0.4.0 is released! :smiley:
featuring Play framework support
Peter Pan
@P3trur0
hi @sake92 could you please explain how it now works in detail the hepek-components part?
I had no chance in previous days to follow all the occurred changes of the source code, but today I am trying to fix some of the Bulma issues although I found it already changed
Sakib Hadžiavdić
@sake92
@P3trur0 yeah, sorry about that.. :D
I wanted to extract these "components" in a separate project
so it can be used in different contexts: Static site generator and Play framework
Play doesn't need some classes like StaticPage, blog support, automatic paths etc

I did some work on Bulma also, you probably saw that
Grid now works fine, forms need some more work :)
Also, started to extract these common classes like btnSuccess, btnDanger etc in Classes trait
Sakib Hadžiavdić
@sake92
Makes sense? xD
Peter Pan
@P3trur0
Yup, I see. So basically the stuff in hepek Is no more necessary? For example all the components written so far
Sakib Hadžiavdić
@sake92
Well, hepek (SSG) depends on components
Peter Pan
@P3trur0
Since now there are Form and Grid ones in hepek-components, right?