User:JamesPoulson

Progress
 * Mercredi 2 Mars: Installation de l'environnement de compilation sous Windows et préparatifs pour avoir accès à un Linux.
 * Lundi 7 Mars: Transfert de fichiers sur un disque externe pour enfin installer un Linux.
 * Mardi 8 Mars: Checkout du code source à partir du SVN après insuccès le Lundi. Début de la documentation.

2011-03-08
Currently exploring classes. I have decided to start with PresenterScreen (PresenterScreen.cxx) and PresenterViewFactory (PresenterViewFactory.cxx).

(Removed as doxygen is more practical than doing this by hand)

2011-03-09
Really need to make progress this week. Will ask someone on the IRC Channel what approaches I can use to document the code.

2011-03-10
Ok. Time to make some progress as I have a breather. As Eric has said it is important to work regularly on the project. Will add notes later on today.

Update: Eric reminded me to use doxygen. I have run it on the source files and it definitely gives a better overview. What I should do is add comments as I attempt to understand what role each class has. He also mentionned UNO which I suppose is a version of C++. The following appears to be a relevant link:

http://udk.openoffice.org/cpp/man/tutorial/unointro.html


 * SAL stands for System abstraction layer.
 * IDL stands for Interactive Data Language.

Edit: This link is good for having an idea what the Presenter Screen is about: http://wiki.services.openoffice.org/wiki/Presenter_Screen

2011-03-14
Some things to look up after chatting on IRC with Eric.

Notions:
 * UNO => atomic interface allowing one to construct objects you want and use them in various programming languages.
 * Canvas => most likely what is used for basic drawing to the screen).
 * udk.
 * Bean interface.
 * Boost.
 * VCL => Some sort of graphics library with components.
 * awt => Graphical library.

Links:
 * http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Introduction
 * http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/C%2B%2B/C%2B%2B_Language_Binding
 * http://wiki.services.openoffice.org/wiki/FR/Documentation/L%27automation_d%27OpenOffice.org_avec_un_binaire_ex%C3%A9cutable
 * http://wiki.services.openoffice.org/wiki/Documentation/FR/Cpp_Guide
 * http://eric.bachard.free.fr/Education/ECN/EducationEffort/reports/ => Explanation of how the overlay is used.
 * http://wiki.services.openoffice.org/wiki/User:Ericb#Sort_of_documentation_about_VCL_around_Native_Mac_OS_X_port

2011-03-18
Haven't had much time these last few days. Need to reorganize this weekend. Sylvain has given me access to clocking IT, a web application for managing projects.


 * http://www.clockingit.com/

2011-03-22
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Introduction

Notes:
 * UNO = Universal Network Objects.
 * UNO objects written in UNO Interface Definition Language abstract meta language.
 * Component: UNO objects in library form using base interface (find more info on this).
 * Instantiation done using Factory pattern and called Service Manager => acts as a registry for components.
 * Service Manager acts transparently on shared objects written in different languages.
 * Communication is done using interface calls.
 * Use of bridges with UNO remote protocol.
 * The specification for the programmable features of OpenOffice.org is called the OpenOffice.org API.

Presenter Screen (sdext\source\presenter)


 * bitmaps [dir] Most likely contains bitmap images which are displayed when the presenter screen is activated. Find out how these are placed/drawn?
 * sdext\source\presenter\registry\schema\org\openoffice\Office\extension Looks like a definitions or properties file. Definitely xml.
 * To be continued.