1
I Use This!
Inactive

Commits : Listings

Analyzed 1 day ago. based on code collected 1 day ago.
Feb 14, 2025 — Feb 14, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Deleted a chunk of the README that was repeated by merging the branch. More... over 10 years ago
Some more editing of README More... over 10 years ago
Merge branch 'hobservableCodeExample' of https://github.com/DaBlick/Hierarchical-Observer-Pattern into hobservableCodeExample More... over 10 years ago
Removed instances of "our" and "the" from the README.MD based on Github comments. More... over 10 years ago
Reduced the wording of the sentences in the README. More... over 10 years ago
Removed words and modified sentences in the README to make for less words and complexity and much more understandable documentation. More... over 10 years ago
Added the CollectionObservable ContactsList example to the README and fixed some of formatting of the file as well such as the JUnit testing not being indented like the other blocks of code. More... over 10 years ago
CollectionObservables all keep a collection of the phone contacts instead of "events" and the consistency of the list among the observables is checked via the junit tester. I also removed license headers and made other changes based on previous Git comments. More... over 10 years ago
CollectionObservables all keep a collection of the phone contacts instead of "events" and the consistency of the list among the observables is checked via the junit tester. I also removed license headers and made other changes based on previous Git comments. More... over 10 years ago
Created a CollectionObservable example using a scenario where different phone applications are notified of changes in the contact list. The main observable is observed by the system app which is usually where the user selects and contacts the contacts on the list. The other apps observe for adds and edits in the list but regardless, the system app must know of these changes and thus it observes the parentObservable of the other observables(Add, remove, edit). The observables in the example code are all ListObservables which is a sub class of the AbstractCollectionObservables. Will use this example in the README.MD and elaborate more on this implementation. Also will refactor and get rid of the main class in the example. More... over 10 years ago
Created a CollectionObservable example using a scenario where different phone applications are notified of changes in the contact list. The main observable is observed by the system app which is usually where the user selects and contacts the contacts on the list. The other apps observe for adds and edits in the list but regardless, the system app must know of these changes and thus it observes the parentObservable of the other observables(Add, remove, edit). The observables in the example code are all ListObservables which is a sub class of the AbstractCollectionObservables. Will use this example in the README.MD and elaborate more on this implementation. Also will refactor and get rid of the main class in the example. More... over 10 years ago
Added the new example with the Scorekeeper observing the Playerlist to the README.MD. More... over 10 years ago
Removed redundancy and the setters from the PlayerList based on comments. More... over 10 years ago
Removed redundancy and the setters from the PlayerList based on comments. More... over 10 years ago
Cut down on redundancy, straightened up the code in terms of the spacing, added setters and getters to the example code such as in PlayerList. Also most if not all the fields in the scoreKeeper and PlayerList classes are now private and can only be accessed via setters and getters. I also removed the test main class and implemented it into the already existing JUnit Tester. More... over 10 years ago
Cut down on redundancy, straightened up the code in terms of the spacing, added setters and getters to the example code such as in PlayerList. Also most if not all the fields in the scoreKeeper and PlayerList classes are now private and can only be accessed via setters and getters. I also removed the test main class and implemented it into the already existing JUnit Tester. More... over 10 years ago
Changed the README.MD example in the examples package to provide a better context to how components can observe changes in other components. The ScoreKeeper implements Observer and can be added to the observables within the PlayerList, thus it is notified of changes within the PlayerList and the update method in ScoreKeeper will override the existing observer method and will then proceed to call a method within the scorekeeper class and make changes depending on the changes in PlayerList. The ScoreKeeper also extends LoggingHObserver and displays information in the SFL4J format in the console. More... over 10 years ago
Changed the README.MD example in the examples package to provide a better context to how components can observe changes in other components. The ScoreKeeper implements Observer and can be added to the observables within the PlayerList, thus it is notified of changes within the PlayerList and the update method in ScoreKeeper will override the existing observer method and will then proceed to call a method within the scorekeeper class and make changes depending on the changes in PlayerList. The ScoreKeeper also extends LoggingHObserver and displays information in the SFL4J format in the console. More... over 10 years ago
Added a coding example for the Logging Observer section that also provides the code and an explanation of how to create LoggingObservers and have them observe an observable in the playerList. More... over 10 years ago
Added a code example which contains a list of players and has observers that view the operations of adding, subtracting, and editing of players on the list. There is also a unit tester that tests these operations to see if the observers are notified of these events in the player list. Also made changes to the README.MD. More... over 10 years ago
Added a code example which contains a list of players and has observers that view the operations of adding, subtracting, and editing of players on the list. There is also a unit tester that tests these operations to see if the observers are notified of these events in the player list. Also made changes to the README.MD. More... over 10 years ago
Simplified the sentences in the README and used fixed width font for the classes mentioned in the document. More... over 10 years ago
Made changes to the README based on comments. Started to remove/change unnecessary phrasing as well. More... over 10 years ago
Added more information to the README and provided a potential real world example of the Collection Observable's use. Still need to add an example to the Logging Observer but I have a few ideas for examples. Used some of the Github Markdown formatting on the README such as the asterisks for class names. More... over 10 years ago
Added a Logging Observer section and added brief information about the Logging Observers functionality in the Hierarchical Observer Pattern and also added a Collection Observable section and gave brief information about the collectionObservable capabilities. More... over 10 years ago
Refactored the code after the revert mistake I made. Will work on the read me soon. More... over 10 years ago
Revert "Added SetEventDataEnum and ListEventDataEnum and also added the setObservable class that extends the AbstractCollectionObservable. Refactored EventDataEnum to CollectionEventDataEnum. Added a listObservable unit test and a setObservable unit test but the set observable needs to be fixed in order to find information in the set and test if the event data is true and exists in the set/collection." More... over 10 years ago
Added SetEventDataEnum and ListEventDataEnum and also added the setObservable class that extends the AbstractCollectionObservable. Refactored EventDataEnum to CollectionEventDataEnum. Added a listObservable unit test and a setObservable unit test but the set observable needs to be fixed in order to find information in the set and test if the event data is true and exists in the set/collection. More... over 10 years ago
AbstractObservables can now fire their most recent change (EventDataEnum) to the TestCollectionObserver when the collection has been changed. All the tests so far pass the unit testing at run time. Will add this feature/implementation to the ListObservable and create more collectionObservables such as setObservable and will create separate enums for those observables to use for their operations/changes. More... over 10 years ago
Added a TestCollectionObserver to the test package to be used by the CollectionObservables. Need to get the eventDataEnum to be read from the collectionObservable and used by the observer and put into the eventDataEnum value of the collectionEvent object generated by the TestCollectionObserver. I wrote a test that is successful for the testCollectionObserver but the Enum cannot be hard coded but should be extracted from the observable. More... over 10 years ago