Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

[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

rpackage does not refresh on class rename
by Tudor Girba 31 Jan '11

31 Jan '11

Hi Cyrille, I noticed a case in which the RPackage did not seem to refresh after performing a class rename refactoring. I did not have a chance to write a test case for this, but I think it probably affects the importing as well. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

2 1

Issue 512 in moose-technology: Implicit browsers should allow for extra transmissions
by moose-technology＠googlecode.com 31 Jan '11

31 Jan '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 512 by tudor.gi...(a)gmail.com: Implicit browsers should allow for extra transmissions http://code.google.com/p/moose-technology/issues/detail?id=512 Currently, there is no way to create custom transmissions in an implicit browser. For example, it might be needed to capture a specific port and export it to outside. Another application is in providing a custom output for the status bar.

1 0

Re: Issue 315 in moose-technology: Moose Finder should be extensible by entities
by moose-technology＠googlecode.com 31 Jan '11

31 Jan '11

Updates: Labels: Milestone-4.3 Comment #2 on issue 315 by tudor.gi...(a)gmail.com: Moose Finder should be extensible by entities http://code.google.com/p/moose-technology/issues/detail?id=315 Currently, it is possible to extend the Moose Finder by defining extensions in the MooseFinder class. It's an Ok first solution but it will not really scale because we always have to test for the type. Instead, we should have a dynamic presentation computed by delegating to the objects.

1 1

Re: Issue 506 in moose-technology: Toolbar should be rendered on the top right
by moose-technology＠googlecode.com 31 Jan '11

31 Jan '11

Updates: Summary: Toolbar should be rendered on the top right Comment #1 on issue 506 by tudor.gi...(a)gmail.com: Toolbar should be rendered on the top right http://code.google.com/p/moose-technology/issues/detail?id=506 (No comment was entered for this change.)

1 3

Issue 511 in moose-technology: Listing presentations should populate the status port
by moose-technology＠googlecode.com 30 Jan '11

30 Jan '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 511 by tudor.gi...(a)gmail.com: Listing presentations should populate the status port http://code.google.com/p/moose-technology/issues/detail?id=511 The status port is used for displaying information on the statusbar, but currently only the Mondrian presentation offers this information.

1 0

follow moose
by Tudor Girba 30 Jan '11

30 Jan '11

Hi, If you want to follow Moose, you can do it via the following channels: - RSS feed: http://www.moosetechnology.org/news?view=PBEntriesRssView - Facebook: http://www.facebook.com/pages/moosetechnologyorg/152851281427491 - Twitter: http://twitter.com/moosetechnology Cheers, Doru -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

1 0

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

30 Jan '11

Updates: Summary: Put author and timestamp in entity property Comment #10 on issue 21 by simon.de...(a)gmail.com: Put author and timestamp in entity property http://code.google.com/p/moose-technology/issues/detail?id=21 We quickly discussed that today, but I think it would be cool to add a switch in the importer telling whether or not we want to import such data - as well as a checkbox in the wizard. Should be easy enough. Also don't forget to meta-describe the properties (it would be cool if Fame could figure it does not need to save data which are nil)

1 4

what is the status of FameDB
by Stéphane Ducasse 29 Jan '11

29 Jan '11

Hi guys in the past marco did a bridge to database for metadescribed but since famix was not regular we could not get famix models in databases. So I would be interested to know if there is an ongoing effort to do that? Because this would be a real plus for FameDescribed models. May be using Glorp and I was thinking that this would be good also to get all the source code of pharo in a db using Ring. And get Torch there too. Stef

8 23

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev