- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Artefact - a PDF framework

by Christian Haider

> Von: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project- > bounces(a)lists.gforge.inria.fr] Im Auftrag von Nicolas Cellier > > What are we speaking of exactly ? > Here are two different features of different level : I'll answer for PDF4Smalltalk > 1) the composition : > - 1a) compose a document with a given structure and a style sheet > For the structure, think of section / subsection etc... No (use Report4PDF) > For the style sheet, think of LaTeX article, book or report.sty No > For the composition, think of page layout (when to insert page break, > compose on several columns, wrap text around figures etc...). No (use Report4PDF) > High level composition rules for example might forbid to begin a sub- > section at the bottom of a page. No (use Report4PDF) > - 1b) compose a document from a sequence of lower level graphics (including > composed paragraph). > The composition rule might be very simple, just compose one item over > the other, insert page break if it does not fit on page. No (use Report4PDF) > For composed text, page break can occur at any composed line or only at a > carriage return. No (use Report4PDF) > A good example was VisualWorks Document class. > 2) the fileout of the composition in pdf format > - 2a) including PDF document structuring conventions (DSC) if ever they exist > at Smalltalk level. Fully supported > - 2b) without DSC, but only low level graphics Fully supported > > Composing the paragraph also means having all the font metrics available > plus eventually all the kerning rules, plus rules for inter-word spacing (non > speaking of alignment and tabulation options which should be part of > paragraph spec). No, but Type-1 fonts and OpenType(PS) fonts are implemented so that this information is available. > > Which PDF library is doing what exactly ? > Are the low level Graphics > - entirely PDF library dependent (which would mean no preview via Smalltalk > graphics), Yes > - entirely dialect dependent (using exclusively > VisualPart/Wrapper/GraphicsContext or Morph/Form/Canvas) No > - mixed (transformation of PDF graphics into Smalltalk graphics for preview > and/or translation of Smalltak graphics to PDF graphics) In the last two cases, > porting VW <->Squeak/Pharo might not be immediate ;) No, there is now viewing - just PDF objects Think of PDF4Smalltalk as a backend for graphics programs which do layout and such. With TrueType fonts and bitmap graphics, it should be easy to hook it up as GraphicsContext for VW or as Canvas(?) for Squeak/Pharo. Christian > > What about composition? > > Nicolas > > 2012/5/2 Yanni Chiu <yanni(a)rogers.com>: > > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: > >> > >> > >> Stephan Eggermont wrote > >>> > >>> > >>> Don't you think it would be much less work to port Christian > >>> Haider's work to Pharo? > >> > >> > >> I was thinking the same thing. The usual Smalltalk duplication of > >> effort seems to have been taken to new heights with PDF libs ;-) > > > > > > I've loaded Artefact, browsed the code, tried the demos. > > > > I've not seen the code for PDF4Smalltalk, because I can't figure out > > how to browse it without VW. However, looking at the examples at: > > Â https://gitorious.org/pdf4smalltalk/pages/Examples > > I get the (possibly mistaken) impression that the two frameworks do > > slightly different things, but the final result is a PDF in both cases. > > > > Looking at the PDFDemos of Artefact, it's clear how text and tables > > can be written. However, looking at the PDF4Smalltalk examples, it > > looks like you have to position the text and tables in your own code. > > Of course, I may be completely wrong about PDF4Smalltalk, since I've > > not seen the full code base. > > > > > >

May 2, 2012

Re: [Pharo-project] [Fwd: Re: [Newbies] Remove trailing spaces of aString]

by StÃ©phane Ducasse

Ben the original UIFinder was showing the methods effectively executed using a * and the implementors without. Now when you show the results you do not distinguish any of them. Stef On Apr 29, 2012, at 1:42 PM, Benjamin wrote: > :) > > Good idea ;) > I will do that, it shouldn't be so difficult ^^ > > Ben > > On Apr 29, 2012, at 5:00 AM, Ben Coman wrote: > >> Ah. ha... Very Good. For the whole time I've used Pharo the last 12 months I've had a misconception about Examples. >> I thought they must have been Example coded somewhere like GLMBasicExamples, the MOEaselExamples and these somehow flagged for searching - and that I never got any results because of some lacking implementation. >> >> Here is some usability feedback then... >> >> 1. The help text in the bottom pane says "for further informations, print 'FinderUI methodFinderExplanation' ". >> Rather better would be when [Examples] is selected, that bottom pane is filled with "print 'FinderUI methodFinderExplanation". >> 2. The help text in the bottom pane says "In these four modes, you can also tick the 'Use RegEx' checkbox." >> might say "In the first four modes and sort [Examples] to appear at the bottom of the list. >> Actually that text is a carry over from when Pramgas was not an option and only the first three modes had RegEx. >> >> 3. The help text in the bottom pane says "The 'Select classes'...." and "The 'All classes'...." >> but the actual buttons are <Choose Packages> and <All packages> >> >> 4. Optional extra, while <Regexp> is selected, put some help text for regular expressions with examples in the bottom pane. >> >> I've logged http://code.google.com/p/pharo/issues/detail?id=5733 >> >> cheers -ben >> >> Benjamin wrote: >>> If you use Pharo, you can also do that >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------ >>> >>> >>> >>> Note that you have to change 'Selector' with 'Example', and then you can type a list of arguments separated by a dot and the expected result. >>> (If you want some inner details, it will do something like methodFor: {_WHAT_YOU_HAVE_ENTER_}) >>> >>> Have fun, >>> Ben >>> >>> >>> >>> On Apr 28, 2012, at 4:00 PM, Ben Coman wrote: >>> >>> >>>> I just discovered this new "bit of magic" from the Newbies list. My first impression playing with it is that MethodFinder>>methodFor: should be somehow more prominent in Tools>Finder and also in PharoByExample book. Quite a unique feature and demonstration of Smalltalk power for newcomers. >>>> >>>> cheers -ben >>>> >>>> Am 2012-04-27 um 17:27 schrieb H. Hirzel: >>>> >>>> >>>>> Hello >>>>> I use Squeak 4.3, Update 11860. >>>>> I want to remove the trailing spaces and or tabs and LF of a String >>>>> something like >>>>> 'abc >>>>> ' >>>>> should just be >>>>> 'abc'. >>>>> If I remember that there was a method in class String to something >>>>> like this. Is this correct? >>>>> Is there a package with additional String convenience methods? >>>>> >>>> you probably want >>>> >>>> 'abc ' withoutTrailingBlanks >>>> >>>> You can find that method by evaluating or printing >>>> >>>> MethodFinder methodFor: { {'abc '} . 'abc' } (a list with arguments {'abc '} and an expected result ( 'abc' )) >>>> >>>> HTH >>>> >>>> Best >>>> -Tobias >>>> _______________________________________________ >>>> Beginners mailing list >>>> Beginners(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners >>>> >>>> >>>> >>>> >>> >>> >> >> > >

May 2, 2012

Re: [Pharo-project] Adding hooks for well known events in morphic

by StÃ©phane Ducasse

Indeed rationalizing the hooks and removing the changed/update mechanism would be good. On Apr 27, 2012, at 8:58 PM, Guillermo Polito wrote: > I've made up a list with all the useful morphic widget I've found in a alpha alpha alpha 2.0 image. > I'd like to put in those widgets empty hooks like: > > Morph>>triggerOnShow > "hook" > > for common events widgets provide usually in MVC frameworks. > That means not changing the whole interface nor refactoring everything. Just adding the hooks. What we were talking with Mariano (I hate you for putting ideas in my head) today in the train was to add those empty hooks and put senders for them, what should be easy. This way we can start to homogenize morphic a bit. > > Most likely, in a not so far future, those empty hooks could be replaced by something like: > > Morph>>triggerOnShow > self announcer announce: (MorphShowAnnouncement show: self) > > Now, here is a list of the most important widgets i've found (I could've missed some) and events they should trigger. I'm not taking into account new multitouch interfaces and stuff. > > For all widgets > onShow > onDelete > onKeyUp > onKeyPress > onKeyDown > onClick > onMouseDown > onMouseUp > onDoubleClick > onDragged > onDropped > onMove? > onResize? > > For all containers > onChildAdded > onChildRemoved > > "Widgets" > > Check/Radio -> CheckboxButtonMorph/SimpleSwitchMorph > onSelectionChanged > > List/Grids -> PluggableListMorph/PluggableMultiColumnListMorph/LazyListMorph/MulticolumnLazyListMorph > onSelectionChanged > > Button -> PluggableButtonMorph/SimpleButtonMorph/MultistateButtonMorph > onClick > > Label -> LabelMorph/FuzzyLabelMorph /MultistateLabelMorph > > Progress Bar-> SystemProgressBarMorph > > Slider -> Slider/PluggableSliderMorph > onSelectionChanged > > Text handling -> TextMorph/PluggableTextMorph > onSelectionChanged > > Field Handling -> PluggableTextFieldMorph/PluggableTextEditorMorph > > Tree -> MorphTreeMorph > onSelectionChanged > onExpandItem > onCollapseItem > > Combo box -> DropListMorph/EditableDropListMorph /SearchMorph/MorphDropListMorph > onSelectionChanged > > Menues -> MenuMorph + friends > onClick (for menu item probably) > > Image -> ImageMorph/ImagePreviewMorph > > Diff -> DiffMorph > > Color Presenter -> ColorPresenterMorph > > Color chooser -> ColorChooserMorph/HSVColorSelectorMorph / SVColorSelectorMorph > onSelectionChanged > > Task var -> TaskbarMorph > > > "Containers" > ScrollPane > Windows -> SystemWindow/PluggableSystemWindow /StandardWindow > Dialog window -> DialogWindow & (lots of) subclasses > Panel -> PanelMorph & subclasses / PluggablePanelMorph > > Tabs -> TabGroupMorph (Other Tab stuff -> PluggableTabBarMorph + PluggableTabButtonMorph ) > onSelectionChanged > > > Guille

May 2, 2012

Re: [Pharo-project] Adding hooks for well known events in morphic

by StÃ©phane Ducasse

On Apr 28, 2012, at 2:39 PM, GastÃ³n Dall' Oglio wrote: > Hi Guillermo. > > When you combine these triggers with ads (as in your example), I see an analogy with the model of qt ui, see: > http://qt-project.org/doc/qt-4.8/signalsandslots.html > > In effect: > "A signal is emitted when a particular event occurs." -> A Announcement is send when a particular event (trigger) occurs. > " Qt's widgets have many predefined signals, but we can always subclass widgets to add our own signals to them" -> Morphic widgets have many predefined triggers, but we can always subclass widgets to add our own triggers to them. > "A slot is a function that is called in response to a particular signal. " -> A AnnouncementSubscription is ? that is used in response to a particular announcement. > > It's a mechanic for decouple between sender and interested in event occurrence. > > > As you surely know Morphic Designer follows basic ideas of the QtDesigner: > https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki… > > Look at doc here (I never see code of this project), this approach not use announcement framework, but a signal implementation: > https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki… I do not see the difference between signals and event. And yes we look at the code, it is not a really good idea to use thisContext for every little notifications.

May 2, 2012

[Pharo-project] NativeBoost help

by Luc Fabresse

Hi Igor and other NB Gurus, A group of students is trying to use NativeBoost to wrap the OpenCV C image library. The problem we are facing is that the function cvSize return a struct. typedef struct { int width; int height; } CvSize; CV_INLINE CvSize cvSize( int width, int height ); But the NBExternalStructure seems to not support that if I understood correctly. NBExternalStructure>>coerceReturn: gen " ... should we support handling return of external structures? " self error: 'returning pointer to structure?' Did I miss something? Any idea or workaround? Thanks, Luc

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Nicolas Cellier

What are we speaking of exactly ? Here are two different features of different level : 1) the composition : - 1a) compose a document with a given structure and a style sheet For the structure, think of section / subsection etc... For the style sheet, think of LaTeX article, book or report.sty For the composition, think of page layout (when to insert page break, compose on several columns, wrap text around figures etc...). High level composition rules for example might forbid to begin a sub-section at the bottom of a page. - 1b) compose a document from a sequence of lower level graphics (including composed paragraph). The composition rule might be very simple, just compose one item over the other, insert page break if it does not fit on page. For composed text, page break can occur at any composed line or only at a carriage return. A good example was VisualWorks Document class. 2) the fileout of the composition in pdf format - 2a) including PDF document structuring conventions (DSC) if ever they exist at Smalltalk level. - 2b) without DSC, but only low level graphics Composing the paragraph also means having all the font metrics available plus eventually all the kerning rules, plus rules for inter-word spacing (non speaking of alignment and tabulation options which should be part of paragraph spec). Which PDF library is doing what exactly ? Are the low level Graphics - entirely PDF library dependent (which would mean no preview via Smalltalk graphics), - entirely dialect dependent (using exclusively VisualPart/Wrapper/GraphicsContext or Morph/Form/Canvas) - mixed (transformation of PDF graphics into Smalltalk graphics for preview and/or translation of Smalltak graphics to PDF graphics) In the last two cases, porting VW <->Squeak/Pharo might not be immediate ;) What about composition? Nicolas 2012/5/2 Yanni Chiu <yanni(a)rogers.com>: > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: >> >> >> Stephan Eggermont wrote >>> >>> >>> Don't you think it would be much less work >>> to port Christian Haider's work to Pharo? >> >> >> I was thinking the same thing. The usual Smalltalk duplication of effort >> seems to have been taken to new heights with PDF libs ;-) > > > I've loaded Artefact, browsed the code, tried the demos. > > I've not seen the code for PDF4Smalltalk, because I can't figure out how to > browse it without VW. However, looking at the examples at: > Â https://gitorious.org/pdf4smalltalk/pages/Examples > I get the (possibly mistaken) impression that the two frameworks do slightly > different things, but the final result is a PDF in both cases. > > Looking at the PDFDemos of Artefact, it's clear how text and tables can be > written. However, looking at the PDF4Smalltalk examples, it looks like you > have to position the text and tables in your own code. Of course, I may be > completely wrong about PDF4Smalltalk, since I've not seen the full code > base. > >

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Christian Haider

> Von: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project- > bounces(a)lists.gforge.inria.fr] Im Auftrag von Yanni Chiu > > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: > > > > Stephan Eggermont wrote > >> > >> Don't you think it would be much less work to port Christian Haider's > >> work to Pharo? > > > > I was thinking the same thing. The usual Smalltalk duplication of > > effort seems to have been taken to new heights with PDF libs ;-) > > I've loaded Artefact, browsed the code, tried the demos. > > I've not seen the code for PDF4Smalltalk, because I can't figure out how to > browse it without VW. Unfortunately, you can't :-( > However, looking at the examples at: > https://gitorious.org/pdf4smalltalk/pages/Examples > I get the (possibly mistaken) impression that the two frameworks do slightly > different things, but the final result is a PDF in both cases. > > Looking at the PDFDemos of Artefact, it's clear how text and tables can be > written. However, looking at the PDF4Smalltalk examples, it looks like you > have to position the text and tables in your own code. Of course, I may be > completely wrong about PDF4Smalltalk, since I've not seen the full code > base. I have not looked at Artefact, but from what I read, these are different things, I guess. PDF4Smalltalk is a system library providing full access to PDF. PDF objects are regular Smalltalk objects which you can read from PDF files or create them with code and write them as PDF. The PDF basics are quite complete and robust (I use it for a few years in production now), but there are also lots of features desired :-) (TrueType fonts and bitmap images to name a few). It deals purely with PDF and does not add any higher concepts like tables and other layouting facilities - in fact not even proper classes for graphics or text... (high on my list when I find time). It is like painting on a canvas: you are completely responsible for the placement of everything. To deal with that, Bob Nemec implemented Report4PDF which uses Seaside like layouting for a report generator. It is done, works and is quite nice! See http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.h tml I'd love if someone would port this to Pharo! I would help with answering questions, but I have not time to do anything substantial in the moment... Cheers, Christian

May 2, 2012

Re: [Pharo-project] browsing versions of a method

by Mariano Martinez Peck

On Wed, May 2, 2012 at 9:43 AM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Wed, May 2, 2012 at 1:00 AM, Francisco Garau <francisco.garau(a)gmail.com > > wrote: > >> Hi - I've noticed we have a new way of showing diffs between two versions >> of a method. Very nice! > > > yes, I did it with Ben in the sprint ;) > > >> >> But it would be more useful if the user had the choice of which two >> versions to compare. >> >> > You can right click a version and you have the option "Compare to current" > and "compare to version..." > > The problem is that they have not been fixed with the nice diff so it > opens an ugly popup diff. > Did it. Wanna test/review please? http://code.google.com/p/pharo/issues/detail?id=5781 > > >> For example, if I maje 10 changes to method Date>>today I would like to >> compare my first and last versions... >> >> Cheers, >> Francisco >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 2, 2012

Re: [Pharo-project] Mouse handler on a morph

by Chris Muller

This is because, under rare circumstances, it is desirable to do something in/on/to the desktop based on the position in the local morph. To get the local coordinates look for a method with the word "global" in it -- globalToLocal: or something like that. It's in Squeak, not sure whether this is still in Pharo though.. If anything, you could always just subtract the upperleft coordinate of your window from the MouseEvent's position.. On Wed, May 2, 2012 at 9:02 AM, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Hi. > > I would like to know if it's possible to add a mouse handler on a specific > morph ? > I have a window and i would like to know the position of my mouse only in > this window. > > For exemple i also use : > > self on: #mouseDown send: #captureMouse: to: self. > > But it give me the mouse position in pharo environment and not only in my > window. > > > Thanks :) > > -- > Douaille Erwan <douaille.erwan(a)gmail.com>

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Yanni Chiu

On 02/05/12 10:53 AM, Sean P. DeNigris wrote: > > Stephan Eggermont wrote >> >> Don't you think it would be much less work >> to port Christian Haider's work to Pharo? > > I was thinking the same thing. The usual Smalltalk duplication of effort > seems to have been taken to new heights with PDF libs ;-) I've loaded Artefact, browsed the code, tried the demos. I've not seen the code for PDF4Smalltalk, because I can't figure out how to browse it without VW. However, looking at the examples at: https://gitorious.org/pdf4smalltalk/pages/Examples I get the (possibly mistaken) impression that the two frameworks do slightly different things, but the final result is a PDF in both cases. Looking at the PDFDemos of Artefact, it's clear how text and tables can be written. However, looking at the PDF4Smalltalk examples, it looks like you have to position the text and tables in your own code. Of course, I may be completely wrong about PDF4Smalltalk, since I've not seen the full code base.

May 2, 2012