[Glamour] default selection in ListPresentation
by Cyrille Delaunay
Hello,
Is there a way to set a default selection to a list presentation? so that
when I open the browser, the morphic list has already a value selected.
I tried that:
|tmpBrowser|
tmpBrowser := GLMTabulator new.
tmpBrowser row: #list.
tmpBrowser transmit to: #list; andShow: [:a |
a list
display: [:input | input];
selection: #a;
yourself
].
tmpBrowser openOn: #( b c d v a d f r).
but the list still open with nothing selected
5 years, 2 months
JavaScript to MSE
by Alexandre Bergel
Hi!
Hernán has worked on an Eclipse plugging to produce MSE file from a JavaScript application. It works well.
The plugging is available on:
https://bitbucket.org/hcvazquez/mseexporterjs/wiki/Home <https://bitbucket.org/hcvazquez/mseexporterjs/wiki/Home>
Here is a teaser:
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
6 years, 7 months
[ann] pillar support in gtinspector
by Tudor Girba
Hi,
I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:
Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load
Then you can just inspect a book folder and you get this:
I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.
It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.
Cheers,
Doru
--
www.tudorgirba.com
www.feenk.com
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."
6 years, 8 months
[Roassal2] ConfigurationOfRoassal2-AlexandreBergel.89 ?
by Bernardo Ezequiel Contreras
hi,
could someone copy this
Name: ConfigurationOfRoassal2-AlexandreBergel.89
Author: AlexandreBergel
Time: 30 August 2016, 6:44:04.870089 pm
UUID: 224cad5b-6467-406d-9ae3-36e949b45229
Ancestors: ConfigurationOfRoassal2-AlexandreBergel.88
fix in Version 1.37
configuration to the
Repository: http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/
, please?
right now, i cannot load roassal2 in pharo5.
thanks.
--
Bernardo E.C.
Sent from a cheap desktop computer in South America.
6 years, 9 months
Custom button in GTPlayground
by Peter Uhnak
Hi,
(how) can one add a new button to GTPlayground, next to the "do it all and go" and "remote publish"?
I want to add integration with Gists (because I find the remote publish only remotely useful),
however it seems that the buttons are hard coded.
Thanks,
Peter
6 years, 9 months
[ann] seaside gtdebugger
by Tudor Girba
Hi,
As presented at ESUG on Monday, we now have a custom GTDebugger for Seaside. This was built by Andrei as an initial experiment.
As we do not know much about Seaside-specific debugging problems, we asked a couple of Seaside users to describe issues that would be useful to be addressed in the debugger, and Andrei allocated some 4h to construct some of these in an custom debugger for Seaside.
Two of the issues that popped up are:
- get a quick view of the current request context
- get an overview of the current component nesting
They are now addressed like depicted in the screenshot below.
You should look at this debugger as a beginning. Beside the current basic extensions one added value is that we now have the scaffolding to build more. Please take a look at it and let’s try to identify more concrete issues that might be addressed. It would be great if this would be taken over by the Seaside community.
The debugger can be loaded on top of a Pharo 6.0 with Seaside inside like this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-SeasideDebugger';
load.
#GTSeasideDebugger asClass register
Cheers,
Doru
--
www.tudorgirba.com
www.feenk.com
"The coherence of a trip is given by the clearness of the goal."
6 years, 9 months
[ann] Lam Research evaluates Pharo
by Tudor Girba
Hi,
We are very happy to make the following announcement:
Lam Research, a leading supplier of wafer fabrication equipment and services to the global semiconductor industry, is an experienced user of the Smalltalk programming language. Smalltalk is a key component in Lam's software control system for a broad range of the equipment it manufactures. Tudor Girba is a leading member of the tools and environment development effort in Pharo, having architected the Glamorous Toolkit for live programming. Eliot Miranda is author of the Cog virtual machine that underlies Pharo and other Smalltalk dialects.
Lam has engaged Tudor and Eliot to explore potential enhancements in Lam's use of Smalltalk. These enhancements range from running highly optimized Smalltalk on low cost, single board computers, to enhancing Lam's Smalltalk development practices with state-of-the-art live programming. During the engagement, Tudor and Eliot successfully moved a key communication component of the control system to Pharo. It was a challenging task aimed at extending the reach of Lam’s system to the Pharo world including the option of executing on ARM processors.
Cheers,
Tudor Girba, Eliot Miranda and Chris Thorgrimsson
6 years, 9 months
[ann] GTExamples alpha
by Tudor Girba
Hi,
Over the last coupe of years Stefan Reichhart and the rest of the GT team worked on an implementation of examples. The work is inspired from previous work done by Markus Gaelli and Adrian Kuhn.
As one of the goals of GT is to offer a live programming environment, one important issue is how to move from the static code to live objects as fast as possible. That is why we worked on this library as a solution to provide a link between the static code and live objects.
Furthermore, this examples library also enables the definition of assertions on the examples, and this provides the possibility of rethinking the way we construct tests throughout our system. Tests are great as they help us create live objects and then to assert live properties. However, they do not allow us to leverage the objects we create, and this can be a tremendous resource for understanding systems.
In our vision, examples should be everywhere and they should be explicitly linked to the static code they exemplify. That is why the library comes with an initial integration in existing tools (such as Nautilus, Spotter, Inspector).
The current solution works well and it is the result of several rewrites. We think that the solution is complete in terms of features, but there are still several things to improve and iterate on. To this end, I kindly ask you to take a look at it while distinguishing between the concrete implementation choice (e.g., the current extensive use of pragmas) and the conceptual benefits of the approach.
To ease the discussion, we put together a short documentation:
http://gtoolkit.org/doc/Examples/examples.html
That being said, you can get it with the full GToolkit in Pharo 6.0:
http://gtoolkit.org/#install
(easiest is to download the ready made image for now)
For those that are at ESUG, I will try to provide a short overview during the Show Us Your Project session from today.
Cheers,
Doru
--
www.tudorgirba.com
www.feenk.com
"Innovation comes in the least expected form.
That is, if it is expected, it already happened."
6 years, 9 months
