Re: [Pharo-project] [squeak-dev] LGPL considered crippling license :)
Igor == Igor Stasenko siguc...@gmail.com writes: Igor P.S. i found it a very good sign, that more and more open-source Igor communities gradually moving towards more permissive license, as MIT Igor is. As I've often said, with licensing, people just want permission to do what they would have done anyway. MIT-style licenses allow people who want to share to do that in the open, instead of share in secret. GPL licenses merely force some kinds of sharing to be done in secret, and we lose out on that. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] LGPL considered crippling license :)
I haven't visited the Orge site long ago, i found an interesting news, that they switching license to MIT! The motivation conclusions why they decided to switch are very interesting: --- citation --- Won’t this mean people can ‘rip off’ OGRE in proprietary software? The LGPL already allowed OGRE to be used in proprietary software, and this is something we’ve always encouraged. The main difference between the LGPL and the MIT License is that there is no requirement to release modified source code; only to include our copyright and the MIT license text in the final product. While not requiring modified source to be released might initially seem like giving up an important motivator to contribute code back to the community, we’ve noticed something in recent years: 99% of useful code contributions come from people who are motivated to participate in the project regardless of what the license tells them they have to do. It’s our experience that a certain percentage of the user community will always participate and contribute back, and therefore encouraging adoption via simpler licensing is likely to result in more contributions overall than coersion via complex and restrictive licensing does. In addition, people who are internally motivated to participate tend to provide much higher quality and more usable contributions than those who only do it because they are forced to. --- citation --- you can read the full article here: http://www.ogre3d.org/2009/09/15/ogre-will-switch-to-the-mit-license-from-1-7#more-685 P.S. i found it a very good sign, that more and more open-source communities gradually moving towards more permissive license, as MIT is. -- Best regards, Igor Stasenko AKA sig. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update] #10459
10459 - rollbacked and merged Kernel-StephaneDucasse.405, SystemSupport.StephaneDucasse.89, Tools-StephaneDucasse.202 - Issue 1219: Left over of uniClasses...in Object Object classnewUserInstance Object classinstanceOfUniqueClass Object classinstanceOfUniqueClassWithInstVarString: instVarString andClassInstVarString: classInstVarString Object classcategoryForUniclasses Object classnewUniqueClassInstVars: instVarString classInstVars: classInstVarString - Issue 1223: reduce message text on full name prompt - Issue 1222: edit Repository information-cancel fails. UIManager#multiLineRequest:centerAt:initialAnswer:answerHeight: returns nil - Issue 1199: Debug log is overwritten with each error - Issue 1233: Needs changes after fix 1129 Fix on issue #1129 changed the interface of UIManager. We have to change each user of the #request: method and its friends. Enjoy ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] ClosureTests remove expected failures
Compiler-MikeRoberts.132 in Inbox Remove unexpected failures since the tests now pass with Eliot's latest batch of closure fixes. thanks, Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] CairoGraphics
Hi Ken, good improvements to Alien! Are you are using Installer to load Alien? Would be better to put the Alien#initialize into a post Install method, does Installer have that? The AlienLoader does that, so your fixes should work. What stuff is in Alien and not in Alien Lite? Fernando Il giorno Sep 26, 2009, alle ore 1:59 AM, Ken Treis ha scritto: On Sep 25, 2009, at 10:57 AM, Stéphane Ducasse wrote: cool For anyone who's been playing with this, I just posted another new revision of Alien that fixes the platform sizes to match C platform sizes. Not sure what I was thinking in the first go-around. Anyhow, if you load Alien-Core-kdt.58 in Pharo, you'll need to re-initialize Alien: Alien initialize In other news, I've got CairoGraphics mostly working in GemStone (2.3.1) now too, running on top of an Alien Lite that provides support for the types of function calls I need to make. If anyone is interested in this, email me directly and I'll send you the code once I've worked out the remaining major bugs. Ken On Sep 25, 2009, at 7:19 PM, Ken Treis wrote: Hi Damien, Yes it definitely works -- at least for me, on Mac OS X. Recent VMs from John McIntosh have the plugin already, though on the mac it only searches for libraries in a few select places and it doesn't accept absolute paths. Hopefully this will be resolved soon; for now I've symlinked the library into my Squeak VM's plugins folder. On Linux you may have to compile a VM yourself to get the plugin; I know it's in the VM source tree. For a quick demo, try: |image cr backgroundGradient textGradient| image := CRImageSurface format: CRFormat argb32 extent: 3...@200. cr := image context. backgroundGradient := CRLinearGradient from: 0...@0 to: 1...@200. backgroundGradient addStopAt: 0 color: Color white. backgroundGradient addStopAt: 1 color: Color lightGray. cr source: backgroundGradient; paint. cr moveTo: 3...@100. cr selectFontFace: 'Sans'; fontSize: 40. cr textPath: 'Hello, World!'. cr source: Color green; strokePreserve. textGradient := CRLinearGradient from: 0...@50 to: 3...@50. textGradient addStopAt: 0 color: Color blue alpha: 0.2. textGradient addStopAt: 1 color: Color blue alpha: 0.8. cr source: textGradient; fill. image writeToPng: '/Users/kdt/Desktop/hello.png'. This isn't anything super exciting to look at, but if you've got the IA32ABI plugin and have set up CRLibrary classlibraryPath to point to the Cairo library, you should be able to see the output (attached). I'll try to post a more impressive demo soon. Ken On Sep 25, 2009, at 2:08 AM, Damien Cassou wrote: Hi Ken, I'm going to have 4 students working during 4 months on Smalltalk. I would like to get a Cairo working implementation. What about yours/Travis'? What can we do with it? Can we draw something in Pharo? Does it work? Thank you -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry -- Ken Treis Miriam Technologies, Inc. hello.png___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Ken Treis Miriam Technologies, Inc. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Compiler tests naming
I've noticed we've got two sets of compiler tests. One category part of the compiler and one part of its own tests package. Assume we want to just the tests all into their own package? thanks, Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] CAnalyer
Sig, Interesting. I looked at swig and decided that I would have a better chance of success with pattern matching, especially since some of the code I want to analyze is barely pseudo code (but still full of valuable information). I ended up with a bit of a mess in Dolphin, but it strangely manages to work; for Pharo, I planned to clean it up, got as far as noticing the regex package, and saw CAnalyzer. That is a long way around saying that I am not eager to tear back into swig, but your argument about the working preprocessor and parser is well taken and I would like to see what you did. I should at least look at CAnalyzer and then either switch to it or begin moving my unit tests and higher-level recognizers to Pharo. Leaving the whole thing in Dolphin is an option too, but the code really needs some cleaning, so the port would do it and me some good. I will be glad to look over your work and maybe put swig back into consideration. Bill -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Saturday, September 26, 2009 12:53 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] CAnalyer 2009/9/26 Schwab,Wilhelm K bsch...@anest.ufl.edu: Sig, Is it something you have made available? One snag in my world is that the code is not always something that can be compiled. However, for GSL and other libraries of interest, the code is valid, if not full of macro-based annoyances and other distractions. the code i written is the module to SWIG. The project what i developed once is to write a smalltalk interpreter by own, and the aim was to use it as a scripting engine for C++ projects. My experiments stopped shortly after i understood that my interpreter implementation having some flaws and i need to spend much time to rewrite everything :) But, along the way, i started making bindings to Ogre 3D engine (http://www.ogre3d.org/) and my SWIG-based binding code generator were able to reflect C++ classes in my own smalltalk, including being able to call constructors/destructors, methods and directly access the fields by using auto-generated primives. If you wanna to get deeper into that, i can send you the sources and examples. With a little effort, the code generation could be easily changed to satisfy the FFI/Alien demands, then you will be able to bind any C library with Squeak VM. Bill -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Friday, September 25, 2009 11:03 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] CAnalyer 2009/9/26 Schwab,Wilhelm K bsch...@anest.ufl.edu: I was digging around on Squeak Source for OSProcess and friends, and ran across CAnalyzer. Are there any papers on it? How robust is it? What does it extract from C code? For example, might one put the GSL (www.gnu.org/software/gsl) header files into it, pull out all of the structure definitions and function prototypes, and generate LOTS of FFI code to make a wrapper? Just a thought... I having a modified version of SWIG, which can parse C++ files, including classes and nested classes, to produce smalltalk code wrappers. Reproducing the SWIG in smalltalk would be very time consuming. But it would be cool to have a C/C++ parser implementation. SWIG is not only parsing, its also doing macro preprocessing, so its can't be fooled with macros :) Bill ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] MethodPropertiesTests mark expected failures
http://code.google.com/p/pharo/issues/detail?id=1246 KernelTests-MikeRoberts.151 in Inbox thanks, Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update] closure fixes :)
thanks for integrating Stef cheers Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] OSProcess question
On Sat, Sep 26, 2009 at 11:04:37AM -0400, Schwab,Wilhelm K wrote: Dave, I just tried command shell; are you _sure_ it is possible to proceed past the errors? No, I had not checked on the most recent Pharo. So I just downloaded a Pharo image to try it. You can proceed through the warnings about missing MVC stuff. And when you get to the end of the install, the CommandShell classinitialize will put you into a debugger. Comment out the last line where it is trying to open a CommandShell window, then proceed. This should get you through the installation. It looks badly broken from here. It looks pretty bad from here also. The Morphic UI no longer works (it was working the last time I looked at Pharo, but not now). Some AioEventHandlerTestCase tests are now failing due to something different in Socket. Some of the CommandShellTestCase tests get hung up when doing very complex command pipelines (i.e. lots of Process coordination). But if you limit yourself to running simple commands and do not use the CommandShell user interface, it should still do what you need. I can't say I'm happy with the way Pharo brings things to a halt over deprecated methods; yes, it gets attention before things go away in future release, but there are times when I would like to gag it and just get some work done. Mea culpa, I just fixed the deprecated method issue in CommandShell, so if you load the latest version now this problem should be gone. I still do not see the tests. Are you saying that they should have been installed with OSProess itself? If there are separate packages on ss, I don't see them either. Open this MC repository: MCHttpRepository location: 'http://www.squeaksource.com/OSProcess' user: '' password: '' Then load the latest versions of both of these packags: OSProcess Tests-OSProcess Open this MC repository: MCHttpRepository location: 'http://www.squeaksource.com/CommandShell' user: '' password: '' And load the latest versions of both these packages: CommandShell Tests-CommandShell HTH, Dave ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ClosureTests remove expected failures
integrated. :) stef On Sep 26, 2009, at 7:27 PM, Stéphane Ducasse wrote: yes On Sep 26, 2009, at 6:22 PM, Michael Roberts wrote: Compiler-MikeRoberts.132 in Inbox Remove unexpected failures since the tests now pass with Eliot's latest batch of closure fixes. thanks, Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] OSProcess question
check the preferences you can also ignore them or get atrace in the transcript On Sep 26, 2009, at 5:04 PM, Schwab,Wilhelm K wrote: Dave, I just tried command shell; are you _sure_ it is possible to proceed past the errors? It looks badly broken from here. I can't say I'm happy with the way Pharo brings things to a halt over deprecated methods; yes, it gets attention before things go away in future release, but there are times when I would like to gag it and just get some work done. I still do not see the tests. Are you saying that they should have been installed with OSProess itself? If there are separate packages on ss, I don't see them either. Bill -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr ] On Behalf Of David T. Lewis Sent: Saturday, September 26, 2009 9:23 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] OSProcess question On Fri, Sep 25, 2009 at 11:48:22PM -0400, Schwab,Wilhelm K wrote: I see various ways to run something, none of which are quite what I want. The objective is to run openssl in a particular directory. I have no need to make this portable (unless you mean running on all of Ubuntu, Debian, Slackware, etc. g), so #forkAndExec:...workingDirectory: would almost be ok, **but**, I need to wait around for the result. In truth, there are a few things that have to happen in sequence; perhaps I could simply write multiple lines to the command string. You should install CommandShell, which is a companion to OSProcess. Look at the class side methods in CommandShell and PipeableOSProcess for examples, also look at the unit tests. CommandShell has an MVC user interface as well as Morphic, so you will have to proceed through the errors when loading on Pharo. Still, in the interest of idealism, it would be nice to run the commands on other than the Pharo main thread (no sense diving into something that might not return[*]), and to know when the work is done, and to get the different steps to happen in sequence. PipeableOSProcess uses non-blocking I/O and event driven input. There should be no problem with blocking if you use this. If you use the lower-level classes in OSProcess, you need to handle issues like this yourself (also beware of pipe handle leaks from failing to close file descriptors if you are handling this yourself). There was mention of tests for OSProcess (which might provide clues), but I have not been able to find them. Any hints? Tests for OSProcess and CommandShell are in the SqueakSource projects. The package names are Tests-OSProcess and Tests- CommandShell. Dave ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] feedback on CLFramework
Hi nullPointer here are some feedback on your work that is really important for us. Use Smalltalk way of formatting code. == btn - button please use normal smalltalk conventions. inClassSideBoolean ifTrue: [ aClass class compile: aStringCodeSource classified: (aSymbolCategoryName asString) notifying: nil. ] ifFalse: [ aClass compile: aStringCodeSource classified: (aSymbolCategoryName asString) notifying: nil. ]. or inClassSideBoolean ifTrue: [ aClass class compile: aStringCodeSource classified: (aSymbolCategoryName asString) notifying: nil. ] ifFalse: [ aClass compile: aStringCodeSource classified: (aSymbolCategoryName asString) notifying: nil. ]. getFiles: aStringPathOfDirectory | aFileDirectory fullPathOfFile aCollection | aFileDirectory := CLFileDirectory on: aStringPathOfDirectory. aCollection := Bag new. aFileDirectory fileNames do: [ :nameOfFile | fullPathOfFile := aFileDirectory fullPathFor: nameOfFile. aCollection add: fullPathOfFile. ]. ^aCollection. Don't use space everywhere is not smalltalk getFiles: aStringPathOfDirectory | aFileDirectory fullPathOfFile aCollection | aFileDirectory := CLFileDirectory on: aStringPathOfDirectory. aCollection := Bag new. aFileDirectory fileNames do: [:nameOfFile | fullPathOfFile := aFileDirectory fullPathFor: nameOfFile. aCollection add: fullPathOfFile]. ^aCollection. If you give me access I can reformat everything. Add some comments == In the examples category there is no class comments so I have no idea about what I'm reading. There is not one single class comment: please add some of them. So far I could not find how to use it Do not refer to your class inside itself == CLCompilercreateMessageInClass: aClass withCodeSource: aStringCodeSource inProtocol: aSymbolCategoryName CLCompiler createMessageInClass: aClass withCodeSource: aStringCodeSource inProtocol: aSymbolCategoryName inClassSide: false. - CLCompilercreateMessageInClass: aClass withCodeSource: aStringCodeSource inProtocol: aSymbolCategoryName self createMessageInClass: aClass withCodeSource: aStringCodeSource inProtocol: aSymbolCategoryName inClassSide: false. Nice to see that you use traits :) = Keep working. I still believe that a windowSpec based on a literal array is better than a byte array. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] SocketconnectTo:port: bug? (was: OSProcess question)
I get a walkback from this: Socket newTCP connectTo: (NetNameResolver addressFromString: '127.0.0.1') port: 8086. Is this a known bug? The reason I am asking is that it causes test failures in the OSProcess test suite. Thanks, Dave ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Debugger fails to launch after stacktrace is dumped to SqueakDebug file
http://code.google.com/p/pharo/issues/detail?id=1249 I marked it as 1.0 It was reported by John Toohey Best Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [ANN] STicky
STicky is a pluggable real-time evaluator and/or translator workspace aimed to learn languages. For a quick overview please take a look at the presentation video: http://www.youtube.com/watch?v=b9uUIEaGyoU The Smalltalk evaluator could be useful in learning courses or for newbies typing expressions, but other translators/evaluators may help with more advanced usage, it all depends of the source and target languages you're using. Some default external translators, which does the real job, were included : Smalltalk to JavaScript (ST2JS by Diego Gomez Deck) Smalltlak to Java (Smalltalk2Java by Alexandre Bergel) Smalltalk to SQL (ROE by Avi Bryant) Smalltalk to AST nodes (Marcus Denker et al) HTML validator (Todd Blanchard) JSON to Smalltalk (Tony Garnock-Jones et al) (...contact me if you want to add your translator in the release, a facility to automatic installation of translators is provided) You can easily plug translators and the workspace will update the current contents dynamically inside a sticky-like dialog or a fixed pane, the updater interface was decoupled to make possible other kinds of widgets too, but this is a bit experimental. Downloads from: http://www.squeaksource.com/STicky.html Comments are welcome. Hernán ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] key pressed
Hi, How can I check whether a certain key is pressed (for example, a modifier like Shift)? Cheers, Doru -- www.tudorgirba.com If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [squeak-dev] [ANN] STicky
Its an awesome. It what i want cause i smalltalk beginer On Sun, Sep 27, 2009 at 01:20, Hernán Morales Durand hernan.mora...@gmail.com wrote: is a pluggable real-time evaluator and/or translator workspace ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] feedback on CLFramework
Stéphane Ducasse-2 wrote: Use Smalltalk way of formatting code. getFiles: aStringPathOfDirectory | aFileDirectory fullPathOfFile aCollection | aFileDirectory := CLFileDirectory on: aStringPathOfDirectory. aCollection := Bag new. aFileDirectory fileNames do: [:nameOfFile | fullPathOfFile := aFileDirectory fullPathFor: nameOfFile. aCollection add: fullPathOfFile]. ^aCollection. If you give me access I can reformat everything. Sorry, but i don´t like that format of code. For me is not readable. I don´t know when starts a block or if is a loop or condition block.That problem is more big when exists various identations. I´m coming of VB and C# and that way seems anarchist for me :) my cerebellum is limited for that way of write code. Why my format not is Smalltalkish way? Perhaps I´m wrong (i have short time with that language) but I believe indeed than Smalltalk don´t have a style defined (Thanks to God) Stéphane Ducasse-2 wrote: Add some comments. In the examples category there is no class comments so I have no idea about what I'm reading. Yes. I´m not add comments basically for my poor english. Today i could try it. Is a relax work for sunday :) Stéphane Ducasse-2 wrote: Nice to see that you use traits :) I´m miss it in another languages :) Stéphane Ducasse-2 wrote: Keep working. I still believe that a windowSpec based on a literal array is better than a byte array. Of course, but I don´t know do it of another way. Literal array is very complicated for me. Xml serialization and Moose serialization don´t be possible. The code generated is HUGE, and fails with complex composite morphs. The one way for me is a mechanism where each morph write his state in a stream. All states togethers will build the final morph. I believe that mechanism works, is elegant and readable. And is easy detect problems too, but i need a little more of time for do it. I want implement various widgets ( a grid is MUCH needed ) and last, before of 1.0 version, the serialization mechanism. Thanks for the feedback :) PS. I added recently the CLSplitterPanel widget - http://www.youtube.com/watch?v=qbd9bbfxNB4 Regards -- View this message in context: http://n2.nabble.com/Re-feedback-on-CLFramework-tp3718474p3718991.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] key pressed
Hi Tudor, You can check the implementation of FixedIPluggableTextMorphkeyStroke: and HandMorph STicky protocol category in my recent STicky project, http://www.squeaksource.com/STicky.html Cheers, Hernán 2009/9/26 Tudor Girba tudor.gi...@gmail.com: Hi, How can I check whether a certain key is pressed (for example, a modifier like Shift)? Cheers, Doru -- www.tudorgirba.com If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] key pressed
+1 to Sig's comments. Another problem with looking at the current state vs. state from an event is that the current state is just that, and often differs (covertly and frustratingly) from the user's intentions. Such problems often arise with mouse cursor positions. Bill -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Saturday, September 26, 2009 6:25 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] key pressed 2009/9/27 Tudor Girba tudor.gi...@gmail.com: Hi, How can I check whether a certain key is pressed (for example, a modifier like Shift)? Depends on context. In Morphic, just take an event (mouse event or keyboard event) and send #shiftPressed, or #controlKeyPressed, or whatever. Another way is to ask the Sensor for same things, but i wouldn't do that, because to my opinion this is the wrong way, because Sensor is low-level object, which should be hidden from the eyes of developer, and normally, if you need to use it, it means that you doing something wrong :) Cheers, Doru -- www.tudorgirba.com If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
