Coding Projects and Duga Heaven :)

Duga

12:00 AM

[retailcoder/Rubberduck] 1 commits. 0 issues opened and 0 closed

[Tejpbit/CodeIT] 2 commits. 0 issues opened and 0 closed

skiwi

12:02 PM

hey

Duga

[skiwi2/HearthMonitor] skiwi2 created wiki page Home

Duga

12:52 PM

[skiwi2/HearthMonitor] skiwi2 created wiki page User Requirements Document

skiwi

I did it!

Duga

[skiwi2/HearthMonitor] skiwi2 edited wiki page User Requirements Document

Duga

1:08 PM

[skiwi2/HearthMonitor] skiwi2 edited wiki page User Requirements Document

skiwi

@SimonAndréForsberg @bazola @Phrancis If any of you could take a look at that document, then it would be great!

Also, can you check if you have edit permissions on the wiki? As I don't think it would be a good idea if anyone had edit permissions

Duga

[skiwi2/HearthMonitor] Zomis edited wiki page User Requirements Document

Simon André Forsberg

not sure if it's possible to turn that off, @skiwi.

After all, it is a wiki.

skiwi

1:27 PM

Wonder if I can easily rollback that edit

Duga

[Zomis/Minesweeper-Analyze] Zomis commented on issue #3: Improve performance

> `GroupValues` could possibly use an `byte[]`, where each field is an index in the array. Something like:

- 0 = unset
- 1 = field has value 1
- -1 = field has value 0

All that is needed then is for a good way of connecting a field to an integer. In worst case, this can be done with `Map<T, Integer>` but I hope for another solution. Perhaps create some `Wrapped<T>` with the T and an int.

Simon André Forsberg

@skiwi AFAIK, github wikis are also github repos. So that should be possible.

Duga

[Zomis/Minesweeper-Analyze] Zomis created branch issue3

[Zomis/Minesweeper-Analyze] Zomis created branch bounded

[Zomis/Minesweeper-Analyze] Zomis pushed commit cbccf385 to bounded

> added BoundedFieldRule

[Zomis/Minesweeper-Analyze] Zomis pushed commit 7a09a159 to bounded

> changed from using copy-constructor to using a method, to allow copying any kind of rule

[Zomis/Minesweeper-Analyze] Zomis pushed commit a7e5d4d3 to bounded

> fixed infinite loop bug when analyzing BoundedFieldRule

[Zomis/Minesweeper-Analyze] Zomis pushed commit 93b945c3 to bounded

> added NQueens analyze test

[Zomis/Minesweeper-Analyze] Zomis pushed commit 78a39b27 to bounded

> made NQueens factory method public static

[Zomis/Minesweeper-Analyze] Zomis pushed commit 6e3e9467 to bounded

> added Binero code and a 'hard' binero puzzle

[Zomis/Minesweeper-Analyze] Zomis pushed commit 02e49e12 to bounded

> added a very hard puzzle (which currently has more solutions than it should have because the rule about each row and column should be unique is not yet implemented)

[Zomis/Minesweeper-Analyze] Zomis pushed commit 84c5ed79 to bounded

> added groupvalues parameter to isEmpty method

[Zomis/Minesweeper-Analyze] Zomis pushed commit 77de2812 to bounded

> added UniqueSequence rule

[Zomis/Minesweeper-Analyze] Zomis pushed commit 577efcae to bounded

skiwi

> Restrict editing to collaborators only

Public wikis will still be readable by everyone.

Duga

> changed how smallest field group is selected

skiwi

1:34 PM

Can you try again @SimonAndréForsberg?

Duga

[Zomis/Minesweeper-Analyze] Zomis pushed commit 648e146d to bounded

> improved isEmpty functionality of a UniqueSequence

[Zomis/Minesweeper-Analyze] Zomis pushed commit 38953b25 to bounded

> using a Set instead of List in UniqueSequence to make it behave properly

[skiwi2/HearthMonitor] skiwi2 edited wiki page User Requirements Document

[Zomis/Minesweeper-Analyze] Zomis opened issue #9: Extract interface for FieldRule

> As of commit cbccf385, other rules besides just FieldRule exist. Extract a proper interface for the desired functionality to reduce coupling and inheritance. (most things does not need to extend FieldRule)

[Zomis/Minesweeper-Analyze] Zomis added label enhancement to issue #9: Extract interface for FieldRule

Simon André Forsberg

@skiwi can't even see the edit button now. How did you change it?

Duga

[Zomis/Minesweeper-Analyze] Zomis added label performance to issue #10: Callback to rules whenever something is added to knownValues

[Zomis/Minesweeper-Analyze] Zomis opened issue #10: Callback to rules whenever something is added to knownValues

> Currently the sequence of operation is:
- Create a `GameAnalyze` with some `knownValues`
- Add something to the knownValues
- Loop through knownValues and simplify.

It *might* improve performance if rules are notified and automatically simplified whenever something is added to the known values.

It feels like it would especially improve performance for some more 'advanced' rules, such as the newly created `UniqueSequence` rule.

[Zomis/Minesweeper-Analyze] Zomis added label enhancement to issue #10: Callback to rules whenever something is added to knownValues

skiwi

@SimonAndréForsberg Repository > Options > Restict editing to collaborators only

Simon André Forsberg

thanks

skiwi

1:43 PM

No problemo.

skiwi

4:23 PM

hey again

Simon André Forsberg

oi

skiwi

What have you been up to last days programming-wise?

Simon André Forsberg

@skiwi N-Queens and other combinatorial puzzles.

skiwi

@SimonAndréForsberg Sounds interesting

Simon André Forsberg

4:44 PM

@skiwi it is. I started working on one combinatorial puzzle before I went to Prague, in C++, now that I'm back I realized that I could easily adapt some Java code to solve it quite smoothly.

skiwi

4:55 PM

I'm trying to create my HearthMonitor one day

In between playing HearthStone... I've improved on Arena

skiwi

6:27 PM

I feel a little bit bad...

Legato

6:50 PM

Ouch. I once pulled double Whirling Zapomatic into rockbiter + bloodlust. Never felt so bad for my opponent. So, this project seems interesting, is there a FAQ I could peruse?

skiwi

@Legato This project == HearthMonitor?

And I didnt'feel that bad, as I got pretty much owned by a Rogue two matches earlier, needed only 2 health more to heal myself up a bit and have a chance again, but to no avail :/

Legato

Yes, but I'm generally interested if there's anything else.

skiwi

And that's up right now is the readme on the project hoempage and the URD

what would you like to know more?

Legato

Just the state of the project/future additions/contributors. I've been wanting to work on something with a group for a while, I want to see if it's something I could add value to.

skiwi

First I intend to finish up the URD, then a Software Requirements Document... which includes a class diagram

After that starting to program

Not exactly sure yet how it would be possible to contribute, it is not that big of a project

Legato

7:00 PM

Understandable. Thank you nonetheless for filling me in.

Simon André Forsberg

@skiwi I think your HearthMonitor is bigger than you think it is

Hi @Legato. Where did you come from? Never seen you in this chat before.

skiwi

Wondering the same actually ^

@SimonAndréForsberg The app part might be the biggest, and parsing the log entries is not going to be easy I reckon either

Simon André Forsberg

@Legato If you're interested in the Cardshifter project, that is an extremely big one, and is meant to be a Trading Card Game, like Hearthstone. Are you interested in that project or just in @skiwi's HearthMonitor?

Legato

I was looking at CR's Meta 2014 wrap up, and it linked to here.

That as well, I just ran it, it does look like it's intended to be an HS clone.

Cardshifter is definitely interesting and your accentuated its size isn't lost on me, as someone who has yet to participate in a group project.

Are those two the only projects?

Phrancis

That we are aware of, so far

Simon André Forsberg

7:22 PM

@Legato we all have some other projects that we are working on aside from the big ones, but those other projects aren't really "collaboration" projects.

Welcome btw to this chatroom, @Legato.

Legato

Thank you.

Duga

8:11 PM

[skiwi2/HearthMonitor] skiwi2 pushed commit f2b0c473 to develop

> Updated readme to use "HearthMonitor application" rather than "tool".

[skiwi2/HearthMonitor] skiwi2 pushed commit 65425436 to develop

> Added documentation section to the readme.

[skiwi2/HearthMonitor] skiwi2 pushed 2 commits to master

Duga

9:53 PM

[Zomis/Minesweeper-Analyze] Zomis opened issue #11: Callbacks to track solving steps

> It would be nice to track the exact solving steps, and count branches and stuff, by having callbacks on the following occasions:

- Something added to `knownValues` (see also #10)
- New branch created (for-loop in GameAnalyze.solveRules)
- Branch closed because of invalid rule

[Zomis/Minesweeper-Analyze] Zomis added label enhancement to issue #11: Callbacks to track solving steps

Duga

11:00 PM

[Zomis/Minesweeper-Analyze] Zomis opened issue #12: FieldRule list of fieldgroups to set

> List<FieldGroup<T>> fields should probably change to Set<FieldGroup<T>> fields, both for performance in general and also possibly with #10 to check if fieldgroup is in rule or not.

Duga

11:59 PM

RELOAD!

[Zomis/Minesweeper-Analyze] 12 commits. 4 issues opened and 0 closed

Transcript for

Coding Projects and Duga Heaven :)