Moose-dev January 2011

moose-dev@list.inf.unibe.ch

23 participants
129 discussions

current development version is 4.3
by Tudor Girba 28 Jan '11

28 Jan '11

Hi, Just a note. We did not release a 4.2 based on Pharo 1.1.1 because we could not get the loading to work cleanly. So, we skipped 4.2 and we switched to 4.3 based on Pharo 1.2. I would focus on fixing the issues and then releasing in a couple of weeks. Here are the current open issues: http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone=4.3 If you have other issues please mark them in the tracker. Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

2 2

Re: Issue 21 in moose-technology: Put author adn timestamp in entity property
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Updates: Labels: Component-VerveineJ Milestone-4.3 Comment #4 on issue 21 by jannik.l...(a)gmail.com: Put author adn timestamp in entity property http://code.google.com/p/moose-technology/issues/detail?id=21 (No comment was entered for this change.)

1 5

Re: Issue 414 in moose-technology: Replace PackageOrganizerCache by RPackage
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Comment #3 on issue 414 by tudor.gi...(a)gmail.com: Replace PackageOrganizerCache by RPackage http://code.google.com/p/moose-technology/issues/detail?id=414 We should make the switch, especially given that in the future Pharo will adopt RPackage :)

1 9

using deprecated methods in moosejee
by Tudor Girba 28 Jan '11

28 Jan '11

Hi Fabrizio, The MooseJEE fails now because I enabled the deprecation mechanism. It looks like you are using the method tag instead of name. If you want to replicate these issues, I suggest to: - download: http://hudson.moosetechnology.org/job/moosejee-latest-dev/ws/moosejee-tests… - file in the moosejee-tests.st file from the archive (this will run the tests like on the server) Cheers, Doru -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

1 0

Re: Issue 48 in moose-technology: Smalltalk importer: fix stub
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Comment #5 on issue 48 by tudor.gi...(a)gmail.com: Smalltalk importer: fix stub http://code.google.com/p/moose-technology/issues/detail?id=48 I would say that we should close this issue. isStub has the meaning of "outside the scope of importing". We could add other flags if needed, but I would keep this one as it is. If no one will object, I will close the issue.

1 2

Re: Issue 209 in moose-technology: Lazy presentations
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Updates: Labels: -Milestone-4.2 Comment #2 on issue 209 by tudor.gi...(a)gmail.com: Lazy presentations http://code.google.com/p/moose-technology/issues/detail?id=209 (No comment was entered for this change.)

1 0

Re: Issue 156 in moose-technology: Table widget for Glamour
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Updates: Labels: -Milestone-4.2 Comment #13 on issue 156 by tudor.gi...(a)gmail.com: Table widget for Glamour http://code.google.com/p/moose-technology/issues/detail?id=156 (No comment was entered for this change.)

1 0

Re: Issue 141 in moose-technology: FAMIXUnknownVariable#container attribute is never set nor used
by moose-technology＠googlecode.com 28 Jan '11

28 Jan '11

Updates: Status: Invalid Cc: simon.denier tudor.girba Comment #6 on issue 141 by jannik.l...(a)gmail.com: FAMIXUnknownVariable#container attribute is never set nor used http://code.google.com/p/moose-technology/issues/detail?id=141 container does not exist anymore. There is a method belongsTo which return nil. We can close this issue.

1 1

Issue 507 in moose-technology: Toolbar buttons should not accept keyboard navigation
by moose-technology＠googlecode.com 27 Jan '11

27 Jan '11

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.3 New issue 507 by tudor.gi...(a)gmail.com: Toolbar buttons should not accept keyboard navigation http://code.google.com/p/moose-technology/issues/detail?id=507 Currently, the buttons in the toolbar can be navigated to using tab. This is counter productive.

1 1

Issue 506 in moose-technology: Window toolbar should be rendered on the top right
by moose-technology＠googlecode.com 27 Jan '11

27 Jan '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.3 New issue 506 by tudor.gi...(a)gmail.com: Window toolbar should be rendered on the top right http://code.google.com/p/moose-technology/issues/detail?id=506 Currently, the toolbar occupies an entire row below the title (either window or pane), even though it typically contains only a handful of icons. It should be displayed on the top right: - if it's in a window, it should be displayed on the top right of the window - if it's in a tab, it should be displayed on the same row as the tab group title - if it's not in a tab, then it should take the entire row, but still aligned to the right. This behavior is already offered by the Seaside rendering,

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2011