Hi Hernán, Here are some pointers about Glamour: - Glamour is an engine for building browsers (not user interfaces, like Spec). From the goal point of view, it is similar to OmniBrowser. However, the concepts behind are different: Glamour can cover significantly more browser flows and presentations, and it offers a DSL. - Load it in Pharo 1.4 (this loads also several prerequisites): Gofer new squeaksource: 'Glamour'; package: 'ConfigurationOfGlamour'; load. ConfigurationOfGlamour loadDevelopment. - You can also load only the core by: (ConfigurationOfGlamour project version: 'default') load: #('Core' 'Morhic') - Browse the built-in examples: GLMBasicExamples open. - Read the chapter from The Moose Book: http://www.themoosebook.org/book/internals/glamour You can ask more questions about Glamour also on the Moose mailing list: http://www.moosetechnology.org/about/contact Cheers, Doru On 23 Jun 2012, at 07:09, Hernán Morales Durand wrote:
Hi Esteban
Would you mind to share some link or more comments about Glamour? It would be really nice to see how to do anything beyond code browsing. Cheers,
Hernán
2012/6/22 Esteban Lorenzano <estebanlm@gmail.com> and btw... for that kind of work is incredible simpler to use glamour (you can have exactly the same browser in 15'... I know that because I made it for mongo databases :). At the unique price of load glamour.
Esteban
On Jun 22, 2012, at 9:16 AM, Stéphane Ducasse wrote:
do not confuse Nautilus and Spec. Nautilus is (or should be) defined using Spec.
Spec is the framework for building UI. We are slowly rewriting all the tools based on spec while learning and improving Spec. Ideally we would like to be able to reuse a builder PAINTER (a tool to place widgets on the screen) and to generate Spec.
Stef
On Jun 22, 2012, at 8:14 AM, Hernán Morales Durand wrote:
First let me apologize for asking without properly evaluating first. I took some time and read about Nautilus which it seems a very nice work. I've developed a phylogenetics classifier using OmniBrowser, but I wondered if Nautilus could save me some effort, and I'm planning to test Pharo 1.4 or 2.0 in some future in which AFAIK OmniBrowser will not be supported anymore.
- Some time ago I've modified the OmniBrowser framework to browse anything I wanted in the "code pane" (the lower pane typically used for displaying/editing code), as we had a complex OODB it was very useful, see http://www.youtube.com/watch?v=VxUaOFRHFPk for a demo. However it was not easy to understand the OB internals and make the modifications. Have you tried to implement such feature in Nautilus? - There is documentation for developing browsers with Nautilus? Something which explains the basic architecture, how it differs from OB? for example: --Do you have to define a metagraph? --May I have multiple definition panels? -Do you have a mapping for each node type (class?) with each column? -OB is not cross-UI (it depends on Morphic). Can I use a Nautilus browser within a web browser? - Another thing which is really easy is to define Commands in OB, (although the #isActive logic could become a mess without some care). How it is different in Nautilus?
I'm sure I would rewrite my browsers with Nautilus, my key question is how much of the OB knowledge I can re-use?
Cheers,
Hernán
-- Hernán Morales Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.
-- www.tudorgirba.com "Value is always contextual."