January 2015 - Pharo-dev - lists.pharo.org

Fwd: 14827 ProtoObject>>pointersTo failing circular references

by Ben Coman

I am revisiting my PointerDetective tool, which relies heavily on ProtoObject>>pointersTo. The example I recorded at the repository home page is currently locking & crashing the image due to #pointersTo being unable to handle the circular reference. This "must" have been working on Windows at least around August 2014, but I've been unable to reproduce a working case since my Windows laptop died and I've since moved to OSX. On OSX, in a fresh image 40467 and latest vm 402, the following crashes the image... testObject := 'TEST'. ref1 := { testObject. nil }. ref2 := { ref1 }. ref3 := { ref2 }. ref1 at: 2 put: ref3. "note the reference loop this creates" testObject pointersTo inspect. OSX Memory Monitor shows memory usage shoot from 50MB to >500MB in a few seconds, then usually the image crashes, but sometimes just hangs. I've logged... https://pharo.fogbugz.com/default.asp?14827 cheers -ben

Jan. 30, 2015

New Cog VMs available

by Eliot Miranda

at http://www.mirandabanda.org/files/Cog/VM/VM.r3236/ CogVM binaries as per VMMaker.oscog-eem.1029/r3236 Fix stupid, stupid bug in copying vm profile samples between buffers when the circular buffer index has wrapped. Fix monumental blunder in jitted store-check code. The saved registers mask needs to be the *or* of the value reg and the caller-saved registers, not the *and*!! Make the pin primitives Spur-only. Never inline mapStackPages, for debugging. Spur: Reduce the max num literals in the alternate header format to 15, and steal the bit for the Sista optimized method flag. Make postBecomeAction's stack sweep only occur in Spur (fix regression). Refactor so that the scan is not inlined. Don't assume newMethod is non-immediate in post-become actions. Fix stack adjust slip in primitiveSmallFloatTimesTwoPower Make ensureBehaviorHash: fail for uninitialized behaviours and hence fix the Behavior basicNew basicNew hang. Optionalize some api methods the Spur Cogit doesn't use. Rename and correct ensureSemaphoreForwardedThroughContext: to ensureSemaphoreUnforwardedThroughContext:, its intended function. Make shouldRemapObj: filter-out objects already in newSpace since mapStackPages, via mapInterpreterOops, can visit objects twice in a scavenge, GC, compact sequence. Make sure the caller (& saved) context(s) in base frames stack page are followed post-become in followForwardingPointersInStackZone:. Fix bad bug introduced in become changes in VMMaker.oscog-eem.841 through 844. The class table contains puns, e.g. using Array and WeakArray. These class index puns must not mislead the allInstances primitive into concluding that the class in question is at multiple indices and wrongly purge it. Fix slip in primitivePin. Also be lenient w.r.t. unpinning married contexts. Move the check down into StackInterpreter's version. This allows e.g. self allObjectsDo: [:o| o unpin] Bow to the inevitable and add a manual override for primitive accessor depth. Use it in at: & at:put:. If manual override is not used then the automatically computed depth is too deep because of context access. Newspeak: Integrate Ryan's newer absent receiver sends, which first apeared in VMMaker.oscog-eem.919, abandoned because of Glue issues now resolved. Includes nice refactoring of absent send argument marshalling into its own routine. LargeIntegersPlugin: Remove/fix assumption of 32-bit digit length in normalization routines. -- best, Eliot

Jan. 30, 2015

Re: [Pharo-dev] Create window group for Playground

by Peter Uhnak

I'm not sure if it still works but as a workaround it was possible to drag the playground into existing window group. Peter -----Original Message----- From: "Torsten Bergmann" <astares(a)gmx.de> Sent: â1/â29/â2015 6:51 PM To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] Create window group for Playground Previous (and still included) Workspace, Transcript and Nautilus provide Window grouping by selecting "Create window group" from the window menu and then dragging two windows onto each other. They are grouped together in one single window then and each one gets a tab. Looks like Playground does not support this feature yet - so currently I end up with many many windows which for me is a step backwards compared to working with workspaces in Pharo 3.0 What is necessary to provide this for the Playground so we have a common behavior for all the tools and a cleaner desktop? Thanks T.

Jan. 29, 2015

Re: [Pharo-dev] [ANN] PUnQLite NoSQL database project updated

by Tudor Girba

Hi Torsten, This sounds very interesting. I tried to play with it on Mac, but I got a bit stuck. Here is what I did: - I downloaded the UnQLite sources from: http://unqlite.org/db/unqlite-db-20130825-116.zip - In that folder I did: gcc -m32 -c unqlite.c gcc -m32 -dynamiclib -o unqlite.dylib unqlite.o - I then copied the unqlite.dylib file in the plugins folder: Pharo.app/Contents/MacOS/Plugins - I started a Pharo 4 image with the corresponding VM - I loaded the stable version of PUnQLite from the ConfigurationBrowser - I executed without errors the code you mentioned: |db| db := PqDatabase open: 'comments.db'. db disableAutoCommit. db transact: [ Object subclasses do: [:cls | | key | key := cls asString. db at: key put: cls comment ] ]. db close. ==> However I do not get a comments.db file/folder, and the Database Browser does not show anything. Am I doing something wrong? Cheers, Doru On Thu, Jan 29, 2015 at 9:20 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > are you in need for really simple out of image persistency? > > If you like to use a small RDBMS solution with Pharo then there is the > embeddable SQLite > shared library and NBSQLite3 project [1] to access it. Combine it with > Glorp [2] and you do > not have to fight too much with SQL. > > On the other end of persistency world there are the so called "NoSQL > databases" and beside > Mongo and all the others that require special setup etc. there is this > wonderful small UnQLite > embeddable database [3] that similar to SQlite world only requires a > simple library. > > Thanks to Masashi Umezawa there is a nice wrapper for Pharo already to > access this > tiny embeddable NoSQL database called "PUnQLite" [4] and [5], also > including access to > the Jx9 machinery of UnQLite. It is really cool that he made this > available. > > This week I updated "PUnQLite" a little bit: > - refactored the Native boost wrapper for UnQLite (using shared pools, > ...) > - documented classes > - added a help topic > - fixed a bug in cursors when accessing the keys in an empty database > - and finally added a small spec based tool to work with a database > file (see attached screenshot) > One can use it to open an unqlite database, show the key value pairs > and remove or add entries. > > If you are in latest Pharo 4 already you can load all of that right from > the config browser. Be aware > that you need the external unqlite shared library which is downloaded and > extracted into a folder > "pharo-vm" when loading the config. > > For instance on Windows it automagically downloads a file > "pharo-vm/unqlite.dll" below your > image directory and you just have to copy this shared library file to the > folder where your > VM (Pharo.exe) resides. Havent tried on other OS platforms. > > From the Pharo side using the UnQLite database basically works like having > some kind > "external dictionary" in a database file. Just run that in a workspace: > > |db| > db := PqDatabase open: 'comments.db'. > db disableAutoCommit. > db transact: [ > Object subclasses do: [:cls | | key | > key := cls asString. > db at: key put: cls comment ] > ]. > db close. > > Then open the "Database Browser" from the world menu and open the > "comments.db" file. > You can browse the keys and values, remove entries or add new. A filter > for the keys > is also included. Nothing fancy but hope you like it or find it usable. > > Couldnt make it to PharoConf 2015 but I hope all participants enjoy their > time there. > Keep the others updated by using the #pharodays2015 on Twitter. Have fun! > > Bye > T. > > > [1] > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104… > [2] > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-January/0… > [3] http://unqlite.org/ > [4] https://github.com/mumez/PunQLite > [5] http://smalltalkhub.com/#!/~MasashiUmezawa/PunQLite -- www.tudorgirba.com "Every thing has its own flow"

Jan. 29, 2015

Create window group for Playground

by Torsten Bergmann

Previous (and still included) Workspace, Transcript and Nautilus provide Window grouping by selecting "Create window group" from the window menu and then dragging two windows onto each other. They are grouped together in one single window then and each one gets a tab. Looks like Playground does not support this feature yet - so currently I end up with many many windows which for me is a step backwards compared to working with workspaces in Pharo 3.0 What is necessary to provide this for the Playground so we have a common behavior for all the tools and a cleaner desktop? Thanks T.

Jan. 29, 2015

Re: [Pharo-dev] [ANN] PUnQLite NoSQL database project updated

by Ben Coman

How would you feel about calling it "PhunQLite" ? * Ph as in Pharo * Phun = fun * PhunQ = funky * PhunQLite = funky light Chose you logo here http://tinyurl.com/funkylights ? :) I guess its already a Punky http://tinyurl.com/punkyyy cheers -ben On Thu, Jan 29, 2015 at 9:34 PM, Masashi UMEZAWA <masashi.umezawa(a)gmail.com> wrote: > Hi Torsten, > > Thank you for the update for Pharo 4. It is awesome! > > 2015-01-29 17:20 GMT+09:00 Torsten Bergmann <astares(a)gmx.de>: > > Hi, > > > > are you in need for really simple out of image persistency? > > > > If you like to use a small RDBMS solution with Pharo then there is the > embeddable SQLite > > shared library and NBSQLite3 project [1] to access it. Combine it with > Glorp [2] and you do > > not have to fight too much with SQL. > > > > On the other end of persistency world there are the so called "NoSQL > databases" and beside > > Mongo and all the others that require special setup etc. there is this > wonderful small UnQLite > > embeddable database [3] that similar to SQlite world only requires a > simple library. > > > > Thanks to Masashi Umezawa there is a nice wrapper for Pharo already to > access this > > tiny embeddable NoSQL database called "PUnQLite" [4] and [5], also > including access to > > the Jx9 machinery of UnQLite. It is really cool that he made this > available. > > > > This week I updated "PUnQLite" a little bit: > > - refactored the Native boost wrapper for UnQLite (using shared > pools, ...) > > - documented classes > > - added a help topic > > - fixed a bug in cursors when accessing the keys in an empty database > > - and finally added a small spec based tool to work with a database > file (see attached screenshot) > > One can use it to open an unqlite database, show the key value > pairs and remove or add entries. > > > > If you are in latest Pharo 4 already you can load all of that right from > the config browser. Be aware > > that you need the external unqlite shared library which is downloaded > and extracted into a folder > > "pharo-vm" when loading the config. > > > > For instance on Windows it automagically downloads a file > "pharo-vm/unqlite.dll" below your > > image directory and you just have to copy this shared library file to > the folder where your > > VM (Pharo.exe) resides. Havent tried on other OS platforms. > > > > From the Pharo side using the UnQLite database basically works like > having some kind > > "external dictionary" in a database file. Just run that in a workspace: > > > > |db| > > db := PqDatabase open: 'comments.db'. > > db disableAutoCommit. > > db transact: [ > > Object subclasses do: [:cls | | key | > > key := cls asString. > > db at: key put: cls comment ] > > ]. > > db close. > > > > Then open the "Database Browser" from the world menu and open the > "comments.db" file. > > You can browse the keys and values, remove entries or add new. A filter > for the keys > > is also included. Nothing fancy but hope you like it or find it usable. > > > > Couldnt make it to PharoConf 2015 but I hope all participants enjoy > their time there. > > Keep the others updated by using the #pharodays2015 on Twitter. Have fun! > > > > Bye > > T. > > > > > > [1] > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104… > > [2] > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-January/0… > > [3] http://unqlite.org/ > > [4] https://github.com/mumez/PunQLite > > [5] http://smalltalkhub.com/#!/~MasashiUmezawa/PunQLite > -- > [:masashi | ^umezawa] > >

Jan. 29, 2015

Re: [Pharo-dev] [ANN] PUnQLite NoSQL database project updated

by Masashi UMEZAWA

Hi Torsten, Thank you for the update for Pharo 4. It is awesome! 2015-01-29 17:20 GMT+09:00 Torsten Bergmann <astares(a)gmx.de>: > Hi, > > are you in need for really simple out of image persistency? > > If you like to use a small RDBMS solution with Pharo then there is the embeddable SQLite > shared library and NBSQLite3 project [1] to access it. Combine it with Glorp [2] and you do > not have to fight too much with SQL. > > On the other end of persistency world there are the so called "NoSQL databases" and beside > Mongo and all the others that require special setup etc. there is this wonderful small UnQLite > embeddable database [3] that similar to SQlite world only requires a simple library. > > Thanks to Masashi Umezawa there is a nice wrapper for Pharo already to access this > tiny embeddable NoSQL database called "PUnQLite" [4] and [5], also including access to > the Jx9 machinery of UnQLite. It is really cool that he made this available. > > This week I updated "PUnQLite" a little bit: > - refactored the Native boost wrapper for UnQLite (using shared pools, ...) > - documented classes > - added a help topic > - fixed a bug in cursors when accessing the keys in an empty database > - and finally added a small spec based tool to work with a database file (see attached screenshot) > One can use it to open an unqlite database, show the key value pairs and remove or add entries. > > If you are in latest Pharo 4 already you can load all of that right from the config browser. Be aware > that you need the external unqlite shared library which is downloaded and extracted into a folder > "pharo-vm" when loading the config. > > For instance on Windows it automagically downloads a file "pharo-vm/unqlite.dll" below your > image directory and you just have to copy this shared library file to the folder where your > VM (Pharo.exe) resides. Havent tried on other OS platforms. > > From the Pharo side using the UnQLite database basically works like having some kind > "external dictionary" in a database file. Just run that in a workspace: > > |db| > db := PqDatabase open: 'comments.db'. > db disableAutoCommit. > db transact: [ > Object subclasses do: [:cls | | key | > key := cls asString. > db at: key put: cls comment ] > ]. > db close. > > Then open the "Database Browser" from the world menu and open the "comments.db" file. > You can browse the keys and values, remove entries or add new. A filter for the keys > is also included. Nothing fancy but hope you like it or find it usable. > > Couldnt make it to PharoConf 2015 but I hope all participants enjoy their time there. > Keep the others updated by using the #pharodays2015 on Twitter. Have fun! > > Bye > T. > > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104… > [2] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-January/0… > [3] http://unqlite.org/ > [4] https://github.com/mumez/PunQLite > [5] http://smalltalkhub.com/#!/~MasashiUmezawa/PunQLite -- [:masashi | ^umezawa]

Jan. 29, 2015

[SO] Error in PointerDetective

by Max Leske

http://stackoverflow.com/questions/28210014/pointer-detective-inspecting-an… <http://stackoverflow.com/questions/28210014/pointer-detective-inspecting-an…> Ben, have you tried PointerDetective lately? :) Cheers, Max

Jan. 29, 2015

Re: [Pharo-dev] Any way to avoid the filmification effect in GTInspector?

by Esteban Lorenzano

On Thu, Jan 29, 2015 at 8:56 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi Tudor, > > 2015-01-28 19:36 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi Hernan, >> >> A couple of things. First, you do not want to disable Raw for an object >> because that implies that you will have no option for inspecting that raw >> state of that object. >> >> You are not forced to have multiple views. Only if you want them :). >> >> It seems to me that you are trying to overuse the inspector for >> customers. That is not the intention. The inspector is for developers. >> >> > I think we finally found the real point. > I see Glamour has the potential to become a framework to build final UI's, > not only for developers. > And I hope one day anyone could build their own view of objects even > visually. > yes, but glamour ~= gtinspector glamour is the framework gtinspector is a tool made with glamour (and a tool intended for developers) Esteban > > >> However, once you have various presentations for an object, you can put >> them together in a filtered inspector or even in a complete browser >> altogether. This is where Glamour kicks in. See here an example: >> >> http://www.humane-assessment.com/blog/creating-custom-browsers-out-of-inspe… >> >> > Thank you for the link *and* the post, I will check if could suit my needs. > > Cheers, > > HernÃ¡n > > Cheers, >> Doru >> >> >> >> On Wed, Jan 28, 2015 at 6:35 PM, HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com> wrote: >> >>> >>> >>> 2015-01-28 5:44 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> >>>> > On 28 Jan 2015, at 08:33, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> > >>>> > >>>> > >>>> > 2015-01-27 5:11 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> > Hi Hernan, >>>> > >>>> > GTInspector was built to be extensible without any subclassing :). >>>> > >>>> > The GTObjectVariablesBrowser shows the raw view and you probably do >>>> not want to mess with that. Rather than that you should create a new tab >>>> for your own class. >>>> > >>>> > The way you extend it for a specific class is by defining a method >>>> like this: >>>> > >>>> > MyClass>>gtInspectorCustomListIn: composite >>>> > <gtInspectorPresentationOrder: 10> >>>> > composite list >>>> > title: 'My list' >>>> > display: [ self list] >>>> > >>>> > If you want to see all inspector extensions available in the image >>>> take a look at the following post: >>>> > http://www.humane-assessment.com/blog/managing-gtinspector-extensions >>>> > >>>> > Nice! >>>> > So it would be: >>>> > >>>> > gtInspectorCustomListIn: composite >>>> > <gtInspectorPresentationOrder: 10> >>>> > >>>> > composite list >>>> > title: 'My list'; >>>> > display: [ self container ]; >>>> > selectionAct: [ self actionForA ] on: $A entitled: 'Menu Item >>>> A'; >>>> > selectionAct: [ self actionForB ] on: $B entitled: 'Menu Item >>>> B'. >>>> > >>>> > It is possible to remove the "Raw" and "Meta" tabs? >>>> >>>> Why ? The whole idea is to have multiple views. >>>> >>>> >>> Even if it were nice one can have multiple views, it would be better no >>> to be forced to have them. >>> As practical reason that would only confuse my users. >>> >>> Beyond that, the inspector doesn't feel flexible enough if one must have >>> multiple views. >>> >>> >>> >>>> If you have a homogeneous list on the left and select one tab on the >>>> right, moving up and down the list should keep the same tab selected, even >>>> if it is not the highest priority one. >>>> >>>> > >>>> > Does it help? >>>> > >>>> > Doru >>>> > >>>> > On Tue, Jan 27, 2015 at 8:52 AM, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> > >>>> > >>>> > 2015-01-27 3:41 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> > Hi, >>>> > >>>> > On Mon, Jan 26, 2015 at 11:58 PM, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> > >>>> > >>>> > 2015-01-26 6:25 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> > Hi, >>>> > >>>> > On Mon, Jan 26, 2015 at 10:18 AM, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> > >>>> > 2015-01-26 5:54 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> > There is no way at the moment. >>>> > >>>> > Just out of curiosity, why do you need to select an item if you do >>>> not want to see the details? >>>> > >>>> > >>>> > This is for two reasons >>>> > >>>> > 1) I have items with big strings inside and it takes too long to load >>>> in the new inspector sub-window. >>>> > >>>> > Why should it take too long? Is it because printString is too >>>> expensive? In that case, perhaps you might want to make printString cheaper >>>> and offer a separate presentation for your object that shows the full >>>> contents. >>>> > >>>> > >>>> > I don't know, I have this 7.7Mb XML file, opened the Time Profiler >>>> with: >>>> > >>>> > 'DLoop_Bovino_31-10-14-Alignment.xml' asFileReference contents >>>> inspect. >>>> > >>>> > it took almost 6 minutes to open the inspector. >>>> > >>>> > Here is the link to the file: >>>> https://www.dropbox.com/s/pzw88gg3wyfkf8o/DLoop_Bovino_31-10-14-Alignment.z… >>>> > Here is the full report >>>> > >>>> > - 350675 tallies, 359630 msec. >>>> > >>>> > Hmm, Something is strange. I open the inspector on the same file in >>>> 1192 ms. It takes so long because the first presentation is a text >>>> presentation of the contents of that file. What image do you use? Is it >>>> possible that you have extra . Could you make it available? >>>> > >>>> > >>>> > I am using #40463 in Windows 8.1 x64. This is how I download the image >>>> > >>>> > $ wget -O- get.pharo.org/40+vm | bash >>>> > >>>> > image link with test file: >>>> https://www.dropbox.com/s/57hprg7cyryd9cs/testGT1.zip?dl=0 >>>> > >>>> > >>>> > Could you (or anyone) reproduce the case? >>>> > The dropbox upload is vanilla image. >>>> > >>>> > >>>> > >>>> > >>>> > 2) I select the item to send a message to it, or bring a pop-up menu >>>> to remove the item (I have implemented it in the old inspector and I would >>>> like to port it to Pharo 4) >>>> > >>>> > This implies that you actually need a custom presentation. For such a >>>> custom presentation you can suppress the propagation of selection. If you >>>> tell me your use case in more details I can try to guide you. >>>> > >>>> > >>>> > My use case is I want to add or remove items from an >>>> Inspector/Explorer. >>>> > The items are classified objects and the user curates false positives. >>>> > Another item I used to have is "Serialize" the inspector contents (or >>>> from a specific item) so that one could import the curated data set and >>>> review. >>>> > >>>> > Do you mean items from collections in general, or items stored as a >>>> collection in a specific object? If you mean the latter, you can create a >>>> custom presentation just for that object and add all the actions you want. >>>> Do you want to give it a try? If yes, let me know the more specific use >>>> case and I can help :) >>>> > >>>> > >>>> > I would be glad to get some help :) >>>> > I tried subclassing GTInspector. I see you implemented menu items in >>>> GTObjectVariablesBrowser. >>>> > So question is how could I implement my own >>>> "GTObjectVariablesBrowser" and link to GTInspector subclass? >>>> > Thank you Doru. >>>> > >>>> > >>>> > HernÃ¡n >>>> > >>>> > >>>> > Doru >>>> > >>>> > >>>> > -- >>>> > www.tudorgirba.com >>>> > >>>> > "Every thing has its own flow" >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > www.tudorgirba.com >>>> > >>>> > "Every thing has its own flow" >>>> >>>> >>>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >

Jan. 29, 2015

Re: [Pharo-dev] DarkTheme, Pharo3 and GTSpotter [WAS] Re: HELP WANTED: improve Dark Theme

by Tudor Girba

Hi, The GT-Spotter is being developed on Pharo 4 now, and the DarkTheme is available in that version. Cheers, Doru On Wed, Jan 28, 2015 at 11:44 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Fri, Jan 23, 2015 at 9:30 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > >> 3) Fix spotter theming (currently ignores dark theme) >> >> >> I added DarkTheme to spotter. Update to check and you can also take a >> look how theming mechanism works in GT. >> There is UITheme>>spotterWidgetThemer that returns themer object for >> Spotter and to add custom theme she needs to override it in her own theme >> like it is done in Pharo3DarkTheme>>spotterWidgetThemer. >> It allows to customize widgets deeply and reduces mess in themes :) >> >> > I cannot make it work by no means :( but I would love to! > > Do you know the exact steps to have a Pharo 3.0 with GTSpotter and > DarkThem working? > > Thanks a lot in advance, > > > > > >> Cheers, >> Alex >> >> On Fri, Jan 23, 2015 at 1:19 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> I think roassal can do that >>> >>> On Fri, Jan 23, 2015 at 2:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> >>>> >>>> On 23 Jan 2015, at 12:53, Torsten Bergmann <astares(a)gmx.de> wrote: >>>> >>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=385003 >>>> https://code.google.com/p/eclipse-svg-icons/ >>>> >>>> >>>> cool! >>>> now I have to figure out how to display svg icons in pharoâ¦ but this is >>>> what I was looking for :) >>>> >>>> Esteban >>>> >>>> >>>> >>>> Gesendet: Freitag, 23. Januar 2015 um 12:24 Uhr >>>> Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>>> Betreff: Re: [Pharo-dev] HELP WANTED: improve Dark Theme >>>> >>>> >>>> On 23 Jan 2015, at 12:03, Esteban Lorenzano <estebanlm(a)gmail.com> >>>> wrote: >>>> >>>> Hi, >>>> >>>> The Dark Theme is a standard theme upcoming in Pharo4, but as you might >>>> noticed, is still far from perfect. >>>> I would like to take some actions on it but I do not have a lot of time >>>> this days, so I thought on asking for help :) >>>> >>>> What I think is needed? >>>> >>>> 1) There are some bugs (for example in the search window, cmd+f in text >>>> panes) >>>> 2) Icon-set is not prepared for dark backgrounds. Now, this is a >>>> problem in eclipse itself who didnât had a dark-theme either until >>>> recently. Now, I know they added a dark-theme and a corresponding set of >>>> icons (a set that can be displayed correctly both in white and black >>>> backgrounds), but I cannot find the icons. So if someone knows where they >>>> are, Iâll gladly replace them. >>>> >>>> >>>> 3) Fix spotter theming (currently ignores dark theme) >>>> >>>> I know in an ideal world we will have our own set of icons, but that >>>> requires a lot of effort and design talentâ¦ so in the mean time, I think >>>> eclipse icons are doing a good job :) >>>> >>>> cheers, >>>> Esteban >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 29, 2015