fcatools / conexp-ng Goto Github PK

Opened dialogs (like "Count Concepts") are not centered in the main frame. I tried to fix it quickly but this problem seems more involved. Here is a link to get one started: http://stackoverflow.com/questions/10283532/set-location-of-jdialog-relative-to-jframe

Write a nice About page.

Analogous to ConExp's Expert Mode for fast editing of contexts but extended, create a shortcut concept and its corresponding implementation of an Expert Mode for ConExpNG.

In my opinion this shortcut concept should mimic VIM's unique mode of editing. E.g.

• hjkl moves the active cell through the context,
• L toggles the current cell and moves to the right cell or to the first cell in the next row,
• J toggles the current cell and moves to the cell below or to the first cell in the next column,
• ...
• g / G jumps to the first/last object,
• 0 / $ jumps to the first/last attribute,
• d / D removes the current object/attribute,
• o / O adds a new object below/above the currently selected row and lets the user input an corresponding name,
• ...
• shortcuts for selections, renaming
  • click on an attributename or object to select only the row or column
  • select other entries by shift+arrowkeys
  • moving attribute or object by ctrl +arrowkeys
  • renaming by r/R for object/attribute
  • click on the first cell to select all
• ...

Since creating the ConExp-mimicking context editor from scratch was enough work as it is, I did not invest much time into the implementation of an expert mode although I believe it would be worthwhile to have it.

Don't forget to provide an explanation of the various shortcuts in the User Guide!

Put state.contextChanged (like in 0e0bf15) in all the appropriate places so that other parts of the program register when something about the context changes.

Please activate anti-aliasing

take a look at ConExp clj and find thinks to imitate.

ConExp's context editor has the option to show arrow relations in the context editor. Provide a togglebutton in the toolbar with the same functionality.

Fill the following wiki page.

We should use some evaluation techniques (e.g. heuristic evaluation) for ConExp's GUI in order to find problems we don't want to recreate and in order to create a better mockup for our new GUI. To that end, we should also obtain a list from Mr.Jäschke in which he describes his personal gripes with ConExp.

Mr.Jäschke suggested that there are problems in terms of zooming inside tha lattice view since, internally, only Integers are used (?).

We need to invent a catchy name for our project.

I think the document tree is out of place. Can there be several roots, i.e. can you have several files opened at the same time? Can a file have more than one context? To both questions the answer is no. It seems to me that this tree representation is superfluous and a much simpler representation would get the job done much better.

This yet-to-be-conceived representation does only have to offer the following capabilities:

• Show filename (although even this could be shown somewhere else)
• Show the list of lattice views (btw: they should be renameable)
• Show links to calculated implications/associations (although even this bould be shown somewhere else)

Allow reordering objects/attributes e.g. by dragging the corresponding header cell. Also provide keyboard shortcuts for moving rows/columns around. Don't forget to update the user guide.

Use free icons in place of ConExp's icons. The creation of a handful custom icons may be needed.

First of all, it should be possible to only resize the objects column, e.g. it makes sense if your objects have long names. To this end, if the mouse is over the vertical line of the first column transform mouse button to resizer and allow resizing while dragging.

Then, it also makes sense to allow resizing of the other columns if the attribute names are long. But for consistency, all attribute columns should always have the same length. Provide the the resizer interaction but only in the attribute header cells.

Note, the column width should be saved in the program state and ideally also in the saved file.

ConExp has cut/copy/paste options in the context menu for selections inside the matrix. Currently, these menu entries do nothing. Implement the functionality (it won't be very trivial to be honest).

Implement the clarify objects/attributes operations.

ConExp only supports unary formal contexts. It would be great to support the creation of many-valued formal contexts where the input of ordinal or scalar data is possible.

Note: Mr.Jäschke suggested that these many-valued inputs could be transformed into binary inputs internally? If possible this reduction would probably make the implementation easier. See also slide 24 of Introduction to FCA ICFCA2004: "The process of creating single-valued contexts from a many-valued data set is called conceptual scaling."

How to handle this problem GUI-wise?

• The Elba User Manual provides an illustrated GUI-flow of working with many-valued contexts.
• The program SPSS provides a way to enter many-valued data.

Implement the reduce objects/attributes/context operations.

This way it will be fast to test the results of the new layout algorithms.

Verify that the problems in ConExp Problems do not exist anymore in our version.

If the user tries to exit the application while having unsaved changes a dialog, like in every other GUI, should pop up reminding the user of this fact and providing appropriate actions.

... or at least so modular that it can easily be exchanged by another algorithm. In particular, the algorithm should have no dependency to the GUI (Swing) classes (and vice versa).

The idea to have it as a separate library would be that other developers could easily re-use it.

Put generated JavaDoc in the gh-pages branch and put a link to them in the Developer Guide.

Put state.contextChanged (like in 0e0bf15) in all the appropriate places so that other parts of the program register when something about the context changes.

ConExp allows a more compact view of the context. Add a togglebutton in the toolbar that, when toggled, shows this compact representation.

Remove unnecessary batik dependencies from pom.xml. Currently, I've just added every batik lib I could find just to be sure but I'm positive that we are only going to use a tiny fraction of these.

We need to set a lower bound for the main window's size so that it is impossible to hide essential GUI elements by resizing the main window.

IIRC, one can style style SVG files with an CSS-like language. It would be cool, if we had the ability to choose from several styles. E.g. one basic style and one Latex-like style. Then Tikz-Export would be superfluous, imho. Maybe we could even discover css files in certain locations (folder, where ConExpNG.jar resides and ConExpNG settings directory) and if found, present these additional styles as an option in the GUI.

Register the context editor actions/operations with the global Undomanager

ConExp's default file format has some deficiencies

1. Calculated implications/associations are not saved => If the file is reopened these, in parts time-consuming, calculations must be repeated
2. According to Mr.Jäschke the structure of the XML files per se is not very elegant

At the very least we should resolve the first problem. Here & here is some useful information for a possible file format.

Extra data that needs to be saved:

• implications/associatons
• graph & snapshots (each snapshot must remember the subset of selected objects/attributes)
• column widths

Hi, could we add Daniel Borchmann (the developer of conexp-clj) = https://github.com/exot to the project?

Thanks

Implement the according functionality in the context menu (analogous to ConExp).

Include a folder examples that contains several examplary contexts as xml files. Their purpose is twofold. For one, they serve as examples for the users. On the other hand, we can repurpose them for internal testing.

Make the Home page pretty.

Create a google group and correctly link to it from the wiki.

I believe it would be great, especially for bigger contexts, if both the attribute header row and the object header column would stay visible at all times. When scrolling horizontally, the attribute header row would scroll horizontally, too, and when scrolling vertically, the object header columns would scroll vertically, too.

enums for property changes.

Hier noch mal die Use Cases (dann muss man nicht immer in der Dropbox nachschauen), die meines Erachtens umgesetzt werden sollten. Jedoch habe ich noch keine Sortierung nach Priorität reingebracht.

Use-Cases:

• Neue Datei erstellen
• Datei öffnen
• Datei speichern
• Programm schließen (extend "Datei speichern")
• Anzahl der formalen Begriff berechen (nötig?)
• Objekten Attribute zuweisen / Attributen Objekte zu weisen
• Redundanz entfernen
• Objekte löschen
• Attribute löschen
• Verband erstellen
• Attribute selektieren
• Objekte selektieren
• Verband bewegen
• Knoten bewegen
• Verband partiell makieren
• Verband als SVG exportieren
• Verband als PDF exportieren
• LaTeX-Code des Verbands anzeigen
• Verband-Anzeige ändern
• Assoziationsregeln berechnen
• Implikationsregeln berechnen
• Attributexploration starten
• Visualisiere Attributexplorationsfragen (include "Attributexploration starten")

It should be possible to export the lattice in a paper friendly format.

When I modify the width of a table column in ConExp and later on add an attribute or object, all widths are reset. That's annoying.

Create an illustrated User Guide. Generally stick to ConExp's documentation but enhance it with annotated pictures.

Maybe even create a short video tutorial and upload it to youtube.

See also the following ressources for insipiration:

• ToscanaJ User Manual

Create an UML diagram till monday the 17.6.

Import of ConExp files must be possible! Backwards compatibility! Everything else would be bad, as users would somehow need to (manually) recreate their potentially large contexts. We can't expect users to do this.

Structure the code in a way so that it is easy to add new layout algorithms. To that end implement at least two different layout algorithms and try to extract an abstract interface from them. In addition, provide a section in the developer guide that explains how to add a new layout algorithm as the addition of a new layout algorithm will probably not only entail the implementation of the algorithm per se but also the addition of GUI code which allows to adjust certain layout parameters.

state.contextChanged() soll passend in ContextEditor aufgerufen werden, falls der Context sich ändert.

As we did for ConExp we should test the usability of our new GUI so that we find possible problems as soon as possible.

Also, we should check that our reimagined imitation of ConExp does indeed provide all of ConExp's orginial functionality by going through this list and ConExp's documentation.

We must find a way to introduce this functionality. Problem ist, we decided not to have a traditional menu. Ideas:

• Another button next to open files that stands for "open a recent file" (maybe folder symbol with a clock) that opens a list of say the 5 last opened files from which you can choose which to open
• Displaying a small arrow on the "open folder" button (like "run" in eclipse) that, when clicked, opened a list or recently opened files

Currently, you can edit the text and type in new text in the textareas. Clearly unwanted.