pelado

i'd like to let you know that my contribution to making jitter more fun(!) is available: p.jit.gl tools

the p.jit.gl objects/tools are designed to provide for easier learning of and experimenting with the many attributes that are avialable to jitter's gl objects by making them a whole lot more transparent and accesible

everyone using jitter gl objects. they are particularly useful to explore the attributes in jitter objects and i think will be especially interesting to beginners.

are there tools for all the other jitter gl objects?

p.jit.gl.template is the starting point for building your own p.jit.gl.object. insert your jitter gl object in the template patch (replace the gridshape object that is there), and follow the instructions to get the menu to reflect it's attributes. you can insert whatever else you like in the patch before saving and using it.

if you make a patch that you think others will find useful then why not share it? there's plenty of jitter objects that haven't got a wrapper yet. if you improve the template in any way then fantastic! share it. get in touch and i can place it on my website.

place the p.jit.gl.tools folder in your max search path and kick off with the p.jit.gl.tools.help patch.

will the template work with non-gl objects?

i haven't tested them extensively but they should work with any jitter object that has attributes exposed using the same format as the gl objects (ie getattributes, getstate etc.)

what are p.jit.gl.tools?
the p.jit.gl objects/tools are designed to provide for easier learning of and experimenting with the many attributes that are avialable to jitter's gl objects by making them a whole lot more transparent and accesible

who are they for?
everyone using jitter gl objects.  they are particularly useful to explore the attributes in jitter objects and i think will be especially interesting to beginners.  

are there tools for all the other jitter gl objects?
p.jit.gl.template is the starting point for building your own p.jit.gl.object.  insert your jitter gl object in the template patch (replace the gridshape object that is there), and follow the instructions to get the menu to reflect it's attributes.  you can insert whatever else you like in the patch before saving and using it.

how can i contribute?
if you make a patch that you think others will find useful then why not share it?  there's plenty of jitter objects that haven't got a wrapper yet.  if you improve the template in any way then fantastic!  share it.  get in touch and i can place it on my website.

how do i use the tools?
place the p.jit.gl.tools folder in your max search path and kick off with the p.jit.gl.tools.help patch.

will the template work with non-gl objects?
i haven't tested them extensively but they should work with any jitter object that has attributes exposed using the same format as the gl objects (ie getattributes, getstate etc.)

where can i get them?
http://www.pelado.co.uk

announce-p-jit-gl-tools

just downloaded & started playing with them, but I can already tell, this is some great stuff!

reminds me a bit of 3DPI, way back in the days of using Director - it was an xtra that made 3D shockwave almost usable (almost) by exposing all the built-in commands in a little window ... this is much more ambitious though.

one minor error: in the p.jit.controls.pat, your poly_mode ubumenus only have a 0 and a 1, they need a 2 as well to render points - (without it, the pointsize field won't do much). Easy enough for anyone to fix, but you might as well fix it at the source.

thanks, these tools are going to be extremely useful, both for !

just downloaded & started playing with them, but I can already tell, this is some great stuff! thanks!

reminds me a bit of 3DPI, way back in the days of using MM Director - it was an xtra (created by an end user) that made 3D shockwave usable (well, almost) by exposing all the well-hidden built-in commands in a little window ... your project is much more ambitious, though.

minor: in the p.jit.controls.pat, your poly_mode ubumenus only have a 0 and a 1, they need a 2 as well to render points (the pointsize field won't do much without it). Easy enough for anyone to change, but you might as well fix it at the source.

thanks again, these tools are going to be incredibly useful, both for teaching & work...

weird - browser freaked out & posted the message before I finished writing it

thanks! i've now updated the package to include polymode 2

thanks!  i've now updated the package to include polymode 2 

Interesting! I'm going to have a close look at this soon.

btw such a shame that I can't simply double click the main path after downloading when the abstractions are in a subfolder.. cycling, please?

On 30 juil. 07, at 10:18, Mattijs Kneppers wrote:

> Interesting! I'm going to have a close look at this soon.

> btw such a shame that I can't simply double click the main path 

> after downloading when the abstractions are in a subfolder.. 

You just have to add the folder to your search path. There's so many 

cases where you don't want your subfolder to be scanned.

> Interesting! I'm going to have a close look at this soon.
>
> btw such a shame that I can't simply double click the main path  
> after downloading when the abstractions are in a subfolder..  
> cycling, please?

You just have to add the folder to your search path. There's so many  
cases where you don't want your subfolder to be scanned.

how about if a folder called 'include' or 'xtra' was present, it'd be 

Am 30.07.2007 um 14:02 schrieb Emmanuel Jourdan:

> On 30 juil. 07, at 10:18, Mattijs Kneppers wrote:

>> Interesting! I'm going to have a close look at this soon.

>> btw such a shame that I can't simply double click the main path 

>> after downloading when the abstractions are in a subfolder.. 

> You just have to add the folder to your search path. There's so 

> many cases where you don't want your subfolder to be scanned.

fredrikolofsson.com klippav.org musicalfieldsforever.com

how about if a folder called 'include' or 'xtra' was present, it'd be  
automatically scanned?

> On 30 juil. 07, at 10:18, Mattijs Kneppers wrote:
>
>> Interesting! I'm going to have a close look at this soon.
>>
>> btw such a shame that I can't simply double click the main path  
>> after downloading when the abstractions are in a subfolder..  
>> cycling, please?
>
> You just have to add the folder to your search path. There's so  
> many cases where you don't want your subfolder to be scanned.
>
> Cheers,
> ej

   #|
      fredrikolofsson.com     klippav.org     musicalfieldsforever.com
   |#


Quote: f wrote on Mon, 30 July 2007 14:14

----------------------------------------------------

> how about if a folder called 'include' or 'xtra' was present, it'd be 

Or another option: a text file per patch that contains relative paths to folders that should be scanned for abstractions (externals would be nice too).

Quote: f wrote on Mon, 30 July 2007 14:14
----------------------------------------------------
> how about if a folder called 'include' or 'xtra' was present, it'd be  
> automatically scanned?
>
> _f  (yes, i'm lazy too)
>

On 30 juil. 07, at 15:44, Mattijs Kneppers wrote:

Quote: Emmanuel Jourdan wrote on Mon, 30 July 2007 15:48

> On 30 juil. 07, at 15:44, Mattijs Kneppers wrote:

Sure, but what do you think of the ideas? Do you recognize the problem that we're trying to solve?

Quote: Emmanuel Jourdan wrote on Mon, 30 July 2007 15:48
----------------------------------------------------
> On 30 juil. 07, at 15:44, Mattijs Kneppers wrote:
>
> > Very good idea! How about this EJ?
>
> I'm just the middle man;-)
>

On 30 juil. 07, at 16:01, Mattijs Kneppers wrote:

> Sure, but what do you think of the ideas? Do you recognize the 

I do. In the meantime, adding the folder in the search path is the 

> Sure, but what do you think of the ideas? Do you recognize the  
> problem that we're trying to solve?

I do. In the meantime, adding the folder in the search path is the  
only solution I can think about.

why not just put a folder on your desktop (call it include or xtra or whatever) & put an alias to it inside your search path?

anything you download to that folder will automatically be scanned next time you start up Max...

in case anyone cares, my solution to the search path problem is to use the following abstraction to add whatever folders need to be added to the search path, and then remove them when the patch is closed.

put these two files inside a project root folder, the same level as the folders that you are adding to the search path.

this enables you to set search paths for individual projects.

(uses _ , just replace with "prepend set" if need be).

in case anyone cares, my solution to the search path problem is to use the following abstraction to add whatever folders need to be added to the search path, and then remove them when the patch is closed.
put these two files inside a project root folder, the same level as the folders that you are adding to the search path.
this enables you to set search paths for individual projects.
(uses _ , just replace with "prepend set" if need be).

Quote: robtherich wrote on Tue, 31 July 2007 01:25

> in case anyone cares, my solution to the search path problem is to use the following abstraction to add whatever folders need to be added to the search path, and then remove them when the patch is closed.

> put these two files inside a project root folder, the same level as the folders that you are adding to the search path.

> this enables you to set search paths for individual projects.

If I get this right though, the folders are added -after- the patch containing your abstraction has loaded. So how does this make files visible that are required -during- load?

Quote: robtherich wrote on Tue, 31 July 2007 01:25
----------------------------------------------------
> in case anyone cares, my solution to the search path problem is to use the following abstraction to add whatever folders need to be added to the search path, and then remove them when the patch is closed.
> put these two files inside a project root folder, the same level as the folders that you are adding to the search path.
> this enables you to set search paths for individual projects.

i open this patch first and then open my project patches.

Quote: robtherich wrote on Wed, 01 August 2007 02:36

> i open this patch first and then open my project patches.

The main reason for me to ask for an option to auto-include subfolders in the search path is that I want be able to provide a download that people can open with a double click without having to juggle with other files first.

Quote: robtherich wrote on Wed, 01 August 2007 02:36
----------------------------------------------------
> i open this patch first and then open my project patches.
----------------------------------------------------

one of the potential problems with robtherich's suggestion is that you might inadvertently change someone's searchpath permanently to reflect the new settings. if you use 0 or no number as the second argument to filepath then the search path is not saved in the max preference file, so it is truly temporary, or at least till the preference is changed or max is shut down. 

one way to approach the issue is in the patch below. if you take the p.jit.gl.tools folder out of your search path, place this patch in it and open it first, you can then direct people to launch patches that reside in the folder and have subpatches in a subfolder. of course, there is still an intermediate stage to getting to the patch. maybe javascript has a way of ensuring that the search path is adjusted before the rest of your main patch is loaded?

one of the potential problems with robtherich's suggestion is that you might inadvertently change someone's searchpath permanently to reflect the new settings.  if you use 0 or no number as the second argument to filepath then the search path is not saved in the max preference file, so it is truly temporary, or at least till the preference is changed or max is shut down.  
one way to approach the issue is in the patch below.  if you take the p.jit.gl.tools folder out of your search path, place this patch in it and open it first, you can then direct people to launch patches that reside in the folder and have subpatches in a subfolder.  of course, there is still an intermediate stage to getting to the patch.  maybe javascript has a way of ensuring that the search path is adjusted before the rest of your main patch is loaded?

Quote: pelado wrote on Wed, 01 August 2007 12:51

of course, there is still an intermediate stage to getting to the patch. maybe javascript has a way of ensuring that the search path is adjusted before the rest of your main patch is loaded?

I don't think there is any way to do this at the moment, with javascript, java nor a custom external. Events are triggered after all objects are instantiated (not necessarily intialized), which makes sense. So this option needs to be built in separately by cycling.

Quote: pelado wrote on Wed, 01 August 2007 12:51
----------------------------------------------------
of course, there is still an intermediate stage to getting to the patch.  maybe javascript has a way of ensuring that the search path is adjusted before the rest of your main patch is loaded?
>
>

announce: p.jit.gl tools