flynx/ImageGrid
1
1
Fork 0
mirror of https://github.com/flynx/ImageGrid.git synced 2025-10-29 10:20:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

more notes...

Browse Source 
Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
This commit is contained in:
Alex A. Naanou 2023-07-27 13:10:02 +03:00
parent a74d745dc1
commit 623689f592
1 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Viewer/doc/NOTES
View File

@ -3,21 +3,23 @@
Initial build Initial build
============= =============
The `Makefile` handles all the dependencies in all cases but the first run The `Makefile` handles all the dependencies in all cases but the first
on a clean system can take a while because `make` uses `npx` to bootstrap run on a clean system can take a while because `make` uses `npx` to
the required apps/libs. bootstrap the required apps/libs.
It is recommended for a clean setup to either run make twice or run an It is recommended for a clean setup to either run make twice or run an
`npm install` first, this needs to be done to avoid version leaking from `npm install` first, this needs to be done to avoid version leaking
the bootstrapped or global node packages to the build as defined by `package.json` from the bootstrapped or global node packages to the build as defined by
`package.json`
Version numbers Version numbers
=============== ===============
The app version number is automatically synced between package.json (primary) The app version number is automatically synced between package.json
and version.js, all version changes should be made in the former. (primary) and version.js, all version changes should be made in the
former.
@ -52,8 +54,9 @@ node-enabled RequireJS instance or node require.
The ideal solution would be to use one require that sees both the browser The ideal solution would be to use one require that sees both the browser
and node contexts, the problem is exactly in this, the browser requirejs and node contexts, the problem is exactly in this, the browser requirejs
does not see either node or node modules while the node require loads code does not see either node or node modules while the node require loads
that is not visible to devtools unless it is running at that exact moment. code that is not visible to devtools unless it is running at that exact
moment.
Thus we are forced to use both mode requirejs loaders which may be Thus we are forced to use both mode requirejs loaders which may be
confusing at times. confusing at times.
@ -91,8 +94,9 @@ arguments combining it with ig.js would make things much-much slower...
- index.html - Browser - index.html - Browser
- electron e.js - electron - electron e.js - electron
<-> ig.js - parse args if given and optionally <-> ig.js - parse args if given and
return control back to e.js... optionally return control back
to e.js...
- ig.js - node - ig.js - node
-> e.js - node can spawn an electron app -> e.js - node can spawn an electron app