Stef wrote

You need to load latest version of OSWindow from what ronie told me.

Thanks, will try

Hi I am also interested in the current status of Woden.I tried to follow the instructions from Alex (under Windows 7) and I get a: NBFFICallout>>error: 'Invalid option name WinUnicode, must begin with ''opt''' Any help is appreciated. Cheers Ricky On Mon, Jan 12, 2015 at 2:46 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:

You should do:

Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: #ConfigurationOfNBOpenGL) project version: '3.0') load.

Gofer new smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'ConfigurationOfOSWindow'; load. (Smalltalk at: #ConfigurationOfOSWindow) loadBleedingEdge.

Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge.

Some of the things are not up to date in pharo.

Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

...

On Jan 11, 2015, at 2:06 PM, Torsten Bergmann <astares@gmx.de> wrote:

Hi,

is woden 3D engine for Pharo working out of the box with Pharo 4 and latest VM on Windows? As OSWindow is already integrated I do not know if the load script still fits. Wanted to ask first. What is required to load?

If so can we have a config in the config browser for easy access?

Thx T.

Hi Richard, this is an error from NativeBoost. Have a look at the previous methods back in the debugger stack. There must be one with a native Boost call including something like options: { WinUnicode }. Change this to optWinUnicode and try again.   I guess we now use "opt" prefix for Native Boost options.  Bye T.     Gesendet: Montag, 12. Januar 2015 um 16:18 Uhr Von: "Richard Wettel" <wettel@gmail.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Woden on Windows? Hi   I am also interested in the current status of Woden.I tried to follow the instructions from Alex (under Windows 7) and I get a:   NBFFICallout>>error: 'Invalid option name WinUnicode, must begin with ''opt'''   Any help is appreciated.   Cheers Ricky   On Mon, Jan 12, 2015 at 2:46 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:You should do: Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: #ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'ConfigurationOfOSWindow'; load. (Smalltalk at: #ConfigurationOfOSWindow) loadBleedingEdge. Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge. Some of the things are not up to date in pharo. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu[http://www.bergel.eu] ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Jan 11, 2015, at 2:06 PM, Torsten Bergmann <astares@gmx.de[astares@gmx.de]> wrote:

Hi,

is woden 3D engine for Pharo working out of the box with Pharo 4 and latest VM on Windows? As OSWindow is already integrated I do not know if the load script still fits. Wanted to ask first. What is required to load?

If so can we have a config in the config browser for easy access?

Thx T.

 

Rhichard Wettel wrote

@all: There were only a couple of places where the "opt" prefix was missing in the parameters of the call to #options: method, which I have now corrected. I would like to commit these changes in NativeBoost-Win32, but I do not know where (which repository). Can someone can help me with directions?

Was already discussed in Nov: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-November/103... http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-November/103...   So create a regular Pharo issue for NativeBoost in pharo issue tracker and fix by submitting a slice for latest 4.0 image. NativeBoost is currently managed internal to the image and the repo has at STHub will be/has to be synched later on anyway. When Pharo continues to manage packages via Configs (like some package in Pharo 4, GTTools for example) the NativeBoost might become managed from the external repo using a config again. For now it is in-image. Regarding the options this might be interesting as well: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-November/102... So WinUnicode seems the only option not having the prefix. Bye T. without h ;)