Comments for greenethumb http://greenethumb.com programming, beer, and other fine things Tue, 24 Apr 2012 21:47:58 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Global Variables in AS3 by Paul http://greenethumb.com/article/11/global-variables-in-as3/#comment-13540 Paul Tue, 24 Apr 2012 21:47:58 +0000 http://dev.greenethumb.com/wordpress/?p=11#comment-13540 Many thanks! Excellent, just what I wanted. First Class!! Well done. Many thanks! Excellent, just what I wanted.

First Class!!

Well done.

]]> Comment on Global Variables in AS3 by Paul http://greenethumb.com/article/11/global-variables-in-as3/#comment-13512 Paul Tue, 24 Apr 2012 16:50:48 +0000 http://dev.greenethumb.com/wordpress/?p=11#comment-13512 Many thanks! Just what I was looking for, I'm building a multi-lingual language learning app in flex 4 and this is just the thing for the client-side static data component. Supperb, clear, and so helpful! Best regards, Paul. Many thanks! Just what I was looking for, I’m building a multi-lingual language learning app in flex 4 and this is just the thing for the client-side static data component.

Supperb, clear, and so helpful!

Best regards,

Paul.

]]> Comment on Drawing Sounds with AS3 by Zanzlanz http://greenethumb.com/article/7/drawing-sounds-with-as3/#comment-13452 Zanzlanz Mon, 23 Apr 2012 23:52:04 +0000 http://dev.greenethumb.com/wordpress/?p=7#comment-13452 Wow this helped me quite a bit at getting started! I wish I could figure out how to manipulate the data though. I will look into this, but thanks very much for getting me started! Wow this helped me quite a bit at getting started!
I wish I could figure out how to manipulate the data though.
I will look into this, but thanks very much for getting me started!

]]> Comment on F**king SVN. How does it work?! An SVN primer for the designer folks by Jonathan Greene http://greenethumb.com/article/63/fking-svn-how-does-it-work-an-svn-primer-for-the-designer-folks/#comment-13092 Jonathan Greene Fri, 20 Apr 2012 01:14:42 +0000 http://dev.greenethumb.com/wordpress/?p=61#comment-13092 The only way to update a working copy is to do an update. The best practice is to always do an update before before making a commit. You won't even be allowed to check in a file that is in conflict. If one file in your commit queue is conflicted, the entire commit will fail. The only way to update a working copy is to do an update. The best practice is to always do an update before before making a commit. You won’t even be allowed to check in a file that is in conflict. If one file in your commit queue is conflicted, the entire commit will fail.

]]> Comment on User-friendly image saving from the canvas by João http://greenethumb.com/article/1429/user-friendly-image-saving-from-the-canvas/#comment-13059 João Thu, 19 Apr 2012 18:25:22 +0000 http://greenethumb.com/?p=1429#comment-13059 Thanks! Thanks!

]]> Comment on F**king SVN. How does it work?! An SVN primer for the designer folks by SG http://greenethumb.com/article/63/fking-svn-how-does-it-work-an-svn-primer-for-the-designer-folks/#comment-13047 SG Thu, 19 Apr 2012 15:56:58 +0000 http://dev.greenethumb.com/wordpress/?p=61#comment-13047 Yes, that makes sense. My question though is more about files that *don't* have any conflicts. Do those get updated every time you commit also? If not, does that mean the "best practice" is to always do an update after every commit? Otherwise, that file you did not edit is just a conflict waiting to happen when you do get around to editing it in 3 months because someone else during that time will have edited it since you first checked out the trunk. Yes, that makes sense. My question though is more about files that don’t have any conflicts. Do those get updated every time you commit also? If not, does that mean the “best practice” is to always do an update after every commit? Otherwise, that file you did not edit is just a conflict waiting to happen when you do get around to editing it in 3 months because someone else during that time will have edited it since you first checked out the trunk.

]]> Comment on F**king SVN. How does it work?! An SVN primer for the designer folks by Jonathan Greene http://greenethumb.com/article/63/fking-svn-how-does-it-work-an-svn-primer-for-the-designer-folks/#comment-13044 Jonathan Greene Thu, 19 Apr 2012 15:22:43 +0000 http://dev.greenethumb.com/wordpress/?p=61#comment-13044 Most version control systems (SVN included) will not automatically push checked in changes to all users. That is what the 'update' command is for. So using your example, Jane would need to update her working copy to receive Bill's changes, and vice versa. If both Bill and Jane were working locally on the same file, and upon updating SVN could not merge the changes together (say the both made edits to the same lines of code), then SVN report a conflict. When SVN reports a conflict, it updates the file(s) in question with annotations describing each version of the conflicting code. It also produces two extra files, whose extensions will be the SVN revision number. If Bill or Jane is notified of a conflict, they will not be able to check the conflicted file until it is resolved. Resolving just means you hash out the changes you want implemented in the repository, mark the file as resolved, and check it in. Most version control systems (SVN included) will not automatically push checked in changes to all users. That is what the ‘update’ command is for. So using your example, Jane would need to update her working copy to receive Bill’s changes, and vice versa.

If both Bill and Jane were working locally on the same file, and upon updating SVN could not merge the changes together (say the both made edits to the same lines of code), then SVN report a conflict.

When SVN reports a conflict, it updates the file(s) in question with annotations describing each version of the conflicting code. It also produces two extra files, whose extensions will be the SVN revision number. If Bill or Jane is notified of a conflict, they will not be able to check the conflicted file until it is resolved.

Resolving just means you hash out the changes you want implemented in the repository, mark the file as resolved, and check it in.

]]> Comment on F**king SVN. How does it work?! An SVN primer for the designer folks by SG http://greenethumb.com/article/63/fking-svn-how-does-it-work-an-svn-primer-for-the-designer-folks/#comment-13043 SG Thu, 19 Apr 2012 15:09:57 +0000 http://dev.greenethumb.com/wordpress/?p=61#comment-13043 If 2 users (let's say 'Bill' and 'Jane') check out the same 2-file project, then Bill changes File 1 and commits those changes, when will Jane - who is working on File 2 and thus has no conflict with person Bill's edits - receive those changes? a) automatically while they sleep b) automatically or with confirmation the next time they commit changes even if it is to File 2 only c) not until either checking out the project completely again or committing edits with a conflict d) other? I ask because I am confused about whether, when working as a team, "conflict resolution" is something that eventually ends up happening constantly because you keep your checked-out copy of File 1 you checked out 3 months ago, even though it's been updated 5 times since then, until you yourself try to commit changes to it, or if every time you commit a different file in the project your unedited version of File 1 gets updated with previously committed edits from other users...? If 2 users (let’s say ‘Bill’ and ‘Jane’) check out the same 2-file project, then Bill changes File 1 and commits those changes, when will Jane – who is working on File 2 and thus has no conflict with person Bill’s edits – receive those changes?
a) automatically while they sleep
b) automatically or with confirmation the next time they commit changes even if it is to File 2 only
c) not until either checking out the project completely again or committing edits with a conflict
d) other?

I ask because I am confused about whether, when working as a team, “conflict resolution” is something that eventually ends up happening constantly because you keep your checked-out copy of File 1 you checked out 3 months ago, even though it’s been updated 5 times since then, until you yourself try to commit changes to it, or if every time you commit a different file in the project your unedited version of File 1 gets updated with previously committed edits from other users…?

]]> Comment on MLB.tv: ADVERTISEments, the loud, the repetitive and the lame by Larry http://greenethumb.com/article/50/mlbtv-and-advertisements-its-pathetic-really/#comment-12144 Larry Mon, 09 Apr 2012 23:21:54 +0000 http://dev.greenethumb.com/wordpress/?p=49#comment-12144 We all need to call the FCC about this. They are implementing new rules re: the volume of ads for cable this upcoming December 2012, and we need to petition our government to make sure those ads include MLB tv. So obnoxious! We all need to call the FCC about this. They are implementing new rules re: the volume of ads for cable this upcoming December 2012, and we need to petition our government to make sure those ads include MLB tv. So obnoxious!

]]> Comment on Public, Private, Protected, Internal: Access Modifiers in AS3 by Kendall http://greenethumb.com/article/27/public-private-protected-internal-access-modifiers-in-as3/#comment-12002 Kendall Sun, 08 Apr 2012 21:09:27 +0000 http://dev.greenethumb.com/wordpress/?p=28#comment-12002 Thank you very much for this explanation! Thank you very much for this explanation!

]]>