(ADDED) Squidink-Frontend Components

[bowring]

This compiles and runs. However, in browser I get the right hand side but the left hand side (filebrowser) tries to connect and then says '192.168.86.29 took too long to respond.' I need instructions for running file browser?

[bowring]

Even with rice embed-go running in http, I get the same error.

[RichardMcCarty1]

That's because your filebrowser endpoint is different from what the i-frame expects, If you go to src/constants/api there should be a constant called FILEBROWSER_URL, if you change that to 127.0.0.1:8080 it should pop up.

Just as a fore-warning, it will probably only pop up the log-in menu, not the full folder view. If you'd like to see what its like with the folder view you can log into Filebrowser in a separate tab then refresh Squidink and it should display.

[bowring]

still get same error although it first says trying to connect to localhost;

[RichardMcCarty1]

Is it still including the http preceding the IP such as "http://127.0.0.1:8080"?

Also is the filebrowser executable running such that its publishing on http://127.0.0.1:8080?

[bowring]

I made the constant "127.0.0.1:8080". and the connecting message says "localhost"

not sure what second question refers to as I just used rice ... am I supposed to do something else

[RichardMcCarty1]

You'll need to add the characters "http://" preceding the constant IP in the API folder. Javascript / HTML by their most default nature don't automatically apply the prefix if I remember correctly.

For the filebrowser, rice simply serves as a way for GO to package all of the static frontend components neatly, so images and .js files and the sort would be packaged for GO to then publish accordingly.

To actually run the filebrowser as a page such that you can access it, you have to go to the the parent directory (The one preceeding frontend or http or any of the other primary folders) and run filebrowser. For me, on my wiindows machine, it is called filebrowser.exe so simply inputting that opens it up. I'm pretty sure for you, you did "open filebrowser" in our last meeting.

[bowring]

lost the chat notes from google call; anyway browser opens in port 8080 but still get error on left hand panel of squidink

[RichardMcCarty1]

The most recent push should fix your issues. The I-Frame wasn't referencing the constant file, must've forgotten, my apologies.

So long as your Filebrowser is running you should be able to open up Squidink and see the log-in page in the far left. Ultimately it will resolve to the file structure once we route Squidink clicks to the filebrowser and then back to the Squidink endpoint, but in its current state you will just see the login page.

[bowring]

I am getting an infinite loop on the right switching between SquidInk and "your file is loading". and a flashing dot on the left

[bowring]

@RichardMcCarty1 - what's up with the package.json conflict?

[RichardMcCarty1]

@bowring Just resolved it, was a slight mismatch because I removed some unused dependencies.

[bowring]

➜  CirdlesWebUI git:(RichardMcCarty1-packageConflictFix) ✗ less /Users/bowring/.npm/eresolve-report.txt

      }
    ]
  },
  "currentEdge": {
    "type": "prod",
    "name": "react",
    "spec": "^17.0.1",
    "from": {
      "location": "/Users/bowring/Development/CirdlesWebUI"
    }
  },
  "edge": {
    "type": "peer",
    "name": "react",
    "spec": "^16.14.0",
    "error": "INVALID",
    "from": {
      "name": "react-dom",
      "version": "16.14.0",
      "whileInstalling": {
        "name": "cirdlesweb",
        "version": "0.1.0",
        "path": "/Users/bowring/Development/CirdlesWebUI"
      },
      "location": "node_modules/react-dom",
      "dependents": [
        {
          "type": "prod",
          "name": "react-dom",
          "spec": "^16.13.1",
          "from": {
            "location": "/Users/bowring/Development/CirdlesWebUI"
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}

[bowring]

did some forcing and got it to take

[bowring]

seeing this:

[RichardMcCarty1]

From the looks of it, the issue is caused by dependency versioning, see here. Your forcing then seems to remove most if not all of the styling associated with the components. Did you happen to run an update on the dependencies?

[bowring]

keep getting this or some flavor of this 👍

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: cirdlesweb@0.1.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from radium@0.26.1
npm ERR! node_modules/radium
npm ERR!   radium@"^0.26.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 

[bowring]

i will try another clean clone

[bowring]

same problem ... do you have a way to update dependencies other than https://flaviocopes.com/update-npm-dependencies/

[RichardMcCarty1]

You can manually change dependencies in the package.json and remove them from node_modules to force them to revert, but beyond that I believe the only method is npm install packageName@version# i.e React@16.8.0.

Supposedly this line will fix this specific issue, seems to be common, from here npm install --save radium --legacy-peer-deps

[RichardMcCarty1]

I'm pulling down a clean clone as well to see if I have a similar issue and to see about resolving it as well.

[bowring]

this works: npm install --save radium --legacy-peer-deps. thanks!

[RichardMcCarty1]

Yeah my clone came up clean so I suppose it's good that that line worked. If it ends up being a recurring issue in additional install cycles we can look into a method for resolving it permanently.

[bowring]

UI looking good!

[RichardMcCarty1]

I removed the package-lock from my branch; however, because it exists as a file in the master of Cirdles/CirdlesWebUI it's throwing a conflict.

[bowring]

Spot average choice did not stick

[RichardMcCarty1]

@bowring Spot Average should now stick between refreshes / sessions, changed the routing from Skeleton to manageproject, and fixed the Z-index for the dropdown in manageproject.

Still working through the rest of the list but that's a temporary update.

[bowring]

Wrong file is specified in Project File item - it shows previous quid file name

[bowring]

also, get this when try to serially open files:

Cannot GET /squidink/manageproject/manageproject

[RichardMcCarty1]

For the project file name, are you saying that when you open a second project the name of the first project you opened is persisting? And for the serially opening files, I take it you're opening a demo file from the manageproject screen?

I can't gain reference to the standard react-router format for redirecting users from the constants file where the POST request for demo file is stored so I just manually force an update to the href so I'll add in a check to see if the user is still on manageprojects and if so push a refresh instead.

[bowring]

it appears above is related to file manager quitting. However, If I open a project and then try to open demofile, I get the error: Cannot GET /squidink/manageproject/manageproject

[bowring]

Nice! - all seems well except file manager menu seems dead now

[bowring]

Much better!

[bowring]

maybe we should have a Files / Manage Files menu item to the left of Project that opens the filebrowser

[RichardMcCarty1]

I can look into it, there was a point in time where you could open/close the filebrowser from a dropdown option in the Project dropdown, I'll have to add the dropdown to the manageproject page but I don't see it being an issue.

[bowring]

it appears the project file text is not updating correctly in the manageproject window

[bowring]

at least when the default project is loaded on top of another project.

there is another project you can use inside the resources of squidcore to check this

[bowring]

Still have issue with Project File text from above.

[bowring]

Project page border looks good; still needs scroll when slightly collapsed

[RichardMcCarty1]

Yeah I haven't been able to investigate the project file issue but its next on my docket.

[bowring]

I like! The window is well-behaved with resizing, which is also great!

[bowring]

that fixes the fie loading!

[bowring]

Looks like we lost the layout and scrolling part of manageproject; see my pull request to this branch for updates re: about etc.

[bowring]

Looking good so far!

[bowring]

Nice!

[bowring]

something is amiss ... I change analyst name and it save it to the projrct name then the file name is changed to something else?

[bowring]

looking good

Issue: the two spinners need refinement: 1) they jump around a little when plus sign is pressed 2) they should be constrained to [0,1] (inclusive) and show only 0.00, 0.05, 0.10, 0.15 ... 1.00

[RichardMcCarty1]

The most recent push introduces all the model / model data handling and generation as well as some more linking between the SquidAPI and the components within the Spot Management page.

Next push should finish the Spot Renaming functionality, wrap up the left-side context menu as well as the (C)RM context menus, and handle the information received from the spot audit to generate error/warning text.

[bowring]

Thanks!

[bowring]

looking good