Menu
▾
▴
colossus-developers — For discussion of design and coding issues
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(11) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(68) |
Feb
(194) |
Mar
(75) |
Apr
(44) |
May
(48) |
Jun
(29) |
Jul
(60) |
Aug
(74) |
Sep
(12) |
Oct
(13) |
Nov
(30) |
Dec
(62) |
| 2003 |
Jan
(63) |
Feb
(28) |
Mar
(63) |
Apr
(27) |
May
(53) |
Jun
(8) |
Jul
(17) |
Aug
(2) |
Sep
(95) |
Oct
(28) |
Nov
(36) |
Dec
(24) |
| 2004 |
Jan
(92) |
Feb
(47) |
Mar
(43) |
Apr
(86) |
May
(64) |
Jun
(10) |
Jul
(4) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
(14) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
| 2006 |
Jan
(1) |
Feb
(4) |
Mar
(14) |
Apr
(22) |
May
(51) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
(25) |
Dec
(1) |
| 2007 |
Jan
|
Feb
(7) |
Mar
(80) |
Apr
(27) |
May
(15) |
Jun
(6) |
Jul
(25) |
Aug
(1) |
Sep
(3) |
Oct
(17) |
Nov
(174) |
Dec
(176) |
| 2008 |
Jan
(355) |
Feb
(194) |
Mar
(5) |
Apr
(28) |
May
(49) |
Jun
|
Jul
(28) |
Aug
(61) |
Sep
(61) |
Oct
(49) |
Nov
(71) |
Dec
(2) |
| 2009 |
Jan
(12) |
Feb
(216) |
Mar
(299) |
Apr
(257) |
May
(324) |
Jun
(222) |
Jul
(103) |
Aug
(127) |
Sep
(72) |
Oct
(76) |
Nov
(2) |
Dec
(23) |
| 2010 |
Jan
(23) |
Feb
(11) |
Mar
(11) |
Apr
(112) |
May
(19) |
Jun
(37) |
Jul
(44) |
Aug
(25) |
Sep
(10) |
Oct
(4) |
Nov
(5) |
Dec
(25) |
| 2011 |
Jan
(44) |
Feb
(19) |
Mar
(18) |
Apr
(3) |
May
(14) |
Jun
(1) |
Jul
(22) |
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(51) |
Feb
(42) |
Mar
(9) |
Apr
(9) |
May
(2) |
Jun
(29) |
Jul
(47) |
Aug
(5) |
Sep
|
Oct
(38) |
Nov
(33) |
Dec
(13) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(22) |
Nov
(18) |
Dec
(7) |
| 2014 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(5) |
Mar
|
Apr
(24) |
May
|
Jun
(18) |
Jul
(10) |
Aug
(21) |
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Norman S. <nsi...@sh...> - 2012-07-10 16:17:54
|
Yes, thanks Dave for putting the webpage together. And Clemens for the videos. Having both webpages and video tutorials is excellent. -----Original Message----- From: Clemens Katzer [mailto:lem...@sa...] Sent: Monday, July 09, 2012 5:46 AM To: re...@ro... Cc: col...@li...; Norman Sillito Subject: Re: [Colossus-developers] Getting Started - video tutorials Ok, thanks Dave for that effort! And I agree with Norman, some of what he wrote came to my mind also when reading Dave's page. Meanwhile: Quite a while ago already I got an idea, how to instruct things differently than just text or text-with-pictures; but I never managed to go for it ... - now I finally did it. Thus while you worked on that page, I tried out something else - to create tutorial videos about it. Here's what I've got so far; feedback welcome! http://www.youtube.com/playlist?list=PL09CAC7FDB091F62C&feature=view_all BR, Clemens -------- Original-Nachricht -------- > Datum: Sun, 8 Jul 2012 19:47:52 -0700 > Von: "Norman Sillito" <nsi...@sh...> > An: "\'David Partridge\'" <re...@ro...> > CC: col...@li... > Betreff: Re: [Colossus-developers] Getting Started > Addition to step 1. There is no installation software to run. Just > unzip the zip file and accept the defaults. Because there is no > installation software, nothing gets added to the windows menu. You > will have to create your own shortcut on the desktop to the eclipse > program. Mine shortcut has target = "C:\Program > Files\eclipse\eclipse.exe" > > > > The second #1 should be #2. > > > > Personally I find the Java site very frustrating. They have tried to > make it > simply and unfortunately they made it idiot proof so only . Anyway, > preamble for #2. > > > > #2 Java comes in many flavours. A runtime version (Java Runtime > Edition, > JRE) which allows you to run java programs. A Java Development Kit > (JDK) which allows you to build java programs. The JDK comes in many > variations that focus on providing different built-in functionality. > JavaFX, NetBeans, JavaEE. Ignore everything except the Java Platform, > Standard Edition JDK download. > > > > Java (and I) recommend removing any old versions of Java. If you need > old versions of Java then you can probably skip all these instructions > as you are already a programming god. Otherwise, go to the java site: > http://www.java.com/en/ select Free Java Download, select Remove Older > Versions and follow the instructions. After you have wiped all the > older versions then you are ready to get the JDK. > > > > The JDK can be found at > > http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-1383 > 63.htm > l#javasejdk > > If the link doesn't work, google Java, then search the Java site for > JDK > > > > > > The line: > > > > Click Next twice, accept the license and click Finish. You may see a > security warning about installing software with unsigned content. If > so, click OK. Once again you need to restart Eclipse.> > > > > Should be changed to > > > > Click Next twice, accept the license and click Finish. You may see a > security warning about installing software with unsigned content. If > so, click OK. Once again you need to restart Eclipse. > > > > #4. Getting the Colossus source code from the SourceForge repository > using Subversion. > > > > >From the Eclipse menu: Select Window ==> Show View ==> SVN Repositories. > Eclipse will open a window with the title SVN Repositories. Right > click inside this window, click on New and then Repository Location. > > > > > > One thing that isn't clear from the webpage is where the Subversion > software puts the colossus source code on my computer. I'm guessing > it is the current default workspace. Understanding workspace and > integrated development environments (IDE) such as Eclipse can be > challenging for those who have worked with simple notepads, writing > code with simple editors. > Despite having a B.Sc. Comp Sci, and understanding what libraries and > classes and namespaces are, it still seems overly complicated using > includes, make files, etc. And having workspaces that save all these > auxiliary files to support the integrated development environment. In > particular I'm referring to Visual Studio's solution files, project > files, database files, and the actual code called packages. It drives me insane. > > > > There Rant finished - provided to assure others that they are not > alone if feeling confused. J > > > > Feel free to use any, all or none of the above. Thanks for posting > what you have, it is an excellent starting point. > > > > From: David Partridge [mailto:re...@ro...] > Sent: Sunday, July 08, 2012 5:33 AM > To: col...@li... > Subject: Re: [Colossus-developers] Getting Started > > > > To make sense of this message, I had sent an original message with a > Doc attached on the process > > I just went through to load Subversion and build Colossus. It didn't > post because it was > > too big. I've now put that up at > colossus.sourceforge.net/Building.html > . > It goes through > > the process starting from scratch. > > > > I'm happy to update it with any suggestions, and to put in ways to > deal with problems as > > people encounter them. John, I don't know if it will help you or not > as some of your issues > > seem to be from having already had previous installations. Please let > me know if it does or > > doesn't help. > > > > BR > > Dave > > > > _____ > > From: David Partridge <re...@ro...> > To: "col...@li..." > <col...@li...> > Sent: Sunday, July 8, 2012 8:08 AM > Subject: Re: [Colossus-developers] Getting Started > > > > Why wait? I've got a new index.html to put up later, but I uploaded > the page on > > building. It's at colossus.sourceforge.net/Building.html . > > > > BR > > Dave > > > > _____ > > From: Clemens <cl...@cl...> > To: col...@li... > Sent: Sunday, July 8, 2012 4:53 AM > Subject: Re: [Colossus-developers] Getting Started > > > > True, most don't need another checkout (at least not of trunk, but > perhaps of a branch or a particular tag, for comparison). > > You checked out the parent folder, thus the "trunk" itself is a thing > that has SVN metadata. And if I got it right, you made that "trunk" > directory the root of the Eclupse workbench. Right? > > If you do something else within same workspace/workbench now, Tortoise > would report the "trunk" directory as "there's differences in it, > compared to repository". > > Additionally, you can only have "Colossus" and "WebSite" - thoses > names are as they are in repo. > > In contrast, I checkout only that level/entity I am interested in. And > I can name the work copy for checkout however I like. The thing I > checkout is the folder "Colossus" but I tend to name them according to > "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., > and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same > Eclipse workbench. > > This way I see them all as independent projects beside each other > within same workbenche (usually I close the projects I don't work > with, otherwise Eclipse might show warnings, or rebuild all, etc.). > > True, one could also have different Eclipse workbenches (one for each > thing one is working on, or something) but switching between > workbenches takes so long ... > > I'll send a screenshot about how it looks ... once I've set it up. > Just trying something else ATM ... > > BR, > Clemens > > > > On 2012-07-08 09:52, Barrie Treloar wrote: > > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: > >> > >> hm, "Interesting" ... first checkout and then import. Feels > >> backwards to me (because "first checkout" would be different that > >> later additional > >> ones) and for me restricts the future usage, would make some things > >> impossible I like to do (for example, I have several checkouts of > >> the "Colossus" beside each other; does not work out well with the > >> check out its parent and import, because if you then do another > >> checkout, it ends up in the "trunk" directory, hence e.g. Tortoise > >> would flag that level as modified. Additionally one checks out the > >> "WebSite" folder which is of really no use right now - causing > >> extra confusion. > > > > Can you please explain? > > Why would the first checkout be different than anything else? > > You keep this in sync just like any other subversion workspace by > > pulling down updates. > > > > Most people aren't going to need as many checkouts as you do, but > > each checkout will need to be in a differently named directory, you > > don't check it out again into a directory named "trunk" again. > > > >> I also favor the "all inside Eclipse" instead of > >> Tortoise/Eclipse-mix way (TortoiseSVN is a Windows only solution, > >> right?). Having it integrated it's easiest to do SVN operations > >> there, but more important, can see what was modified and what not, > >> etc... > >> > >> What's wrong with the approach Peter described in the Trac Wiki? > > > > Because there is no documentation that mentions the wiki anywhere... > > > > > > > ---------------------------------------------------------------------- > ------ > -- > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. > > Discussions > > will include endpoint security, mobile security and the latest in > > malware threats. > > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Colossus-developers mailing list > > Col...@li... > > https://lists.sourceforge.net/lists/listinfo/colossus-develop > > ---------------------------------------------------------------------- > ------ > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > > > ---------------------------------------------------------------------- > ------ > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > |
|
From: Norman S. <nsi...@sh...> - 2012-07-10 16:10:56
|
Wow, thanks Clemens. I've downloaded and played a couple of games against 11 computer AIs. Haven't involved many of the gods so far but I'll let you know when I have some experience with them. I also made an announcement on the server and directed everyone to the webpage. The link below http://colossus.sourceforge.net/special-build/ didn't' work. An error has been encountered in accessing this page. 1. Server: colossus.sourceforge.net 2. URL path: /special-build/ 3. Error notes: NONE 4. Error type: 403 5. Request method: GET 6. Request query string: NONE 7. Time: 2012-07-10 16:08:06 UTC (1341936486) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): Contact the project via their designated support resources. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at use...@us... If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line: Options +Indexes However I found the link on the Colossus webpage that pointed to the Public Test Builds http://sourceforge.net/apps/trac/colossus/wiki/PublicTestingBuild and the link at the bottom of the page. Zoro found it from my directions so hopefully we will be able to try it out between us. -----Original Message----- From: Clemens [mailto:cl...@cl...] Sent: Monday, July 09, 2012 8:54 AM To: David Partridge Cc: col...@li... Subject: Re: [Colossus-developers] Beelzebub12Gods testing build Hello Dave, I have made a "special testing" build for the BG 12 stuff. But contrary to what you suggested, I uploaded it to http://colossus.sourceforge.net/special-build/ because that location already existed, and I was not willing to fiddle with the "how to get another new jnlp file working" today... I added link to it also in main web page (link to RecentChanges... doc removed since I did neither update, nor upload that one). BTW, this also includes a temporary fix for the "Can't connect to socket" error you encountered. (And I realized why I didn't get that error earlier - I had stored an option "do not stop accepting clients" as true in my local Colossus-server.cfg, and due to that I didn't notice it when the change with the internal spectator client broke things. So that needs some cleanup... one more lesson of the category "how to fool yourself...") BR, Clemens On 2012-07-09 08:17, David Partridge wrote: > Hi Clemens, > > I've committed the changes for the Beelzebub12Gods testing build. > > Could you please make the version and put it in the > Beelzebub12Gods-testing directory. > > After you do that I'll put up a new page for > colossus.sourceforge.net/index.html that has > an icon for that and puts things into frames for better accessibility > and readability. > > BR > Dave ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Clemens <cl...@cl...> - 2012-07-09 16:11:56
|
>> I'm pretty happy with Github for wiki pages, if you're looking for a >> new >> free place to host them. Thanks for pointing that out, but... If somebody else would be willing to do that migration work - fine. Otherwise.... the wiki pages haven't been very wiki-ish anyway, so as easiest way forward, if it's me, I would probably just take the content and preserve it as plain html page "somewhere", instead of taking "yet another place where docs could be stored somehow" into use. BR, Clemens On 2012-07-04 03:28, Barrie Treloar wrote: > On Wed, Jul 4, 2012 at 7:57 AM, David Ripton <dr...@ri...> > wrote: >> On 07/03/2012 01:06 PM, Clemens wrote: >>> >>> We have basically only wiki pages. Let's see it as an opportunity >>> to >>> consolidate our scattered documentation bits & pieces :) >> >> I'm pretty happy with Github for wiki pages, if you're looking for a >> new >> free place to host them. > > And github support markdown (and I think a few other formats, not > really looked) so that it can take your raw pages and convert them to > html for people to view. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Clemens <cl...@cl...> - 2012-07-09 15:54:07
|
Hello Dave, I have made a "special testing" build for the BG 12 stuff. But contrary to what you suggested, I uploaded it to http://colossus.sourceforge.net/special-build/ because that location already existed, and I was not willing to fiddle with the "how to get another new jnlp file working" today... I added link to it also in main web page (link to RecentChanges... doc removed since I did neither update, nor upload that one). BTW, this also includes a temporary fix for the "Can't connect to socket" error you encountered. (And I realized why I didn't get that error earlier - I had stored an option "do not stop accepting clients" as true in my local Colossus-server.cfg, and due to that I didn't notice it when the change with the internal spectator client broke things. So that needs some cleanup... one more lesson of the category "how to fool yourself...") BR, Clemens On 2012-07-09 08:17, David Partridge wrote: > Hi Clemens, > > I've committed the changes for the Beelzebub12Gods testing build. > > Could you please make the version and put it in the > Beelzebub12Gods-testing directory. > > After you do that I'll put up a new page for > colossus.sourceforge.net/index.html that has > an icon for that and puts things into frames for better accessibility > and readability. > > BR > Dave |
|
From: Clemens <cl...@cl...> - 2012-07-09 14:11:12
|
> * Making a change Yeah, I started with that one, but when I ran Colossus then, I go the socket error Dave reported recently, so no point to publish that. Meanwhile I fixed that issue, next I will go for the new PTB for BG12, and then let's see for how much my power/motivation still suffices.... Actually some other tutorials I have in mind first, would be about how to use Colossus. For example the various nice features which most users don't know about (Auto-pick marker, auto pick color, auto-recruit, auto-pick recruiter, ...), or the "click user name in Summary window", etc.) > This is where having a Git repository would be handy. > SVN patches go stale very quickly. At the moment it's not like we are flooded with patches and nobody's working them in so they would get stale.... And I personally get pretty well around with working in patches (if necessary into a branch, and merge from there back to trunk) -- changing the whole thing to git would be quite a big change, I fear, and at least _I_ am not ready for that yet. Especially since I am worried how well git will work on windows. (Struggling with those "this works well on Linux but is trouble with Windows" issues is a thing which I *** REALLY REALLY REALLY *** don't need right now....) BR, Clemens On 2012-07-09 16:34, Barrie Treloar wrote: > On Mon, Jul 9, 2012 at 10:58 PM, Clemens <cl...@cl...> wrote: >> >>> You need a video tutorial about making video tutorials :) >> >> >> Perhaps; I noticed it myself, that "there's room for improvement". >> >> However in this occasion I didn't let this stop me from publishing >> it, as it >> happened dozens of times last 3 years (not putting a thing I had >> done >> public, just because it isn't perfect...) >> >> I came to conclusion that even a crappy tutorial with echoing voice, >> doing >> things too fast and whatever, is better than no tutorial at all.... > > The first videos had nice sound quality. Something happened at video > 3 or 4. > > I think it gives a nice overview for someone who does not know > anything to get started. > > It will be very useful. > > >>From previous emails I think we are missing, > * download Java SDK (which would be the first step) > * Building Colossus > * Running Colossus > * Using the Bug Tracker > * Finding a Bug to Fix > * Making a change > * Providing a patch for your change > > This is where having a Git repository would be handy. > SVN patches go stale very quickly. |
|
From: Barrie T. <bae...@gm...> - 2012-07-09 13:34:29
|
On Mon, Jul 9, 2012 at 10:58 PM, Clemens <cl...@cl...> wrote: > >> You need a video tutorial about making video tutorials :) > > > Perhaps; I noticed it myself, that "there's room for improvement". > > However in this occasion I didn't let this stop me from publishing it, as it > happened dozens of times last 3 years (not putting a thing I had done > public, just because it isn't perfect...) > > I came to conclusion that even a crappy tutorial with echoing voice, doing > things too fast and whatever, is better than no tutorial at all.... The first videos had nice sound quality. Something happened at video 3 or 4. I think it gives a nice overview for someone who does not know anything to get started. It will be very useful. >From previous emails I think we are missing, * download Java SDK (which would be the first step) * Building Colossus * Running Colossus * Using the Bug Tracker * Finding a Bug to Fix * Making a change * Providing a patch for your change This is where having a Git repository would be handy. SVN patches go stale very quickly. |
|
From: Clemens <cl...@cl...> - 2012-07-09 13:29:00
|
> You need a video tutorial about making video tutorials :) Perhaps; I noticed it myself, that "there's room for improvement". However in this occasion I didn't let this stop me from publishing it, as it happened dozens of times last 3 years (not putting a thing I had done public, just because it isn't perfect...) I came to conclusion that even a crappy tutorial with echoing voice, doing things too fast and whatever, is better than no tutorial at all.... BR, Clemens On 2012-07-09 16:15, Barrie Treloar wrote: > On Mon, Jul 9, 2012 at 10:15 PM, Clemens Katzer > <lem...@sa...> wrote: >> >> Ok, thanks Dave for that effort! And I agree with Norman, some of >> what he wrote came to my mind also when reading Dave's page. >> >> Meanwhile: Quite a while ago already I got an idea, how to instruct >> things differently than just text or text-with-pictures; but I never >> managed to go for it ... - now I finally did it. >> >> Thus while you worked on that page, I tried out something else - to >> create tutorial videos about it. >> >> Here's what I've got so far; feedback welcome! >> >> >> http://www.youtube.com/playlist?list=PL09CAC7FDB091F62C&feature=view_all > > You need a video tutorial about making video tutorials :) |
|
From: Barrie T. <bae...@gm...> - 2012-07-09 13:15:51
|
On Mon, Jul 9, 2012 at 10:15 PM, Clemens Katzer <lem...@sa...> wrote: > > Ok, thanks Dave for that effort! And I agree with Norman, some of what he wrote came to my mind also when reading Dave's page. > > Meanwhile: Quite a while ago already I got an idea, how to instruct things differently than just text or text-with-pictures; but I never managed to go for it ... - now I finally did it. > > Thus while you worked on that page, I tried out something else - to create tutorial videos about it. > > Here's what I've got so far; feedback welcome! > > http://www.youtube.com/playlist?list=PL09CAC7FDB091F62C&feature=view_all You need a video tutorial about making video tutorials :) |
|
From: Clemens <cl...@cl...> - 2012-07-09 13:11:17
|
> I'll send a screenshot about how it looks ... once I've set it up. Ok, here is the screenshot as I promised. In that picture I have checkouts (work copies) of trunk, the tag from release 0.13.1, and from the 0.13.x development branch. And as said, I can name those work copies (or Eclipse projects) however I want, so the names "trunk1", "release-0.13.2" and "branch-0.13.x" are totally my own choosing. BTW, about that branch... it's funny, I didn't even remember that branch any more myself, until Dave asked, because he was not able to find the "exact" revision of release 0.13.2 (or latest public test build, for that matter), from trunk; so only when he asked that, then I remembered, that I did the 0.13.2 in the 0.13.x branch, because in trunk I had already started "more risky changes" which I didn't want to take in into next coming release... So, right now, question is whether to make next release from trunk and hope to get the hickups out quickly, or be conservative and make a "hopefully more safely working build" from the 0.13.x branch... hm.... decisions decisions decisions ... I hate that.... > Just trying something else ATM ... BTW, that "something else" was the "trying to create video tutorials" about which I sent another mail recently :) BR, Clemens On 2012-07-08 11:53, Clemens wrote: > True, most don't need another checkout (at least not of trunk, but > perhaps of a branch or a particular tag, for comparison). > > You checked out the parent folder, thus the "trunk" itself is a thing > that has SVN metadata. And if I got it right, you made that "trunk" > directory the root of the Eclupse workbench. Right? > > If you do something else within same workspace/workbench now, > Tortoise would report the "trunk" directory as "there's differences > in > it, compared to repository". > > Additionally, you can only have "Colossus" and "WebSite" - thoses > names are as they are in repo. > > In contrast, I checkout only that level/entity I am interested in. > And I can name the work copy for checkout however I like. The thing I > checkout is the folder "Colossus" but I tend to name them according > to > "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., > and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same > Eclipse workbench. > > This way I see them all as independent projects beside each other > within same workbenche (usually I close the projects I don't work > with, otherwise Eclipse might show warnings, or rebuild all, etc.). > > True, one could also have different Eclipse workbenches (one for each > thing one is working on, or something) but switching between > workbenches takes so long ... > > I'll send a screenshot about how it looks ... once I've set it up. > Just trying something else ATM ... > > BR, > Clemens > > > > On 2012-07-08 09:52, Barrie Treloar wrote: >> On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: >>> >>> hm, "Interesting" ... first checkout and then import. Feels >>> backwards >>> to me (because "first checkout" would be different that later >>> additional >>> ones) and for me restricts the future usage, would make some things >>> impossible I like to do (for example, I have several checkouts of >>> the >>> "Colossus" beside each other; does not work out well with the check >>> out >>> its parent and import, because if you then do another checkout, it >>> ends >>> up in the "trunk" directory, hence e.g. Tortoise would flag that >>> level >>> as modified. Additionally one checks out the "WebSite" folder which >>> is >>> of really no use right now - causing extra confusion. >> >> Can you please explain? >> Why would the first checkout be different than anything else? >> You keep this in sync just like any other subversion workspace by >> pulling down updates. >> >> Most people aren't going to need as many checkouts as you do, but >> each >> checkout will need to be in a differently named directory, you don't >> check it out again into a directory named "trunk" again. >> >>> I also favor the "all inside Eclipse" instead of >>> Tortoise/Eclipse-mix >>> way (TortoiseSVN is a Windows only solution, right?). Having it >>> integrated it's easiest to do SVN operations there, but more >>> important, >>> can see what was modified and what not, etc... >>> >>> What's wrong with the approach Peter described in the Trac Wiki? >> >> Because there is no documentation that mentions the wiki anywhere... |
|
From: Clemens K. <lem...@sa...> - 2012-07-09 12:45:44
|
Ok, thanks Dave for that effort! And I agree with Norman, some of what he wrote came to my mind also when reading Dave's page. Meanwhile: Quite a while ago already I got an idea, how to instruct things differently than just text or text-with-pictures; but I never managed to go for it ... - now I finally did it. Thus while you worked on that page, I tried out something else - to create tutorial videos about it. Here's what I've got so far; feedback welcome! http://www.youtube.com/playlist?list=PL09CAC7FDB091F62C&feature=view_all BR, Clemens -------- Original-Nachricht -------- > Datum: Sun, 8 Jul 2012 19:47:52 -0700 > Von: "Norman Sillito" <nsi...@sh...> > An: "\'David Partridge\'" <re...@ro...> > CC: col...@li... > Betreff: Re: [Colossus-developers] Getting Started > Addition to step 1. There is no installation software to run. Just unzip > the > zip file and accept the defaults. Because there is no installation > software, > nothing gets added to the windows menu. You will have to create your own > shortcut on the desktop to the eclipse program. Mine shortcut has target = > "C:\Program Files\eclipse\eclipse.exe" > > > > The second #1 should be #2. > > > > Personally I find the Java site very frustrating. They have tried to make > it > simply and unfortunately they made it idiot proof so only . Anyway, > preamble for #2. > > > > #2 Java comes in many flavours. A runtime version (Java Runtime Edition, > JRE) which allows you to run java programs. A Java Development Kit (JDK) > which allows you to build java programs. The JDK comes in many variations > that focus on providing different built-in functionality. JavaFX, > NetBeans, > JavaEE. Ignore everything except the Java Platform, Standard Edition JDK > download. > > > > Java (and I) recommend removing any old versions of Java. If you need old > versions of Java then you can probably skip all these instructions as you > are already a programming god. Otherwise, go to the java site: > http://www.java.com/en/ select Free Java Download, select Remove Older > Versions and follow the instructions. After you have wiped all the older > versions then you are ready to get the JDK. > > > > The JDK can be found at > > http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-138363.htm > l#javasejdk > > If the link doesn't work, google Java, then search the Java site for JDK > > > > > > The line: > > > > Click Next twice, accept the license and click Finish. You may see a > security warning about installing software with unsigned content. If so, > click OK. Once again you need to restart Eclipse.> > > > > Should be changed to > > > > Click Next twice, accept the license and click Finish. You may see a > security warning about installing software with unsigned content. If so, > click OK. Once again you need to restart Eclipse. > > > > #4. Getting the Colossus source code from the SourceForge repository using > Subversion. > > > > >From the Eclipse menu: Select Window ==> Show View ==> SVN Repositories. > Eclipse will open a window with the title SVN Repositories. Right click > inside this window, click on New and then Repository Location. > > > > > > One thing that isn't clear from the webpage is where the Subversion > software > puts the colossus source code on my computer. I'm guessing it is the > current default workspace. Understanding workspace and integrated > development environments (IDE) such as Eclipse can be challenging for > those > who have worked with simple notepads, writing code with simple editors. > Despite having a B.Sc. Comp Sci, and understanding what libraries and > classes and namespaces are, it still seems overly complicated using > includes, make files, etc. And having workspaces that save all these > auxiliary files to support the integrated development environment. In > particular I'm referring to Visual Studio's solution files, project files, > database files, and the actual code called packages. It drives me insane. > > > > There Rant finished - provided to assure others that they are not alone if > feeling confused. J > > > > Feel free to use any, all or none of the above. Thanks for posting what > you > have, it is an excellent starting point. > > > > From: David Partridge [mailto:re...@ro...] > Sent: Sunday, July 08, 2012 5:33 AM > To: col...@li... > Subject: Re: [Colossus-developers] Getting Started > > > > To make sense of this message, I had sent an original message with a Doc > attached on the process > > I just went through to load Subversion and build Colossus. It didn't post > because it was > > too big. I've now put that up at colossus.sourceforge.net/Building.html > . > It goes through > > the process starting from scratch. > > > > I'm happy to update it with any suggestions, and to put in ways to deal > with > problems as > > people encounter them. John, I don't know if it will help you or not as > some of your issues > > seem to be from having already had previous installations. Please let me > know if it does or > > doesn't help. > > > > BR > > Dave > > > > _____ > > From: David Partridge <re...@ro...> > To: "col...@li..." > <col...@li...> > Sent: Sunday, July 8, 2012 8:08 AM > Subject: Re: [Colossus-developers] Getting Started > > > > Why wait? I've got a new index.html to put up later, but I uploaded the > page on > > building. It's at colossus.sourceforge.net/Building.html . > > > > BR > > Dave > > > > _____ > > From: Clemens <cl...@cl...> > To: col...@li... > Sent: Sunday, July 8, 2012 4:53 AM > Subject: Re: [Colossus-developers] Getting Started > > > > True, most don't need another checkout (at least not of trunk, but > perhaps of a branch or a particular tag, for comparison). > > You checked out the parent folder, thus the "trunk" itself is a thing > that has SVN metadata. And if I got it right, you made that "trunk" > directory the root of the Eclupse workbench. Right? > > If you do something else within same workspace/workbench now, Tortoise > would report the "trunk" directory as "there's differences in it, > compared to repository". > > Additionally, you can only have "Colossus" and "WebSite" - thoses names > are as they are in repo. > > In contrast, I checkout only that level/entity I am interested in. And > I can name the work copy for checkout however I like. The thing I > checkout is the folder "Colossus" but I tend to name them according to > "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., > and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same > Eclipse workbench. > > This way I see them all as independent projects beside each other > within same workbenche (usually I close the projects I don't work with, > otherwise Eclipse might show warnings, or rebuild all, etc.). > > True, one could also have different Eclipse workbenches (one for each > thing one is working on, or something) but switching between workbenches > takes so long ... > > I'll send a screenshot about how it looks ... once I've set it up. Just > trying something else ATM ... > > BR, > Clemens > > > > On 2012-07-08 09:52, Barrie Treloar wrote: > > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: > >> > >> hm, "Interesting" ... first checkout and then import. Feels > >> backwards > >> to me (because "first checkout" would be different that later > >> additional > >> ones) and for me restricts the future usage, would make some things > >> impossible I like to do (for example, I have several checkouts of > >> the > >> "Colossus" beside each other; does not work out well with the check > >> out > >> its parent and import, because if you then do another checkout, it > >> ends > >> up in the "trunk" directory, hence e.g. Tortoise would flag that > >> level > >> as modified. Additionally one checks out the "WebSite" folder which > >> is > >> of really no use right now - causing extra confusion. > > > > Can you please explain? > > Why would the first checkout be different than anything else? > > You keep this in sync just like any other subversion workspace by > > pulling down updates. > > > > Most people aren't going to need as many checkouts as you do, but > > each > > checkout will need to be in a differently named directory, you don't > > check it out again into a directory named "trunk" again. > > > >> I also favor the "all inside Eclipse" instead of > >> Tortoise/Eclipse-mix > >> way (TortoiseSVN is a Windows only solution, right?). Having it > >> integrated it's easiest to do SVN operations there, but more > >> important, > >> can see what was modified and what not, etc... > >> > >> What's wrong with the approach Peter described in the Trac Wiki? > > > > Because there is no documentation that mentions the wiki anywhere... > > > > > > > ---------------------------------------------------------------------------- > -- > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. > > Discussions > > will include endpoint security, mobile security and the latest in > > malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Colossus-developers mailing list > > Col...@li... > > https://lists.sourceforge.net/lists/listinfo/colossus-develop > > ---------------------------------------------------------------------------- > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > > > ---------------------------------------------------------------------------- > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > |
|
From: Norman S. <nsi...@sh...> - 2012-07-09 02:48:01
|
Addition to step 1. There is no installation software to run. Just unzip the zip file and accept the defaults. Because there is no installation software, nothing gets added to the windows menu. You will have to create your own shortcut on the desktop to the eclipse program. Mine shortcut has target = "C:\Program Files\eclipse\eclipse.exe" The second #1 should be #2. Personally I find the Java site very frustrating. They have tried to make it simply and unfortunately they made it idiot proof so only . Anyway, preamble for #2. #2 Java comes in many flavours. A runtime version (Java Runtime Edition, JRE) which allows you to run java programs. A Java Development Kit (JDK) which allows you to build java programs. The JDK comes in many variations that focus on providing different built-in functionality. JavaFX, NetBeans, JavaEE. Ignore everything except the Java Platform, Standard Edition JDK download. Java (and I) recommend removing any old versions of Java. If you need old versions of Java then you can probably skip all these instructions as you are already a programming god. Otherwise, go to the java site: http://www.java.com/en/ select Free Java Download, select Remove Older Versions and follow the instructions. After you have wiped all the older versions then you are ready to get the JDK. The JDK can be found at http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-138363.htm l#javasejdk If the link doesn't work, google Java, then search the Java site for JDK The line: Click Next twice, accept the license and click Finish. You may see a security warning about installing software with unsigned content. If so, click OK. Once again you need to restart Eclipse.> Should be changed to Click Next twice, accept the license and click Finish. You may see a security warning about installing software with unsigned content. If so, click OK. Once again you need to restart Eclipse. #4. Getting the Colossus source code from the SourceForge repository using Subversion. >From the Eclipse menu: Select Window ==> Show View ==> SVN Repositories. Eclipse will open a window with the title SVN Repositories. Right click inside this window, click on New and then Repository Location. One thing that isn't clear from the webpage is where the Subversion software puts the colossus source code on my computer. I'm guessing it is the current default workspace. Understanding workspace and integrated development environments (IDE) such as Eclipse can be challenging for those who have worked with simple notepads, writing code with simple editors. Despite having a B.Sc. Comp Sci, and understanding what libraries and classes and namespaces are, it still seems overly complicated using includes, make files, etc. And having workspaces that save all these auxiliary files to support the integrated development environment. In particular I'm referring to Visual Studio's solution files, project files, database files, and the actual code called packages. It drives me insane. There Rant finished - provided to assure others that they are not alone if feeling confused. J Feel free to use any, all or none of the above. Thanks for posting what you have, it is an excellent starting point. From: David Partridge [mailto:re...@ro...] Sent: Sunday, July 08, 2012 5:33 AM To: col...@li... Subject: Re: [Colossus-developers] Getting Started To make sense of this message, I had sent an original message with a Doc attached on the process I just went through to load Subversion and build Colossus. It didn't post because it was too big. I've now put that up at colossus.sourceforge.net/Building.html . It goes through the process starting from scratch. I'm happy to update it with any suggestions, and to put in ways to deal with problems as people encounter them. John, I don't know if it will help you or not as some of your issues seem to be from having already had previous installations. Please let me know if it does or doesn't help. BR Dave _____ From: David Partridge <re...@ro...> To: "col...@li..." <col...@li...> Sent: Sunday, July 8, 2012 8:08 AM Subject: Re: [Colossus-developers] Getting Started Why wait? I've got a new index.html to put up later, but I uploaded the page on building. It's at colossus.sourceforge.net/Building.html . BR Dave _____ From: Clemens <cl...@cl...> To: col...@li... Sent: Sunday, July 8, 2012 4:53 AM Subject: Re: [Colossus-developers] Getting Started True, most don't need another checkout (at least not of trunk, but perhaps of a branch or a particular tag, for comparison). You checked out the parent folder, thus the "trunk" itself is a thing that has SVN metadata. And if I got it right, you made that "trunk" directory the root of the Eclupse workbench. Right? If you do something else within same workspace/workbench now, Tortoise would report the "trunk" directory as "there's differences in it, compared to repository". Additionally, you can only have "Colossus" and "WebSite" - thoses names are as they are in repo. In contrast, I checkout only that level/entity I am interested in. And I can name the work copy for checkout however I like. The thing I checkout is the folder "Colossus" but I tend to name them according to "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same Eclipse workbench. This way I see them all as independent projects beside each other within same workbenche (usually I close the projects I don't work with, otherwise Eclipse might show warnings, or rebuild all, etc.). True, one could also have different Eclipse workbenches (one for each thing one is working on, or something) but switching between workbenches takes so long ... I'll send a screenshot about how it looks ... once I've set it up. Just trying something else ATM ... BR, Clemens On 2012-07-08 09:52, Barrie Treloar wrote: > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: >> >> hm, "Interesting" ... first checkout and then import. Feels >> backwards >> to me (because "first checkout" would be different that later >> additional >> ones) and for me restricts the future usage, would make some things >> impossible I like to do (for example, I have several checkouts of >> the >> "Colossus" beside each other; does not work out well with the check >> out >> its parent and import, because if you then do another checkout, it >> ends >> up in the "trunk" directory, hence e.g. Tortoise would flag that >> level >> as modified. Additionally one checks out the "WebSite" folder which >> is >> of really no use right now - causing extra confusion. > > Can you please explain? > Why would the first checkout be different than anything else? > You keep this in sync just like any other subversion workspace by > pulling down updates. > > Most people aren't going to need as many checkouts as you do, but > each > checkout will need to be in a differently named directory, you don't > check it out again into a directory named "trunk" again. > >> I also favor the "all inside Eclipse" instead of >> Tortoise/Eclipse-mix >> way (TortoiseSVN is a Windows only solution, right?). Having it >> integrated it's easiest to do SVN operations there, but more >> important, >> can see what was modified and what not, etc... >> >> What's wrong with the approach Peter described in the Trac Wiki? > > Because there is no documentation that mentions the wiki anywhere... > > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-develop ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: David P. <re...@ro...> - 2012-07-08 19:30:31
|
Yes, I cancelled it as I put it up on the website. Dave ________________________________ From: Clemens <cl...@cl...> To: col...@li... Sent: Sunday, July 8, 2012 9:17 AM Subject: Re: [Colossus-developers] Getting Started Actually I wanted to do it when I sent the mail but there's nothing to approve. Did you "cancel" it ? BR, Clemens On 2012-07-08 16:15, Clemens wrote: > On 2012-07-08 15:32, David Partridge wrote: >> To make sense of this message, I had sent an original message with a >> Doc attached on the process >> I just went through to load Subversion and build Colossus. It didn't >> post because it was too big. > > mails over 300 KB require mailing list moderators (David Ripton or > mine) approval. > > I've done that now. > > BR, > Clemens > > >> I've now put that up at >> colossus.sourceforge.net/Building.html [1] . It goes through >> the process starting from scratch. >> >> I'm happy to update it with any suggestions, and to put in ways to >> deal with problems as >> people encounter them. John, I don't know if it will help you or not >> as some of your issues >> seem to be from having already had previous installations. Please >> let >> me know if it does or >> doesn't help. >> >> BR >> Dave >> >> ------------------------- >> FROM: David Partridge <re...@ro...> >> TO: "col...@li..." >> <col...@li...> >> SENT: Sunday, July 8, 2012 8:08 AM >> SUBJECT: Re: [Colossus-developers] Getting Started >> >> Why wait? I've got a new index.html to put up later, but I uploaded >> the page on >> building. It's at colossus.sourceforge.net/Building.html [2] . >> >> BR >> Dave >> >> ------------------------- >> FROM: Clemens <cl...@cl...> >> TO: col...@li... >> SENT: Sunday, July 8, 2012 4:53 AM >> SUBJECT: Re: [Colossus-developers] Getting Started >> >> True, most don't need another checkout (at least not of trunk, but >> perhaps of a branch or a particular tag, for comparison). >> >> You checked out the parent folder, thus the "trunk" itself is a >> thing >> that has SVN metadata. And if I got it right, you made that "trunk" >> directory the root of the Eclupse workbench. Right? >> >> If you do something else within same workspace/workbench now, >> Tortoise >> >> would report the "trunk" directory as "there's differences in it, >> compared to repository". >> >> Additionally, you can only have "Colossus" and "WebSite" - thoses >> names >> are as they are in repo. >> >> In contrast, I checkout only that level/entity I am interested in. >> And >> >> I can name the work copy for checkout however I like. The thing I >> checkout is the folder "Colossus" but I tend to name them according >> to >> >> "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", >> ..., >> and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same >> Eclipse workbench. >> >> This way I see them all as independent projects beside each other >> within same workbenche (usually I close the projects I don't work >> with, >> otherwise Eclipse might show warnings, or rebuild all, etc.). >> >> True, one could also have different Eclipse workbenches (one for >> each >> thing one is working on, or something) but switching between >> workbenches >> takes so long ... >> >> I'll send a screenshot about how it looks ... once I've set it up. >> Just >> trying something else ATM ... >> >> BR, >> Clemens >> >> On 2012-07-08 09:52, Barrie Treloar wrote: >>> On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl... [3]> >> wrote: >>>> >>>> hm, "Interesting" ... first checkout and then import. Feels >>>> backwards >>>> to me (because "first checkout" would be different that later >>>> additional >>>> ones) and for me restricts the future usage, would make some >>>> things >>>> impossible I like to do (for example, I have several checkouts of >>>> the >>>> "Colossus" beside each other; does not work out well with the >>>> check >> >>>> out >>>> its parent and import, because if you then do another checkout, it >>>> ends >>>> up in the "trunk" directory, hence e.g. Tortoise would flag that >>>> level >>>> as modified. Additionally one checks out the "WebSite" folder >>>> which >> >>>> is >>>> of really no use right now - causing extra confusion. >>> >>> Can you please explain? >>> Why would the first checkout be different than anything else? >>> You keep this in sync just like any other subversion workspace by >>> pulling down updates. >>> >>> Most people aren't going to need as many checkouts as you do, but >>> each >>> checkout will need to be in a differently named directory, you >>> don't >>> check it out again into a directory named "trunk" again. >>> >>>> I also favor the "all inside Eclipse" instead of >>>> Tortoise/Eclipse-mix >>>> way (TortoiseSVN is a Windows only solution, right?). Having it >>>> integrated it's easiest to do SVN operations there, but more >>>> important, >>>> can see what was modified and what not, etc... >>>> >>>> What's wrong with the approach Peter described in the Trac Wiki? >>> >>> Because there is no documentation that mentions the wiki >>> anywhere... >>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. >>> Discussions >>> will include endpoint security, mobile security and the latest in >>> malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Colossus-developers mailing list >>> Col...@li... [4] >>> https://lists.sourceforge.net/lists/listinfo/colossus-develop [5] >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [6] >> _______________________________________________ >> Colossus-developers mailing list >> Col...@li... [7] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers [8] >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [9] >> _______________________________________________ >> Colossus-developers mailing list >> Col...@li... [10] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers >> [11] >> >> >> >> Links: >> ------ >> [1] http://colossus.sourceforge.net/Building.html >> [2] http://colossus.sourceforge.net/Building.html >> [3] mailto:cl...@cl... >> [4] mailto:Col...@li... >> [5] https://lists.sourceforge.net/lists/listinfo/colossus-develop >> [6] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [7] mailto:Col...@li... >> [8] https://lists.sourceforge.net/lists/listinfo/colossus-developers >> [9] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [10] mailto:Col...@li... >> [11] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Clemens <cl...@cl...> - 2012-07-08 13:17:52
|
Actually I wanted to do it when I sent the mail but there's nothing to approve. Did you "cancel" it ? BR, Clemens On 2012-07-08 16:15, Clemens wrote: > On 2012-07-08 15:32, David Partridge wrote: >> To make sense of this message, I had sent an original message with a >> Doc attached on the process >> I just went through to load Subversion and build Colossus. It didn't >> post because it was too big. > > mails over 300 KB require mailing list moderators (David Ripton or > mine) approval. > > I've done that now. > > BR, > Clemens > > >> I've now put that up at >> colossus.sourceforge.net/Building.html [1] . It goes through >> the process starting from scratch. >> >> I'm happy to update it with any suggestions, and to put in ways to >> deal with problems as >> people encounter them. John, I don't know if it will help you or not >> as some of your issues >> seem to be from having already had previous installations. Please >> let >> me know if it does or >> doesn't help. >> >> BR >> Dave >> >> ------------------------- >> FROM: David Partridge <re...@ro...> >> TO: "col...@li..." >> <col...@li...> >> SENT: Sunday, July 8, 2012 8:08 AM >> SUBJECT: Re: [Colossus-developers] Getting Started >> >> Why wait? I've got a new index.html to put up later, but I uploaded >> the page on >> building. It's at colossus.sourceforge.net/Building.html [2] . >> >> BR >> Dave >> >> ------------------------- >> FROM: Clemens <cl...@cl...> >> TO: col...@li... >> SENT: Sunday, July 8, 2012 4:53 AM >> SUBJECT: Re: [Colossus-developers] Getting Started >> >> True, most don't need another checkout (at least not of trunk, but >> perhaps of a branch or a particular tag, for comparison). >> >> You checked out the parent folder, thus the "trunk" itself is a >> thing >> that has SVN metadata. And if I got it right, you made that "trunk" >> directory the root of the Eclupse workbench. Right? >> >> If you do something else within same workspace/workbench now, >> Tortoise >> >> would report the "trunk" directory as "there's differences in it, >> compared to repository". >> >> Additionally, you can only have "Colossus" and "WebSite" - thoses >> names >> are as they are in repo. >> >> In contrast, I checkout only that level/entity I am interested in. >> And >> >> I can name the work copy for checkout however I like. The thing I >> checkout is the folder "Colossus" but I tend to name them according >> to >> >> "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", >> ..., >> and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same >> Eclipse workbench. >> >> This way I see them all as independent projects beside each other >> within same workbenche (usually I close the projects I don't work >> with, >> otherwise Eclipse might show warnings, or rebuild all, etc.). >> >> True, one could also have different Eclipse workbenches (one for >> each >> thing one is working on, or something) but switching between >> workbenches >> takes so long ... >> >> I'll send a screenshot about how it looks ... once I've set it up. >> Just >> trying something else ATM ... >> >> BR, >> Clemens >> >> On 2012-07-08 09:52, Barrie Treloar wrote: >>> On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl... [3]> >> wrote: >>>> >>>> hm, "Interesting" ... first checkout and then import. Feels >>>> backwards >>>> to me (because "first checkout" would be different that later >>>> additional >>>> ones) and for me restricts the future usage, would make some >>>> things >>>> impossible I like to do (for example, I have several checkouts of >>>> the >>>> "Colossus" beside each other; does not work out well with the >>>> check >> >>>> out >>>> its parent and import, because if you then do another checkout, it >>>> ends >>>> up in the "trunk" directory, hence e.g. Tortoise would flag that >>>> level >>>> as modified. Additionally one checks out the "WebSite" folder >>>> which >> >>>> is >>>> of really no use right now - causing extra confusion. >>> >>> Can you please explain? >>> Why would the first checkout be different than anything else? >>> You keep this in sync just like any other subversion workspace by >>> pulling down updates. >>> >>> Most people aren't going to need as many checkouts as you do, but >>> each >>> checkout will need to be in a differently named directory, you >>> don't >>> check it out again into a directory named "trunk" again. >>> >>>> I also favor the "all inside Eclipse" instead of >>>> Tortoise/Eclipse-mix >>>> way (TortoiseSVN is a Windows only solution, right?). Having it >>>> integrated it's easiest to do SVN operations there, but more >>>> important, >>>> can see what was modified and what not, etc... >>>> >>>> What's wrong with the approach Peter described in the Trac Wiki? >>> >>> Because there is no documentation that mentions the wiki >>> anywhere... >>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. >>> Discussions >>> will include endpoint security, mobile security and the latest in >>> malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Colossus-developers mailing list >>> Col...@li... [4] >>> https://lists.sourceforge.net/lists/listinfo/colossus-develop [5] >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [6] >> _______________________________________________ >> Colossus-developers mailing list >> Col...@li... [7] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers [8] >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [9] >> _______________________________________________ >> Colossus-developers mailing list >> Col...@li... [10] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers >> [11] >> >> >> >> Links: >> ------ >> [1] http://colossus.sourceforge.net/Building.html >> [2] http://colossus.sourceforge.net/Building.html >> [3] mailto:cl...@cl... >> [4] mailto:Col...@li... >> [5] https://lists.sourceforge.net/lists/listinfo/colossus-develop >> [6] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [7] mailto:Col...@li... >> [8] https://lists.sourceforge.net/lists/listinfo/colossus-developers >> [9] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> [10] mailto:Col...@li... >> [11] >> https://lists.sourceforge.net/lists/listinfo/colossus-developers > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Clemens <cl...@cl...> - 2012-07-08 13:15:33
|
On 2012-07-08 15:32, David Partridge wrote: > To make sense of this message, I had sent an original message with a > Doc attached on the process > I just went through to load Subversion and build Colossus. It didn't > post because it was too big. mails over 300 KB require mailing list moderators (David Ripton or mine) approval. I've done that now. BR, Clemens > I've now put that up at > colossus.sourceforge.net/Building.html [1] . It goes through > the process starting from scratch. > > I'm happy to update it with any suggestions, and to put in ways to > deal with problems as > people encounter them. John, I don't know if it will help you or not > as some of your issues > seem to be from having already had previous installations. Please let > me know if it does or > doesn't help. > > BR > Dave > > ------------------------- > FROM: David Partridge <re...@ro...> > TO: "col...@li..." > <col...@li...> > SENT: Sunday, July 8, 2012 8:08 AM > SUBJECT: Re: [Colossus-developers] Getting Started > > Why wait? I've got a new index.html to put up later, but I uploaded > the page on > building. It's at colossus.sourceforge.net/Building.html [2] . > > BR > Dave > > ------------------------- > FROM: Clemens <cl...@cl...> > TO: col...@li... > SENT: Sunday, July 8, 2012 4:53 AM > SUBJECT: Re: [Colossus-developers] Getting Started > > True, most don't need another checkout (at least not of trunk, but > perhaps of a branch or a particular tag, for comparison). > > You checked out the parent folder, thus the "trunk" itself is a thing > that has SVN metadata. And if I got it right, you made that "trunk" > directory the root of the Eclupse workbench. Right? > > If you do something else within same workspace/workbench now, > Tortoise > > would report the "trunk" directory as "there's differences in it, > compared to repository". > > Additionally, you can only have "Colossus" and "WebSite" - thoses > names > are as they are in repo. > > In contrast, I checkout only that level/entity I am interested in. > And > > I can name the work copy for checkout however I like. The thing I > checkout is the folder "Colossus" but I tend to name them according > to > > "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., > and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same > Eclipse workbench. > > This way I see them all as independent projects beside each other > within same workbenche (usually I close the projects I don't work > with, > otherwise Eclipse might show warnings, or rebuild all, etc.). > > True, one could also have different Eclipse workbenches (one for each > thing one is working on, or something) but switching between > workbenches > takes so long ... > > I'll send a screenshot about how it looks ... once I've set it up. > Just > trying something else ATM ... > > BR, > Clemens > > On 2012-07-08 09:52, Barrie Treloar wrote: >> On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl... [3]> > wrote: >>> >>> hm, "Interesting" ... first checkout and then import. Feels >>> backwards >>> to me (because "first checkout" would be different that later >>> additional >>> ones) and for me restricts the future usage, would make some things >>> impossible I like to do (for example, I have several checkouts of >>> the >>> "Colossus" beside each other; does not work out well with the check > >>> out >>> its parent and import, because if you then do another checkout, it >>> ends >>> up in the "trunk" directory, hence e.g. Tortoise would flag that >>> level >>> as modified. Additionally one checks out the "WebSite" folder which > >>> is >>> of really no use right now - causing extra confusion. >> >> Can you please explain? >> Why would the first checkout be different than anything else? >> You keep this in sync just like any other subversion workspace by >> pulling down updates. >> >> Most people aren't going to need as many checkouts as you do, but >> each >> checkout will need to be in a differently named directory, you don't >> check it out again into a directory named "trunk" again. >> >>> I also favor the "all inside Eclipse" instead of >>> Tortoise/Eclipse-mix >>> way (TortoiseSVN is a Windows only solution, right?). Having it >>> integrated it's easiest to do SVN operations there, but more >>> important, >>> can see what was modified and what not, etc... >>> >>> What's wrong with the approach Peter described in the Trac Wiki? >> >> Because there is no documentation that mentions the wiki anywhere... >> >> >> > > ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Colossus-developers mailing list >> Col...@li... [4] >> https://lists.sourceforge.net/lists/listinfo/colossus-develop [5] > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > [6] > _______________________________________________ > Colossus-developers mailing list > Col...@li... [7] > https://lists.sourceforge.net/lists/listinfo/colossus-developers [8] > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > [9] > _______________________________________________ > Colossus-developers mailing list > Col...@li... [10] > https://lists.sourceforge.net/lists/listinfo/colossus-developers [11] > > > > Links: > ------ > [1] http://colossus.sourceforge.net/Building.html > [2] http://colossus.sourceforge.net/Building.html > [3] mailto:cl...@cl... > [4] mailto:Col...@li... > [5] https://lists.sourceforge.net/lists/listinfo/colossus-develop > [6] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > [7] mailto:Col...@li... > [8] https://lists.sourceforge.net/lists/listinfo/colossus-developers > [9] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > [10] mailto:Col...@li... > [11] https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: David P. <re...@ro...> - 2012-07-08 12:33:02
|
To make sense of this message, I had sent an original message with a Doc attached on the process I just went through to load Subversion and build Colossus. It didn't post because it was too big. I've now put that up at colossus.sourceforge.net/Building.html . It goes through the process starting from scratch. I'm happy to update it with any suggestions, and to put in ways to deal with problems as people encounter them. John, I don't know if it will help you or not as some of your issues seem to be from having already had previous installations. Please let me know if it does or doesn't help. BR Dave ________________________________ From: David Partridge <re...@ro...> To: "col...@li..." <col...@li...> Sent: Sunday, July 8, 2012 8:08 AM Subject: Re: [Colossus-developers] Getting Started Why wait? I've got a new index.html to put up later, but I uploaded the page on building. It's at colossus.sourceforge.net/Building.html . BR Dave ________________________________ From: Clemens <cl...@cl...> To: col...@li... Sent: Sunday, July 8, 2012 4:53 AM Subject: Re: [Colossus-developers] Getting Started True, most don't need another checkout (at least not of trunk, but perhaps of a branch or a particular tag, for comparison). You checked out the parent folder, thus the "trunk" itself is a thing that has SVN metadata. And if I got it right, you made that "trunk" directory the root of the Eclupse workbench. Right? If you do something else within same workspace/workbench now, Tortoise would report the "trunk" directory as "there's differences in it, compared to repository". Additionally, you can only have "Colossus" and "WebSite" - thoses names are as they are in repo. In contrast, I checkout only that level/entity I am interested in. And I can name the work copy for checkout however I like. The thing I checkout is the folder "Colossus" but I tend to name them according to "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same Eclipse workbench. This way I see them all as independent projects beside each other within same workbenche (usually I close the projects I don't work with, otherwise Eclipse might show warnings, or rebuild all, etc.). True, one could also have different Eclipse workbenches (one for each thing one is working on, or something) but switching between workbenches takes so long ... I'll send a screenshot about how it looks ... once I've set it up. Just trying something else ATM ... BR, Clemens On 2012-07-08 09:52, Barrie Treloar wrote: > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: >> >> hm, "Interesting" ... first checkout and then import. Feels >> backwards >> to me (because "first checkout" would be different that later >> additional >> ones) and for me restricts the future usage, would make some things >> impossible I like to do (for example, I have several checkouts of >> the >> "Colossus" beside each other; does not work out well with the check >> out >> its parent and import, because if you then do another checkout, it >> ends >> up in the "trunk" directory, hence e.g. Tortoise would flag that >> level >> as modified. Additionally one checks out the "WebSite" folder which >> is >> of really no use right now - causing extra confusion. > > Can you please explain? > Why would the first checkout be different than anything else? > You keep this in sync just like any other subversion workspace by > pulling down updates. > > Most people aren't going to need as many checkouts as you do, but > each > checkout will need to be in a differently named directory, you don't > check it out again into a directory named "trunk" again. > >> I also favor the "all inside Eclipse" instead of >> Tortoise/Eclipse-mix >> way (TortoiseSVN is a Windows only solution, right?). Having it >> integrated it's easiest to do SVN operations there, but more >> important, >> can see what was modified and what not, etc... >> >> What's wrong with the approach Peter described in the Trac Wiki? > > Because there is no documentation that mentions the wiki anywhere... > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-develop ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: David P. <re...@ro...> - 2012-07-08 12:08:14
|
Why wait? I've got a new index.html to put up later, but I uploaded the page on building. It's at colossus.sourceforge.net/Building.html . BR Dave ________________________________ From: Clemens <cl...@cl...> To: col...@li... Sent: Sunday, July 8, 2012 4:53 AM Subject: Re: [Colossus-developers] Getting Started True, most don't need another checkout (at least not of trunk, but perhaps of a branch or a particular tag, for comparison). You checked out the parent folder, thus the "trunk" itself is a thing that has SVN metadata. And if I got it right, you made that "trunk" directory the root of the Eclupse workbench. Right? If you do something else within same workspace/workbench now, Tortoise would report the "trunk" directory as "there's differences in it, compared to repository". Additionally, you can only have "Colossus" and "WebSite" - thoses names are as they are in repo. In contrast, I checkout only that level/entity I am interested in. And I can name the work copy for checkout however I like. The thing I checkout is the folder "Colossus" but I tend to name them according to "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same Eclipse workbench. This way I see them all as independent projects beside each other within same workbenche (usually I close the projects I don't work with, otherwise Eclipse might show warnings, or rebuild all, etc.). True, one could also have different Eclipse workbenches (one for each thing one is working on, or something) but switching between workbenches takes so long ... I'll send a screenshot about how it looks ... once I've set it up. Just trying something else ATM ... BR, Clemens On 2012-07-08 09:52, Barrie Treloar wrote: > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: >> >> hm, "Interesting" ... first checkout and then import. Feels >> backwards >> to me (because "first checkout" would be different that later >> additional >> ones) and for me restricts the future usage, would make some things >> impossible I like to do (for example, I have several checkouts of >> the >> "Colossus" beside each other; does not work out well with the check >> out >> its parent and import, because if you then do another checkout, it >> ends >> up in the "trunk" directory, hence e.g. Tortoise would flag that >> level >> as modified. Additionally one checks out the "WebSite" folder which >> is >> of really no use right now - causing extra confusion. > > Can you please explain? > Why would the first checkout be different than anything else? > You keep this in sync just like any other subversion workspace by > pulling down updates. > > Most people aren't going to need as many checkouts as you do, but > each > checkout will need to be in a differently named directory, you don't > check it out again into a directory named "trunk" again. > >> I also favor the "all inside Eclipse" instead of >> Tortoise/Eclipse-mix >> way (TortoiseSVN is a Windows only solution, right?). Having it >> integrated it's easiest to do SVN operations there, but more >> important, >> can see what was modified and what not, etc... >> >> What's wrong with the approach Peter described in the Trac Wiki? > > Because there is no documentation that mentions the wiki anywhere... > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-develop ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Colossus-developers mailing list Col...@li... https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Clemens <cl...@cl...> - 2012-07-08 08:53:47
|
True, most don't need another checkout (at least not of trunk, but perhaps of a branch or a particular tag, for comparison). You checked out the parent folder, thus the "trunk" itself is a thing that has SVN metadata. And if I got it right, you made that "trunk" directory the root of the Eclupse workbench. Right? If you do something else within same workspace/workbench now, Tortoise would report the "trunk" directory as "there's differences in it, compared to repository". Additionally, you can only have "Colossus" and "WebSite" - thoses names are as they are in repo. In contrast, I checkout only that level/entity I am interested in. And I can name the work copy for checkout however I like. The thing I checkout is the folder "Colossus" but I tend to name them according to "what they are" - like: "trunk", (or rather, "trunk1", "trunk2", ..., and "release-0.13.1", or "romain-battleAI-SQL-stuff". All in same Eclipse workbench. This way I see them all as independent projects beside each other within same workbenche (usually I close the projects I don't work with, otherwise Eclipse might show warnings, or rebuild all, etc.). True, one could also have different Eclipse workbenches (one for each thing one is working on, or something) but switching between workbenches takes so long ... I'll send a screenshot about how it looks ... once I've set it up. Just trying something else ATM ... BR, Clemens On 2012-07-08 09:52, Barrie Treloar wrote: > On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: >> >> hm, "Interesting" ... first checkout and then import. Feels >> backwards >> to me (because "first checkout" would be different that later >> additional >> ones) and for me restricts the future usage, would make some things >> impossible I like to do (for example, I have several checkouts of >> the >> "Colossus" beside each other; does not work out well with the check >> out >> its parent and import, because if you then do another checkout, it >> ends >> up in the "trunk" directory, hence e.g. Tortoise would flag that >> level >> as modified. Additionally one checks out the "WebSite" folder which >> is >> of really no use right now - causing extra confusion. > > Can you please explain? > Why would the first checkout be different than anything else? > You keep this in sync just like any other subversion workspace by > pulling down updates. > > Most people aren't going to need as many checkouts as you do, but > each > checkout will need to be in a differently named directory, you don't > check it out again into a directory named "trunk" again. > >> I also favor the "all inside Eclipse" instead of >> Tortoise/Eclipse-mix >> way (TortoiseSVN is a Windows only solution, right?). Having it >> integrated it's easiest to do SVN operations there, but more >> important, >> can see what was modified and what not, etc... >> >> What's wrong with the approach Peter described in the Trac Wiki? > > Because there is no documentation that mentions the wiki anywhere... > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-develop |
|
From: Barrie T. <bae...@gm...> - 2012-07-08 06:52:38
|
On Sun, Jul 8, 2012 at 3:17 PM, Clemens <cl...@cl...> wrote: > > hm, "Interesting" ... first checkout and then import. Feels backwards > to me (because "first checkout" would be different that later additional > ones) and for me restricts the future usage, would make some things > impossible I like to do (for example, I have several checkouts of the > "Colossus" beside each other; does not work out well with the check out > its parent and import, because if you then do another checkout, it ends > up in the "trunk" directory, hence e.g. Tortoise would flag that level > as modified. Additionally one checks out the "WebSite" folder which is > of really no use right now - causing extra confusion. Can you please explain? Why would the first checkout be different than anything else? You keep this in sync just like any other subversion workspace by pulling down updates. Most people aren't going to need as many checkouts as you do, but each checkout will need to be in a differently named directory, you don't check it out again into a directory named "trunk" again. > I also favor the "all inside Eclipse" instead of Tortoise/Eclipse-mix > way (TortoiseSVN is a Windows only solution, right?). Having it > integrated it's easiest to do SVN operations there, but more important, > can see what was modified and what not, etc... > > What's wrong with the approach Peter described in the Trac Wiki? Because there is no documentation that mentions the wiki anywhere... |
|
From: Clemens <cl...@cl...> - 2012-07-08 05:47:55
|
hm, "Interesting" ... first checkout and then import. Feels backwards to me (because "first checkout" would be different that later additional ones) and for me restricts the future usage, would make some things impossible I like to do (for example, I have several checkouts of the "Colossus" beside each other; does not work out well with the check out its parent and import, because if you then do another checkout, it ends up in the "trunk" directory, hence e.g. Tortoise would flag that level as modified. Additionally one checks out the "WebSite" folder which is of really no use right now - causing extra confusion. I also favor the "all inside Eclipse" instead of Tortoise/Eclipse-mix way (TortoiseSVN is a Windows only solution, right?). Having it integrated it's easiest to do SVN operations there, but more important, can see what was modified and what not, etc... What's wrong with the approach Peter described in the Trac Wiki? - install Eclipse, creating an initial workspace - install Subclipse or Subversive - create a repo location (or two: the "svnroot/colossus/trunk/Colossus" as the one to work mostly with and "svnroot/colossus" as top level if one wants to browse also tags + branches one day) - checkout the .../trunk/Colossus/ folder into the workspace (without using the wizard!!); checking out that level Eclipse automatically finds the .project stuff, and you're instantly ready to go. Starting that way, one can checkout e.g. another trunk instance beside it in exactly same way, just repeating last step. BR, Clemens On 2012-07-08 07:41, Barrie Treloar wrote: > On Sun, Jul 8, 2012 at 6:04 AM, John David Galt > <jd...@di...> wrote: >>> On Sun, Jul 1, 2012 at 1:56 AM, John David Galt wrote: >>>> I have yet to manage to get the code to download and compile. ?It >>>> seems like >>>> every time I make the effort, somebody changes the tools the >>>> project is using, >>>> shutting me out again. >> >> On Sun, 1 Jul 2012 07:15:32 +0930, Barrie Treloar wrote: >>> Then the documentation should be improved so that others don't get >>> the >>> same problem as you. It is always helpful to get fresh people on >>> the >>> project for exactly this reason, to make sure that the getting >>> started >>> documentation is correct. >>> >>> Try again and mail the list any problems that you have so that we >>> can >>> get them fixed. >> >> OK, thanks, I'll take you up on that. So far I have: > > So which instructions did you follow? > > http://colossus.sourceforge.net/ says in the Download section: > "Or you can grab the code via Subversion. (This will often get you > newer code, so do this if you want to make changes.) See the > Subversion instructions on " > and the link takes you to the generic sourceforge (sf) help about > subversion and at the bottom has a link for ""Subversion (Version > Control for Source Code)" at > http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion. Under > "Features" it lists Subversion clients. > >>From your email it looks like you are using Microsoft Windows. > So your choices are using TortoiseSVN or configuring Eclipse to use > Subversion. > > I would probably recommend Eclipse and Subversion, just to keep the > number of tools down. > Unfortunately someone completely new to the development process is > stuck at this point because there is not enough documentation. > So I'm just checking out the source onto my laptop to see what is in > there. > The generic colossus subversion page instructions say to use > svn co https://colossus.svn.sourceforge.net/svnroot/colossus > colossus > which is not correct as this will check out the trunk, branches and > tags. > You need > svn co https://colossus.svn.sourceforge.net/svnroot/colossus/trunk > colossus > If you use Eclipse it will catch this error and fix it for you. > > On the colossus developer page > http://sourceforge.net/projects/colossus/ you can browse the source > code at http://sourceforge.net/projects/colossus/ > Code > SVN Browse > and then find > > http://colossus.svn.sourceforge.net/viewvc/colossus/trunk/Colossus/docs/, > which unfortunately also doesn't have beginner level docs. > > So on to Eclipse > >> 1. Downloaded several versions of Apache Subversion. >> a) 1.7.5 from subversion.apache.org -- Source code only. I don't >> know how to >> build it (& the tools may not be there on Windows). >> b) WANdisco binary -- Not a client at all. Sets up a server >> without even asking >> if you want one. I uninstalled it and posted a WTF? on their >> message board. >> c) VisualSVN -- Has a command-line version of the client. After >> setting my PATH >> to enable the commands, I have successfully checked out the current >> trunk, >> placing it in >> C:\Programming\Colossus\work . >> >> 2. Downloaded and installed Eclipse. (Indigo Service Release 1, if >> it matters.) >> >> Eclipse starts up, but I have yet to get it to do anything useful. >> It is making >> obsolete assumptions about where I keep things on the system (mostly >> references >> to E:, a 1TB hard drive that lasted 8 months before biting the big >> one). >> >> I have downloaded the manual from red-bean.com, but haven't found >> anything about >> setting paths or config options. >> >> The obvious way to get it to show the code I've downloaded is >> File -> Switch Workspace >> on the menu. But when I do this, Eclipse shows some pop-up that >> disappears much >> too quickly to read a word of it, then exits and restarts itself in >> the same >> state it was in before. So Eclipse appears to be absolutely >> useless. >> >> Any suggestions on what to try next would be appreciated. > > I tend to recommend the Subversive plugin for Eclipse/Subversion > integration. > Subversive made it as an Eclipse project so it may have better > integration. > As Tim has pointed out you can also use TortoiseSVN instead. > I prefer the Eclipse integration as you can do patch creation etc all > in Eclipse. > > However for complete novices TortoiseSVN would be a better choice. > Working out how to install the Eclipse Plugin is a bit of a chore. > > TortoiseSVN is available here http://tortoisesvn.net/downloads.html > > Unfortunately I am on a Mac and I can't remember the steps. > Something like > * Create a folder where you want to develop Colossus > * Right click on the folder and there should be something like SVN > Checkout. > * Use https://colossus.svn.sourceforge.net/svnroot/colossus/trunk as > the SVN checkout URL > * Click Ok > After a short time you should have a directory with all the Colossus > source in it. > > As Tim points out, "workspace" is an Eclipse concept that keeps all > of > the settings for that workspace together as well as all the projects > you are working on. > This allows you to have multiple workspaces with different projects > and settings. > > We don't have a wiki installed, and while I normally love wikis, it > helps to have the docs kept with the source so there is more change > they will be kept in sync. This does leave the problem that the > initial instructions are not easily accessible, so we will need to > fix > that. > > With the Colossus Source checked out, start Eclipse. > As Tim points out specify the workspace directory as the same place > that Colossus was checked out. > For you that would be C:\Programming\Colossus\work > > In Eclipse select File > Import > General > Existing Projects into > Workspace > "Select root directory" = C:\Programming\Colossus\work > This will show two Projects; "Colossus", "Website" > > In the Colossus/docs directory are html pages. If you open them in > Eclipse the internal web browser will display them. > Start with index.html which will point you at other documentation. > build.html will give you the steps you need to rebuild your client > locally. > > > If you are able to document the steps you used that would benefit > other new people who come along. > As noted before, we have too many assumptions about what level of > detail is needed and what is assumed knowledge. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers |
|
From: Barrie T. <bae...@gm...> - 2012-07-08 04:41:15
|
On Sun, Jul 8, 2012 at 6:04 AM, John David Galt <jd...@di...> wrote: >> On Sun, Jul 1, 2012 at 1:56 AM, John David Galt wrote: >>> I have yet to manage to get the code to download and compile. ?It seems like >>> every time I make the effort, somebody changes the tools the project is using, >>> shutting me out again. > > On Sun, 1 Jul 2012 07:15:32 +0930, Barrie Treloar wrote: >> Then the documentation should be improved so that others don't get the >> same problem as you. It is always helpful to get fresh people on the >> project for exactly this reason, to make sure that the getting started >> documentation is correct. >> >> Try again and mail the list any problems that you have so that we can >> get them fixed. > > OK, thanks, I'll take you up on that. So far I have: So which instructions did you follow? http://colossus.sourceforge.net/ says in the Download section: "Or you can grab the code via Subversion. (This will often get you newer code, so do this if you want to make changes.) See the Subversion instructions on " and the link takes you to the generic sourceforge (sf) help about subversion and at the bottom has a link for ""Subversion (Version Control for Source Code)" at http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion. Under "Features" it lists Subversion clients. >From your email it looks like you are using Microsoft Windows. So your choices are using TortoiseSVN or configuring Eclipse to use Subversion. I would probably recommend Eclipse and Subversion, just to keep the number of tools down. Unfortunately someone completely new to the development process is stuck at this point because there is not enough documentation. So I'm just checking out the source onto my laptop to see what is in there. The generic colossus subversion page instructions say to use svn co https://colossus.svn.sourceforge.net/svnroot/colossus colossus which is not correct as this will check out the trunk, branches and tags. You need svn co https://colossus.svn.sourceforge.net/svnroot/colossus/trunk colossus If you use Eclipse it will catch this error and fix it for you. On the colossus developer page http://sourceforge.net/projects/colossus/ you can browse the source code at http://sourceforge.net/projects/colossus/ > Code > SVN Browse and then find http://colossus.svn.sourceforge.net/viewvc/colossus/trunk/Colossus/docs/, which unfortunately also doesn't have beginner level docs. So on to Eclipse > 1. Downloaded several versions of Apache Subversion. > a) 1.7.5 from subversion.apache.org -- Source code only. I don't know how to > build it (& the tools may not be there on Windows). > b) WANdisco binary -- Not a client at all. Sets up a server without even asking > if you want one. I uninstalled it and posted a WTF? on their message board. > c) VisualSVN -- Has a command-line version of the client. After setting my PATH > to enable the commands, I have successfully checked out the current trunk, > placing it in > C:\Programming\Colossus\work . > > 2. Downloaded and installed Eclipse. (Indigo Service Release 1, if it matters.) > > Eclipse starts up, but I have yet to get it to do anything useful. It is making > obsolete assumptions about where I keep things on the system (mostly references > to E:, a 1TB hard drive that lasted 8 months before biting the big one). > > I have downloaded the manual from red-bean.com, but haven't found anything about > setting paths or config options. > > The obvious way to get it to show the code I've downloaded is > File -> Switch Workspace > on the menu. But when I do this, Eclipse shows some pop-up that disappears much > too quickly to read a word of it, then exits and restarts itself in the same > state it was in before. So Eclipse appears to be absolutely useless. > > Any suggestions on what to try next would be appreciated. I tend to recommend the Subversive plugin for Eclipse/Subversion integration. Subversive made it as an Eclipse project so it may have better integration. As Tim has pointed out you can also use TortoiseSVN instead. I prefer the Eclipse integration as you can do patch creation etc all in Eclipse. However for complete novices TortoiseSVN would be a better choice. Working out how to install the Eclipse Plugin is a bit of a chore. TortoiseSVN is available here http://tortoisesvn.net/downloads.html Unfortunately I am on a Mac and I can't remember the steps. Something like * Create a folder where you want to develop Colossus * Right click on the folder and there should be something like SVN Checkout. * Use https://colossus.svn.sourceforge.net/svnroot/colossus/trunk as the SVN checkout URL * Click Ok After a short time you should have a directory with all the Colossus source in it. As Tim points out, "workspace" is an Eclipse concept that keeps all of the settings for that workspace together as well as all the projects you are working on. This allows you to have multiple workspaces with different projects and settings. We don't have a wiki installed, and while I normally love wikis, it helps to have the docs kept with the source so there is more change they will be kept in sync. This does leave the problem that the initial instructions are not easily accessible, so we will need to fix that. With the Colossus Source checked out, start Eclipse. As Tim points out specify the workspace directory as the same place that Colossus was checked out. For you that would be C:\Programming\Colossus\work In Eclipse select File > Import > General > Existing Projects into Workspace > "Select root directory" = C:\Programming\Colossus\work This will show two Projects; "Colossus", "Website" In the Colossus/docs directory are html pages. If you open them in Eclipse the internal web browser will display them. Start with index.html which will point you at other documentation. build.html will give you the steps you need to rebuild your client locally. If you are able to document the steps you used that would benefit other new people who come along. As noted before, we have too many assumptions about what level of detail is needed and what is assumed knowledge. |
|
From: Tim S. <ts...@ai...> - 2012-07-08 02:29:47
|
Hi John, I'm no expert by any means with Eclipse so I went through what you did a long time ago when I first got the source. SVN: I use Tortoise SVN because it's what we use at work. It's a very nice handy GUI based SVN client that works with the Colossus repository. No need to build anything to get it to work and no command line stuff. It doesn't auto-integrate into Eclipse but I doubt you care much about that since it has a nice GUI interface. I recommend it. Eclipse: I just double click on the Project file in the Colossus directory. That should open Eclipse and ask about a workspace. The fact it's pointing to an old Drive just means you once ran Eclipse before and stored the Eclipse Workspace there so it's remembering that from the registry. Just select a new directory for the workspace (I put mine directly in the Colossus source folder. Eclipse stores all its stuff in a .metadata folder so don't check that back into SVN). Once you do that you'll have a new workspace created for the Colossus source. At that point you should be able to edit, compile etc. Tim >> On Sun, Jul 1, 2012 at 1:56 AM, John David Galt wrote: >>> I have yet to manage to get the code to download and compile. ?It seems like >>> every time I make the effort, somebody changes the tools the project is using, >>> shutting me out again. > On Sun, 1 Jul 2012 07:15:32 +0930, Barrie Treloar wrote: >> Then the documentation should be improved so that others don't get the >> same problem as you. It is always helpful to get fresh people on the >> project for exactly this reason, to make sure that the getting started >> documentation is correct. >> >> Try again and mail the list any problems that you have so that we can >> get them fixed. > OK, thanks, I'll take you up on that. So far I have: > > 1. Downloaded several versions of Apache Subversion. > a) 1.7.5 from subversion.apache.org -- Source code only. I don't know how to > build it (& the tools may not be there on Windows). > b) WANdisco binary -- Not a client at all. Sets up a server without even asking > if you want one. I uninstalled it and posted a WTF? on their message board. > c) VisualSVN -- Has a command-line version of the client. After setting my PATH > to enable the commands, I have successfully checked out the current trunk, > placing it in > C:\Programming\Colossus\work . > > 2. Downloaded and installed Eclipse. (Indigo Service Release 1, if it matters.) > > Eclipse starts up, but I have yet to get it to do anything useful. It is making > obsolete assumptions about where I keep things on the system (mostly references > to E:, a 1TB hard drive that lasted 8 months before biting the big one). > > I have downloaded the manual from red-bean.com, but haven't found anything about > setting paths or config options. > > The obvious way to get it to show the code I've downloaded is > File -> Switch Workspace > on the menu. But when I do this, Eclipse shows some pop-up that disappears much > too quickly to read a word of it, then exits and restarts itself in the same > state it was in before. So Eclipse appears to be absolutely useless. > > Any suggestions on what to try next would be appreciated. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Colossus-developers mailing list > Col...@li... > https://lists.sourceforge.net/lists/listinfo/colossus-developers > |
|
From: John D. G. <jd...@di...> - 2012-07-07 20:35:05
|
> On Sun, Jul 1, 2012 at 1:56 AM, John David Galt wrote: >> I have yet to manage to get the code to download and compile. ?It seems like >> every time I make the effort, somebody changes the tools the project is using, >> shutting me out again. On Sun, 1 Jul 2012 07:15:32 +0930, Barrie Treloar wrote: > Then the documentation should be improved so that others don't get the > same problem as you. It is always helpful to get fresh people on the > project for exactly this reason, to make sure that the getting started > documentation is correct. > > Try again and mail the list any problems that you have so that we can > get them fixed. OK, thanks, I'll take you up on that. So far I have: 1. Downloaded several versions of Apache Subversion. a) 1.7.5 from subversion.apache.org -- Source code only. I don't know how to build it (& the tools may not be there on Windows). b) WANdisco binary -- Not a client at all. Sets up a server without even asking if you want one. I uninstalled it and posted a WTF? on their message board. c) VisualSVN -- Has a command-line version of the client. After setting my PATH to enable the commands, I have successfully checked out the current trunk, placing it in C:\Programming\Colossus\work . 2. Downloaded and installed Eclipse. (Indigo Service Release 1, if it matters.) Eclipse starts up, but I have yet to get it to do anything useful. It is making obsolete assumptions about where I keep things on the system (mostly references to E:, a 1TB hard drive that lasted 8 months before biting the big one). I have downloaded the manual from red-bean.com, but haven't found anything about setting paths or config options. The obvious way to get it to show the code I've downloaded is File -> Switch Workspace on the menu. But when I do this, Eclipse shows some pop-up that disappears much too quickly to read a word of it, then exits and restarts itself in the same state it was in before. So Eclipse appears to be absolutely useless. Any suggestions on what to try next would be appreciated. |
|
From: Barrie T. <bae...@gm...> - 2012-07-04 00:28:08
|
On Wed, Jul 4, 2012 at 7:57 AM, David Ripton <dr...@ri...> wrote: > On 07/03/2012 01:06 PM, Clemens wrote: >> >> We have basically only wiki pages. Let's see it as an opportunity to >> consolidate our scattered documentation bits & pieces :) > > I'm pretty happy with Github for wiki pages, if you're looking for a new > free place to host them. And github support markdown (and I think a few other formats, not really looked) so that it can take your raw pages and convert them to html for people to view. |
|
From: David R. <dr...@ri...> - 2012-07-03 22:45:30
|
On 07/03/2012 01:06 PM, Clemens wrote: > > We have basically only wiki pages. Let's see it as an opportunity to > consolidate our scattered documentation bits & pieces :) I'm pretty happy with Github for wiki pages, if you're looking for a new free place to host them. -- David Ripton dr...@ri... |
|
From: Clemens <cl...@cl...> - 2012-07-03 17:06:32
|
We have basically only wiki pages. Let's see it as an opportunity to consolidate our scattered documentation bits & pieces :) On 2012-07-03 18:37, Bruno Wolff III wrote: > On Tue, Jul 03, 2012 at 17:25:49 +0200, > Clemens Katzer <lem...@sa...> wrote: >>Hello all, >> >>for everybody's information, the Hosted Apps feature will be removed >> in Sourceforge. >>As far as I see it, in Colossus this affects only our wiki page. > > I saw discussion about that for the smartmontools project. They are > looking at options for hosting their trac instance somewhere else. |
26 messages has been excluded from this view by a project administrator.