Hi,
I remind you that the MooseDay will take place in Lille on the 19th December and a joint Moose and Pharo sprint on the 20th. I know that some of you will come even if they don't have yet filled in the doodle (so please fill in it http://www.doodle.com/d82xvu7ad4umqqxy).
I also need to know who wants to present something on what topic in order to organize the program and diffuse it. If you plan to make a presentation, can you please send me an email rapidly?
Thanks in advance.
Anne
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 1011 by usman.bh...(a)gmail.com: Rubric presentation does not
display text attribtues
http://code.google.com/p/moose-technology/issues/detail?id=1011
We could format Text by adding various attributes and show the text in a
glamour text presentation. However, with rubric text presentation, text
attribute are not shown. Is this a feature or bug?
The script below can be used to reproduce the bug.
| browser text|
text := (Text fromString: 'A new text') addAttribute: (TextColor color:
Color orange ).
browser := GLMTabulator new.
browser row: #text.
browser transmit to: #text; andShow: [ :a |
a rubricText
title: 'Text with selection'; "Text is orange"
display: text; format: #yourself ].
browser openOn:1
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Hi,
Is it possible to have an element that does not scale when the camera extent changes? Eg. I want to have circle that is always 10px in diameter no matter what is the zoom.
Cheers.
Uko
I think this is an important synchronization mechanism, and we should try
to keep it going. It takes only a couple of minutes to write down what you
have done.
### Here's what I've been up to since the last WhatsUp:
- Consolidated Moose 5.0 (it's now working fully in Pharo 3.0)
- Cleaned the Moose issue tracker
- Looked into the problem related to SpecDebugger requiring Spec inspector.
Unfortunately, the problem is still not solved. A little story is described
here:
http://www.humane-assessment.com/blog/debugging-the-debugger-with-the-inspe…
- Reviewed and improved GTDebugger (with Andrei)
- Installed GTInspector and GTDebugger as default tools in the Moose image
(with Andrei). A preview screenshot is available here:
https://www.dropbox.com/s/hzxg82nzz163gb1/2013-11-15%2019.20.42%20-%20gtdeb…
### What's next, until 2013-11-30 (*):
- Work on the GTDebugger to make it even sexier
- Build a simple overview visualization for software systems
- Translate the Moose book into Pillar
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
Due to the pragma-based recognition of properties and class-side
annotations for Moose entities we never know if we put the all the needed
pragmas and that there was no typing error involved in our custom entities
and properties. We only get to know if there is some information missing
once we start manipulating the entities in the interface where we may have:
1/ missing information or 2/ nils + DNUs.
So, what I am thinking to do is to run my battery of tests on a generated
model and the MSE (export and then import) version of the model to see if
we didn't lose information in saving the model in an MSE file and getting
it back.
Do we have such types of tests in Moose: same tests that are run on a model
before exporting it and after importing it?
regards,
Usman
Hi Fabrizio and others,
I loaded the Petit PHP parser. Now I want to use it but I see no clues. Do
anyone has an example how to parse PHP code like this:
class myClass
{
public $abc;
public function test() {
include "abc.php"; }
}
Cheers,
Hernán
I create a new property in a MooseEntity.
isFlag
<MSEProperty: #isFlag type: #Boolean>
<MSEComment: 'An exemplary flag'>
^ isFlag
I do MooseModel resetMeta.
I export the model with the entity containing the flag to an MSE.
isFlag property is absent in the mse file.
Is this a known bug/feature or do I need to update something?
Usman