- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fogbugz Area

by Esteban Lorenzano

> On 27 Apr 2015, at 16:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > External projects have various "Areas" - External, Misc, Image. Which is the > appropriate one and will that automatically make the monkey skip the issue? None. Also the monkey now can check also configurations so you do not need to skip them (but in case you still want to skip them, you can use the tag ânoMonkeyâ). Esteban > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Fogbugz-Area-tp4822198.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 27, 2015

Re: [Pharo-dev] Tx Pass

by Sean P. DeNigris

Sean P. DeNigris wrote > Design Questions... I also started https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/TxTextRo… to capture the result ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Pass-tp4822173p4822202.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

Re: [Pharo-dev] Tx Pass

by Sean P. DeNigris

Sean P. DeNigris wrote > Issue 15414: TxText Cleanup for Pharo 5.0 #1 > https://pharo.fogbugz.com/default.asp?15414 It would be great to get this into the image ASAP so I can keep working on it :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Pass-tp4822173p4822199.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

Fogbugz Area

by Sean P. DeNigris

External projects have various "Areas" - External, Misc, Image. Which is the appropriate one and will that automatically make the monkey skip the issue? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Fogbugz-Area-tp4822198.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

Re: [Pharo-dev] Tx Pass

by Sean P. DeNigris

Sean P. DeNigris wrote > I did a first pass I made some of the more obvious fixes/enhancements... Issue 15414: TxText Cleanup for Pharo 5.0 #1 Fixes in Tx repo: TxText-Styler-SeanDeNigris.4 - Update for TxCursorAttribute to TxMouseCursorAttribute rename TxText-Model-SeanDeNigris.52 Higher-level: - Rename TxCursorAttribute to TxMouseCursorAttribute; we must differentiate between the insertion cursor, which is already named the "Cursor" Cleanups: - Rename TxModel>>#setNewContents, which does not follow Constructor Parameter Method, to #initializeContents - Many comment enhancements - Several small refactorings - Extract TxInterval>>#normalize to return a copy with start < end; this logic was duplicated everywhere TxText-Athens-SeanDeNigris.45 Higher-level: - Initial TxBlockCursor implementation as an experiment, mostly copied from TxCaretCursor. It might be to have a pluggable drawing strategy instead of a whole separate class... Cleanups: - Many comment enhancements - Several small refactorings ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Pass-tp4822173p4822193.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

Re: [Pharo-dev] Fixes to External Pharo Projects

by Esteban Lorenzano

individual package in the repo. > On 27 Apr 2015, at 16:13, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > How do we commit fixes to e.g. Tx? Just commit the individual packages to the > Tx repo? Commit a slice there? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Fixes-to-External-Pharo-Projects-tp4822177.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 27, 2015

Re: [Pharo-dev] [NB] NBExternalArray not working for complex types?

by Henrik Johansen

> On 26 Apr 2015, at 7:29 , Max Leske <maxleske(a)gmail.com> wrote: > > Hi guys > > I have a problem with NBExternalArray. AFAICT the generated assembly should be able to handle arbitrary elements in the array (as long as they are all of the same type). The operations required to read / write an element are given by the external type specified for the collection (e.g âcharâ or âintâ). All of this works wonderfully for char, int, NBExternalAddress etc. But Iâm trying to get it working for strings. So here is the code that I would expect to work: > > arrayClass := NBExternalArray anonymousSubclassInitElementType: 'String'. > array := arrayClass new: 1. > array at: 1 put: âfoo'. > array at: 1. ââ> should procude âfooâ, but produces arbitrary stringsâ > > I can make it work with NBExternalAddress of course but I donât want to if I can avoid it. > > Iâd appreciate it if someone (Nicolai?) could take a look at NBExternalArray>>emitRead / emitWrite and see if thereâs an easy solution. Especially for strings I donât think it should be too hard since all thatâs needed is already present in the string handling facilities. > > Cheers, > Max There's a solution, but I doubt you could call it simple. NBExternalArray is meant to hold const sized objects, so is allocated with the proper amount of slots up front. If you want it to hold pointers to variably sized objects (like strings), since we can't pin the objects, they need to be copied (well, would have to do that anyways for Strings, which need it'd need to do dynamic allocation (and freeing when appropriate), so emitWrite would become quite a bit more complicated, + necessary object finalization would have to occur. You *can* work around it, by using an element type that is externally allocated, but it adds quite a bit of boilerplate, here's the workspace PoC code: string := 'herruâ¬'. bytes := ZnUTF8Encoder new encodeString: string. mem := NativeBoost allocate: bytes size + 1. NativeBoost memCopy: bytes to: mem size: bytes size. arrClass := NBExternalArray anonymousSubclassInitElementType: 'char *'. arr := arrClass new: 1. arr at: 1 put: mem. ZnUTF8Encoder new decodeBytes: (arr at:1) readString asByteArray Cheers, Henry

April 27, 2015

Fixes to External Pharo Projects

by Sean P. DeNigris

How do we commit fixes to e.g. Tx? Just commit the individual packages to the Tx repo? Commit a slice there? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Fixes-to-External-Pharo-Projects-tp4822177.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

Tx Pass

by Sean P. DeNigris

Just like Bloc (which has *great* class comments), I think it's crucial to document the high level design decisions in Tx. I did a first pass and noted some initial impressions... Design Questions: - TxModel - what is the advantage of a double linked list vs the old Text implementation? - TxLayoutViewMorph vs. TxTextEditorMorph - I'm not clear on the purpose/relationship/pattern here? Implementation Questions: - TxBasicSpan#< seems overly complex. Why two-way searching. Was it the result of profiling? Intuition? Random? - TxTextEditorMorph>>#openInWindowWithText: says not part of API, but this code is pretty much the only way to use it for now, right? - applyAttribute:to: sends an unimplemented message, but I'm not sure what should be done here - Why no strike fonts? Why is Verdana commented out in TxFontAttribute class>>#defaultValue? - TxLayoutViewMorph class>>#text: sends #asTxModel to argument, but TxTextEditorMorph doesn't. Which one is right? I think there's not much harm in sending it in both to make it a bit easier for users... - TxBasicViewMorph>>#fullDrawOnAthensCanvas: checks if fullBounds are visible on canvas, then checks #bounds again. Are both necessary? Tx already seems very usable! I'm starting to play with it in one of my projects... I've been dreaming about this for a long time :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Pass-tp4822173.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 27, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50012 Home: https://github.com/pharo-project/pharo-core

April 27, 2015