The URL object should probably also support normal http requests over the internet also (just passing the URL to the browser, using exec?) I think this would be much more useful than making it a PDDP only object. Actually as an object it would be handy to have:
* Inlet to dynamically change URL from a patch * An inactive mode where an outlet could be connected to a symbol to send the URL to other objects.
Ah just some ideas anyhow (the first point being much more useful than the second!)
I think we did agree on the html viewer being important for some information. I don't recall us discussing what works better in one form compared to the other.
Had a chance to look at the PDDP templates I put up on the wiki?
B?>
Krzysztof Czaja wrote:
B. Bogart wrote: ...
Should the "hyperlink" object be a toxy widget or an external or an internal? Should it just be part of the [comment] or some new [text] object? hyperlinks inline with comments/text would be pretty familiar to
ideally, bulk of the code would be included in pd.tk, driven by a simple comment-like internal class. Until that happens, the pd-gui code would have to be sourced into pd-gui by a simple comment-like external class, instantiated [pddplink mypage.html] or [pddplink mypatch.pd], but presenting itself as an active text, not an object box.
I have the client/server part ready for testing, will try to make the Pd object part during this weekend.
Krzysztof
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev