Skip to content
This repository was archived by the owner on Jan 7, 2025. It is now read-only.

Conversation

@BienioM
Copy link
Contributor

@BienioM BienioM commented Nov 15, 2017

#73 Part 2.
Basic description/'importants':

  • QuickTemplate component.
  • Read/parse output*.json JSON only for current page/index
  • Show component inside modal
  • No connection to main-window/scope, so you can't open QuickTemplate yet
  • Very simple paging - grid

@kamil-mrzyglod
Copy link
Contributor

Two things:

  • how can I access QuickTemplate to test it?
  • I get following error by running npm run dev command:
    0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'aqt-merge' ] 2 info using npm@5.4.2 3 info using node@v8.8.0 4 verbose run-script [ 'preaqt-merge', 'aqt-merge', 'postaqt-merge' ] 5 info lifecycle ARMata@1.0.0~preaqt-merge: ARMata@1.0.0 6 info lifecycle ARMata@1.0.0~aqt-merge: ARMata@1.0.0 7 verbose lifecycle ARMata@1.0.0~aqt-merge: unsafe-perm in lifecycle true 8 verbose lifecycle ARMata@1.0.0~aqt-merge: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\MINE\ARMata-fork\node_modules\.bin;C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\MINE\ARMata-fork\node_modules\.bin;C:\Program Files\Microsoft MPI\Bin\;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Program Files (x86)\Yarn\bin;C:\Users\kamz\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\Microsoft VS Code\bin;C:\Users\kamz\AppData\Roaming\npm;C:\Users\kamz\AppData\Local\Yarn\bin 9 verbose lifecycle ARMata@1.0.0~aqt-merge: CWD: C:\MINE\ARMata-fork 10 silly lifecycle ARMata@1.0.0~aqt-merge: Args: [ '/d /s /c', 'node _aqt_merge.js' ] 11 silly lifecycle ARMata@1.0.0~aqt-merge: Returned: code: 1 signal: null 12 info lifecycle ARMata@1.0.0~aqt-merge: Failed to exec aqt-merge script 13 verbose stack Error: ARMata@1.0.0 aqt-merge:node _aqt_merge.js13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16) 13 verbose stack at emitTwo (events.js:125:13) 13 verbose stack at EventEmitter.emit (events.js:213:7) 13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack at emitTwo (events.js:125:13) 13 verbose stack at ChildProcess.emit (events.js:213:7) 13 verbose stack at maybeClose (internal/child_process.js:927:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 14 verbose pkgid ARMata@1.0.0 15 verbose cwd C:\MINE\ARMata-fork 16 verbose Windows_NT 10.0.14393 17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "aqt-merge" 18 verbose node v8.8.0 19 verbose npm v5.4.2 20 error code ELIFECYCLE 21 error errno 1 22 error ARMata@1.0.0 aqt-merge:node _aqt_merge.js22 error Exit status 1 23 error Failed at the ARMata@1.0.0 aqt-merge script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

should I run some command before?

@BienioM
Copy link
Contributor Author

BienioM commented Nov 28, 2017

To test, you need to merge last part: #85.

No connection to main-window/scope, so you can't open QuickTemplate yet

This PR purpose is to allow you to check QuickTemplate.js and it's source code, before connection to MainWindow.....and ...divide this PR into sub-PRs so it'll be easier to manage those changes

  • I'm still using const templates = JSON.parse inside generateGrid()m but now we have many outputs*.json files (each max 10-element)
  • QuickTemplate now reside within Modal
  • Redux state of currentPage, and action changePage

...if you want to test, before merge -> you can use #85 where you have all changes (1/3, 2/3 and 3/3).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants