Hi,
We are happy to announce the first preview version of Brick, a new widget
set created from scratch on top of Bloc.
Brick is being developed primarily by Alex Syrel (together with Alain
Plantec, Andrei Chis and myself), and the work is sponsored by ESUG. Brick
is part of the Glamorous Toolkit effort and will provide the basis for the
new versions of the development tools.
Brick's goal is to provide a beautiful looking widget set, and the default
look is based on material design. The widgets are theme-able.
Right now, there exists:
- Label
- Simple button
- Toggle button
- Checkbox
- Radio button
- Window with or without an active title bar that can include various
visual actions and info
- Menu
- Beautiful scrollbars that are thin by default and enlarge when the mouse
hovers over it
- Scalable list for huge amounts of items with various heights
(The list also allows one for embedding text widgets with in place editing)
The next immediate target is the creation of a new Pager widget (the widget
that is behind the current GTInspector).
You can see some screenshots on the official site:
http://gt.moosetechnology.org/brick
To play with it, you can download a ready-made image:
https://ci.inria.fr/moose/job/gtoolkit5/lastSuccessfulBuild/artifact/gtoolk…
and, in a Bloc space, you can browse the examples:
BrExampleBrowser exampleOpen
We would be happy to hear your feedback.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I'm getting acquainted more with Moose and FAMIX and I am not really sure
how to proceed (mostly due to lack of documentation and link rot).
What I want to do is add "multiplicity" attribute to FAMIXAttribute.
Now I see an option:
1) create a subclass of FAMIXAttribute
2) add a method.. something like
FAMIXAttribute>>multiplicity
<MSEProperty: #multiplicity type: #MyFAMIXMultiplicity>
^ multiplicity
now Moose can generate models from smalltalk source code and I would like
to infer this information.
For example for types, there is
MooseImportingContext>>computeTypeOfAttributes
So I'm assuming I would have to do something similar.
And finally, if I want to help the importer and actually write that
information into the source code, I would have to add another pragma
there... something like
MyClass>>myAttribute
<MSEMultiplicity: '2..*' type: MyType>
^ myAttribute
and then modify the smalltalk importer to be able to recognize this and
produce MyFAMIXAttribute instead of the default one.
Am I on the right track? Should it be done differently?
Any pointers appreciated,
Peter
Hi,
There seems to be a problem with simple the rubric presentation in Moose
5.0. TextColor attributes are overridden with default text color from the
theme when the morph is created.
There is a flag in the morph creation code that says that the code needs
reviewing in Pharo 4.0. So removing two lines below after the flag resolve
this issue:
GLMMorphicRubricTextRenderer>>morph
|morph|
morph := RubScrolledTextMorph new
getSelectionSelector: #primarySelectionInterval;
model: textModel;
color: Smalltalk ui theme backgroundColor;
textFont: StandardFonts defaultFont;
yourself.
self flag: 'Temporary solution until Moose moves to Pharo 4'.
(Smalltalk ui theme class canPerform: #textColor) ifTrue: [
morph textColor: Smalltalk ui theme textColor ].
^ morph
Should I commit a fix removing the flagged lines? Should I create a new
branch for the fix?
Hi!
I would like to add a new menu entry when I right click on a text in GT. Something titled ‘execution coverage’ which will spawn an Hapao visualization.
Is there an easy way to do it?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
As you may have heard, Hapao is a test coverage tool. It measures the coverage of test executions. For more info, you can check publications on http://bergel.eu , do a textual search on 'Test' or 'Hapao'.
We have improved Hapao today with the ability to visual the coverage of any arbitrary execution. This short video demonstrates this:
Loading Spy (soon in the catalog browser, but until then):
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Spy2';
configurationOf: 'Spy2';
loadBleedingEdge.
There is a video here:
https://www.facebook.com/ObjectProfile/videos/vb.340543479365589/9659290501… <https://www.facebook.com/ObjectProfile/videos/vb.340543479365589/9659290501…>
Here is a screenshot example:
The visualization indicates which methods of the RTMondrian class have been executed, how many times, which ones have not been executed…
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am trying to load the Bleeding edge of Bloc in the last Moose image.
Bloc loads well, but I cannot switch space :-( The image freezes.
Gofer it
smalltalkhubUser: 'Pharo' project: 'Bloc';
configurationOf: 'Bloc';
loadBleedingEdge.
Any idea?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
What can I do with that?
I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.
How comes that the system is so unstable. This is puzzling me.
I will not use the Moose image anymore.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
View in Roassal can now be rotated.
-=-=-=-=-=-=-=-=
v := RTView new.
b := RTMondrian new.
b view: v.
b nodes: (1 to: 20).
b edges connectFrom: [ :value | value // 2 ].
b layout tree.
b build.
v @ (RTRotableView new center: [v elements first position ]).
v
-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am playing with the treemap again, but the leafColor: is not working.
Could anyone take a look at it?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
