Per Akos's request

the inheritance relation should point towards the base type (as it is in the META editor) not the other way around

• canvas should not be red
• reset to base class value icon is not snapped to property value field

Also add share button to get url to active object (and state)

Look at intro.js

Models with self containment enabled in the meta are not allowed to be created.

See screen below.

In UI header/footer redesign effort I am planning to externalize the html segments found in FooterControlPanel.js into a stand-alone template file and load it with require.js but the loading of the template.html results in an exception on the server-side which is not handled and the server stops. See screenshot.

This technique is used at other places but not right in the initialization process.

The tree-browser currently doesn't show some names with some special characters (although those names are visible elsewhere like in the composer or property editor).

example: "<"example">"

JSDoc

• http://usejsdoc.org/about-tutorials.html

Identify all public APIs.

• Configuration - Patrik
• Storage APIs (db/project/etc.) - Patrik
• Core - Tamas
• Plugin - Patrik
• Blob - Zsolt
• Executor - Zsolt
• Bin scripts
  • apply - Tamas
  • diff- Tamas
  • export - Tamas
  • import - Tamas
  • merge - Tamas
  • run_plugin - Patrik
  • start_server - Patrik
  • usermanger - Zsolt
• Rest APIs
  • users - Zsolt
  • projects - Zsolt
  • organizations - Patrik
  • plugin - Patrik
  • executor - Zsolt
  • blob - Zsolt
• WebSocket API - post-pone.

The readme file should contain:

Plugin

• Requirements
• Conceptual design
• Class descriptions
• Code has to be reviewed and comments cleaned up. (e.g. meta-type, META type, etc.)

Requirements - Status bar

To reproduce it:

• create a branch called 'b' or 'backup'
• reload the page
• 'b' or 'backup' branch is loaded instead of master

Observation: the branches are ordered alphabetically and the first one is loaded.

see what can be done to make touch events work

A standalone tool might provide a short-term solution for doing one-way meta and library udates.
The meta (and library) will have to reside in a dedicated containment tree with incoming relations (pointers) only.

Alt + mouse scroll => Ctrl + mouse scroll

If you lasso select multiple objects and then try to CTRL+Lclick copy them, the object you made your final click will be missing from the selection...

Now the containment relation cannot be seen on the crosscut editor. This could be enhanced.

Need for replacing tree browser and unifying context-menus across the UI.

Requirements - Tree browsers

Also, extend state to store panels, panel and visualizer. -- this is pushed to later.

Use the state object that we already have.

This would be useful for testing plugins. The only way to do this right now seems to be to export the project and import it again.

Background of the selected hex value should be the selected color or currently active color.

It would be easier to navigate the projects. The browsers might support this functionality if the full REST URIs are updated in the address bar.

Add maybe solution based on moments.js

WebGME version [email protected]

Using the mongo at zsolt-ws.isis.vanderbilt.edu (maybe Zsolt can give you a copy of the data files, or you can connect to it)

Trying to "Export Project... " CyPhyLight, i.e. GETing
http://localhost:8888/rest/etf?project=CyPhyLight&root=%238282dcbc609c855a1c0eb204820a862370450666&path=&output=CyPhyLight_master

Results in this stack:

C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\util\assert.js:17
                        throw error;
                              ^
Error: ASSERT failed
    at assert (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\util\assert.js:12:16)
    at Object.core.getAttribute (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\coretype.js:257:4)
    at Object._core.getMiddleGuid (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\guidcore.js:87:51)
    at Object._core.getGuid (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\guidcore.js:94:32)
    at UnwrapListener.callback (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\coreclient\tojson.js:320:65)
    at UnwrapListener.onResolved (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:502:8)
    at Future.resolve (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:51:17)
    at tasync_trace_start [as onResolved] (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:379:9)
    at Future.resolve (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:51:17)
    at tasync_trace_start [as onResolved] (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:379:9)
    at Future.resolve (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:51:17)
    at tasync_trace_start [as onResolved] (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:379:9)
    at Future.resolve (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\core\tasync.js:51:17)

Using the project from the tutorial. If you delete the meta sheet, you cannot create new models until the models are dragged back onto a meta sheet. The meta information is maintained in the models themselves and being on a sheet should not affect behavior.

Before the deletion of the meta sheet.

After the deletion of the meta sheet.

It would be useful if we could locate an object in Object Browser from the Editor

A generic-enough solution for browsing assets, most importantly icons and maybe replacing the project browser interface.

If a connection is closed by the OS (because the client process exited), WebGME crashes.

Running this:

C:\Users\kevin\Documents\blob-testing>type close_conn.js
var net = require('net');
var socket = net.createConnection(8888, 'localhost');
socket.on('data', function(data) {
  console.log('RESPONSE: ' + data);
}).on('connect', function() {
  // Manually write an HTTP request.
  socket.write("GET / HTTP/1.0\r\n\r\n");
  throw ""; // this kills the process
});

Results in this:

C:\Users\kevin\Documents\webgme-domain-tools>node app.js
   info  - socket.io started
worker 6984 is ready for tasks

http.js:689
    throw new Error('Can\'t set headers after they are sent.');
          ^
Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (http.js:689:11)
    at ServerResponse.res.setHeader (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\node_modules\express\node_modules\connect\lib\patch.js:59:22)
    at SendStream.setHeader (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\node_modules\express\node_modules\send\lib\send.js:469:44)
    at SendStream.send (C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\node_modules\express\node_modules\send\lib\send.js:345:8)
    at C:\Users\kevin\Documents\webgme-domain-tools\node_modules\webgme\node_modules\express\node_modules\send\lib\send.js:323:10
    at Object.oncomplete (fs.js:107:15)

Enable in meta view

We have seen this on Mac and Windows. We do not know how to reproduce it. We have seen it when the webserver was running from 'home' and connected to a mongodb, which is located at 'work'.

/Users/zsolt/GitHub/webgme-domain-tools/node_modules/webgme/storage/mongo.js:145
                        mongo.collectionNames(function (err, collections) {
                              ^
TypeError: Cannot call method 'collectionNames' of null
    at Object.getProjectNames (/Users/zsolt/GitHub/webgme-domain-tools/node_modules/webgme/storage/mongo.js:145:10)

If you try to export a project without have an active project, you get a black screen with "Bad Request" in the top left. It should probably fail more gracefully.

I attached a screenshot of the error screen.

Branch names that have invalid characters (spaces, dashes, quotes, etc.) crash the server in such a way that if the server is restarted while the browser is on the repository page, the server keeps on crashing.