Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 03:35
    huffSamuel opened #703
  • Oct 16 21:12
    superbonaci commented #589
  • Oct 16 18:35
    gep13 commented #589
  • Oct 16 17:01
    superbonaci commented #589
  • Oct 16 12:19
    gep13 commented #589
  • Oct 16 09:26
    superbonaci commented #589
  • Oct 16 07:36
    gep13 closed #701
  • Oct 16 07:36
    gep13 commented #701
  • Oct 16 06:44
    gep13 commented #589
  • Oct 13 16:49
    bhargava-raju synchronize #702
  • Oct 13 16:45
    bhargava-raju opened #702
  • Oct 13 08:19
    superbonaci opened #701
  • Oct 13 08:19
    superbonaci commented #589
  • Oct 12 19:01
    bhargava-raju commented #694
  • Oct 10 17:20
    dialex synchronize #700
  • Oct 10 17:19
    dialex opened #700
  • Oct 08 18:59

    gep13 on develop

    (doc) Fix spelling of Chocolate… (compare)

  • Oct 08 18:58
    gep13 commented #699
  • Oct 08 18:58

    gep13 on develop

    Update about.md Merge pull request #699 from Ge… (compare)

  • Oct 08 18:58
    gep13 closed #699
jackkav
@jackkav
*install packages
Gary Ewan Park
@gep13
Hello @jackkav if there is anything in particular that you want to start working on, feel free to raise an issue for it on the Github site here: https://github.com/chocolatey/ChocolateyGUI/issues?direction=desc&sort=updated&state=open and then we can start discussing it in more depth, and once everyone is happy, we can start accepting pull requests to get the features/suggestions/defects included into the beta version of ChocolateyGUI. You will also see a number of open issues, all of which are essentially "up for grabs" if there is something that you feel that you can help out on, free feel to jump right in :-)
Richard Simpson
@RichiCoder1
@gep13 Goodness, someones moving busily.
Anything I can do to help? Still crazy busy, but I'll have some free tim esoon
Gary Ewan Park
@gep13
@RichiCoder1 I have finally got some time to do some stuff, so I thought I would jump in :-)
I will give you a shout if there is anything that I am confused about though.
I have just merged the wpf_refresh branch into master, ready to start tidying up the last remaining issues
I have also just created a new "develop" branch that I would like us to start using, been using Gitflow at work, and want to start using it here
I will set up all the MyGet Build stuff in order to have that work
I am finally been able to get to a point that my todo list is a little more free, and ChocolateyGUI is at the top for a change :-D
This was also spurred on by some of the stuff that Rob has been working on, there is some VERY cool stuff coming to Chocolatey, and I would like ChocolateyGUI to be in a position to take advantage of some of it when it lands
Richard Simpson
@RichiCoder1
Sounds awesome! Very excited for what's coming down the Pipeline.
Very fond of gitflow now that Ive been using it
Gary Ewan Park
@gep13
me too! There are loads of new features! Rob really has been a busy guy!
woot! glad we are on the same page there, I really like using it now!
have you played with GitVersion? Going to be using that to set the semantic version, based on the state of the repo
Richard Simpson
@RichiCoder1
Nope! Heard of it though
I may have to turn of github notifications if you keep being this busy :)
Gary Ewan Park
@gep13
choco install gitversion.portable
ha ha, just tidying up some issues, so that we know where we are
once i have done that, I am hitting the hay, been a busy day
Gary Ewan Park
@gep13
right, that is me done, you can turn back on Github Notifications. signing off
talk to you later :-)
Richard Simpson
@RichiCoder1
Haha, have a good night!
Rob Reynolds
@ferventcoder
Glad to see you are excited @gep13
:)
Richard Simpson
@RichiCoder1
@gep13 When would you be available to chat? Thanks!
Gary Ewan Park
@gep13
@RichiCoder1 Most evening's, after 7pm GMT, I could be available. What time of day is that for you? Would that work?
Richard Simpson
@RichiCoder1
That works pretty well I think. That's 2pm on for me.
Random food for thought: Was exposing underlying chocolatey in the powershell loading popup a good idea?
Gary Ewan Park
@gep13
ok cool, let me know when you would like to have a chat
I think that it definitely helps in terms of showing that something is happening, as to whether it is required, that I don't know.
You could argue that it is too much information.
@RichiCoder1 would it make sense to have this as a setting that the user could activate if they wanted additional information?
that does lead to the question about what we show instead of this, because we would still want to show "something" to indicate that work was being done behind the scenes
Richard Simpson
@RichiCoder1
We'd just revert to a "normal" text box instead of the one we have now
progress box*
Gary Ewan Park
@gep13
sounds fine have me
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.