Squeak-dev July 2004

squeak-dev@lists.squeakfoundation.org

146 participants
464 discussions

[BUG]? with POOH
by stéphane ducasse 07 Jul '04

07 Jul '04

Hi while preparing my demo I tried to get pooh working in 3.6 full but it was not working. It worked well in 3.5 so I demoed it with this version. could somebody else try and let me know because I tried all the VM I got and on multiple platform. Stef

2 3

Re: [ENH] speedup for DateAndTime
by pinkney_b＠www.aircom.co.za 07 Jul '04

07 Jul '04

Hi, Since I introduced and maintain the Chronology package, I will submit a solution when I return next week. What is required, IMHO, is a solution in the spirit of the Integer classes. DateAndTime SimpleDateAndTime PrecisionDateAndTime TimeStamp SimpleDateAndTime has second precision and no support for timezones. Not only will it be fast, it will have terse representation - 2 SmallIntegers for those concerned about storing instances. PrecisionDateAndTime is the current all singing and dancing DateAndTime. TimeStamp remains a legacy class. A preference will determine which gets instanciated I have had a draft of this on my pc for a while. I just need to dust it off and ensure the two versions play nicely together. Cheers Brent -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

2 1

Re: start activeX out of Squeak possible?
by John R. Pierce 07 Jul '04

07 Jul '04

Now on to wrapping a COM object and automating it in Squeak. For this demonstration I will choose a rather boring COM object because I know it generally is installed on any Windows machine. We will automate the Windows Script Host objects, an instance of the WshShell class in particular. First, we have to get the COM object wrapped with .NET wrappers before this will be useful. You must open a command prompt and ensure you are in the Microsoft.NET\SDK\v1.1\bin folder (generally under c:\Program Files) or you have a path setup to this folder. We want to run tlbimp.exe (in this folder). This is the Type Library to Assembly Converter program from the Microsoft .NET SDK. It basically adapts the COM interface to a .NET one. As a matter of definition, .NET DLLs are called "assemblies" (not entirely correct, but good enough for this discussion). Now that you are in the right folder let's create the .NET wrapper for the WSH COM objects. Depending on your computer your WSH DLL may be in a different location, but on my Windows XP computer it is the following file: C:\WINDOWS\System32\wshom.ocx So I will run the following command: tlbimp c:\windows\system32\wshom.ocx This will generate a file called "IWshRuntimeLibrary.dll" in the current folder. Move this file to your squeak default folder for ease of use. That's all we needed the Microsoft .NET SDK for at this point. If you browse the Microsoft SDK documentation you will see that there is a WshShell class. To access this class in Squeak we first need to load this new assembly we just created. In a workspace do the following: DotNet Assembly loadFrom: 'IWshRuntimeLibrary.dll'. NOTE: You will get warnings about unknown selectors when using the .NET bridge because nearly everything in this bridge is implemented via the magic of DNU. With nearly 1600 classes in the .NET framework we took this short cut. Just proceed through the warnings. Now this .NET wrapper is loaded in the .NET execution environment. Next we instantiate an instance of the WshShell class as follows: shell := DotNet WshShellClass new. Why not just WshShell? WshShell is the interface and WshShellClass is the class that implements this interface. This is a common idiom when using wrapped COM objects via .NET (not a Squeak .NET bridge idiom). Now that we have an instance of COM object "WScript.WshShell" in hand, let's send it the Popup message to get a messagebox on the screen. Here's the signature of that message from the MSDN documentation: intButton = object.Popup(strText,[nSecondsToWait],[strTitle],[nType]) So in Smalltalk we say: buttonPressed := shell popup: 'Hello from Squeak' secToWait: 5 title: '.NET Bridge Demo' type: 0. As you will notice, with the Squeak / .NET Bridge you have to invent keywords for each argument. Here, I used explaining keywords, but you can write this as: shell popup: with: with: with: if you like. It really doesn't matter what you make your keywords, just get the function name correct up front. Additionally, the .NET bridge in Squeak is case insensitive, so it doesn't matter if you call POPUP, popup, or Popup. Lastly, you may notice the signature of Popup had optional arguments. Well, guess what? .NET does not support this notion of COM and IDispatch so you must provide all arguments. (Again -- not a Squeak / .NET bridge issue). If you need more examples and/or more info on using the bridge go to our wiki on this technology at: http://www.saltypickle.com/squeakDotNet or write me. Regards, John PS - To make discovery of the .NET wrapper interface easier we find using Reflector on any .NET assembly a real time save. You can get a copy of reflector at: http://www.aisto.com/roeder/dotnet/. It is like OleView, but for .NET assemblies (not COM DLLs).

1 0

Visualworks compatibility packages?
by Roel Wuyts 07 Jul '04

07 Jul '04

Hi, I am trying to get some work done for the StarBrowser again... therefore I was wondering whether there are some packages around that add VisualWorks-specific methods and/or classes to Squeak? -- Roel Wuyts DeComp roel.wuyts(a)ulb.ac.be Université Libre de Bruxelles http://homepages.ulb.ac.be/~rowuyts/ Belgique Board Member of the European Smalltalk User Group: www.esug.org

1 0

Web service
by chenais 07 Jul '04

07 Jul '04

Hello!! Is it possible to call a web service from Squeak? Alternate question - Does somebody have a good and simple solution for a communication between Squeak and Java applications. Thank you for your help. Patrick

2 1

Re: start activeX out of Squeak possible?
by John R. Pierce 07 Jul '04

07 Jul '04

Hi Thom, To wrap a COM or ActiveX object with .NET and automate it in Squeak you will need to do the following steps. First you need to ensure you have the .NET Framework Runtime Redistributable and the .NET Framework SDK installed to do what I am about to show you. Here's some URLs if you need to download and install: 1. .NET Runtime Redistributable: http://tinyurl.com/95zt 2. .NET SDK: http://tinyurl.com/97x7 Basically you only need to install the .NET Runtime to use the Squeak .NET interface and to automate .NET objects, but to do the COM automation you need a small utility out of the .NET SDK to wrap the COM object so you are stuck getting and installing 100+ Megs of the SDK just to make this work. Sorry about that part. *SIDEBAR* : Interestingly enough, once you have the relatively small .NET Runtime installed, Microsoft gives away the C#, C++, J#, and VB.NET compilers in the runtime redistributable so you can write, build, and run .NET applications with your favorite text editor and command-line builds without buying a thing from anyone. In fact, any machine that has the .NET runtime installed on it (which are many these days) is essentially a development box since the compilers come with .NET for free. Now that you have .NET installed you can install the Squeak .NET interface (just to get software installation activities completed). Open Package Loader and find and install the Squeak/.NET Bridge package. You can test your installation to ensure you have both .NET and the Squeak .NET bridge installed correctly by opening a workspace and printing the following line: DotNet ArrayList new count It should create a new .NET ArrayList (which has no elements) and print its count (the .NET equivalent of "size"). Of course, zero should be printed. If you have all this successfully, you are well on your way to automating your COM object. I will demonstrate the wrapping of a COM object and automating in Squeak in a subsequent post since this posting is more general in nature. Regards, John

1 0

Hierarchical List Morph with Icons and StarBrowser
by Torsten Bergmann 07 Jul '04

07 Jul '04

Hi, after loading StarBrowser from SqueakMap it looks like the package needs some cleaning for 3.7beta. Any volunteers? The SAR package also includes Ned's support for icons (HierListWithIcons-nk.cs) in Hierarchical List morphs which would be nice for other applications too. Instead of including this changeset in each application it would be nice if we could either add it to the base package or repackage it as separate sar/mcz/cs on SqueakMap. Is there a newer version from Ned available, maybe with a different icon for the clicked state? Any comments ? Thanks Torsten -- +++ Jetzt WLAN-Router f�r alle DSL-Einsteiger und Wechsler +++ GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl

2 2

[BUG]SystemWindows>>addMorph:fullFrame:(new
by Karl Ramberg 07 Jul '04

07 Jul '04

If you try to embed a morph into a system window, from the halo menu or sending a embedInWindow, it will go very wrong. In addMorph:fullFrame: the morph get's modified and the result is not very nice. I suspect that some modification from the alternativeWindowLook is to blame. It seems like the method is used both for constructing windows and adding new morphs to a window. Karl

1 0

[BUG]Array(Object)>>doesNotUnderstand: #build3DObject
by ducasse＠iam.unibe.ch 07 Jul '04

07 Jul '04

Wonderland new Click on pooh and draw a line and boom. May be fixed in 3.7 but I could try. Stef 7 July 2004 11:04:29 am VM: unix - Squeak3.7beta of '1 April 2004' [latest update: #5868] Image: Squeak3.6 [latest update: #5429] Array(Object)>>doesNotUnderstand: #build3DObject Receiver: #(-0.04285714285714286(a)-0.338095238095238 -0.1761904761904762(a)-0.2047619047619048 -0.26190...etc... Arguments and temporary variables: aMessage: a Message with selector: #build3DObject and arguments: #() Receiver's instance variables: #(-0.04285714285714286(a)-0.338095238095238 -0.1761904761904762(a)-0.2047619047619048 -0.26190...etc... WonderlandCameraMorph>>createPoohActor Receiver: a WonderlandCameraMorph<camera>(404) Arguments and temporary variables: actor: nil pointList: #(0.0904761904761905(a)-0.4523809523809524 0.0904761904761905@-0.45238...etc... box: 117@84 corner: 176@179 scale: 0.00952380952380952(a)-0.00952380952380952 center: 146.5(a)131.5 subdivision: #(-0.04285714285714286(a)-0.338095238095238 -0.1761904761904762@-0.2...etc... mesh: nil tex: nil each: 156@179 Receiver's instance variables: bounds: 20@20 corner: 228@230 owner: a PasteUpMorph(1973) [world] submorphs: #() fullBounds: 20@20 corner: 228@230 color: Color transparent extension: a MorphExtension (1599) [externalName = camera ] [eventHandler = an...etc... myWonderland: a Wonderland myCamera: WonderlandCamera11<'camera'> myControls: nil eventFocus: nil lastCursorPoint: 0@0 mouseUpButton: nil firstPersonControls: nil mode: #stroke outline: a ReadWriteStream currentActor: nil currentPosition: nil currentCanvas: nil currentColor: nil currentNib: nil lastPosition: nil paintMode: nil palette: nil restore: nil backup: nil pickedPoint: nil pickedActor: nil myRenderer: nil WonderlandCameraMorph>>mouseUpStroke: Receiver: a WonderlandCameraMorph<camera>(404) Arguments and temporary variables: evt: [166@171 mouseUp 251230] Receiver's instance variables: bounds: 20@20 corner: 228@230 owner: a PasteUpMorph(1973) [world] submorphs: #() fullBounds: 20@20 corner: 228@230 color: Color transparent extension: a MorphExtension (1599) [externalName = camera ] [eventHandler = an...etc... myWonderland: a Wonderland myCamera: WonderlandCamera11<'camera'> myControls: nil eventFocus: nil lastCursorPoint: 0@0 mouseUpButton: nil firstPersonControls: nil mode: #stroke outline: a ReadWriteStream currentActor: nil currentPosition: nil currentCanvas: nil currentColor: nil currentNib: nil lastPosition: nil paintMode: nil palette: nil restore: nil backup: nil pickedPoint: nil pickedActor: nil myRenderer: nil EventHandler>>send:to:withEvent:fromMorph: Receiver: an EventHandler; mouseUpSelector=mouseUpStroke: recipients: #(a WonderlandCameraMorph<came...etc... Arguments and temporary variables: selector: #mouseUpStroke: recipient: a WonderlandCameraMorph<camera>(404) event: [166@171 mouseUp 251230] sourceMorph: a WonderlandCameraMorph<camera>(404) arity: 1 Receiver's instance variables: mouseDownRecipient: nil mouseDownSelector: nil mouseMoveRecipient: a WonderlandCameraMorph<camera>(404) mouseMoveSelector: #mouseMoveStroke: mouseStillDownRecipient: nil mouseStillDownSelector: nil mouseUpRecipient: a WonderlandCameraMorph<camera>(404) mouseUpSelector: #mouseUpStroke: mouseEnterRecipient: nil mouseEnterSelector: nil mouseLeaveRecipient: nil mouseLeaveSelector: nil mouseEnterDraggingRecipient: nil mouseEnterDraggingSelector: nil mouseLeaveDraggingRecipient: nil mouseLeaveDraggingSelector: nil keyStrokeRecipient: nil keyStrokeSelector: nil valueParameter: nil startDragRecipient: nil startDragSelector: nil doubleClickSelector: nil doubleClickRecipient: nil doubleClickTimeoutSelector: nil doubleClickTimeoutRecipient: nil clickSelector: nil clickRecipient: nil gestureSelector: nil gestureRecipient: nil gestureDictionaryOrName: nil --- The full stack --- Array(Object)>>doesNotUnderstand: #build3DObject WonderlandCameraMorph>>createPoohActor ...etc...

1 0

start activeX out of Squeak possible?
by John R. Pierce 07 Jul '04

07 Jul '04

Hi Thom, We used Squeak on the job to automate COM components quite successfully. We didn't build a COM interface, but we did build a .NET interface. So it seems a bit like technology soup, but if you use tlbimp.exe in the .NET Framework SDK (I believe) you can generate a .NET wrapper around a COM object/control. Then using the Squeak .NET bridge on SqueakMap you can then instantiate and automate your COM object. Yes, it does indeed work (at least for our COM components we tried it with). If you need more specific examples I can provide those in a follow-up email. I am assuming you are familiar with tlbimp.exe and the .NET programming model a bit here. Regards, John

2 1

← Newer
1
...
39
40
41
42
43
44
45
46
47
Older →

Jump to page: