Trying to load npm package justgage into UIBUILDER 7.4.3 NR 4.0.9

Dashboard
21

Just one question.

Raphael is apparently downloaded with Justgage. I can’t seem to see where these paths are derived from.

Looking at File Explorer in node_modules Raphael and Justgage are in two separate same level directories, and there is no Raphael under Justgage, so how does the ‘tree’ work? Is there some kind of command in Justgage to show where Raphael is?

UIBUILDER libraries only shows Justgage available.

EDIT: Node_modules in the uibuilder directory

22

Not totally incorrect..

Reading the justgage install guide - justGage says;

“Include JustGage and Raphael scripts in your page.” So was not aware that justgage was actually bundled with Raphael, and I loaded both as separate libraries. Obviously a duplication, but it made life easier because it was easier to determine their paths.

I seem to recall that Justgage is in the root of the Justgage library, and Raphael is in a sub- directory called of course raphael, but I could be wrong.

23

I see and understand what you are saying,

I am trying to get my head around this, purely because it is not yet clear. This is the deepest I have been into npm, so you will have to excuse my ‘innocence’ and on getting a grasp on what it happening.

24

It was a is a learning curve for me too, and I've not necessarily got things right, for example a lost of my javascript needs further work to integrate the chart etc into my 'Centralised Message Handling'.

It seems that all the pieces for UIBUILDER are documented & available, but arranging those pieces into the jigsaw is proving hard.
It would be very useful to have some very basic templates to work from, especially for SPA structures, which introduce a number of problem areas for none-professional users.

1 Like
25

And this is something that needs work for sure. In truth, it isn't really UIBUILDER causing this but the strange life of JavaScript library developers who don't quite seem to be able to get to a solid standard for everyone.

This is why there are caveats in the library manager in uibuilder. There ARE standards for declaring where the top-level entry point is for a library. But not everyone uses them and some people misuse them.

And, using a library from a CDN often has different entry points to when you install it using NPM!

This is also why I just make the whole library's folder structure available to the front-end when you use the library manager to install things. Because it is literally impossible to know where the necessary files might be.

Very frustrating all round. If it makes you feel any better (I won't!), I have the same issues.

If you can at least identify some that may be needed, I will work them up for sure.

26

As a novice in all this, I am learning all the time, which is one of the things that gets me up in the morning! I have used Julian’s examples to help me along the way, and agree, the information is there, but to me, at times, I have found it confusing, mainly because I want to run before I can walk. Your flows have really helped me a lot in this journey.

Reading the manual is not something I do easily. The problem is, I see an idea and, like a kid, want to run with it, so only me to blame!

I/We are lucky in that people on this Forum with more experience than me/us are ready to help work through our problems. A fact of which I am truly grateful for.

To me, the ‘modern’ programming style seems similar to what I was using back in the 80’s on a far larger scale. Lots of Subroutines to carry out specific tasks called from a main routine. It is just that bigger ‘subroutines’ exist these days. pulled together by a central routine. That is of course if I understand correctly.

27

Oh, don't worry, you'll still be doing that many years from now! I certainly am.

:wink: Well don't forget that I was taught my programming skills in the same way. Some things don't stop being good.

Yes, things got a lot bigger and more complex, that's for sure. But the central routine thing was there before in most cases - unless you were directly bit-bashing hardware. It just got a bit more complex.

Fun fact, my Dad worked on the first computer at Cadbury's. It was made by Singer (yup, the sowing machine manufacturer!) and was programmed using toggle switches.

Years later, I ended up working on the computers at Cadbury's as well. Except, by then, they were £10m+ worth of IBM mainframes and a room full of tape drives (the big-cupboard sized ones) and hard drives (the ones the size of slightly smaller cupboards). For operations, we used punch cards, magnetic tapes and green-screen cathode-ray tubes. :rofl: