Julian, it sounds like you're looking at the debugger in the browser. Look at the console and use the console.log() function to give you a better idea of what's going on.

On Wed, Jun 24, 2015 at 6:35 AM s p <sebpiq@gmail.com> wrote:
No worries :)

Short answer ... yes the JS file which contains all the WebPd code is "webpd-latest.js"

I could give you more infos if you tell me what you are looking for exactly!

On Wed, Jun 24, 2015 at 1:15 PM, Julian Brooks <jbeezez@gmail.com> wrote:
Apologies for vagueness, not explaining myself very well.

In the browser debugging console there are source files on the left side.

In which of those is the js version of the pd patch running, or am I missing something fundamental (it wouldn't surprise me)?

Cheers Seb,

Jb

On 24 June 2015 at 10:53, s p <sebpiq@gmail.com> wrote:
Julian, what do you mean by "action" ? All messages (and error messages) are directly printed to the browser console, so there is no special "WebPd debgging console".

Is that what you mean?

On Wed, Jun 24, 2015 at 12:45 PM, Julian Brooks <jbeezez@gmail.com> wrote:
Thanks a lot Seb, will be back in touch when I'm stuck again.

Pall, your comment throws up a good question: I'm not sure where the pd patch 'action' is taking place in the debugging console, is it in 'webpl-latest.js'?

Regards,

Julian

On 24 June 2015 at 08:26, s p <sebpiq@gmail.com> wrote:
Hi Julian,

In that area there sure is room for improvement, and I should integrate WebPd better with pd-fileutils (which is the module used to render patches to SVG, but also to parse patches from text file to JavaScript). For the moment, you can use the same hack I've used in the examples : https://github.com/sebpiq/WebPd/blob/master/examples/phasor/index.html#L42
Basically, pd-fileutils is available globally as "pdfu" (ideally it shouldn't be there). Then you take the patch file you loaded (here called "mainStr") you re-parse it with pdfu (ideally you shouldn't need to do), you render the result as SVG and insert the SVG in your web page. In the example it is done in one line, but decomposing the whole thing looks like :

var parsedPatch = pdfu.parse(mainStr)
var svgStr = pdfu.renderSvg(parsedPatch, {svgFile: false, ratio: 1.5})
$('#svg').html(svgStr)


Hope this helps. Please tell me if you need more help.

On Wed, Jun 24, 2015 at 2:09 AM, Pall Thayer <pallthay@gmail.com> wrote:
What does your browser's javascript console say? Any errors showing up?

On Tue, Jun 23, 2015 at 7:03 PM Julian Brooks <jbeezez@gmail.com> wrote:
Hello,

I'm exploring WebPd and am stuck - hopefully someone can advise.

Going through Seb's gitpage (good job Seb btw, this is great) I get stuck when attempting to create an svg for my own supersimple patch.

Following instructions from here:
https://github.com/sebpiq/WebPd#step-by-step-guide

I've got as far as successfully loading myPatch.pd and can hear it.

Would like my patch to appear like your 'example' patches in a browser.

I'm think it's something to do with 'pd-fileutils' but not sure what to do next?

Thanks in advance,

Julian
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list



--
Sébastien Piquemal

 ----- @sebpiq
 ----- http://funktion.fm




--
Sébastien Piquemal

 ----- @sebpiq
 ----- http://funktion.fm




--
Sébastien Piquemal

 ----- @sebpiq
 ----- http://funktion.fm