Meeting 11: Unterschied zwischen den Versionen

Aus Java Student User Group Austria - Java + JVM in Wien Österreich / Vienna Austria
Wechseln zu: Navigation, Suche
(FILXDJIOsKzfd)
(oadwYqtStMRZckbY)
Zeile 1: Zeile 1:
Thanks, this has been puzzling me for a while now, in my case just prtneveing updates (over a dependency issue, which made no sense), but I'd just skip them until now when I couldn't install something because my Eclipse was too old Thanks for the post, fixed it for me too.
+
At the very least, I would rellay, rellay love my source code to be presented in a more readable manner with the use of more sophisticated typographic techniques (different fonts for different structual parts of the code, better alignment, etc).Another step further is the alternate representation of code, e.g., a state-change diagram for GUI state changes, a truth table, or perhaps a more readable view of java annotations.Another would be the ability to annotate code in a less intrusive way, add diagrams, some way to mark particular concerns (e.g., logging or transactional code).And even further, perhaps the code could be presented as a bit of visual narrative.  There's no particular reason that objects/variables have to be represented as text only. In particular, it would be interesting to see what could be gained by adding some type of visual moniker for objects of different classes.We should be able to come up with a way to make use of our visual perception abilities, to help with the much harder task of the pure abstract thought of coding.The sky's the limit!  You have nothing to lose but your 80-column ASCII display!

Version vom 16. Dezember 2012, 07:41 Uhr

At the very least, I would rellay, rellay love my source code to be presented in a more readable manner with the use of more sophisticated typographic techniques (different fonts for different structual parts of the code, better alignment, etc).Another step further is the alternate representation of code, e.g., a state-change diagram for GUI state changes, a truth table, or perhaps a more readable view of java annotations.Another would be the ability to annotate code in a less intrusive way, add diagrams, some way to mark particular concerns (e.g., logging or transactional code).And even further, perhaps the code could be presented as a bit of visual narrative. There's no particular reason that objects/variables have to be represented as text only. In particular, it would be interesting to see what could be gained by adding some type of visual moniker for objects of different classes.We should be able to come up with a way to make use of our visual perception abilities, to help with the much harder task of the pure abstract thought of coding.The sky's the limit! You have nothing to lose but your 80-column ASCII display!