hoplon

The :hoplon: ClojureScript Web Framework - http://hoplon.io/
2017-11-28T00:39:25.000071Z

@rfhayashi have you used the profiler in the browser to identify what is running slow?

2017-11-28T01:52:57.000242Z

@rfhayashi also, i don't think it should be too hard to upgrade if you do it in a few chunks

flyboarder 2017-11-28T01:56:03.000057Z

@rfhayashi if you need help working through the upgrade process let us know!

flyboarder 2017-11-28T01:56:29.000166Z

@thedavidmeister have you used Angular2 before?

2017-11-28T01:57:04.000024Z

@flyboarder angular 4 i think it was

flyboarder 2017-11-28T01:57:36.000132Z

I want to write an adapter for hoplon, to be able to make use of the angular goodies floating around the web, looks like a tough road tho

2017-11-28T01:57:51.000304Z

from what i've seen angular is a bit of a walled garden

2017-11-28T01:58:11.000105Z

it's like a monolithic framework that touches everything

2017-11-28T01:58:40.000035Z

i think react plays more nicely with others

2017-11-28T01:59:07.000058Z

and vue.js explicitly states compatibility with other systems as a design goal

flyboarder 2017-11-28T02:01:07.000210Z

yeah vue.js looks cool too, we have some stakeholders that are pressuring for portions of our product extremely quickly so I am trying to figure out an approach on the client side that would help move more rapidly

2017-11-28T02:01:26.000328Z

ah ok

flyboarder 2017-11-28T02:01:48.000173Z

like someone literally asked if they could have a demo tomorrow

flyboarder 2017-11-28T02:01:55.000186Z

i laughed

2017-11-28T02:01:58.000229Z

hah

2017-11-28T02:02:32.000124Z

well they just want what you have

2017-11-28T02:02:37.000154Z

it's a good sign šŸ™‚

2017-11-28T02:02:53.000077Z

but hmmm, my experience with angular wasn't "rapid"

2017-11-28T02:03:22.000270Z

and their native data model would probably conflict with javelin in nasty ways

flyboarder 2017-11-28T02:03:28.000009Z

yeah i think ill stick with the hoplon stuff anyway, just wondering if I could pull some fancy ui stuff together

2017-11-28T02:03:42.000180Z

actually the whole time i was working with angular, i was thinking about how much faster i could get what i was doing done in hoplon

flyboarder 2017-11-28T02:04:23.000047Z

:thumbsup:

flyboarder 2017-11-28T02:04:46.000123Z

now if only there were better UI kits available

2017-11-28T02:04:58.000091Z

what UI bits are you looking for?

2017-11-28T02:05:15.000109Z

i might have some elements that i could share

flyboarder 2017-11-28T02:06:09.000065Z

they are wanting us to shift focus to the webstore

2017-11-28T02:07:33.000012Z

should we shift this convo to a different chat?

2017-11-28T02:07:59.000298Z

maybe we can plan something, probably not for tomorrow, but soon

flyboarder 2017-11-28T02:08:23.000227Z

yeah amelia said sunday she was free for a chat

2017-11-28T02:08:55.000277Z

yup, she told me yesterday that she'll be working on your stuff in the next few days

flyboarder 2017-11-28T02:10:43.000089Z

yeah thats fine, ill try to get more stuff up on the workspace, been working on the product pages

flyboarder 2017-11-28T18:15:38.000397Z

I am anxiously awaiting the 1.9 release, builds still passing for hoplon tests šŸ™‚

2017-11-28T19:14:54.000605Z

@thedavidmeister @flyboarder i managed to reproduce my problem in a small project, and upgrading hoplon does fix it. it seems like the best way forward, but as it's quite an old codebase and I'll also have to change some libs that are based on the old hoplon version, I was just wondering if you guys can think of anything that I could do to fix the problem without going through the upgrade process (sorry to insist)

flyboarder 2017-11-28T19:17:10.000678Z

@rfhayashi you could try something like 6.0.0-alpha15 which might need less changes, however there were many things that were improved within the 6-alphaX builds

flyboarder 2017-11-28T19:18:03.000084Z

we rolled most of them into v7 and then stripped out a bunch of things for 7.1-SNAPSHOT

2017-11-28T19:23:37.000042Z

both 6.0.0-alpha17 and 7.0.3 worked in the small project, probably 6.0.0-alpha15 will work as well, I was wondering if you'd happen to know which bug was that and than I'll could try to cherry-pick it to the version I'm using

flyboarder 2017-11-28T19:24:36.000472Z

v7 is almost a complete rewrite, prior to that Hoplon is tied to jQuery, in v7+ itā€™s not

flyboarder 2017-11-28T19:25:09.000725Z

I didnt work too much on the v6 builds, those were happening a few years back now

flyboarder 2017-11-28T19:26:18.000312Z

so it will be hard to cherry pick anything to v6

flyboarder 2017-11-28T19:30:10.000746Z

@rfhayashi in all honesty it will probably be easier to upgrade to v7.0.3

2017-11-28T19:30:45.000026Z

actually the fix is in v6 (it worked for me with 6.0.0-alpha17 in the small project), but we'd have to know what we need to cherry pick anyway, I'll try to work on the upgrade, thank you for your help

flyboarder 2017-11-28T19:44:43.000152Z

@rfhayashi what did you change after upgrading to alpha17?

flyboarder 2017-11-28T19:44:54.000302Z

To get it working?

flyboarder 2017-11-28T19:45:36.000057Z

There are many changes to the tpl system itself throughout those builds, like skipping non-hoplon elements to improve performance

2017-11-28T19:48:58.000486Z

I just used the cond-tpl from alpha17 instead of the one I added to alpha1 (the cond-tpl code I copied from master)

flyboarder 2017-11-28T19:53:39.000285Z

@rfhayashi Iā€™m probably not the best person to speak on the tpl system, parts of that code still boggle me, @thedavidmeister might have more info

2017-11-28T21:07:37.000249Z

I am upgrading a lib to 6.0.0-alpha17, I have a couple of .hl files in it, after upgrading, the files are not being compiled anymore, I noticed I don't have a :source-paths entry, only a :resource-paths, but that also didn't work. the task does (comp (hoplon :lib true :pretty-print true)) (build-jar)) (removing the :lib attribute which does not exist anymore does not make any effect as well), any ideas?

flyboarder 2017-11-28T21:10:24.000428Z

although it should be noted that using manifest is undesirable in most cases, as it requires the consuming project to use the boot-hoplon tasks

flyboarder 2017-11-28T21:10:46.000156Z

not an issue if you are going hoplon all the way down

2017-11-28T21:11:43.000136Z

it worked! thanks again! yeap, that is not an issue for me

2017-11-28T21:13:52.000068Z

although, it hasn't actually compiled the files, so the :manifest makes the consuming project eventually compile them, is that right?

flyboarder 2017-11-28T21:14:09.000070Z

yes make sure you call the hoplon task in your main project

flyboarder 2017-11-28T21:14:32.000326Z

prior to compiling cljs

2017-11-28T23:20:58.000119Z

@rfhayashi this is really testing my memory of hoplon, but i think some early versions of the tpls were a bit buggy

2017-11-28T23:21:32.000234Z

might need to try a few different iterations of it to get the results you want