Enda Farrell

@sossienl Can you close this issue?

+1: I too would like this data.

I too need something similar. For many reasons, I cannot get all of my site into parcel (not parcel's fault) and of the options listed above I think I prefer...

Using conda and a fresh checkout of vibora: my ``environment.yml``: ``` name: vibora-py37 dependencies: - python>=3.7 - pip: - vibora ``` * ``conda env create --file environment.yml`` * ``conda activate...

Same on the v0.1.0 branch: ``` endafarrell@SpaceGrey ~/W/g/v/v/samples (master) [1]> git checkout v0.1.0 (vibora-py37) Switched to branch 'v0.1.0' Your branch is up to date with 'origin/v0.1.0'. endafarrell@SpaceGrey ~/W/g/v/v/samples (v0.1.0)> python...

OK: I realise I've made a mistake by having vibora in my conda env file. New env file: ``` name: vibora-py37 dependencies: - python>=3.7 - cython=0.28.3 ``` Then update conda...

You didn't create a Button, you created a base/abstract `H.ui.base.Element` which you called `button`. Try changing `button` to be a `new H.ui.base.Button`: https://developer.here.com/documentation/maps/3.1.18.1/api_reference/H.ui.base.Button.html

The /value/ that's exposed through crontab, .profile and therefore the command-line env is the API_HASHED_SECRET, not the API_SECRET itself. In the future I'd like to take a stab at updating...

I'm torn - but I understand that getting existing users to change things is not going to be a good ask. Is there a way that this could be flagged...

I think it's necessary that we have backwards compatibility :-o @sulkaharo I'm not sure that this is "significant" work, but I wouldn't quote myself on that just yet ;-) Perhaps...