On Thu, Aug 20, 2015 at 4:42 AM Alexandre Bergel <alexandre.bergel@me.com> wrote:

> 2) Gave a deep reading on Pharo auto completion.

Auto-completion in Pharo is really bad. It would be fantastic to improve it.

Yes indeed, my effort for now is focused in documenting it. I cannot improve what I dont understand. Then will see if I can improve it, by making it more customizable or making it a bit smarter.

��

> 3) Study how Playgrounds draws its GUI to improve it by making far more flexible.

Can you say more about this?

I have talked about this long time ago. I was imagining a new tool I called "Cyclops". The idea of Cyclops was born when I was reading the GTPlayground�� comment that says

"Playground is the correspondent of a classic Smalltalk Workspace. The problem with the name Workspace is that it implies that work should be carried out in this space, while this is not a best practice. Playground describes better the intention of providing a place in which we can quickly play with some code."

My first reply to this comment was "Why not ?". So the idea is to have a new Workspace that allows the user to create code , add it to a class, inspect, debug , print and do all code tasks without ever leaving the boundaries of the tool. GTPlayground already does this in some way by implementing the inspector inside workspace that also has some browsing capabilities. I would also like to integrate the GTSpotter gui�� inside GTPlayground. The idea here is to bring all these tools inside a single window.

It will be a slow process , for now documenting GTPlayground is the goal, next will be to provide a cleaner design for printing values, creating blocks of code that the GTPlayground is aware of and allows the user to be added to a new or existing class as methods and some code browsing abilities. I am also interested into browsing documentation inside workspace and I have many other ideas.

For now the goal is just to read the code of GTPlayground GUI and try to document it

��

One step at a time ;)

Cheers,
Alexandre


> 4) Study a new programming language Nim , for making dynamic libraries for pharo , replacing C/C++. Possible scenario of porting SqueakNim to Pharo.
>
> To Do
>
> 1) Improve my blue theme (Nireas)
> 2) Create an API for Blender for Pharo
> 3) Create my own custom Playground which will be more powerful
> 4) Integrate Nim with Pharo
>
> On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris <sean@clipperadams.com> wrote:
> ### Here's what I've been up to since the last WhatsUp:
> - Ported Moose issue tracker to GitHub
> - GT extension for presentations semi-auto-generated from Magritte
> descriptions
>�� ��- data, label, etc pre-filled by default
>�� ��- Magritte actions appear as e.g. presentation list selection context menu
> - Magritte
>�� ��- extension for above
>�� ��- many little fixes and enhancements
> - [WIP]: Created Glamour browsers from presentations
> - Glamour/GT patches
> - GSoC Mentoring for sQuick Smalltalk project
>
> ### What's next, until 2015-08-31 (*):
> - Camp Smalltalk Portland!
>
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p4843818.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel�� http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.