Hi,
Is anyone (Nicolas :)) interested in investigating how difficult would it be to have Java 7 support in VerveineJ?
Cheers,
Doru
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
Hello,
I'm looking to have the selection right-click menu working with
glamour-seaside (which is currently not implemented ?).
Does somoene already woked on this or have any suggestions about how to do
that ?
After looking a bit, maybe it is possible to reuse the scripts used for the
actions menu of a presentation (?)
The "optional" below crashes my Pharo 1.2.2 image, and user interrupt has no
effect...
categoryName := $- asParser negate plus flatten, ($- asParser, #any asParser
star flatten) optional star.
categoryName parse: 'SuperMe'.
Sean
--
View this message in context: http://forum.world.st/PetitParser-crash-tp3725129p3725129.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
I would like to release 4.6. We use it since quite a while now and it is stable. The main reason for the release is to provide users with the fixes related to Glamour and FAMIX.
Cheers,
Doru
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
Status: Started
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Difficulty-Easy
New issue 688 by damien.c...(a)gmail.com: Trait browser #build3StackerBis
dynamic presentation does not work
http://code.google.com/p/moose-technology/issues/detail?id=688
I can't make the dynamic presentation in #build3StackerBis to work. Doru
asked for simple example with numbers to show the problem.
Hi,
The examples from the thesis of Philipp are out of date. The up-to-date documentation is in The Moose Book.
If you want to discuss Glamour, I would suggest to use the moose-dev(a)iam.unibe.ch mailing list - follow the registration from:
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Further examples can be found in the built-in example browser (also done in Glamour):
GLMBasicExamples open
Regarding your first question, the current way to integrate a Workspace is by using something like:
...
a text
forSmalltalk.
Cheers,
Doru
On 4 Aug 2011, at 16:56, Offray Vladimir Luna Cárdenas wrote:
> Hi all,
>
> Following with my idea of Tree like workspace I have started to see Glamour to find my way to the problem. After trying to install it on Pharo and getting some error message I tried the preinstalled version of Moose and followed the Moose Book example[1]. It worked well, and I like the flexibility of glamour to define browsers, but you loose some of the most important characteristic in the Workspace is interactivity (auto-completion, syntax highlighting and so on) So I have some questions:
>
> [1] http://www.themoosebook.org/book/internals/glamour/glimpse
>
> * ¿There is any way to make the details panel contain a Workspace?.
>
> * When I try the first example in the Bunge's Thesis tutorial:
>
> browser := TableLayoutBrowser new.
>
> I don't get full autocompletion on TableLayoutBrowser only until TableLayout. This is because this Class is not supported on Moose Glamour, another reason or Am I misunderstanding something else?
>
> Cheers,
>
> Offray
>
--
www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
Hi,
If you are a member of IEEE Computer Society you are now entitled to vote for the Chair of Technical Council on Software Engineering.
Here is my endorsement: Please vote for Hausi Müller.
The reasons:
- He has a software analysis background which, if nothing else, can serve the interest of our community, and
- He is a very nice person :)
If you want to vote, you can use the instructions below.
Cheers,
Doru
Begin forwarded message:
> Hausi A. Muller, PhD, PEng
> Professor, Department of Computer Science
> Associate Dean Research, Faculty of Engineering
> Department of Computer Science
> Faculty of Engineering
> University of Victoria
> P.O. Box 3055, STN CSC
> Victoria, BC V8W 3P6 Canada
> Voice: 1-250-472-5719
> Fax: 1-250-472-5708
> E-mail: hausi(a)cs.uvic.ca
> Homepage: http://webhome.cs.uvic.ca/~hausi/
> BSENG: http://www.bseng.uvic.ca
> Engineering: http://www.engr.uvic.ca
>
> =====================
> Dear IEEE Computer Society Technical Council on Software Engineering (TCSE) ExCom Members,
>
> The 2011 TCSE Chair and Member-At-Large election is now open. The Chair's term will run from October 1, 2011 through September 30, 2013.
>
> Polls close August 15, 2011, at 5 pm Pacific time.
>
> Before entering the poll, please read the following:
> Please take a few moments to review candidate Biosketches and Position Statements in advance of voting here:
> http://www.computer.org/portal/web/tandc/tcse
>
> To cast your vote, you will need your IEEE CS Member number--to obtain a misplaced number, please
> visit: https://sbwsweb.ieee.org/ecustomercme_enu/start.swe?SWECmd=Login&SWECM=S&SW…
>
> You may vote only one time.
>
> **Only CS Members can vote. **
>
> VOTE here:
> http://www.surveymonkey.com/s/XC6Z6QY
>
> If you have trouble voting, please contact T&C Sr. Program Specialist, Carrie Walsh (ccwalsh(a)computer.org).
>
> *To ensure your TC membership is valid and up to date, please log in to TECA and update your contact information
> and TC affiliation: (https://cima.computer.org/TECA_Login.htm - this requires an IEEE Web account,
> which is available free: http://www.ieee.org/go/create_web_account).
>
> Thank you for your participation in this election.
>
> Sincerely yours,
>
> Carrie
> Carrie Clark Walsh
> Sr. Program Specialist
> IEEE Computer Society
> 10662 Los Vaqueros Circle
> Los Alamitos, CA 90720
> Tel: 714/816-2118
> Fax: 714/821-4010
> URL: http://www.computer.org
>
> IEEE: Advancing Technology for Humanity
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.4
New issue 574 by tudor.gi...(a)gmail.com: Nodes with complex shapes do not
position the children nodes with complex shapes properly
http://code.google.com/p/moose-technology/issues/detail?id=574
Another issue related to complex shapes. Try the following code:
view shape umlClass.
view node: 'hello' forIt: [
view shape umlClass.
view nodes: (1 to: 5).
view verticalLineLayout
]
You will see that the children now move properly with the parent node, but
they are not positioned correctly. However, it works well with simple
shapes for the children.
A more complex example can be seen below:
view shape umlClass.
view node: 'hello' forIt: [
view shape umlClass.
view nodes: (1 to: 5) forEach: [:each |
view shape umlClass.
view nodes: (1 to: each ).
view verticalLineLayout ].
view verticalLineLayout
]
Hi
I've been using Glamour to create a browser for a project that I am working
on.
I have encountered a weird rendering issue when using
GLMCompositePresentation>>accordionArrangement.
The GLMPresentations that I want to display get cut off at the bottom of the
window. The image below shows the problem.
http://forum.world.st/file/n3707211/accordion.png
I have two GLMTextPresentations being displayed in the "Projecting" pane.
One of
them is called "Context Checking" and the other is "Definition". "Context
Checking" and "Definition" are displayed using
GLMCompositePresentation>>accordionArrangement. When I try to expand both of
them, the one at the bottom runs off the screen and it gets cut off. I would
have expected the renderer to space both GLMTextPresentations evenly in the
available vertical space and add scroll bars to them when both are expanded.
I am not sure which part of the code is causing the problem. I am not
intimately
familiar with how Glamour does its layout so any pointers to the cause or
solution to the problem would be appreciated.
A temporary fix that might work would be to set a minimal size for the
window. I
noticed that if the window is big enough i.e. half the screen then the text
does
not get cut off. How can I specify a minimal size for a GLMBrowser window?
Thanks!
--
Nick
--
View this message in context: http://forum.world.st/Glamour-tp3707211p3707211.html
Sent from the Moose mailing list archive at Nabble.com.
I have a grammar that is quite ambiguous. Ambiguities aren't solved easily because the grammar is quite complex and the task of resolving ambiguity is probably not possible. Ambiguities are supposed to be solved later after establishing some context in which it can be resolved.
The biggest source of parsing failures I have because in the alignment of the matching rules a short match often prevents a long match from being found. And I wonder if I can look for the longest match with petit parser. Combining parsers with / always finds the first matching and | does not find anything if more than one rule matches.
Any advize how to do this with petit?
Norbert