It seems that GLMTabulator when creating rows, does not take into account
size of the container into which rows are placed. The bottom row surpasses
the size of its container by the amount of the size specified for the top
row and it is not completely visible. Here is a script that shows the
problem.
|tab|
tab := GLMTabulator new.
tab column: [ :col |
col
row: #first size: 80;
row: #second;
row: #third size: 100].
tab transmit to: #first; andShow: [:a | a dropDownList display: [:x | 1 to:
x ] ].
tab transmit to: #second; andShow: [:a | a list display: [:x | 1 to: x ]
].tab transmit to: #third; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab openOn: 10
I know the specifying size as span shows correctly the tree rows but then
droplistMorph get resized awkwardly, and size works better for the widget.
Is this a known issue?
usman
[image: Inline image 2]
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1039 by ssadams....(a)gmail.com: Glamour layout clipping bug
http://code.google.com/p/moose-technology/issues/detail?id=1039
When sizing a presentation row, I noticed the bottom pane extends below the
top window bounds and is clipped.
browser := GLMTabulator new.
browser row:#textField size:30;
row: #listField.
browser transmit to:#textField; andShow:[:a| a text
display:[:x| 'Hello Doru!']].
browser transmit to:#listField; andShow:[:a| a list
display:[:x| 1to:200]].
browser openOn: 123
Additional information: platform, context which may impact the problem
Pharo 2.0
ConfigurationOfGlamour-TudorGirba.123
* Type-Defect
* Component-Glamour
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1083 by chisvasi...(a)gmail.com: Wrong offset when rendering a
GLMTabulator
http://code.google.com/p/moose-technology/issues/detail?id=1083
The renderer of a GLMTabulator does not properly compute the offset of a
column/row if a column/row contains at the end multiple panes with a fixed
size:
|tab|
tab := GLMTabulator new.
tab
row: #first size: 100;
row: #second;
row: #third size: 100;
row: #forth size: 100.
tab transmit to: #first; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #second; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #third; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #forth; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab openOn: 10
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 757 by tudor.gi...(a)gmail.com: Smalltalk completion appears at
absolute coordinates, instead of relative ones in Finder
http://code.google.com/p/moose-technology/issues/detail?id=757
Try this:
GLMFinder new
show: [:a |
a smalltalkCode ];
openOn: ''.
and then type "1 as".
You will see that the completion appears in the top right of the world,
instead of the top right of the text pane. This only happens in the finder,
and it is likely due to some problems of transforming coordinates.
Good, now I can try it. How do you deal with copy books?
I really like that you remembered that Cobol should be
compilable in less than 16K of ram. Multiple stages really
help understandability here.
Stephan
Hello Moose developers,
Trying this list, because it looks like info(a)moosetechnology.org<mailto:info@moosetechnology.org> is not so actively read ;-)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
Is this correct?
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
All answers or pointers to the correct people are welcome.
Greetings,
Peter
Peter Goessaert
Software Engineer
T +32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
peter.goessaert(a)mediagenix.tv<mailto:peter.goessaert@mediagenix.tv>
www.mediagenix.tv<http://www.mediagenix.tv>
[cid:logomediagenix2013-106pxdc2753]<http://www.mediagenix.tv>
This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.
From: Peter Goessaert
Sent: vrijdag 27 juni 2014 11:38
To: 'info(a)moosetechnology.org'
Subject: EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
Is this correct?
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings,
Peter
Hi,
The GTInspector now offers dedicated presentations for managing keybindings
defined with the KeyMapping framework.
For example, the attached screenshot shows how you can go through the
submorphs and preview the associated keybindings.
[image: Inline image 2]
Here is a more detailed description of what is available:
http://www.humane-assessment.com/blog/managing-morph-keybindings-with-gtins…
Let us know what you think.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello. It gives me great pleasure to announce my COBOL parser. This is a
fixed format COBOL parser. I expect that it could be expanded to work with
free format COBOL, but I have not need for that use.
Code is located at:
http://www.smalltalkhub.com/#!/~cbc/PetitCobol
To invoke the parser, evalutate:
CobolProg parseCobolCodingForm: <fileName>
This 'parser' contains 4 parsers plus a fair amount of additional logic to
prep the files for for the prarsers (and output from previous parsers for
later parsers). The rough outline of what happens:
1) File is read line by line. Each line is parsed as a formatted card.
2) Take these cards, and format them into sentences.
3) Parse the coding structure. (Parse it out into the various divisions,
and parse out the level 01 data).
4) Aggregate the structure into a segments.
5) Finally, parse the actual code, division by division.
The parser includes a full AST representation, along with a visitor to
subclass to help handling the resulting AST.
The parser is not complete - it should parse any fixed format COBOL program
file, but not all commands are implemented. I have implemented a way to
iteratively develop the parser. It will continue to parse each sentence
up to a point where it cannot continue - at that point, it will parse into
a CDJunk (for data division unknowns) and CobolStatement (for program
division unknowns). This later will point out any missing commands (which
exist), or possibly incomplete commands (which may exist); a simple visitor
over the AST trapping for those nodes should find them.
The result of the parse will leave you with a CobolProg containing the
final parsed AST in the variable formattedStructure. Comments in the code
will be in the variable comments (along with the line number that they
originated from). In addition, most of the interim steps will also be
present in the CobolProg instance, should you be interested in them. If
not, you can send #cleanup to the instance to get rid of all but the final
AST nodes.
Thanks,
cbc