Re: easy display system?

2013/7/17 Carlo Capelli <[email protected]>

>
>
>
> 2013/7/17 Alan Baljeu <[email protected]>
>
>> basically view_term(Term) opens a window to show that term.
>>
>> I've never heard of prolog_ide(debug_monitor).  It might be useful as
>> well.
>>
>> I'm not sure yet what will be most useful.  I'd want a window dedicated
>> to one thing, and show a list of such things in there.
>
>
> Alan, I think the simpler interface could be just multiple named consoles.
> I learned about them these days, attempting to complete the Qt console
> port (thanks to Jan, we are near to something working now),
> but if you can prototype under Windows (or you are incline to the bleeding
> edge, testing our efforts toward Qt portability layer) see plwin<http://www.swi-prolog.org/pldoc/man?section=plwin>interface.
>
>
I forgot: fdqueens <https://github.com/CapelliC/fdqueens> showcases a
CLP(FD) mini application interface, reusing this
code<http://web.student.tuwien.ac.at/~e0225855/queens/queens.html>from
Markus, thus showing attributed vars state change.
If you can think of some graphical interface specification, maybe I could
help.


bye Carlo
>
>
>>  But it might be more convenient to have a window that I just send things
>> to it one by one, like that debug monitor.
>> (Example, list all my constraints in the active group)
>>
>> Alan Baljeu
>>
>>
>> ----- Original Message -----
>> From: Anne Ogborn <[email protected]>
>> To: Alan Baljeu <[email protected]>
>> Cc: Prolog <[email protected]>
>> Sent: Tuesday, July 16, 2013 5:29:40 PM
>> Subject: Re: [SWIPL] easy display system?
>>
>> ok, I'm stumped - what's view_term  ??
>>
>> Alan - I assume you're aware of  prolog_ide(debug_monitor).
>> which opens a window where you can look at a keyword typed, controllable
>> log of debug/3 messages.
>>
>>
>>
>> On 07/16/2013 09:54 PM, Alan Baljeu wrote:
>> > I've got a nice, but complex system working, for which I
>> > now feel I need a higher-level view for tracing its operations.
>> > I've figured at various points in execution certain lists that
>> > would be useful to see sometimes.  Currently the only way
>> > I know is to read and write to the console.  Certainly very
>> > easy, but I wonder if there's another way that's also easy,
>> > but not so scrolly.  Plain message boxes would not be sufficient,
>> > as I'd need persistent access and copy/paste.
>>
>> Not sure what you want.  Select specific messages or selectively
>> (maybe interactively) dig into the details of messages?
>>
>> Selecting messages is fairly well supported using debug/3 for
>> printing them and debug/1 or nodebug/1 for defining which ones
>> are actually printed.  The Windows console offers Debug/Debug messages
>> in the menu, which provides a (simple) GUI interface.  Interactively
>> digging into terms is (in a limited way) provided by the GUI debugger.
>> You can also call this window yourself by loading
>>
>>     :- use_module(library(trace/viewterm)).
>>
>> and then call view_term/1 or view_term/2.  Of course, you know
>> about the portray hook.
>>
>> There is enough stuff around to help you.  Something really fancy
>> and well integrated is still welcome ...
>>
>>     Cheers --- Jan
>>
>>
>> >
>> > Alan Baljeu
>> > _______________________________________________
>> > SWI-Prolog mailing list
>> > [email protected]
>> > https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog
>> >
>>
>> _______________________________________________
>> SWI-Prolog mailing list
>> [email protected]
>> https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog
>> _______________________________________________
>> SWI-Prolog mailing list
>> [email protected]
>> https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog
>>
>
>
-------------- next part --------------
HTML attachment scrubbed and removed