Ad Maiorem Dei Gloriam (a.m.D.g.)

Juli 29, 2015

Nenn‘ ihn, wie Du willst.

Sag zu ihm „das kosmische Grundprinzip“, „die ewige Liebe“, „das, was die Welt im Innersten zusammenhält“, viele Namen hat er.

Und alle Menschen sind auf der Suche nach Liebe, viele wissen es nicht.

Doch am klarsten kommt sie zu Tage, diese Kraft, im Leben, im Sterben und in der Auferstehung unseres Herrn Jesus Christus.

Der der erste ist aller Propheten, Könige und Priester.

Der jedoch mehr ist. Er ist der Sohn, der zu Petrus gesagt hat: „Weide meine Lämmer“.

Meint
Euer Christoph


33rd Newsletter of SMUOS – Project Clean Up (PCU)

Juli 29, 2015

Dear Friends of SrrTrains,

The SrrTrains project has been an attempt to learn about the basics of Web3D multiuser scenes. Additionally we elaborated a few ideas, which could be related to standards for MU capable VR/AR systems.

Thank you for all your good wishes during the last 7 years.

The project clean up comprised following topics:

  1. error in the demo layout: the windmill had turned the wrong direction
  2. removed historic information about DIGITS from concepts/src/
  3. explained „Basic Initialization“ in the Concepts‘ Descriptions
  4. updated the project data base (PDB SRR) – generated .pdf files
  5. some small editorial changes

Find more information at https://letztersein.wordpress.com/srrtrains-v0-01/

Btw: Currently they’re encountering severe troubles at sourceforge.net. Hence I have already updated the SVN repository, but the freshest .zip files are not yet available.

Kind regards
Christoph


Der Code und die Botschaft……

Juli 26, 2015

Metaphern sollte man nur verwenden, wenn man vorher ihre Bedeutung erklärt hat.

Oder wenn man sich sicher ist, dass ALLE ZUHÖRER den Code kennen, zumindest die, für die die Botschaft GEDACHT ist.

Und dann gibt es da noch die Geheimcodes und die Wahnsinnigen, von denen jeder einen Code benützt, den nur ER/SIE kennt. Warum eigentlich? Aus Angst, verstanden zu werden? Oder weil man die Größe der Botschaft fürchtet?

Oder die Sprengkraft?

Und was ist mit der Spreizbandtechnik? Da ist doch auch so.

Meint
Euer Christoph


Mission Possible – SrrTrains Project Clean Up

Juli 24, 2015

SrrTrains project clean up has has been finished nearly completely.

Due to some problems they are currently encountering at sourceforge.net, the final update will still need a few days.

Things already done:

  1. error in the demo layout: the windmill had turned the wrong direction
  2. removed historic information about DIGITS from concepts/src/
  3. explained „Basic Initialization“ in the Concepts‘ Descriptions
  4. updated the project data base (PDB SRR) – generated .pdf files
  5. some small editorial changes

Things still to do:

  1. Commit source at SF – Update of the readmes – Commit source at SF – update „Home of SrrTrains“
  2. Release of the .zip Files at SF
  3. Update SF Fora, SF Features and so on, clean up SF
  4. Update PFUs „published“
  5. Update the SrrTrains „Hibernation Page“ about new release (it is not „official“)
  6. Update PFUs = „consummatum est“, hibernation information at: letztersein……
  7. Write 33rd Newsletter of SMUOS – Project Clean Up (PCU)

Nice weekend


Auch Bettler verkaufen eine Ware,……

Juli 24, 2015

……nämlich „gutes Gewissen“.

Meint
Euer Christoph


Mission Impossible – Project Clean Up

Juli 19, 2015

I really don’t know, when I should perform the project clean up for the SrrTrains/SMUOS project.

I don’t have time for this activity.

However, to be „fit for the future“, I’m now trying to write down the

Goals and Steps for the Project Clean Up (PCU)

  1. Main Goal: enable other people to derive their own projects from the frozen open source projects http://simulrr.sourceforge.net and http://smuos.sourceforge.net
  2. Update the source code, so that all concepts can be derived from the inline comments
  3. Update the „new concept paper“, so that all concepts can be learnt from a theoretical point of view

This is it
Yours Christoph


It’s only to Clean Up the Project

Juli 12, 2015

SrrTrains v0.01 is hibernating now, no doubt – everybody knows the reason – I’m waiting for an improvement of the Network Sensor.

OK, but why to write a new blog entry about that?

I think, we should clean up the project in the mean time, to be fit for the future. Anybody like to help?

Please see the additional info in the „P.S.“.

All the best
Christoph

P.S.:

SrrTrains-Hibernation

SrrTrains v0.01

Some parts of the Project Follow Up (PFU)
Step 0033.07 – „Web Spaces“ (done)

  • testing: Monolithic Layout on Webspace — DONE
  • publish step 0033.07 — DONE -> „third official pre-alpha“ 0033.07bf4

Step 0033.08 – „Rebase to SMUOS“ (done)

  • testing: Support Octaga Player again — later
  • asynchronous controllers of Extension Modules — later
  • replace base module by Smuos — DONE
  • update models for model prototypes — DONE
  • instrument station house – DONE
  • publish step 0033.08 – DONE -> „fourth official pre-alpha“ 0033.08bf1

Step 0033.09 – „Preps for Rail Vehicles and Trains II“ (hibernating)

  • console improvements — done
  • rename setup points -> replicators — done
  • MIDAS Object: Replicator — done -> „fifth official pre-alpha“ 0033.09bf2
  • Key Container improvements
  • publish step 0033.09
  • finish new concept paper
  • Consummatum est

 

SMUOS

Some parts of the Project Follow Up (PFU)
Block A: Hobby Usage – halted

  • Step A.1: Simplify SIMUL-RR – done
  • Step A.2: Introduce Support for SrrTrains – done
  • Step A.3: Enhance Support for SrrTrains – halted
    • MIDAS Object: Trigger – done
    • concept for dynamic models and replicators – done
    • MIDAS Object: Creator – done
    • publish first version of step A.3 (still without dynamic model support) – done
    • MIB improvement – halted
    • publish step A.3.bugfix<N>

Block B: Try Going to Get Serious – not yet planned

  • Step B.1: Mature Network Sensor (Network Semaphores) – not yet planned
  • Step B.2: Start SMUOS/C3P – not yet planned
  • Step B.3: ……
  • Step B.4: ……
  • and so on

Block C: Professional Usage by SIMUL-RR and/or other Projects – not yet planned

  • Step C.1: ……
  • Step C.2: ……
  • and so on