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

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

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

@thedavidmeister have you used Angular2 before?

@flyboarder angular 4 i think it was

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

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

it's like a monolithic framework that touches everything

i think react plays more nicely with others

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

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

ah ok

like someone literally asked if they could have a demo tomorrow

i laughed

hah

well they just want what you have

it's a good sign 🙂

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

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

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

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

:thumbsup:

now if only there were better UI kits available

what UI bits are you looking for?

i might have some elements that i could share

they are wanting us to shift focus to the webstore

should we shift this convo to a different chat?

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

yeah amelia said sunday she was free for a chat

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

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

I am anxiously awaiting the 1.9 release, builds still passing for hoplon tests 🙂

@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)

@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

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

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

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

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

so it will be hard to cherry pick anything to v6

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

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

@rfhayashi what did you change after upgrading to alpha17?

To get it working?

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

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

@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

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?

@rfhayashi :lib is now :manifest https://github.com/hoplon/boot-hoplon/blob/master/src/hoplon/boot_hoplon.clj#L148-L148

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

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

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

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

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

prior to compiling cljs

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

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