Timeline for Simple Activity Monitor - For Educational Purposes only.
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Aug 17, 2010 at 1:02 | comment | added | Sky Sanders |
not a bad thing at all - ultimately beneath the layers of abstraction in soapi, something similar is happening. Whereas you use UserQuery, I use UsersParameters and reading your code with my eyes painted a different picture, which I also found interesting.
|
|
| Aug 17, 2010 at 0:41 | comment | added | jjnguy | @code, I'm not versed on design patterns...but, yeah. It's basically a parameter bag. (Not sure if that's a bad thing...) | |
| Aug 16, 2010 at 23:02 | comment | added | Sky Sanders |
on second look, i wonder if your UserQuery could be characterized as a parameter bag?
|
|
| Jul 26, 2010 at 13:13 | comment | added | jjnguy | @code Yeah, we like it too. It seems to simplify worrying about all of the possible parameters for all of the different routes. | |
| Jul 26, 2010 at 4:43 | comment | added | Sky Sanders |
I just noticed you are using a composition paradigm rather that the more imperative syntax that most of us are. I think I like the way that looks and I can immediately see some benefits. It it the case that your UserQuery is simply a property bag with parameters and such
|
|
| Jul 26, 2010 at 2:05 | history | edited | jjnguy | CC BY-SA 2.5 |
wrong version number
|
| Jul 26, 2010 at 0:33 | history | answered | jjnguy | CC BY-SA 2.5 |