inkandswitch / farm Goto Github PK

Need a UI flow for removing gizmos from the launcher

Example widgets

• trivial static HTML rendering
• text input
• rendering other widgets
• importing a file
• generating a random number
• animating something

We've been stacking functionality without regard for the UI by using hot pink links and inputs. Should come up with a nicer UI for edit links, remove, and add gizmo flows.

Things to improve:

• Right-click -> "Inspect" and "Open console"
• Check in feed and fix
• Style things a bit
• Animation
• A single root doc in realm with all widgets
  • New widget button
• Fix root titles in extension (abc...123) and link titles (code-abc123)
  • [abc123] Doc title
• open dev tools by default
• make compiler errors visible in realm
• display compile errors in vscode
• get elm-format working in vscode
• include NoOp msg by default
• put main at very top of file
• put type alias Doc/State/Msg next to init and update
• use Html.div
• import Html.Attributes as Attr exposing (style) by default
• Open href links in chrome by default
  • unless it's hypermerge:// ?
• need forking
• display doc title in editor tab
• nav doc disappeared from vscode
• fix doc navigation in vscode
  • navigation is easy to get lost
  • right-click tree node -> "Add as root"
  • vscode recently opened docs?
  • vscode display "All docs" from ledger
  • don't expand nested docs
    • click to preview
    • save as new root on change or double-click
• need timeout on unloadable docs in vscode

A small feedback popup with something like "Share link copied to your clipboard!" will fix this.

Need a way to add new gizmo types to the "create gizmo" flow. A button/input which accepts a code url and adds it to the known gizmo types would solve this.

gozala [9:38 AM]
@pvh Do I need to build an app bundle to get farm:// links handled ?

pvh [9:45 AM]
'lo. shouldn't though it may be broken
@matt and @jeff reported it always worked for them but being on windows i just assume things like that need fixing to work for me 🙂

gozala [9:48 AM]
Hmm does not work on my end on OSX even if I have yarn start running (edited)

file me a github issue? i can look into it.

I created a chat gizmo and shared it between two of my computers. On reopening the document on the originating computer it was missing the reply from the second. I haven't dug in but for my own reference it was a chat named 'radchat'.

As a user/developer I often want to modify a gizmo or view the data. To do this, you currently need to either grab the root code and/or data urls, open them in VS Code, and navigate down to the documents you're interested in (which can be several levels deep), or you can use the chrome developer tools to find the relevant realm-ui element, and open its urls in VS Code - which is non-obvious, clunky, and slow.

Instead, this issue will implement a context menu which contains "Edit source" and "Edit data" options when a gizmo is right-clicked, which opens source and data documents in VS Code.

• good layout -- Msg by update, main at top etc
• NoOp message
• use element, not sandbox
• use Html.Styled
• non interactive renders a document

The current ways to add a gizmo to the launcher are:

• manually edit the data doc
• click a realm url to open the gizmo, which also adds it to the launcher.

Should be able to simply add a gizmo. This is lower priority because clicking a realm url does do this - just can't do it without popping windows atm.

They should probably show up somehow associated with the gizmo that caused them.

This is a bug, probably? We should either compile all of the app at startup or none. Ideally we should calculate based on changes.

A UI flow for forking gizmos and adding the forked gizmo to your launcher.

An example flow: pvh shares a chat gizmo with Orion. Orion wants his chat UI to have a hot pink background. Orion can right-click the gizmo, select the "fork" option, and a new gizmo appears in his launcher with a forked code/source doc and the same data doc. Orion can then modify the new gizmo however he likes without affecting pvh's original copy.

But ... how?

I get a lot of error output when I try yarn and yarn build and most of it seems to be complaints about ToObject inside .node-gyp.

I can try to dig in, but just checking if there's any quick ideas on the issue.

Here's the last page of the error output (there's a lot more, but it's similar):
``
/home/hryanjones/.node-gyp/12.2.0/include/node/v8config.h:322:3: note: in definition of macro ‘V8_DEPRECATE_SOON’
declarator attribute((deprecated(message)))
^
/home/hryanjones/.node-gyp/12.2.0/include/node/v8.h:2546:35: note: candidate expects 1 argument, 0 provided
Local ToObject(Isolate* isolate) const);
^
/home/hryanjones/.node-gyp/12.2.0/include/node/v8config.h:322:3: note: in definition of macro ‘V8_DEPRECATE_SOON’
declarator attribute((deprecated(message)))
^
sodium.target.mk:117: recipe for target 'Release/obj.target/sodium/binding.o' failed
make: Leaving directory '/home/hryanjones/Documents/github/farm/node_modules/sodium-native/build'
make: *** [Release/obj.target/sodium/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:196:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:257:12)
gyp ERR! System Linux 4.4.0-164-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/hryanjones/Documents/github/farm/node_modules/sodium-native
gyp ERR! node -v v12.2.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok"
info This module is OPTIONAL, you can safely ignore this error

I'm running on ubuntu 16.04, node version 12.

Thanks!
Ryan

Kind of a pain to click to another window to get it .