Re: OT: A better way to code, by Mike Bostock

[Offray Vladimir Luna Cárdenas]

Hi,

On "talking code", I have not found nothing better that Smalltalk,
specially current incarnations (like Pharo[1]) that feed on a long
tradition of live coding[1a], mainly because you can create custom tools
with custom presentations that can accommodate to your work flows and
needs investing just half and hour or less. See for example a moldable
objects inspector in [2][3], a customized and powerful playground with
live objects preview[4], where you play with objects[5] or see your
whole software project as a graph[6]. Other examples, about such
moldable environment that made the "code talk" can be found at [7]

[1] http://pharo.org/
[1a]
https://www.quora.com/What-is-the-essence-of-Smalltalk/answer/Dimitris-Chloupis
[2] http://scg.unibe.ch/research/moldableinspector
[3]
http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed
[4] http://www.humane-assessment.com/blog/introducing-the-gtplayground/
[5] https://vimeo.com/channels/ndc2014/97315968
[6] https://vimeo.com/94724841
[7] https://feenk.com/

I still remember the day when, just three months after using Pharo and
its ecosystem, I was able to prototype an outliner with live coding [8]
nodes, something I was proposing/trying with Leo + IPython without much
advancements for years [9] (that post is older that the original idea).

[8] https://twitter.com/offrayLC/status/500803908424712192
[9]
http://mutabit.com/offray/static/blog/output/posts/on-deepness-and-complexity-of-ipython-documents.html

Comparing the fluency and momentum I get with Pharo with Python or
Javascript or similar file based and indirect techs, is difficult to
invest time in learning them deeply (I was kind of an ethernal newbie on
them). But I really like the idea of live coding and making code talk
being explored in different technologies. I think there is a lot to
learn from crosspollination of ideas and communities. At least, that's
what I'm trying with Grafoscopio, mixing ideas from Leo, IPython,
Smalltalk and some of my own harvest.

Cheers,

Offray

On 18/03/18 03:15, Xavier G. Domingo (xgid) wrote:
> Great! Many thanks for your encouraging words. 
>
> So I think I should try to explain first what I mean by "talking
> code". The idea is simple: when someone tells you that he is a
> programmer, he's telling you what he DOES. But that's not, by far, all
> he IS. There's much more he can *tell* you about him: how are his
> parents, where does he live, what's his recent history of life events,
> his preferences...
>
> Well, any code we see is normally telling us what it DOES (at least in
> imperative programming languages). Sometimes, if the programmer has
> taken the care and time to add comments, it will tell you WHY it does
> it, it's INTENT and maybe even some reasons WHY it does it in the way
> it does. But I want it to tell me also about it's recent past history
> (git commits), all it's parents (commit authors), who is using it
> (callers), how well is it doing what it does (profiling), what kind of
> data it uses to handle and so on. We have tools to gather all that
> info, but the point is that I want the code itself to *tell me *this
> all the time, in a natural way.
>
> OK, enough poetry. Let's go to the Vision: my ideal IDE is the one
> that tells you all the info related to the code at hand in a
> non-intrusive, expressive, a click-away manner, all the time. The main
> info I would like to have "shown around the code" includes, amongst
> others:
>
>   * Comments, by author
>   * Git info (git log, git blame)
>   * Tests that test that code
>   * Examples of input and output data
>   * Type info
>   * Callers and uses
>   * Bugs that have impacted the code, by severity, date
>   * Benchmarks
>   * Profiling
>
>  (the list above is in no particular order of preference)
>
> The IDE should have to handle the different levels of granularity
> needed (module, class, method, function) and show the info accordingly.
>
> The key feature here is the *density of information without cluttering
> up the visual space*. That's probably the most tricky part. And that's
> the "visual side" of the question: the best the IDE can show all this
> info in a visual expressive way, the better. My idea is that the IDE
> shows summaries of the relevant info (visually or textually) around
> the code and a hover and/or click takes you to the details. Of course,
> the idea is not "new" in any sense. IDEs are already doing some of the
> above with mixed success, but I would like to bring it to Leo.
>
> Do you think that something like this will be possible with Leo? 
>
> Please, your comments Amigos! ;-)
>
> Xavier
>
> On Saturday, March 17, 2018 at 1:36:56 PM UTC-3, Edward K. Ream wrote:
>
>
> ​An exciting goal.  I'll help you any way I can.
>
> Edward
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to 

Re: Basic Layout of the Leo GUI

[Chris George]

GammaRay is working again.

Did you have any specific questions?

Immediately below LeoTabbedTopLevel is 
QStackedWidget#qt_tabwidget_stackedwidget and QtTabBarWrapper. The only 
child of QtTabBarWrapper is a close button. The only child of 
QStackedWidget#qt_tabwidget_stackedwidget is DynamicWindow#MainWindow. I am 
not sure if I am using the # correctly. DynamicWindow is the type of 
widget, MainWindow is the object. I think I am doing it corectly as further 
down the tree is Type: LeoQTreeWidget and Object: treeWidget. I have 
successfully put these together LeoQTreeWidget#treeWidget and styled the 
result. In fact it is the only way I could style the outline tree. 
QTreeView works for most everything else in that window but the background 
and the font.

None of the top three types/objects are styleable. At least not using the 
type alone or the combination of type#object.

Chris




-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Basic Layout of the Leo GUI

[Chris George]

My system is haunted. GammaRay suddenly stopped working. I am
currently rebuilding it to reinstall.

GammaRay displays all of the attributes available for Qt widgets and
shows which ones have been enabled for that widget.

Was there anything specific you wanted to know? Once I get GammaRay up
and running again I can forward you the info. Or you could try it out
for yourself.


https://github.com/KDAB/GammaRay

Chris




On Mon, Mar 19, 2018 at 9:48 AM, Edward K. Ream  wrote:
> On Mon, Mar 19, 2018 at 10:44 AM, Chris George  wrote:
>
>> According to
>> Gammaray, LeoTabbedTopLevel has the StyleSheet attribute enabled, but not
>> the
>> StyledBackground attribute. Is there a reason for this?
>
>
> Almost certainly this is unplanned.
>
>>
>> Can it be enabled?
>
>
> I would imagine show, but I can find no info about w.
> StyledBackground.
>
> Is there any way to get more info from
> Gammaray.
>
> Edward
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Basic Layout of the Leo GUI

[Edward K. Ream]

On Mon, Mar 19, 2018 at 10:44 AM, Chris George  wrote:

According to
> ​​
> Gammaray, LeoTabbedTopLevel has the StyleSheet attribute enabled, but not
> the
> ​​
> ​​
> ​​
> StyledBackground attribute. Is there a reason for this?
>

​Almost certainly this is unplanned.
​


> Can it be enabled?
>

​I would imagine show, but I can find no info about w.
StyledBackground.

Is there any way to get more info from
​
Gammaray.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Basic Layout of the Leo GUI

[Chris George]

I am working on a logical template for themes.

Part of this is working from the most general to the most specific for 
every visible widget. I should be able to style the top level widget and 
have that style flow down to all other widgets in the ui unless that style 
is overridden specifically for a descendant widget. ie. I can currently 
style a background image for QWidget and have that flow to all visible 
widgets, except for QTabBar. QTabBar will accept font-family, font-size 
etc. but will not accept a directly styled background-image or 
background-color. It inherits the background-color from QWidget, but not 
the background-image.

According to Gammaray, LeoTabbedTopLevel has the StyleSheet attribute 
enabled, but not the StyledBackground attribute. Is there a reason for 
this? Can it be enabled?

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Basic Layout of the Leo GUI

[Edward K. Ream]

On Sun, Mar 18, 2018 at 7:30 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:

> Hi,
>
> I share Terry's opinion on this. Even more considering how particular
> documents could load customizations to buttons and other GUI items.
>

​I have just closed #822.  It would be a lot of work for dubious/negative
gain.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.