telescopest/telescope

Telescope is an engine for efficiently creating meaningful visualizations

telescope's Issues

Interactions are too long after upgrating Cytoscape version

Layout: Composites should consider the labels for the positions

TLStyleCustomizationAction>>#actionOn:

This method does not seems to be used. Instead the #regularActionOn: and #reversedActionOn: are used.

Is there a case I miss? Is it still needed or is it an artifact from the past?

Enable CI 64 bits

Currently, we test only 32bit. Would be cool to also test 64bit.

TLConnectAction does not work with Cytoscape

Get a lot of `XX not found` after saving.

When I save my image with Telescope I get a lot of key XX not found in Dictionary errors because of the websocket.

Impove Demo page

• Style (CSS)
• Text area to create our own visualization on web
• See the code of the visualization
• If a demo fail, catch the exception and show an error message
• A description of the demo?
• Labels and filter in demos?

Correct Telescope test failures

Need a forced based layout

TLHide actions does not work with Cytoscape

Rename test packages to follow a convention

Seems to have a bug on menu interactions update when an entity change of group

See in Cytoscape #examplePathBuilder. When an entity change of group it is still the old label in the menu (but the action is right)

TreeLayout: the graph should use a width route and not a depth route to place nodes

With this method if a node is a child of two nodes from different levels it will be on the right level.

Correct Telescope Cytoscape test failures

Add a template to visualize a project map from a ConfigurationOf or a BaselineOf

Telescope should not depend on BabyMock 1 and 2

The tests requiring baby mock 1 should move to baby mock 2.

Customizing connection with the TLConnectAction might berak the visu during the update

I don't have a reproducible case for now :(

TLDistribution map seems abnormaly slow

Remove action: create an action to remove multiple shapes with one command

Instead of sending X commands.

Cytoscape: could be cool to get source and target label to do some visu as UML

Cytoscape properties:
source-label : The text to display for an edge’s source label.
target-label : The text to display for an edge’s target label.

To add to the connections style.

Need to implement DoubleClick interaction with cytoscape.

When we add a style to an element we should maybe not update the layout all the time.

It's too much work when sometimes it is not needed.

Extract all the subclass of TLVisualization in another package "VisualizationTemplates"?

Finish to remove references to Roassal

TLTreeLayout should redefine #topToBottom & co

Because this is not the right orientation for this kind of layout.

I used a #rightToLeft and the result is closer to the #topToBottom

Should we implements #isLeaf of nodes? (EOM)

TLStyleCustomisationAction does not revert all the time

I have a composite with node inside. Some nodes have connections. On mouseOver I add some style to the connections but the revert action is not called when I leave the drawable with the interaction.

Demo not working on chrome

TreeLayout: using incomming link with multiple root node can make connections cross

Removing connections should not update the node?

When we add a connection to a node we flag it for update. But when we delete a connection we do not flag it for update. Is that normal?

Should we update a node if we add a connection? (EOM)

For V1.0.0 disable all broken demo visualizations

Cytoscape: Title are not displayed?

Cytoscape: problem with interaction in exampleMovingNodeToAnotherGroup

In this demo if you go on the node "a" then click the node will stay red. It should turn back to orange when moving to the second group.

#addCompositeDefaultCollapseInteraction broken on Cytoscape

StarVisualization depends on a RTClusterLayout not here anymore

Demo: click to unfold button works only at one level then do nothing

See for example demo CompositeExploringHierarchy

The layout update can do unecessary work.

I am not sure of the exact way to reproduce but I had this problem:

I have a composite node with composite nodes inside. I added an interaction of mouseOver to add some connections. The connections had no influence on the layout. But if the layout was update when we added the connections, a lot of nodes where update and the composites with no child inside were changed and took all the height possible.

I consider this as a bug because if a layout is updated while we did not added/deleted anything, it should not change the visualization.

Cytoscape: Add Legend for connection style

As we did for the node shape.

Removing a composite should not remove all the child

If a framework does not remove the children of a composite by himself it should be managed in the connector and not the model.

Asking if a composite has children to display during the legend building make the layout update at the first interaction

This happen because of the defensive strategy on the #expended of the Composite node. While we build the legend, the nodes are already in place but we create a requirement for a layout update.

Legend: Add group and columns

I think it would be good to have some "groups". For example

Connection style
--------------------
---   Something
....   Something else
___   Something new

Border style
--------------------
…

Also it could be cool to be able to say way want columns when the legend is too big.

Cytoscape: Hidden nodes are rendered at visualization openning.

For example:

| visualization secondNode firstNode thirdNode |
	visualization := TLVisualization new.
	visualization layout: (TLLinearLayout gap: 50).
	firstNode := visualization addNodeFromEntity: 2.
	secondNode := visualization addNodeFromEntity: 1.
	secondNode styleSheet nodeLabel: 'Click on me!' position: #top.
	thirdNode := visualization addNodeFromEntity: 3.
	thirdNode hide.
	secondNode
		addInteractions:
			{(TLHideAction on: firstNode) onClick.
			(TLShowAction on: thirdNode) onClick}.
	^ visualization

Here the visibility of thirdNode is set to false but the node appears during the rendering.

Remove everything relatif to positions.

Extract demos to their own package

Tree layout mix elements order

Example

| visu |
	(visu := TLVisualization new)
		addNodesFromEntities: (1 to: 9);
		layout:
				(TLTreeLayout new
						useOutgoingLinks;
						leavesGap: 40;
						levelGap: 20;
						yourself);
		addInteraction: (TLExpandCollapseNodesAction property: [ :n | (0 to: 9) collect: [ :i | n * 10 + i ] ]) onClick;
		yourself.
	visu styleSheet nodeLabel: #asString.
	^ visu

Here I get the nodes in this order: 3 4 2 7 1 6 5 9 8

But when I expand a node, they are in the right order.

Debug visu does not manage groups.

In the TelescopeOnWeb demo.

Cytoscape: #exampleRecursiveCompositeNode seems broken

Layout: New layout would be cool for the NameCloud

Maybe we could have a circular layout including elements in the center. That would be really cool for the Name Cloud for example.

Cytoscape: Improve management of TLNoShape

I think we can find a way to put a node with a transparent background and border instead of raising an error.