When the user exits, they may have made edits which are not yet saved.

Steps:

1. Create a core.saveprompt.js file and include it in index.html.
2. Catch the updateItem event and change a 'item edited' flag
3. Catch user close and fire a beforeunload event which prompts save.

Current behaviour

1. Create a new document
2. Create an itemlist
3. Add some items
4. Press the cog
5. Press 'Save table'

Desired result: table opens in new tab

Actual result: table: table downloads as a file; must subsequently be opened

Synergist 1.0 was great, but synergist 2.0 is better!

However, many existing documents are still using synergist 2.0. Here's what we need to do:

• Allow synergist 1.0 to still be served but not visible on operator select. (We'll need to upgrade operator select to allow this.)
• Add an 'Upgrade to 2.0!' button in Synergist 1.0, and make it work.

Real workflowy allows you to drilldown into certain items; i.e. limit the viewport to just that item.
We could have this feature - it would make things look cleaner.

The navigation bar (or "nav bar" for short) is a critical component of any website or application, as it provides users with a way to easily navigate between different sections and pages. When designing a nav bar, it's important to consider factors such as the number of items that will be included, the hierarchy of the items, and the overall visual design. One common challenge in nav bar design is balancing the need to include all relevant sections with the need to keep the nav bar clean and uncluttered. This can be achieved through techniques such as collapsible menus or dropdown lists, which allow users to access additional options without overwhelming them with too much information at once. Additionally, it's important to ensure that the nav bar is clearly labeled and easy to use, with intuitive icons and labels that make it clear what each section or page represents. Overall, a well-designed nav bar can greatly enhance the user experience and help users find what they are looking for quickly and easily.

this.renderedItemCache is regenerated every time a new item is created. Instead, it could be improved by only updating the cache when an item is created or destroyed, saving on querySelector calls for large amounts of data.

We're currently using fullcalendar 3.0. Fullcalendar 4.0 has less dependencies and is probably more modern, so it would be good to switch to it.

Create a subitem system for Synergist 2.0, just like its predecessor Synergist 1.0:

Current behaviour:
Head to the website (acenturyandabit.github.io/polymorph).
Open a new document.
Click "itemcluster 2" to load an itemcluster 2 operator.
Double click to add a new item, and then double click elsewhere to add another new item.
When an item is dragged onto another item, the first item is added to the second item's subview and itemcluster navigates to the second item's subview.

Desired behaviour:
When an item is dragged onto another item, make the border red and dotted.
When an item is dropped onto another item, nest the first item in the second.

Also, a new feature:
When an item is dragged and held for some time onto another item, make the border purple and dotted.
When an item is dropped in this purple state, send the item to the target's subview.

Currently the mobile UI could do with some work (a new stylesheet).

Put it as a menu item under the (currently empty) "help" menu on the upper toolbar.

You'll have to wrangle with topbar.js which isn't documented suuper well (sorry) but you can learn the syntax off of the New and Load/Save buttons!

Extra thanks if you add some documentation to topbar.js so the next person to work on the topbar can see what's going on.

In itemcluster, there is a bottom tray that holds items which are not used.
When the context menu for an item in the bottom tray is hovered over, the bottom tray hides.
The bottom tray should not hide in this instance.
Fix this pls

A profile check shows that innerHTML=etc calls are causing lag.

Your mission, if you choose to accept it, is to hunt down as many innerHTML sets and eliminate them.

u should have a section of feedback a whole page and do not direct the user to an email box to write an email it can lead to minimize the number of feedback can come

Put it in the gear menu for list operator; make it create a modal with a table that can be copied into other applications like word.

Hey! If you're here from upforgrabs.net or some other site, comment below and I can help you get started! :) Don't feel obliged to do everything in all parts of the PR, one or two bits are fine :)

If you're lost, check out readme.md for details regarding some of the terminology.

Currently items can be deleted in two ways:

1. An operator 'forgets' about the item by deleting just enough information to not see it anymore
2. An operator calls for the item to be deleted using core.fire('delete',{id:itm}), and the item is deleted globally for all operators.

What the system should do:

1. An operator 'forgets' about the item by deleting just enough information to not see it anymore
2. The operator also calls delete using core.fire('delete',{id:itm})
3. Core goes around to all operators calling core.fire('updateItem',{id:itm}), and each operator responds with a true/false stating whether or not that item is still EDITABLE (not just visible)
4. If the item is not editable anywhere (all operators return false), then delete the item for real.

To achieve this:
1.a change eventAPI.js to handle return codes so that we can actually return true or false
1.a.1. Ensure that eventAPI.js retains original functionality so it is compatible with genUI
1.b. Ensure that all operators return either true or false based on whether or not an object is editable for it.
1.c. Create the delete function which fires updateItem and checks whether or not the item is editable, before deleting it
1.d. For all operators, change their delete functions to delete minimal information and call the core delete function.
2.a. Hook up function in 1.c. to core.on('deleteItem').
2.a.1. Also call deleteItem for all items during save to clean up any stragglers.

In itemList.js, I use querySelectorAll() for the resize handler which may be inefficient for large numbers of calls.

Additionally, while resizing, moving the mouse outside the textarea hitbox causes the resize to be canceled.

this needs to be fixed :3

Replace all instances of 'synergist' in the source with 'itemcluster', including file names. Shouldn't be too difficult.

Improve the tutorial and in-app documentation.

Use template.js!

Hi, I'm trying to use polymorph on my pc. I just extract the zipped file and run index.html with firefox.
It seems work but when I try to add mind map it didn't work at all. If I double click with left mouse button no one concept start.
Is it necessary to upload in a web server?
Is it possible to change the sky picture on the ground?
Sorry for these dummies question.
Thank you

Using either this delta system specified in quill.js: https://quilljs.com/docs/delta/
Or your own delta system, create a save method which allows two similar documents to be merged, and implement a versioning system.

Display a little indicator in the corner of the screen if the document has successfully saved (i.e. will not trigger save-on-exit prompt).

In synergist, when alt is held and an item is dragged, move all the items connected to it. In this way you can drag trees at a time.

To produce:

1. Click the save icon and press open.
2. Type in a new document name into the textbox.
3. Press enter.

Expected behaviour: This takes you to a new document just like the new doc button.

Actual behaviour: crickets

its slow :(

Collapsing items is currently bound to control+up which also opens the desktops menu on mac. Should replace with command+up

Oddly specific, I know. Should be fixable via an if statement.

Look in core_modules / core.palette.js. It would be cool if i could get a colour picker and edit the colour of my ui, and other aesthetic elements like the background image.

Literally what the title says. You'll be working in dialog.js, one of the UI extensions. Listen for the escape key press and close the dialog.