2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:

On 6 Mar 2017, at 07:57, phil@highoctane.be wrote:

https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simple/7294/artifact/report.html is not integrated for some Monkey reason anyway - still should b/c if you put sublimish, you need a decent matching Spotter.

Also, I see��https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate-code-from-SublimishTheme on 5/3. If this moves forward, why not the other one?

BTW Sublimish was an extra thing. Who got that in image?

I don���t know.��
It shouldn���t :)

What we should do is to create a page for themes and links to it (and they should be in catalog) :)

Well, it was me who proposed the slice and yes, I was aware of the fact that I should not do it because of code freeze (I was not aware of the two themes policy).

We can remove it again, I will prepare a slice.��

-- Pavel



��

Esteban


Phil

On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm@gmail.com> wrote:

Hi,

First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions.��

By the way, even if I like it, I would not have integrated SublimishTheme. For same reason I didn���t integrated DarkMetalTheme: My idea is to have just two themes *in image*: one white, one dark, and allow people to install other themes from catalog.��

Why? Because each class inside image becomes our responsibility and then a maintainability issue. With themes in particular already happened that existing themes became abandonware inside the image and we needed to clean up, not without problems.��

cheers,��
Esteban

ps: which means also yes: that issue got integrated because I failed to control the flow of issues...


And I know, most of those additions are usability enhancements so a good thing.

But can you guys stop pushing new features into a (in theory) frozen version?

Pharo 7 will arrive soon��� *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version.��

There are still plenty of bugs to fix there, like for example why Spotter does not shows search line.��

Last week I added support to Athens and SDL2 in 64bits but that meant:��

- some important changes in UFFI
- discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem).

I would say all this and the fact we are working on 64bits in general deserves a lot of testing.��

I will add links in Pharo page to download 64bits (I���m at the train now), but in the mean time you can download all from here:��


cheers,��
Esteban