search

fcatools / conexp-ng

ConExp-NG is a simple GUI-centric tool for the study & research of Formal Concept Analysis (FCA) that allows you to create formal contexts, draw concept lattices and explore dependencies between attributes.
https://github.com/fcatools/conexp-ng/wiki
GNU General Public License v3.0
29 stars 8 forks source link

Scrolling in the Context Editor while Headers Stay Visible #43

Open eugenkiss opened 11 years ago

eugenkiss commented 11 years ago

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.

blu2lz commented 10 years ago

In fact, this is quite easy. You design two tables. One with only the first column and the second one with the rest of the table. Needs adjustment of the table model and the table itself and you got a fixed row header. The column header is even simpler. It works out of the box…if you use it. The column header in the context editor is not used. I don't really understand why, but the table is done in a weird way anyway. I suppose this does not have the highest priority, so I get to some more important issues first. Maybe later I redesign the whole table because I'm afraid this would be easier than adjusting this one.

blu2lz commented 10 years ago

see also #116.

blu2lz commented 10 years ago

This table has the most awful design I have ever seen. In the javadocs you read that the code is ugly because JTable is not meant to be too flexible. WTF? JTable is very flexible. Every swing element is flexible because it follows the MVC and you can extend/override/adjust every bit of functionality in it. Whoever wrote this was just not capable of doing so. BTW his code is ugly because he did not meant to comment it too much…before adjusting this spaghetti code I'd rather do it again from scratch. After all the time I burned with trying to fix the related bugs this got to be said…

So anybody waiting for #33, #42, #116 and this issue to be fixed: I'm working on it but it can take a while to be finished completely.