State of different projects for work with 3D

Regards; excuse me for my poor english.

I want create a language similar to XAML for define UI interfaces. My doubt is the number and state of different projects for access to OpenGL. I need running on different OS without differences. Well, perhaps is a great question, but I haven´t a global look of that in Pharo. Is possible implements something like that in Smalltalk?

Thanks for the answers.

> I want create a language similar to XAML for define UI interfaces. My doubt
> is the number and state of different projects for access to OpenGL. I need
> running on different OS without differences. Well, perhaps is a great
> question, but I haven´t a global look of that in Pharo. Is possible
> implements something like that in Smalltalk?

I am not sure to understand your email.
From what I've heard and seen, Lumiere is probably the bext starting point for any new opengl related project.

http://www.squeaksource.com/Lumiere.html

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






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

There was a patch discussed on the Squeak mailing list
http://bugs.squeak.org/view.php?id=7266
names serial ports. (not just by Number)

There are patchs for the plugin. I wonder how do I build such a new
plugin? Or can't I use that in Pharo?

Regards
Friedrich

Friedrich,

I recall having success with the vm as-is and just patching the image.  One thing the vm certainly should do is tell us the translations it makes.  I think it is always a good idea to know which port was actually opened, or failed to open :)  Double that for external libraries, but that's another story.

Try the attached.  It is basically lifted from Squeak (to handle numbers and names) and then tweaked to avoid the silent failure trap.

Bill



________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Friedrich Dominicus [[hidden email]]
Sent: Wednesday, March 02, 2011 6:54 AM
To: [hidden email]
Subject: [Pharo-project] Where to download

There was a patch discussed on the Squeak mailing list
http://bugs.squeak.org/view.php?id=7266
names serial ports. (not just by Number)

There are patchs for the plugin. I wonder how do I build such a new
plugin? Or can't I use that in Pharo?

Regards
Friedrich

Just wondering if anyone has build a 64-bit virtual machine for Pharo
Or are you sticking to 32-bit. If so how do you build the virtual
machine on a 64-bit system?

Regards
Friedrich

"Schwab,Wilhelm K" <[hidden email]> writes:

> Friedrich,
>
> I recall having success with the vm as-is and just patching the image.  One thing the vm certainly should do is tell us the translations it makes.  I think it is always a good idea to know which port was actually opened, or failed to open :)  Double that for external libraries, but that's another story.
>
> Try the attached.  It is basically lifted from Squeak (to handle
> numbers and names) and then tweaked to avoid the silent failure trap.
Thansk I'll try it tomorrow.

Regards
Friedrich

--
Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

"Schwab,Wilhelm K" <[hidden email]> writes:

> Friedrich,
>
> I recall having success with the vm as-is and just patching the image.
> One thing the vm certainly should do is tell us the translations it
> makes.  I think it is always a good idea to know which port was
> actually opened, or failed to open :)  Double that for external
> libraries, but that's another story.

Sorry I wonder the primitive is placed in
libSerialPlugin.a
this are the function I found in the
Content/Linux subdirectory

e
08102f10 t primitiveSerialPortOpen
08102df0 t primitiveSerialPortRead
08102cc0 t primitiveSerialPortWrite
08105980 t primitiveSocketBindToPort
081055c0 t primitiveSocketConnectToPort
08104b40 t primitiveSocketListenOnPort
08104a00 t primitiveSocketListenOnPortBacklog
08104830 t primitiveSocketListenOnPortBacklogInterface
08104670 t primitiveSocketLocalPort
08103e60 t primitiveSocketRemotePort
08102630 t secCanConnectToPort
081025d0 t secCanListenOnPort
081034a0 T serialPortClose
081030d0 T serialPortInit
080d9a90 T serialPortMidiClockRate
08103210 T serialPortOpen
08103190 T serialPortReadInto
081030b0 T serialPortShutdown
08103120 T serialPortWriteFrom


The code in Pharo is:
<primitive: 'primitiveSerialPortOpenByName' module:'SerialPlugin'>
So hasn't there  a function with that name?


Regards
Friedrich


--
Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

On Wed, Mar 02, 2011 at 04:14:31PM +0100, Friedrich Dominicus wrote:
> Just wondering if anyone has build a 64-bit virtual machine for Pharo
> Or are you sticking to 32-bit. If so how do you build the virtual
> machine on a 64-bit system?

Hi Friedrich,

For a standard VM, you get a 64-bit VM just by compiling the VM on
a 64-bit platform and not using the -m32 compiler flag. It works fine,
but some plugins have not been updated to be 32/64 bit clean, so for
most folks it is better to just use the 32-bit version. Personally,
I usually use a VM compiled for 64-bit, but there is no real advantage
to doing this.

Additional info is at http://www.squeakvm.org/squeak64/faq.html.

Dave

Hi all,

On Wed, Mar 02, 2011 at 12:54:30PM +0100, Friedrich Dominicus wrote:
> There was a patch discussed on the Squeak mailing list
> http://bugs.squeak.org/view.php?id=7266
> names serial ports. (not just by Number)
>
> There are patchs for the plugin. I wonder how do I build such a new
> plugin? Or can't I use that in Pharo?

Friedrich,

The updated plugin with support for named serial ports is in the
standard VM, but possibly not yet in the Cog VM. If you need to use
named serial ports, try using a standard VM from squeakvm.org. If
you are building your own Cog VM, the updates are not complex so
you may be able to just apply them in your VMMaker package.

HTH,
Dave