Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 13 13:54

    choco-bot on gh-pages

    AppVeyor Publish: 37873ee8f8415… (compare)

  • Dec 13 13:48

    gep13 on develop

    (doc) Add note callouts where r… (doc) Altered structure of user… (doc) Added info to the About U… and 6 more (compare)

  • Dec 12 12:47
    gep13 commented #719
  • Dec 12 12:47
    gep13 commented #720
  • Dec 12 12:46
    gep13 commented #595
  • Dec 12 12:46
    gep13 edited #719
  • Dec 12 12:46
    gep13 labeled #719
  • Dec 12 12:46
    gep13 edited #720
  • Dec 12 12:45
    gep13 labeled #720
  • Dec 12 12:00
    opusforlife2 edited #719
  • Dec 12 11:58
    opusforlife2 commented #595
  • Dec 12 11:57
    opusforlife2 opened #720
  • Dec 12 11:53
    opusforlife2 opened #719
  • Dec 12 11:28

    choco-bot on gh-pages

    AppVeyor Publish: 32c0357e6edd1… (compare)

  • Dec 12 11:22

    gep13 on develop

    (doc) Add docs for default tile… (doc) Add info about use delaye… (doc) Add docs about exclude in… and 5 more (compare)

  • Dec 12 08:08
    gep13 commented #595
  • Dec 12 00:33
    BananaAcid commented #595
  • Dec 11 21:53
    opusforlife2 commented #595
  • Dec 11 16:38

    gep13 on develop

    (doc) Added information about f… (doc) Add info about default lo… (compare)

  • Dec 11 14:36

    choco-bot on gh-pages

    AppVeyor Publish: 1d34c991187a5… (compare)

Gary Ewan Park
@gep13
just something to think about...
Richard Simpson
@RichiCoder1
Hmm. I may have a nit to pick with the new style rules.
Gary Ewan Park
@gep13
would it be possible for you to create a fork of ChocolateyGUI into your own GitHub account, and create branches from there? Rather than create branches directly in ChocolateyGUI? This will prevent AppVeyor from kicking off a build for every commit, until we merge directly into develop/master, or create Pull Requests for the work in progress
Richard Simpson
@RichiCoder1
Oops, I thought I had. Apologies
Gary Ewan Park
@gep13
coolio :-)
Richard Simpson
@RichiCoder1
Any reason you went with explicit _this?
this*
Gary Ewan Park
@gep13
It is one of the core StyleCop tenants. Means that when reading through code, you know exactly the scope of a variable, without relying on some form of variable notation.
Richard Simpson
@RichiCoder1
Hmm. I'm not sure I'm for it. It adds noise to the code, especially when the "_variableName" notation already does say the same thing.
Of the many idle mistakes I've made, none ever would have been fixed adding "this" xD
Gary Ewan Park
@gep13
well, that is something that I wanted to talk to you about :-) That is one of the other StyleCop rules that I turned off, as it was a rather large change to fix, was to not allow the _ notation for variables.
I am happy to discuss the merits of each StyleCop rule, and turn them on/off as required, and agreed within the team
Richard Simpson
@RichiCoder1
Goodness gracious, that's a bizzare rule O.o
Gary Ewan Park
@gep13
I am guessing you haven't played with StyleCop before, there are a few bizarre rules, or which appear bizarre, until you dig into them
it is really all about enforcing consistency across the code base
each rule can be turned on/off easily though
Richard Simpson
@RichiCoder1
I admit, the most vigorous rules I've ever applied were resharper's
Gary Ewan Park
@gep13
ReSharper and StyleCop work in parallel. ReSharper can apply refactoring for the StyleCop rules
Richard Simpson
@RichiCoder1
Hmmm. I really want to chat about this now, but work calls >_<
Gary Ewan Park
@gep13
no worries, will catch up soon about it
Richard Simpson
@RichiCoder1
Pushed the .Net 4.5 changes to a PR for review and comments
Gary Ewan Park
@gep13
coolio
Richard Simpson
@RichiCoder1
Evening
You're up late (I think)
Gary Ewan Park
@gep13
ha ha, nope, this is me getting up in the morning
:-)
06:52 here
Richard Simpson
@RichiCoder1
Then you're up early :)
Gary Ewan Park
@gep13
indeed :-D
Actually, this is my normal. Up at 0500 every day
Richard Simpson
@RichiCoder1
Goodness. I stuggle to get up at 7:30
Gary Ewan Park
@gep13
lucky you! :-P
Rob Reynolds
@ferventcoder
I'm up around 6:30
:)
Gary Ewan Park
@gep13
slacker! :-P
Gary Ewan Park
@gep13
@RichiCoder1 you around? Did you see my question here? chocolatey/ChocolateyGUI#81
Cheers!
Richard Simpson
@RichiCoder1
@gep13 poke
Gary Ewan Park
@gep13
@RichiCoder1 i'm here
Richard Simpson
@RichiCoder1
@gep13 We need to pick a good time for both of us to meet so we can strategize :). Maybe pull @ferventcoder in. I'm using chocolatey more as an internal tool now, so I actually have more time to devote to improving the Gui (and maybe chocolatey too)
Gary Ewan Park
@gep13
Test from Developer API
Johnny Ramos
@johnnyramos
I'm wondering, is there a way to change the default nuget feed it's pointing to?
Gary Ewan Park
@gep13
@johnnyramos hello, thanks for reaching out. Yes, this is definitely possible. What version of ChocolateyGUI are you using?
Johnny Ramos
@johnnyramos
@gep13 0.12
Gary Ewan Park
@gep13
@johnnyramos ok, this: https://github.com/chocolatey/ChocolateyGUI/wiki/How-to-add-a-new-custom-source should work, but it looks like we have a bug :-( For now, you should be able to use the choco sources add command to add the new default feed. This is documented here: https://github.com/chocolatey/chocolatey/wiki/CommandsSources
we will work on the bug and post a new version as soon as possible
Johnny Ramos
@johnnyramos
@gep13 thanks, I'll take a look as well.
Gary Ewan Park
@gep13
@johnnyramos I have just pushed a fix this issue, which I documented here: chocolatey/ChocolateyGUI#204
It is currently building on AppVeyor just now, and once that is complete, a new package will be pushed to MyGet, where you will be able to update an update, to pull in the latest version
Please let me know if your issue is resolved, and I will close the Issue on Github