I tried to load GToolkit in Pharo 3 today and I got this:
* Error: Name not found: CoreExtras*
Loading like this:
#ConfigurationOfGToolkit asClass loadDevelopment.
Ooops, used to work a couple days ago...
Very nice initiative!
On Tue, Sep 9, 2014 at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
> This is excellent!
> Just to let you know, if you need to do a demo of Roassal, you have here
> the video a an easy to do demo: https://vimeo.com/94724841
> Alexandre Bergel http://www.bergel.eu
> On Sep 9, 2014, at 12:27 PM, Offray Vladimir Luna Cárdenas <
> offray(a)riseup.net> wrote:
> This is just a short mail to let you know whats happening here on the
> Pharo/Roassal front. We will be starting our workshops on what we I call
> Visual Data Narratives. Details (in Spanish) here:
> ps: I will show the Moose outliner, in its alpha stage. Hopefully the
> threads where I ask how to solve the problems will move a little more and
> we will be able to integrate this to the workshops memories building.
"Every thing has its own flow"
When one is in Monticello (Pharo 3.0) and asks for "View Past Comments" on
a package, there is a #mnu on GTPlayground class>>openLabel:
Not only there but the FileList (aka FileBrowser) has that "Workspace with
contents" command which is broken in the same way.
There is for sure an interesting equivalent in GTPlayground. Why not name
it as the Workspace thing?
What is asked:
edit: aText label: labelString accept: anAction
"Open an editor on the given string/text"
^(Smalltalk tools workspace openLabel: labelString)
What GTPlayground implements:
We can deal with openLabel: and acceptContents but an acceptAction
equivalent is not to be found.
Also, after looking around (see changeset in attachment), it is hard to do
the acceptContents: as we get a self new openOn: page which isn't returning
anything I can work with to chain acceptContents: to.
What to do there?
Also, there is a super annoying thing in the GTPlayground, namely the
disappearance of the top right menu, with all the interesting options that
are in there and that I do use all the time (like open/save, previous
contents, ...). What's the point of a Playground if I can't save my plays?
I think I am missing something here.
I now have to go back to the old Workspace for the default.
It may be good to have a way to have the playground as a specific menu
I've started using the ZnWorkspace and as it extends the Workspace, its
features aren't picked up in GTPlayground of course.
Now, it may be great to include those Pastebin style things into
GTPlayground so that we can all play together from little urls from Twitter
All the best,
I defined a new property:
<MSEProperty: #mode type: #String>
<MSEComment: 'The mode (input/output) for this parameter'>
I reinitialized the meta model
I set the property for an entity
but the property is not exported in "model asMSEString" :-(
Hi, when trying out the new pillar inspector (Great!)
I noticed some issues with PetitTest and PetitAnalyzer.
Their packages are dirty after
#ConfigurationOfPetitParserIslands asClass loadDevelopment.
I've tried it on Pharo For The Enterprise
Much easier to use than a plain text viewer.
Here are some more common constructs to handle:
- ending a code block with]]] at the end of line
- ClassName class>>methodName
Documentation is important. To make it more likely and more enjoyable for
people to write more of it, I teamed up with Andrei and Jan to build up
support for Pillar in the GTInspector.
The current solution brings the following:
- Pillar specific syntax highlighting including Shout highlighting for code
- Embedded files validation and preview possibility
- Quick browsing of Pillar book projects when inspecting the book folder
- Class comment rendering using Pillar syntax when inspecting the class
- Text editor support for custom highlighting in Glamour (using Rubric for
- Island parsing for quick specification of incomplete parser
You can learn more about it here:
[image: Inline image 1]
There is much more to do in this direction, and I would be happy to inspire
some of you to join forces. Please let us know what you think.
"Every thing has its own flow"