Moose-dev February 2011

moose-dev@list.inf.unibe.ch

23 participants
136 discussions

moose web license
by Tudor Girba 03 Feb '11

03 Feb '11

Hi, I noticed that the new MooseWeb repository is under BSD. Is that intentional? I am asking because all packages newly developed are under MIT. Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

1 0

what's the glamorous tookit?
by Esteban Lorenzano 02 Feb '11

02 Feb '11

Hi, Yeah, that... I wonder what's that :) Cheers, Esteban

2 1

Re: Issue 175 in moose-technology: Rename in Famix-Extensions "referenced/referencing" to "invoked/invoking"
by moose-technology＠googlecode.com 01 Feb '11

01 Feb '11

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #7 on issue 175 by tudor.gi...(a)gmail.com: Rename in Famix-Extensions "referenced/referencing" to "invoked/invoking" http://code.google.com/p/moose-technology/issues/detail?id=175 This should go away when MooseChef is integrated. I would close it for now.

1 2

Re: Issue 57 in moose-technology: [FAMIX] code the LAN sample model in Java for reference and test
by moose-technology＠googlecode.com 01 Feb '11

01 Feb '11

Updates: Cc: anquetil.nicolas Comment #5 on issue 57 by jannik.l...(a)gmail.com: [FAMIX] code the LAN sample model in Java for reference and test http://code.google.com/p/moose-technology/issues/detail?id=57 (No comment was entered for this change.)

3 4

[ANN] pharo focused sprint - bern, feb 26
by Tudor Girba 01 Feb '11

01 Feb '11

Hi, We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, University of Berne, Switzerland (room 107): http://scg.unibe.ch/contact/maps Unlike other sprints, this would not be about fixing things from the tracker, but about building something new and reviewing the situation around one central topic. For this one, the main topic will be Morphic and the IDE. Why? Because it is time to rethink our day-to-day tools and bring them closer to this century (ok, maybe decade :)). It is Ok if you are not a specialist. It is more important to want to participate and learn. The rest will come in time. ***** Please let us know by mail if you plan to attend and what you would wish to work on (see below). Proposed tasks (other tasks are possible in the same area): - Enhancements of Morphic widgets: --- TabGroupMorph with lazy pages, closable tabs, overflow handling and toolbars (a start exists in Glamour) --- High level support for collapsable panes (based on the input of Gary) --- SearchMorph with multiple groups of items (like in Spotlight) --- MorphTreeMorph integrated with GeneralScrollPane to allow for space filling --- BreadcrumbMorph --- Hyperlinks in TextMorphs - Test and enhance the current IDE - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, SMxPluggableTextMorph etc - Prototype a new ToolSet solution - Enhancements of Glamour and of the Glamorous Toolkit --- Debugger --- Coder --- Multipage Workspace --- CodeBubbles - Develop WeakAnnouncement (start from the implementation of Lukas) - Evaluate the various keybinding implementations - Evaluate ToolBuilder - Evaluate the path to adopt SimpleMorphic A second working topic is getting Monticello faster, but this will only be tackled if there are enough people for the first one. Cheers, Adrian and Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

1 0

Issue 513 in moose-technology: The composite concerns should not offer the update action in Arki
by moose-technology＠googlecode.com 01 Feb '11

01 Feb '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Arki New issue 513 by tudor.gi...(a)gmail.com: The composite concerns should not offer the update action in Arki http://code.google.com/p/moose-technology/issues/detail?id=513 Because of the update menu item, people add the concern in the specification and then expect that refreshing the composite to magically add the item.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2011