ConflictEditor: revision graph

graph

less more | rev 38: (0) -15 tip

add a toplevel pom, make this a reactor build
2011-10-09, by Dirk Olmes
add a comment why we discard the index here
2011-10-07, by dirk
do not use the selection index in conflict list from the event, get it from the list instead. If the selection is cleared in the list, the event will report a wrong index.
2011-10-07, by dirk
do not use a custom combo box model, instead fill a default one from preferences and attach an action listener to the combo that ensures that yet unknown database URLs will be stored in preferences.
2011-10-07, by dirk
replace the text field for the db url with a combo box that is populated from the preferences.
2011-10-07, by dirk
remove the selected conflict after saving - does not fully work yet, e.g. does not proplerly reset the differences table
2011-09-20, by dirk
do not blindly cast to Component ... the source of the event may be some arbitrary object (e.g. a model)
2011-09-20, by dirk
Implement HttpAccess using Apache's HTTP components. This works much better in conjunction with UTF-8 encoded JSON
2011-09-20, by dirk
as per Jackson recommendation, don't use Reader objects but instead use just plain input stream
2011-09-20, by dirk
implement resolving the conflict
2011-09-18, by dirk
fix a bug with selection in the differences table
2011-09-18, by dirk
the current conflict is an ObjectNode now so there's less need for casts
2011-09-18, by dirk
wire up the current value, conflict value and preview buttons
2011-09-18, by dirk
pull the buttons into their own panel so they can be activated/deactivated in a single operation
2011-09-18, by dirk
change column names
2011-09-18, by dirk

less more | rev 38: (0) -15 tip