New revs - Public comments

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: New revs - Public comments
« Reply #630, on January 21st, 2014, 09:06 PM »
Quote, from New Revs thread: Should I keep posting new revs here, when you can now just access the rev log here..?
https://github.com/Wedge/wedge/commits/

Is there a way to receive notifications of new revs? Personally I like reading them; even though I understand very little it does give an indication of areas that are being changed / added.


Another quote: Apparently, MySQL doesn't like being asked the unsigned keyword on bit fields. It should have been smart enough to ignore them, but whatever... (install.sql)
While I'm at it, minor regex simplifications. (install.php)

So one assumes that one can download those two files only and have the latest version of Wedge? (ie along with the zip I downloaded this morning[1].) And if so is there an easy was to do this as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair.
 1. this afternoon Paris time

Nao

  • Dadman with a boy
  • Posts: 16,018
Re: New revs - Public comments
« Reply #631, on January 21st, 2014, 10:46 PM »
Quote from Farjo on January 21st, 2014, 09:06 PM
Is there a way to receive notifications of new revs?
You can also subscribe to the RSS feed.
https://github.com/Wedge/wedge/commits/master.atom
It doesn't give you the number of line additions and deletions, though, which is a mood killer for me. I like being able to differentiate between "quick fixes" and "large commits".

Other than that, I'm planning to write some kind of script that'll use the RSS feed to get new commit IDs, then use the GitHub API to receive statistics for each of these commits, and then post them to a specific topic. This'll make a perfect candidate for a plugin, but honestly, if someone else could write it for me, I'd be thrilled... :P
Quote from Farjo on January 21st, 2014, 09:06 PM
Personally I like reading them; even though I understand very little it does give an indication of areas that are being changed / added.
And I like that people are reading them ;)
Quote from Farjo on January 21st, 2014, 09:06 PM
So one assumes that one can download those two files only and have the latest version of Wedge?
Yes. But apparently, some servers don't play nice.
I made a test install on my Wamp server, and it worked.
I made a test install on wedge.org, and it worked.
If it doesn't work elsewhere, it'll need fixing, but it's EXACTLY the reason I needed to go public at some point... Because there are more setups out there, and they need to be accounted for.

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: New revs - Public comments
« Reply #632, on January 23rd, 2014, 03:19 AM »
"If I do one at a time I'll be done in 10 years"
 :lol: Only understood this once I looked at the change in github :)

"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."
I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)

MultiformeIngegno

  • Posts: 1,337
Re: New revs - Public comments
« Reply #633, on April 5th, 2014, 03:20 AM »
Regarding commit eda89f6: there's a function in Google Analytics I think where you can let googlebot login (you provide credentials).

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,666
Re: New revs - Public comments
« Reply #634, on April 5th, 2014, 04:14 AM »
Quote
Removing the 'Posterity' link on your thoughts if they're not public.
Am I the only one who used that on a "self" thought?
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

madfitz

  • Elite Class Non Coder
  • Posts: 97
Re: New revs - Public comments
« Reply #635, on April 5th, 2014, 07:52 AM »
Quote from Farjo on January 23rd, 2014, 03:19 AM
"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."
I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)
Or use Github for Windows. Clone the repo then it will only download the latest changed files.

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: New revs - Public comments
« Reply #636, on April 5th, 2014, 10:12 AM »
Quote from madfitz on April 5th, 2014, 07:52 AM
Quote from Farjo on January 23rd, 2014, 03:19 AM
"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."
I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)
Or use Github for Windows. Clone the repo then it will only download the latest changed files.
Thank you - yes that's what I do now, and then an FTP client synchronises what's on my PC to the web space. It's still a way away from a one-click solution but it's easier with less chance of missing changes.

Nao

  • Dadman with a boy
  • Posts: 16,018
Re: New revs - Public comments
« Reply #637, on April 8th, 2014, 08:13 PM »
Quote from Farjo on April 5th, 2014, 10:12 AM
Thank you - yes that's what I do now, and then an FTP client synchronises what's on my PC to the web space. It's still a way away from a one-click solution but it's easier with less chance of missing changes.
Eventually, I'll stick my finger out of my arse, and I'll write a module to automatically update files from github as long as you're using an alpha or beta install.

Then again, it'll probably come *after* I write the code to automatically update files on non-alpha versions. (Which, in this case, will only retrieve official releases.)

Farjo

  • "a valuable asset to the community"
  • Posts: 492

Nao

  • Dadman with a boy
  • Posts: 16,018
Re: New revs - Public comments
« Reply #639, on April 8th, 2014, 11:17 PM »Last edited on April 10th, 2014, 01:06 PM
It'd be practical even for me.... :P

I have so many things to add before I can call it beta material.... :-/
UI for contact lists.
UI for auto-updates.
Web installer.
Soft-deletion of posts...
What else..? I don't remember. So many...

:edit: Also, a quick editor to determine which elements to put onto the homepage.

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: New revs - Public comments
« Reply #640, on April 9th, 2014, 09:42 AM »
Contact lists needs doing, but perhaps the rest can start the list for version 1.1 of Wedge. What you have now is already so much better than SMF.

If you wait until everything is completed then everyone else will have released their versions, some of Wedge's membership will have gone and you will be fed up / burnt out.

OTOH releasing sooner, once all loose ends are tied up / tidied away will attract users and you may get more offers of help.

[1]
 1. A few months ago you may have thought "He just wants to get his hands on the software" but it is available and is being used live in many locations, so I have no conflict of interest :)

MultiformeIngegno

  • Posts: 1,337

Nao

  • Dadman with a boy
  • Posts: 16,018
Re: New revs - Public comments
« Reply #642, on May 12th, 2014, 01:12 AM »
I don't now. For instance, with the German flag, simplifying it to only use 3 colors would bring the GIF size down to 99 bytes. After embedding and gzipping, it should be between 90 and 110 bytes. With SVG, I'm guessing it would have to be a bit more than 100 bytes just for the code itself, but it might compress much better. Still, SVG isn't supported by IE 6-8, so I don't know if it's worth dropping these to save a few bytes.

The change from PNG to GIF allowed me to save over 300 bytes per flag. Now THAT was worth it!! ;)

(BTW, I don't know if I'll keep the ability to have a PNG version around... I noticed that the board list needed a flag test as well, and it sucks. I'd probably have to store the actual extensions in the database or something, meh.)