pixellightfoundation / pixellight Goto Github PK

The PLProject tool is a great utility, but has several problems. First, it does make a lot of things up - for example it works only with exactly named module .cpp's and output DLLs. Second, the way it parses source files using regular expressions is error prone by nature and also prevents us to make any significant changes to the API without the need for a rewrite.

The proposed solution would be to create a simpler tool, that would directly load the target dynamic library and extract the information directly.

The PLCore::String class provides a number of constructors and operators allowing to create (or attach) a string from numerical types. However, these are not marked as explicit and can be therefore confused with other similar methods for the character types.

See PLCore/String/BufferedReaderFile.cpp line 226 for an example of bad implicit conversion.

Also, some of the ctors and operators are marked for export while others are not, making the API possibly incnosistent.

Design and implement an improved build pipeline for PL's external dependencies. Replace the legacy custom system with CMake's ExternalProject.

First phase should at least check for the presence of library on user's system (with required version) and download & build the package if necessary. Other options, such as an optional prebuilt package repository for Windows, may be added in a future iteration.

Review the overall build process of PL. Remove duplicities and unused stuff.

CMake should be the only build system for the future.

Spent last two days trying to register on forum: http://pixellight.org/forum, but failed. ( Can't beat the confirmation code, always getting: The confirmation code you entered was incorrect.)

Develop and upload the new website onto the pixellight.org domain server.

• Showcase section
• Features section
• Fixed links

Write a basic set of tutorials for beginners and intermediate users.

These should concentrate on more complete tasks than the samples provided with the SDK do. They should have the form of wiki entries with code snippets (full source may be available with the SDK or provided in a separate git repo).

Basic concepts behind PL should be explained in great detail. There should be two categories of tutorials:

• Basic: use the framework to its fullest to setup the basic application, load a scene, spawn a character, move it etc
• Technical: more like the SDK samples - discover the features of PL in a more technical manner, focusing at one problem at once