Disruption Simple Content Manager - Revision history

Esr: Hide historical references to "SVN" from the wiki search function

2013-03-21T03:45:59Z

Hide historical references to "SVN" from the wiki search function

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T03:01:59Z

Hide historical references to Subversion from the wiki search function

Disruption: /* Application GUI Mockup */

2011-04-17T13:10:54Z

‎Application GUI Mockup

Disruption: /* Timeline */

2011-04-11T19:12:27Z

‎Timeline

Disruption: /* Timeline */

2011-04-11T18:21:20Z

‎Timeline

Disruption: /* Timeline */

2011-04-11T18:19:33Z

‎Timeline

Disruption: /* Timeline */

2011-04-11T18:19:02Z

‎Timeline

Disruption: /* Timeline */

2011-04-11T18:18:15Z

‎Timeline

Disruption at 18:03, 11 April 2011

2011-04-11T18:03:09Z

Disruption: /* Application GUI Mockup */

2011-04-09T23:20:42Z

‎Application GUI Mockup

@@ Line 81: / Line 81: @@
 =Application Brief and Workflow=
-Brief: The SMC will give users an easy-to-use program for checkout,update and commit operations, without requiring any SVN knowledge at all.
+Brief: The SMC will give users an easy-to-use program for checkout,update and commit operations, without requiring any S&shy;&shy;V&shy;&shy;N knowledge at all.
 Workflow:
@@ Line 134: / Line 134: @@
 thespaceinvader: hrm...
-thespaceinvader: the major operations would be checkout and update, for me.  I rarely use any other SVN operations
+thespaceinvader: the major operations would be checkout and update, for me.  I rarely use any other S&shy;&shy;V&shy;&shy;N operations
 thespaceinvader: solving conflicting merges would be useful, too
@@ Line 163: / Line 163: @@
 | 23 May || 30 May || Design SCM GUI and prepare Java framework || Compulsory<br/>
 |-
-| 31 May || 13 June|| Implementation of SVN support for the SCM || Compulsory<br/>
+| 31 May || 13 June|| Implementation of S&shy;&shy;V&shy;&shy;N support for the SCM || Compulsory<br/>
 |-
 | 14 June || 16 June || Time Buffer || Optional<br/>
@@ Line 227: / Line 227: @@
 :2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.
 I played Battle for Wesnoth when it was around version 1.24. I really enjoyed playing it, but due to my university studies being a bit overwhelming I had to stop playing. I loved both single and multiplayer modes, but at the moment I played multiplayer was very buggy(Connection was lost regularly, and multiplayer failed suddenly) so it was difficult to finish a game, and it ended up being somehow frustrating.
-:2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.
+:2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.
 Info about submitted patches can be found in a specific section in this wiki page.
 ) Communication skills
@@ Line 270: / Line 270: @@
 :5.1) Are you familiar with any of the following tools or languages?
 * Sub&shy;&shy;version (used for all commits)
-I have used SVN in a lot of projects
+I have used S&shy;&shy;V&shy;&shy;N in a lot of projects
 * C++ (language used for all the normal source code)
 I have a lot of experience developing in C/C++

@@ Line 269: / Line 269: @@
 ) Practical considerations
 :5.1) Are you familiar with any of the following tools or languages?
-* Subversion (used for all commits)
+* Sub&shy;&shy;version (used for all commits)
 I have used SVN in a lot of projects
 * C++ (language used for all the normal source code)

← Older revision		Revision as of 13:10, 17 April 2011
Line 72:		Line 72:

	The gui mockup .jar can be downloaded from: http://www.programarte.org/guimockup/StandardJar.jar		The gui mockup .jar can be downloaded from: http://www.programarte.org/guimockup/StandardJar.jar
		+
		+	The gui mockup source code project(For JDeveloper) can be downloaded from: http://programarte.org/guimockup/SCM.rar
		+	Even though the project is for JDeveloper, it contains normal .java files, so you should be able to explore the code from any interface, or directly using text editors like gedit, wordpad, text wrangler...

	The file explorer used for the mockup is a very inefficient version, so the .jar should be executed inside a directory with little content(That is, only a few folders or subfolders), as the file explorer goes recursively from the folder the .jar is placed getting as deep as possible and obtaining the full directory structure below the .jar(That is, if you place the .jar inside your main checkout directory, the file explorer will show Wesnoth's trunk content, although it will take a few seconds to load(I just tested it)).		The file explorer used for the mockup is a very inefficient version, so the .jar should be executed inside a directory with little content(That is, only a few folders or subfolders), as the file explorer goes recursively from the folder the .jar is placed getting as deep as possible and obtaining the full directory structure below the .jar(That is, if you place the .jar inside your main checkout directory, the file explorer will show Wesnoth's trunk content, although it will take a few seconds to load(I just tested it)).

@@ Line 154: / Line 154: @@
 {| border="1"
-| From || To || Description<br/>
+| From || To || Description || Type<br/>
 |-
-| 23 May || 22 August|| Full Project Duration<br/>
+| 23 May || 22 August|| Full Project Duration || Compulsory<br/>
 |-
-| 23 May || 30 May || Design SCM GUI and prepare Java framework<br/>
+| 23 May || 30 May || Design SCM GUI and prepare Java framework || Compulsory<br/>
 |-
-| 31 May || 13 June|| Implementation of SVN support for the SCM<br/>
+| 31 May || 13 June|| Implementation of SVN support for the SCM || Compulsory<br/>
 |-
-| 14 June || 16 June || Time Buffer<br/>
+| 14 June || 16 June || Time Buffer || Optional<br/>
 |-
-| 17 June || 17 June || GUI callback configuration and set up<br/>
+| 17 June || 17 June || GUI callback configuration and set up || Compulsory<br/>
 |-
-| 18 June || 18 June || Set up windows implementation<br/>
+| 18 June || 18 June || Set up windows implementation || Compulsory<br/>
 |-
-| 19 June || 30 June || Checkout operation implementation with conflict resolution<br/>
+| 19 June || 30 June || Checkout operation implementation with conflict resolution || Compulsory<br/>
 |-
-| 1 July || 11 July || Update operation implementation with conflict resolution<br/>
+| 1 July || 11 July || Update operation implementation with conflict resolution || Compulsory<br/>
 |-
-| 12 July || 22 July || Commit Operation implementation<br/>
+| 12 July || 22 July || Commit Operation implementation || Compulsory<br/>
 |-
-| 23 July || 25 July || Time Buffer <br/>
+| 23 July || 25 July || Time Buffer || Optional<br/>
 |-
-| 26 July || 11 August || Implementation of GIT support for the SCM<br/>
+| 26 July || 11 August || Implementation of GIT support for the SCM || Optional<br/>
 |-
-| 12 August || 14 August || Time Buffer <br/>
+| 12 August || 14 August || Time Buffer || Optional<br/>
 |-
-| 15 August || 22 August || Final testing and polishing<br/>
+| 15 August || 22 August || Final testing and polishing || Compulsory<br/>
 |}
 =Questionnaire=

@@ Line 170: / Line 170: @@
 | 19 June || 30 June || Checkout operation implementation with conflict resolution<br/>
 |-
-| 1 July || 12 July || Update operation implementation with conflict resolution<br/>
+| 1 July || 11 July || Update operation implementation with conflict resolution<br/>
 |-
-| 13 July || 24 July || Commit Operation implementation<br/>
+| 12 July || 22 July || Commit Operation implementation<br/>
 |-
-| 25 July || 15 August || Implementation of GIT support for the SCM<br/>
+| 23 July || 25 July || Time Buffer <br/>
 |-
 | 15 August || 22 August || Final testing and polishing<br/>

@@ Line 151: / Line 151: @@
 Disruption: thanks for your feedback :)
-== Timeline ==
+= Timeline =
 {| border="1"
-| From|| To || Description<br/>
+| From || To || Description<br/>
 |}
 =Questionnaire=

← Older revision		Revision as of 18:03, 11 April 2011
Line 150:		Line 150:

	Disruption: thanks for your feedback :)		Disruption: thanks for your feedback :)
		+
		+	== Timeline ==
		+
		+	{\| border="1"
		+	\| From\|\| To \|\| Description<br/>
		+	\|}
		+

	=Questionnaire=		=Questionnaire=

@@ Line 31: / Line 31: @@
 ==Main Window==
-Window seen when the application is open
+Window seen when the application is open.The main window offers 3 main options, checkout, update, and commit, that are the general options available for any versioning system. It also has a menu bar, with tabs for the configuration options.
 http://www.programarte.org/guimockup/main.png
 ==Configuration Windows==
@@ Line 70: / Line 68: @@
 http://www.programarte.org/guimockup/commitLastPhase.png
 =Application Brief and Workflow=