Usman wrote:
>Do we the demo live somewhere so that we can have a look at it?
QCMagritte is on https://ci.inria.fr/pharo-contribution/job/QCMagritte
ZnZincServerAdapter startOn: 8080
Click through the welcome app, set browse as default
and start the qcmagritte web app
Stephan
subclassHierarchy
| subclasses |
subclasses := OrderedCollection new.
self allSubclassesDo: [:each | subclasses add: each].
^ subclasses
to me it looks like too much thinking and this kind of API sucks.
I can understand
subclassHierarchyDepth
because it is about hierarchy but no subclasses.
Stef
Hi
This is several times that I ask and I got no reaction but the printOn: of FAMIX entities is a problem.
I do not think that it makes sense to have ClassName in namespace (namespace) :: namespace (namespace) (class)
So how do we address it?
- I would introduce either a strategy to control what is displayed
- I would make the dinstction between full name and name.
Of course I can hack it and have my own implementation because it really get on my nerves that I cannot
even see the name of a class in a set in the inspector.
Syeg
Today we finished porting the magritte demo to the
new version of bootstrap in TorstenBergmann/Bootstrap.
Next step would be to use that as a basis for the QCMagritte demo.
There we have live editing & filtering of tables, multi-language support,
ajax validation etc.
Diego & Stephan
Hello,
We are working to port our tools (browsers) to the web. Mostly, these are
developed using Glamour. So, Glamour-seaside can save us time because, in
this way, we can reuse existing presentation logic with a different
renderer. I worked with Andrei during one of his visits to Lille and we
ported one of our browsers to the web. I didn't take us very long. However,
there were some missing widgets (e.g. table). So, Andrei wanted to improve
the existing set of widgets and probably reuse a new library (such as
Bootstrap) make them more glamourous (as in sexy ;).
I think it can be helpful for us to use this infrastructure as there is
some major progress made already. The participation of the initial
contributors will be essential in the effort because rendering is just one
aspect, we also have the transmissions, panes, and ports in Glamour. So my
questions:
- How does Glamour-Seaside manage transmissions, ports and panes?
- What are the missing widgets?
- How about using Bootstrap?
- Would you be interested in participating in the effort of improving
Glamour-Seaside infrastructure?
- Is there any doc that we can start looking at to understand
implemented/missing features?
A glimpse of our tools that we need to port to the web can be found here:
http://www.synectique.eu/en/files/4D-Flyer-eng.pdf
tx,
Usman
Hi
when I open a mondrianEasel and press the right triangle I get an error tell me that error message is not understood.
withAll: bindings.
[ Smalltalk compiler evaluate: script in: context to: context ]
on: Error
do: [ :e |
self inform: e class name , ': ' , e errorMessage.
(renderer pieDiagram)
radius: 100;
models: #('Error');
pieValue: [:x | 100];
displayLegend: true;
defaultColor: Color red ] ];
defaultActions