Hi klaranosan,
First, welcome!
Second, thanks for the work on the issues.
Third, would you like to introduce yourself? :)
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"To lead is not to demand things, it is to make them happen."
Hi!
I would like to parse some visual works source code to load it in Moose
in Pharo.
Does someone has such a MSE parser and the associated Moose model to
import it?
Thanks in advance!
Cheers,
Vincent
Hello everyone!
Today with Anne we changed a little moose query to make it possible to
query specialized associations.
What I mean by that is: If you created a FAMIXSpecializedInvocation
and stored it in
FAMIXBehaviouralEntity>>#incomingInvocations/#outgoingInvocations,
MooseQuery was not able to query it because is checked only
FAMIXInvocations.
Now it is possible.
This will not change anything for most meta-models since only a few
use specialized associations. I updated the documentation present at
moosequery.ferlicot.fr and I added a test in Moose.
Have a nice day!
--
Cyril Ferlicot
https://ferlicot.fr
Hi,
Here is an update of the work on Bloc, Brick and GT. As always, please do let us know what you think.
Bloc:
- Improved the deletion in the text editor and covered the scenarios with examples
- Worked on the text selection. Still work needed for selection to be production ready:
https://twitter.com/feenkcom/status/969183393547259905
- Balanced rope structure for even better performance of the editor. Overall, the performance of the text editor improved 2x.
https://twitter.com/feenkcom/status/971009488789516288
- Selectable curves:
https://twitter.com/feenkcom/status/967690664589910016
Brick:
- Resizer overlay. The tweet below also shows how we can now easily script dragging behavior in examples:
https://twitter.com/feenkcom/status/971990195011690496
GToolkit:
- Diagrammer is a new engine for drawing diagrams based on Bloc. This is the first version, and we will continue working on it in the following weeks, so stay tuned for more news. This is also one of the first Bloc applications:
https://twitter.com/feenkcom/status/972243179599794180
- Andrei put together a beautiful description of a scenario in which an application is molded interactively in the Playground & Inspector. The subject is face recognition, and the resulting code is both functional and explainable. This is intended as a tutorial material that shows what moldable development means and how it changes the way we program:
https://twitter.com/feenkcom/status/972907051448979458
Have fun,
The feenk team
www.feenk.com
--
www.tudorgirba.comwww.feenk.com
"To utilize feedback, you first have to acquire it."
Hi,
A while ago, I put together an initial version of a Moose Playground.
I noticed since a while a couple of things:
- I often need the inspector, and not only Moose Finder.
- I start from different places: sometimes a Moose model, sometimes a file, or sometimes a script.
So, the idea of the new arrangement is to offer a single entry point to multiple workflows. To this end, right now we have a playground that has three tabs:
- a regular one for a Pharo script:
- a list of models and a way to import like those from the Moose Panel
- the current directory for quick entry into the file system
I have been using it since a while and it seems to work quite well. Please let me know what you think.
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
“Software has no shape. Actually, it has no one shape. It has many."
