Difference between revisions of "Education ClassRoom/Practice"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 27: Line 27:
 
* Visualize changes in a cws
 
* Visualize changes in a cws
 
1) Go to http://bonsai.go-oo.org/cvsqueryform.cgi
 
1) Go to http://bonsai.go-oo.org/cvsqueryform.cgi
[We'll try to do a request :)
+
 
 +
We'll try to do a request :)
 +
 
 
2) Don't modify Module (must be All files in the repository ) Remark : note the name "repository "
 
2) Don't modify Module (must be All files in the repository ) Remark : note the name "repository "
 +
 
3) In the Field "Branch" replace HEAD with cws_dev300_aquavcl07
 
3) In the Field "Branch" replace HEAD with cws_dev300_aquavcl07
 +
 
4) in the field "Date" check "Since the beginning of time "
 
4) in the field "Date" check "Since the beginning of time "
 +
 
5) do not modify the other fields
 
5) do not modify the other fields
 +
 
6) Click "Run Query"
 
6) Click "Run Query"
 +
 
=> all the changes in the code, based on DEV300_m9 ( we'll explain later) are on the page !!
 
=> all the changes in the code, based on DEV300_m9 ( we'll explain later) are on the page !!
 +
 
7) To see the diff for any commit, click in the Rev. columns. Back to retrieve the current page.
 
7) To see the diff for any commit, click in the Rev. columns. Back to retrieve the current page.
 +
 
Strongly advised : 8) Look carefully at other changes, what information you can obtain here.
 
Strongly advised : 8) Look carefully at other changes, what information you can obtain here.
 +
 
Remark: Bonsai helps when you are searching for changes in the code, author date .. precise information about CODE
 
Remark: Bonsai helps when you are searching for changes in the code, author date .. precise information about CODE
  
 
=== LXR use ===  
 
=== LXR use ===  
  
 +
[Complete me]
  
 
=== Checkout the code  
 
=== Checkout the code  
Line 45: Line 56:
  
 
Preliminary:
 
Preliminary:
 +
 
- we suppose you have some bash knowledge, and some programming skills
 
- we suppose you have some bash knowledge, and some programming skills
 +
 
- your .cvsrc file is ok (else ask on #education.openoffice.org )
 
- your .cvsrc file is ok (else ask on #education.openoffice.org )
 +
 
Now, open a terminal, use bash, and do :
 
Now, open a terminal, use bash, and do :
 +
 
0 ) create the environment
 
0 ) create the environment
 +
 
what follows are command lines
 
what follows are command lines
 +
 
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
 
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
 +
 
create TMP dir (command: mkdir TMP )
 
create TMP dir (command: mkdir TMP )
 +
 
cd TMP
 
cd TMP
 +
 
1) checkout vcl module from DEV300_m11
 
1) checkout vcl module from DEV300_m11
 +
 
cvs co -r DEV300_m11 dtrans
 
cvs co -r DEV300_m11 dtrans
 +
 
Question: what happens ?
 
Question: what happens ?
 +
 
[2) Modify one file, do "cvs up" , and comment on the result
 
[2) Modify one file, do "cvs up" , and comment on the result
 +
 
[3) using grep , retrieve the name of the milestone in the sources
 
[3) using grep , retrieve the name of the milestone in the sources
 +
 
4) checkout vcl from a cws under development
 
4) checkout vcl from a cws under development
 +
 
cvs -z4 co -r cws_dev300_aquavcl07 vcl
 
cvs -z4 co -r cws_dev300_aquavcl07 vcl
 +
 
5) retrieve the cwsname in the sources
 
5) retrieve the cwsname in the sources
 +
 
6) analyse the list of the subdirectories vcl contains
 
6) analyse the list of the subdirectories vcl contains
 +
 
7) modify the code in vcl/source/gdi/sallayout.cxx
 
7) modify the code in vcl/source/gdi/sallayout.cxx
 +
 
(write whatever you want, respecting C++ syntax prefered ;)
 
(write whatever you want, respecting C++ syntax prefered ;)
 +
 
8) create a diff with the OpenOffice.org repository
 
8) create a diff with the OpenOffice.org repository
 +
 
change directory outside of vcl
 
change directory outside of vcl
 +
 
[in the current dir ( TMP ) , do :
 
[in the current dir ( TMP ) , do :
 +
 
cvs diff -u vcl > my_pretty_patch.diff
 
cvs diff -u vcl > my_pretty_patch.diff
 +
 
9) What does contain the patch ?
 
9) What does contain the patch ?
 +
 
10) How reverse your changes ?
 
10) How reverse your changes ?
 +
 
11) Be sure you have enough place on your hard disk ( count 2GB )
 
11) Be sure you have enough place on your hard disk ( count 2GB )
 +
 
Download all OpenOffice.org tree :
 
Download all OpenOffice.org tree :
 +
 
mkdir DEV300_m11
 
mkdir DEV300_m11
 +
 
cd DEV300_m11
 
cd DEV300_m11
 +
 
cvs -4 co -r DEV300_m11 OpenOffice3 swext tomcat apache-commons
 
cvs -4 co -r DEV300_m11 OpenOffice3 swext tomcat apache-commons
 +
 
( -z4 is optional )
 
( -z4 is optional )
 +
 
-> once done ( can be very long), and if no error occurs, you got all OpenOffice.org source code from DEV300_m11 Milestone !!
 
-> once done ( can be very long), and if no error occurs, you got all OpenOffice.org source code from DEV300_m11 Milestone !!

Revision as of 15:36, 7 May 2008

Draft

Objective : create exercices, to practice OpenOffice.org tools used for development

TODO : define a list of items

Join the Project

Login and accounts

Find a page or a document

  • Find the web page for your own locale in OpenOffice.org project ( e.g. nl.openoffice.org )
  • Find the OpenOffice.org Coding Guidelines on the Wiki ( and read it ... )
  • Find the page about cws ( Child Workspace )
  • Find dev@gsl.openoffice.org mailing list archive
  • Subscribe to dev@education.openoffice.org mailing list if you didn't yet
  • Extract mails 10 to 14 from any mailing list


Bonsai use

  • Discover Bonsai
  • Visualize changes in a cws

1) Go to http://bonsai.go-oo.org/cvsqueryform.cgi

We'll try to do a request :)

2) Don't modify Module (must be All files in the repository ) Remark : note the name "repository "

3) In the Field "Branch" replace HEAD with cws_dev300_aquavcl07

4) in the field "Date" check "Since the beginning of time "

5) do not modify the other fields

6) Click "Run Query"

=> all the changes in the code, based on DEV300_m9 ( we'll explain later) are on the page !!

7) To see the diff for any commit, click in the Rev. columns. Back to retrieve the current page.

Strongly advised : 8) Look carefully at other changes, what information you can obtain here.

Remark: Bonsai helps when you are searching for changes in the code, author date .. precise information about CODE

LXR use

[Complete me]

=== Checkout the code


Preliminary:

- we suppose you have some bash knowledge, and some programming skills

- your .cvsrc file is ok (else ask on #education.openoffice.org )

Now, open a terminal, use bash, and do :

0 ) create the environment

what follows are command lines

export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"

create TMP dir (command: mkdir TMP )

cd TMP

1) checkout vcl module from DEV300_m11

cvs co -r DEV300_m11 dtrans

Question: what happens ?

[2) Modify one file, do "cvs up" , and comment on the result

[3) using grep , retrieve the name of the milestone in the sources

4) checkout vcl from a cws under development

cvs -z4 co -r cws_dev300_aquavcl07 vcl

5) retrieve the cwsname in the sources

6) analyse the list of the subdirectories vcl contains

7) modify the code in vcl/source/gdi/sallayout.cxx

(write whatever you want, respecting C++ syntax prefered ;)

8) create a diff with the OpenOffice.org repository

change directory outside of vcl

[in the current dir ( TMP ) , do :

cvs diff -u vcl > my_pretty_patch.diff

9) What does contain the patch ?

10) How reverse your changes ?

11) Be sure you have enough place on your hard disk ( count 2GB )

Download all OpenOffice.org tree :

mkdir DEV300_m11

cd DEV300_m11

cvs -4 co -r DEV300_m11 OpenOffice3 swext tomcat apache-commons

( -z4 is optional )

-> once done ( can be very long), and if no error occurs, you got all OpenOffice.org source code from DEV300_m11 Milestone !!

Personal tools