Current [[center|BB Center]] Chair:

'''Robert D Campbell'''

Begun: 1 July 2017

==ExChairs==

'''Robert D Campbel'''

Begun: 1 January 2017

----

'''Douglas G Danforth'''

Begun: Jul 2nd, 2016

----

'''Ivan Denisov'''

Begun: Jan 1st, 2016

----

'''Helmut Zinn'''

Begun: Jul 1st, 2015

----

'''Josef Templ'''

Begun: Jan 1st, 2015

Charter: Maintain stability and quality of BlackBox/Component Pascal.

Goal: Continue working on the 1.7 release based on the changes introduced in Helmut Zinn's CPC 1.7 rc4 plus additional requests that may show up.

Subgoal: Maintain backwards compatibility whenever possible.

----

'''Douglas G Danforth'''

Begun: Aug 27(29), 2014

Charter: Maintain stability and quality of BlackBox/Component Pascal.

Goal: Expand the use of BlackBox and complete the design of operating system independence.

Subgoal: Generate revenue by software development and consulting.

----

'''Rene Krywult'''

Begun: Jan 1st, 2014

2017-03-06T13:59:40Z

Robert:

This page describes how to update the Git master branch with the changes in an alternative branch.

This task should be conducted by the Center Chair after a vote has approved the proposed changes.

== Close the issue ==

Go to
https://redmine.blackboxframework.org/projects/blackbox/issues
Alternatively:
Go to the Center page: https://forum.blackboxframework.org
Click on the top level yellow option "Redmine mirror"
Click on the "Issues" tab.

Click on the issue. You can use either the number "#" or the "Subject" in the list of issues.

You now need to be logged in.

Select the "Edit" option (upper right hand corner).

Change the "Status" to "Closed".

"Submit" to apply the change; this button is in the bottom-left corner.

Exit redmine.

== Merge the Branch ==

Go to GitHub
https://github.com/BlackBoxCenter/blackbox
Alternatively:
Go to the Center page: https://forum.blackboxframework.org
Click on the top level yellow option "Github repository"
Click on the large blue "blackbox" text in the center of the page.

Use the drop-down on the left of the page "Branch: master ▼" to select the required branch.
The branch is identified by its issue number.

Press "New pull request" button just to the right of the previous drop-down.

Click the large green "Create pull request" button.

Click the large green "Merge pull request" button.
This assumes there were no "conflicts with the base branch".

Click the large green "Confirm merge" button.

You should now have a box that says "Pull request successfully merged and closed".
In this box click the "Delete branch" button.

== Check the new build ==

This should be the end of the task.

You can confirm the master has been updated successfully by going to:
http://blackboxframework.org/unstable/master/
I find this as below; there may be a more direct route:
Go to the Center page: https://forum.blackboxframework.org
Click on the top level yellow option "Main page"
Click on "Goto Download page" (bottom of top-left region).
Click on "A repository of all Center development versions is available".
Click on the "master/" directory.

Check the date / time of the latest master.
It may take a few minutes before the new master is available.

Main Page

2017-03-06T10:22:33Z

Robert: Link to "Updating the Git master branch"

This Wiki is for documentation of [[BlackBox Component Builder]] and for building it's knowledge base.

BlackBox is available from the BlackBox Framework Center [http://blackboxframework.org/index.php?cID=goto-download-page,en-us Download page].

Also this wiki is used for [[center|BlackBox Сenter]].

== Urgent pages ==

* [[Center Members Admin Guide]]
* [[Bug fixing pipeline]]
* [[How to develop with Git]]
* [[How to develop with Tortoise Git]]
* [[BlackBox Versioning Strategy|The BlackBox Versioning Strategy]]
* [[The BlackBox Build Engine]]
* [[Localizing BlackBox]]
* [[Running BlackBox under Linux]]

== Technical notes ==

* [[Diff|Setting up a diff viewer for BlackBox .odc binary files]]
* [[H2O|Generation of import modules from C-headers]]
* [[Git|Git Gui Instructions]]
* [[Console|Low-level logging to Console]]
* [[ModuleUnloading|On Module Unloading in BlackBox]]
* [[Updating the Git master branch]]

== Links ==

* [http://blackboxframework.org/ Main website]
* [http://forum.blackboxframework.org Center Forum]
* [http://github.com/BlackBoxCenter Public repository and issues tracker]
* [http://redmine.blackboxframework.org/projects/blackbox Center project and issues tracker]

Updating the Git master branch

2017-03-06T10:20:53Z

Robert: Created page with "This page describes how to update the Git master branch with the changes in an alternative branch. This task should be conducted by the Center Chair after a vote has approved..."

User:Robert

2017-03-06T10:16:20Z

Robert: Created page with "Updating the Git master branch"

[[Updating the Git master branch]]

Chair

2017-01-27T10:56:42Z

Robert:

Current [[center|BB Center]] Chair:

'''Robert D Campbell'''

Begun: 1 January 2017

==ExChairs==

'''Douglas G Danforth'''

Begun: Jul 2nd, 2016

----

'''Ivan Denisov'''

Begun: Jan 1st, 2016

----

'''Helmut Zinn'''

Begun: Jul 1st, 2015

----

'''Josef Templ'''

Begun: Jan 1st, 2015

Charter: Maintain stability and quality of BlackBox/Component Pascal.

Goal: Continue working on the 1.7 release based on the changes introduced in Helmut Zinn's CPC 1.7 rc4 plus additional requests that may show up.

Subgoal: Maintain backwards compatibility whenever possible.

----

'''Douglas G Danforth'''

Begun: Aug 27(29), 2014

Charter: Maintain stability and quality of BlackBox/Component Pascal.

Goal: Expand the use of BlackBox and complete the design of operating system independence.

Subgoal: Generate revenue by software development and consulting.

----

'''Rene Krywult'''

Begun: Jan 1st, 2014

Main Page

2016-12-16T13:07:34Z

Robert:

This Wiki is for documentation of [[BlackBox Component Builder]] and for building it's knowledge base.

BlackBox is available from the BlackBox Framework Center [http://blackboxframework.org/index.php?cID=goto-download-page,en-us Download page].

Also this wiki is used for [[center|BlackBox Сenter]].

== Urgent pages ==

* [[Center Members Admin Guide]]
* [[Bug fixing pipeline]]
* [[How to develop with Git]]
* [[How to develop with Tortoise Git]]
* [[BlackBox Versioning Strategy|The BlackBox Versioning Strategy]]
* [[The BlackBox Build Engine]]
* [[Localizing BlackBox]]
* [[Running BlackBox under Linux]]

== Technical notes ==

* [[Diff|Setting up a diff viewer for BlackBox .odc binary files]]
* [[H2O|Generation of import modules from C-headers]]
* [[Git|Git Gui Instructions]]
* [[Console|Low-level logging to Console]]
* [[ModuleUnloading|On Module Unloading in BlackBox]]

== Links ==

* [http://blackboxframework.org/ Main website]
* [http://forum.blackboxframework.org Center Forum]
* [http://github.com/BlackBoxCenter Public repository and issues tracker]
* [http://redmine.blackboxframework.org/projects/blackbox Center project and issues tracker]

BlackBox Component Builder

2016-12-16T12:55:26Z

Robert: /* Downloads */

'''BlackBox Component Builder''' is an integrated development environment optimized for component-based software development. It consists of development tools, a library of reusable components, a framework that simplifies the development of robust custom components and applications, and a run-time environment for components.

In BlackBox, the development of applications and their components is done in [[Component Pascal]]. This language is a descendant of Pascal, Modula-2, and Oberon. It provides modern features such as objects, full type safety, components (in the form of modules), dynamic linking of components, and garbage collection. The entire BlackBox Component Builder is written in Component Pascal: all library components, all development tools including the Component Pascal compiler, and even the low-level run-time system with its garbage collector.

As its name implies, BlackBox Component Builder supports blackbox abstractions and reuse as opposed to whitebox as defined in <ref>Szyperski, Clemens. ''Component Software''. Addison Wesley, 2002, p. 40f and Chap.7 (p. 109ff)</ref>. It started 1993 as Oberon/F<ref>http://www.edm2.com/0608/oberon.html</ref><ref>D. Pountain, The Oberon/F System, ''BYTE'' 20(1), Jan. 1995.</ref> and was renamed to BlackBox Component Builder with Release 1.3 end of the 1990s. BlackBox Component Builder went open source with Release 1.5 mid-2004.

The design principles of the BlackBox Component Framework are based on Clemens Szyperski's research, published in his PhD thesis <ref>Szyperski, Clemens. ''Insight ETHOS: On Object Orientation in Operating Systems''. PhD thesis: Swiss Federal Institute of Technology (ETH Zurich), Dissertation No 9884. vdf Hochschulverlag AG an der ETH Zürich, Zurich, Switzerland, ISBN 3-7281-1948-2, 1992, [http://e-collection.library.ethz.ch/eserv/eth:38713/eth-38713-02.pdf PDF in ETHZ E-Collection]</ref><ref>Clemens Szyperski's [https://groups.google.com/forum/#!search/Clemens$20Szyperski/comp.lang.oberon/M-y1bJwEYE8/VIiedaFfIfIJ post in c.l.o.]</ref>.

== Downloads ==

BlackBox is available from the BlackBox Framework Center [http://blackboxframework.org/index.php?cID=goto-download-page,en-us Download page].

Also see [[BlackBox_Component_Builder_1.7|Some notes about migration from 1.6 to 1.7]]

== References ==

<references></references>

== External links ==
*[http://www.oberon.ch/BlackBox.html Official site]
*[http://userserv.reutlingen-university.de/~hug/buch/cf.htm An introductory text using BlackBox: Stan Warford - Computing Fundamentals]
*[http://www.zinnamturm.eu/ Tools and Utilities for BlackBox]

How to develop with Tortoise Git

2016-11-07T15:32:28Z

Robert: /* Committing changes, etc. */

If you work under Windows and if you do not want to learn the git command line tools there is an option, use Tortoise Git. Tortoise Git is a powerful GUI based git tool that is integrated nicely with the Windows Explorer. It is known to work reliably and it offers all the git functionality without forcing you to use or learn all of it. It is also easy to install a diff tool for BlackBox .odc files for Tortoise Git. Without a diff tool, it is not possible to use git effectively.

== Installation ==

The first step is to install Git, which is available from https://git-scm.com/. During the install process it is acceptable to take default choices.

The next step is to download and install Tortoise Git for Windows, which is a graphical front-end for Git. This is available from https://tortoisegit.org/download/. This is only done once. See [[Diff]] for setting up a diff tool for BlackBox .odc files.

== Cloning a repository ==

Git always works on a local repository and so does Tortoise Git. For getting a local repository you must first clone the remote github repository to your local machine.

* Click '''Mouse-Right''' on a directory that does not already contain a .git folder and activate the "Git Clone ..." menu item.

* fill in the form: '''URL''': https://github.com/BlackBoxCenter/blackbox.git
* '''Directory''': a default is presented. It is recommended to append the issue number. This helps a lot to stay organized in particular if you want to work on several issues in parallel. You can also add a mnemonic. An example directory for issue-#140 is "<path>\blackbox#140 unwrap".
* '''Branch''': Check this option and specify the branch name in the field to its right. This is the branch name in the github repository, for example "issue-#140". If the branch does not yet exist, you have to create the branch first on github (see [[How to develop with Git]] for instructions.). Note: Without checking the "Branch" option the cloned repository would be working on "master". This bears the danger that changes can easily and unintentionally be pushed back to master rather than to an issue branch. Therefore, never clone the "master" branch.

* Press "'''OK'''".

== Running BlackBox with the clone==

The cloned directory contains only the sources and resources of BlackBox. It does not contain any binaries. Therefore, after the clone has been created, you must set up an existing BlackBox installation to /USE the clone. This can be done by creating a link to the BlackBox.exe file and editing the properties manually or, more efficiently, by copying a prepared batch file into the clone's root directory. The batch file can be reused for several such directories. The contents of the batch file is:

<nowiki>start /b C:\"Program Files"\"BlackBox Component Builder 1.7"\BlackBox.exe /USE .</nowiki>

You may have to adapt the path, though, and you can add more options, e.g. /NOSCROLL.

Give the batch file (plain ANSI from a simple editor like Notepad) a name like "Run.bat", and save it into the Git path (eg <path>\blackbox#140 unwrap) where it is run by double clicking it.

== Committing changes, etc. ==

After starting the link or the batch file, BlackBox will store any changes into the cloned repository. You can commit the changes by means of the context menus offered by Tortoise Git. Mouse-Right on a folder or file shows an extended Windows context menu and allows you to see a log, a diff, or to commit changes (look also into submenus). The Commit command button can be found on the bottom line of the "TortoiseGit -> Diff", "TortoiseGit -> Diff with previous version", and "TortoiseGit -> Check for modifications" dialogs. When committing changes follow the conventions for the first line of the commit message as specified in [[How to develop with Git#Bi-Directional Traceability]]. In particular, end the first line of the message with a string like "Refs: #140.".

== Pushing back changes to github ==

Git commits any changes locally and so does Tortoise Git. After the work on the issue has been finished the context menu item '''Push...''' can be used for pushing back the locally stored sequence of commits to the related github branch.