Page 1 of 1

User Interface is from the 80s ...

Posted: Fri Jun 18, 2021 9:16 am
by Jas
Hi Folks,
Just installed Cmap for OS X, and it's like I've just gone back in time 40 years. The fonts are grey, fuzzy, coarse. The icons are the same - it's nostalgic but unusable. Any ideas?
Cmap = v6.04, on a Mac MIni i7 with OS X 11.4, 32GB RAM, 4K monitor.

P.S. I donated. Be fairly nice to me.

Re: User Interface is from the 80s ...

Posted: Fri Jun 18, 2021 9:22 am
by cmapadmin
Well, we wouldn't use the term unusable. We've been concentrating on the Cmap Cloud version lately. The desktop version is stable -- but written in Java which in itself has aged. And in your case using OS X, with Apple's move to new silicon (M1) its not clear what the roadmap for Java is on that hardware. So we are waiting for that roadmap to clear up, in particular in terms of GUI libraries. For servers (e.g. CmapServer), java seems to continue to be a good choice.

Re: User Interface is from the 80s ...

Posted: Sat Jun 19, 2021 3:17 pm
by Jas
Very many thanks for the reply and the insights ... I should be more grateful for what you folk have delivered and I'll get over the legacy Java issues.

Re: User Interface is from the 80s ...

Posted: Mon Jul 19, 2021 7:50 am
by julio45
IMHO personally I think that the CmapTools application is resisting the passage of time, precisely because of the good design combined of its functionalities with its user interface. I think that the special history of this application has contributed to it.

I have made conceptual and mental maps with more than 5 different applications and studied the operation of as many applications for the same purpose. I keep recommending CmapTools because I have not yet found an application as efficient as this for all kinds of people. Also free and without hidden costs.

For example this is not essential but, anyway, I find it fantastic that this application allows you -with the help of a screen recorder- to make videos like this in a few minutes. Perfect -with voice explanations- for asynchronous teaching: ... sp=sharing