pvillez@gmail.com

interface grid "snap to grid" (grid size etc). please, very very

useful, saves a lot of time when building layouts.

interface grid "snap to grid" (grid size etc). please, very very
useful, saves a lot of time when building layouts.

-- 
www.centuryofnoise.com
www.perevillez.com


max-5-interface-wish-item

if possible, include a "user interface layer", where the user can re-order the selected objects (a check box on the inspector window) to create the interface. This re-ordering of the objects on the "user interface layer" do not afect the order of the objects on the "programing Layer".

The "user interface layer" will be the final "face" of the patch builted.

Quote: Rui Caldas wrote on Mon, 30 July 2007 12:22

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

> if possible, include a "user interface layer"

Why not just have "layers" in general, with control over the layers (show, hide, move, lock etc) similar to most layout apps. Individual objects could still be hidden/unhidden on lock within each layer of course.

Quote: Rui Caldas wrote on Mon, 30 July 2007 12:22
----------------------------------------------------
> if possible, include a "user interface layer"

Op 30-jul-2007, om 3:35 heeft John Pitcairn het volgende geschreven:

> Quote: Rui Caldas wrote on Mon, 30 July 2007 12:22

> ----------------------------------------------------

>> if possible, include a "user interface layer"

> Why not just have "layers" in general, with control over the layers 

> (show, hide, move, lock etc) similar to most layout apps. 

> Individual objects could still be hidden/unhidden on lock within 

Zip Boterbloem
Media Mechanics
Zwaluwstraat 54
2025 VR  Haarlem
The Netherlands
+31627014758
zip@knoware.nl

>
> Quote: Rui Caldas wrote on Mon, 30 July 2007 12:22
> ----------------------------------------------------
>> if possible, include a "user interface layer"
>
> Why not just have "layers" in general, with control over the layers  
> (show, hide, move, lock etc) similar to most layout apps.  
> Individual objects could still be hidden/unhidden on lock within  
> each layer of course.
>
> Object groups would be handy too.
>


- and something like a user patch library would be great. like tweaky, maybe.

Op 4-aug-2007, om 12:37 heeft i.te het volgende geschreven:

> - and something like a user patch library would be great. like

What's wrong with http://www.maxobjects.com/?

>
> - and something like a user patch library would be great. like
> tweaky, maybe.
>
> best


this thread gave me a beserk idea which might actually be doable.

put a directory in max objects.com (or somewhere else) that just had a ton of max-text files. it could even be two layers deep so that we could have categories. Any registrant could upload a patch.

write an mxj which takes a max-text file name and does the following

A. goes to said directory and reads the text named txt file.

B. Pastes the abstraction into the patcher where you instantiated the mxj.

End result: communal patch library in the cloud.

this thread gave me a beserk idea which might actually be doable. 

Step 1
put a directory in max objects.com (or somewhere else) that just had a ton of max-text files.  it could even be two layers deep so that we could have categories.  Any registrant could upload a patch.

Step 2.
write an mxj which takes a max-text file name and does the following

A. goes to said directory and reads the text named txt file.
B. Pastes the abstraction into the patcher where you instantiated the mxj.
C. deletes itself.

End result: communal patch library in the cloud.


> I Just had a beserk idea which might actually be doable. 

> put a directory in max objects.com (or somewhere else) that just had a ton of max-text files. it could even be two layers deep so that we could have categories. Any registrant could upload a patch.

> write an mxj which takes a max-text file name and does the following

> A. goes to said directory and reads the text named txt file.

> B. Pastes the abstraction into the patcher where you instantiated the mxj.

> End result: communal patch library in the cloud.

That idea is brilliant in its simplicity, man... we should so do this... 

ahem, so, anybody feel up to the challenge?

Matthew Aidekman skrev:
> I Just had a beserk idea which might actually be doable. 
>
> Step 1
> put a directory in max objects.com (or somewhere else) that just had a ton of max-text files.  it could even be two layers deep so that we could have categories.  Any registrant could upload a patch.
>
> Step 2.
> write an mxj which takes a max-text file name and does the following
>
> A. goes to said directory and reads the text named txt file.
> B. Pastes the abstraction into the patcher where you instantiated the mxj.
> C. deletes itself.
>
>
>
> End result: communal patch library in the cloud.
That idea is brilliant in its simplicity, man... we should so do this... 
ahem, so, anybody feel up to the challenge?

getting the text off the net appears to be the easy part.

I just looked at the max api. I'm not sure we can reliably convert max-text to patcher commands. I'm not knowledgable enough to do things like embedded values etc.

it would be cool though. maybe we can load it into the clipboard and get max to "paste" some how.

I just looked at the max api.  I'm not sure we can reliably convert max-text to patcher commands. I'm not knowledgable enough to do things like embedded values etc.

it would be cool though.  maybe we can load it into the clipboard and get max to "paste" some how.


>> write an mxj which takes a max-text file name and does the following

> That idea is brilliant in its simplicity, man... we should so do this... 

> ahem, so, anybody feel up to the challenge?

I don't see the need for the mxj in step 2, as you can copy past patches 

already directly... It just needs a database with the abstractions as 

Andreas Wetterberg schrieb:
>> Step 2.
>> write an mxj which takes a max-text file name and does the following
>>
> That idea is brilliant in its simplicity, man... we should so do this... 
> ahem, so, anybody feel up to the challenge?

I don't see the need for the mxj in step 2, as you can copy past patches 
already directly... It just needs a database with the abstractions as 
text...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


>>> write an mxj which takes a max-text file name and does the following

>> That idea is brilliant in its simplicity, man... we should so do 

>> this... ahem, so, anybody feel up to the challenge?

> I don't see the need for the mxj in step 2, as you can copy past 

> patches already directly... It just needs a database with the 

Well, getting winXP to copy/paste automatically isn't all that simple... 

Stefan Tiedje skrev:
> Andreas Wetterberg schrieb:
>>> Step 2.
>>> write an mxj which takes a max-text file name and does the following
>>>
>> That idea is brilliant in its simplicity, man... we should so do 
>> this... ahem, so, anybody feel up to the challenge?
>
> I don't see the need for the mxj in step 2, as you can copy past 
> patches already directly... It just needs a database with the 
> abstractions as text...
Well, getting winXP to copy/paste automatically isn't all that simple... 
is it? We're two kinds of OSes here.
Andreas.


> I don't see the need for the mxj in step 2, as you can copy past patches 

> already directly... It just needs a database with the abstractions as text...

move to objects to desired location in patcher

Also, consider a web-based alternative to the new object palette

think about the search field in firefox, where the suggestions are done over the net. (yes everything you google in firefox is seen by a remote computer)

As for applescript. I think it might be a bit slow but worth looking into.

> I don't see the need for the mxj in step 2, as you can copy past patches 
> already directly... It just needs a database with the abstractions as  text...

OPTION A:
switch to browser
navigate to site/directory/desired patch
select all
copy
switch to max
paste
move to objects to desired location in patcher

Also, consider a web-based alternative to the new object palette
think about the search field in firefox, where the suggestions are done over the net.  (yes everything you google in firefox is seen by a remote computer)

As for applescript.  I think it might be a bit slow but worth looking into.


> navigate to site/directory/desired patch

> move to objects to desired location in patcher

> Also, consider a web-based alternative to the new object palette

> think about the search field in firefox, where the suggestions are done over the net. (yes everything you google in firefox is seen by a remote computer)

Whatever I want to use I have to know about it before. Option B only 

works, if I have done Option A once. But then I have a lokal copy on my 

computer. Its not attractive to be dependent on having an internet 

connection while patching... (I get my best ideas in the metro... ;-)

Matthew Aidekman schrieb:
> compare:
>
> OPTION A:
> switch to browser
> navigate to site/directory/desired patch
> select all
> copy
> switch to max
> paste
> move to objects to desired location in patcher
>
> OPTION B:
> [mxj webpatch mattsflanger]
>
>
> Also, consider a web-based alternative to the new object palette
> think about the search field in firefox, where the suggestions are done over the net.  (yes everything you google in firefox is seen by a remote computer)

Whatever I want to use I have to know about it before. Option B only 
works, if I have done Option A once. But then I have a lokal copy on my 
computer. Its not attractive to be dependent on having an internet 
connection while patching... (I get my best ideas in the metro... ;-)

you'd need some kind of app that auto-downloaded a text file list of 

available abstractions/externals (their names, short descriptions, 

and # of inlets and outlet) from maxobjects (or a list of places) at 

regular intervals when you had an internet connections. It's be 

great to also have settings (pre-download all of the most popular 

externals? pre-download up to 100MB of externals?). Then, when you 

are patching (possibly offline) you have a patch that floats open in 

your max environment, like the JitterReferenceLauncher extra patch, 

and you can search for and then add either "empty" externals to your 

patch (if you're offline) that have the correct inlets and outlets 

and will be auto-filled in later when you are connected, or if you 

are online it downloads the correct external and adds it max 

externals folder, and since you are using Max 4.6.3 then you just 

have to type it into a blank object box and it loads right up.

Writing out this whole scenario, it seems like it'd be easier to 

simply have a standalone app that could search and auto-download from 

the various max externals sites and stick externals in the proper 

place on your disk ("Cycling74/externals/auto-download"), instead of 

an integrated solution. Unless, you pre-downloaded ALL externals (I 

wonder how many MB of data that would be? A lot? They're not very 

On Aug 8, 2007, at 10:25 PM, Stefan Tiedje wrote:

>> navigate to site/directory/desired patch

>> move to objects to desired location in patcher

>> Also, consider a web-based alternative to the new object palette

>> think about the search field in firefox, where the suggestions are 

>> done over the net. (yes everything you google in firefox is seen 

> Whatever I want to use I have to know about it before. Option B 

> only works, if I have done Option A once. But then I have a lokal 

> copy on my computer. Its not attractive to be dependent on having 

> an internet connection while patching... (I get my best ideas in 

you'd need some kind of app that auto-downloaded a text file list of  
available abstractions/externals (their names, short descriptions,  
and # of inlets and outlet) from maxobjects (or a list of places) at  
regular intervals when you had an internet connections.  It's be  
great to also have settings (pre-download all of the most popular  
externals? pre-download up to 100MB of externals?).  Then, when you  
are patching (possibly offline) you have a patch that floats open in  
your max environment, like the JitterReferenceLauncher extra patch,  
and you can search for and then add either "empty" externals to your  
patch (if you're offline) that have the correct inlets and outlets  
and will be auto-filled in later when you are connected, or if you  
are online it downloads the correct external and adds it max  
externals folder, and since you are using Max 4.6.3 then you just  
have to type it into a blank object box and it loads right up.

Writing out this whole scenario, it seems like it'd be easier to  
simply have a standalone app that could search and auto-download from  
the various max externals sites and stick externals in the proper  
place on your disk ("Cycling74/externals/auto-download"), instead of  
an integrated solution.  Unless, you pre-downloaded ALL externals (I  
wonder how many MB of data that would be?  A lot?  They're not very  
big...)

> Matthew Aidekman schrieb:
>> compare:
>> OPTION A:
>> switch to browser
>> navigate to site/directory/desired patch
>> select all
>> copy
>> switch to max
>> paste
>> move to objects to desired location in patcher
>> OPTION B:
>> [mxj webpatch mattsflanger]
>> Also, consider a web-based alternative to the new object palette
>> think about the search field in firefox, where the suggestions are  
>> done over the net.  (yes everything you google in firefox is seen  
>> by a remote computer)
>
> Whatever I want to use I have to know about it before. Option B  
> only works, if I have done Option A once. But then I have a lokal  
> copy on my computer. Its not attractive to be dependent on having  
> an internet connection while patching... (I get my best ideas in  
> the metro... ;-)
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>


I feel that need to point out that such a system sounds like a great way to more easily deliver malicious software to a Max user's computer. Most of us wouldn't download arbitrary executables and run them on our computer, but unfortunately Max is so cool that most/all of us do just that all the time with Max externals. I think making it require a little bit of effort to seek out externals that I know I want and probably have heard about on the forum, and being very much aware that I am installing someone else's code on my machine, is not such a bad thing. I wouldn't for example, want a tool auto-installing browser plug-ins for me.

Anyway, I am probably being overly paranoid. And don't get me wrong, in many ways I do like this idea, it's just that I worked in the software security industry for a while and over and over again I've seen people sacrifice their security and privacy for a little bit of convenience.

So I'm wondering if some of this convenience is better implemented by improving the maxobjects.com site. Like let me download the externals directly from the site (don't I always have to follow links to the authors home page right now?). And make it really easy to view the text for abstractions right on the site, so they can be easily copy and pasted into Max. In some ways, I guess it's not that different than the tool you are proposing, but it feels better to me that I have to more actively go out and seek the external.

Also, having RSS/atom feeds of any objects newly posted would be pretty cool so I could stay more easily up to date on new objects people are posting.

Quote: Matthew Aidekman wrote on Tue, 07 August 2007 16:20

> > I don't see the need for the mxj in step 2, as you can copy past patches 

> > already directly... It just needs a database with the abstractions as text...

> As for applescript. I think it might be a bit slow but worth looking into.

I feel that need to point out that such a system sounds like a great way to more easily deliver malicious software to a Max user's computer. Most of us wouldn't download arbitrary executables and run them on our computer, but unfortunately Max is so cool that most/all of us do just that all the time with Max externals. I think making it require a little bit of effort to seek out externals that I know I want and probably have heard about on the forum, and being very much aware that I am installing someone else's code on my machine, is not such a bad thing. I wouldn't for example, want a tool auto-installing browser plug-ins for me. 

Quote: Matthew Aidekman wrote on Tue, 07 August 2007 16:20
----------------------------------------------------
> > I don't see the need for the mxj in step 2, as you can copy past patches 
> > already directly... It just needs a database with the abstractions as  text...
>
> compare:
>
> OPTION A:
> switch to browser
> navigate to site/directory/desired patch
> select all
> copy
> switch to max
> paste
> move to objects to desired location in patcher
>
> OPTION B:
> [mxj webpatch mattsflanger]
>
>
> Also, consider a web-based alternative to the new object palette
> think about the search field in firefox, where the suggestions are done over the net.  (yes everything you google in firefox is seen by a remote computer)
>
>
> As for applescript.  I think it might be a bit slow but worth looking into.
----------------------------------------------------


you know something? I've taken a half assed idea way to far in this thread... Its true malicious code would be absolutely horrible in this case. I personally hate being dependant on the internet to program java.

you know something?  I've taken a half assed idea way to far in this thread...  Its true malicious code would be absolutely horrible in this case.  I personally hate being dependant on the internet to program java.

Quote: johnpitcairn wrote on Sun, 29 July 2007 19:35

> > if possible, include a "user interface layer"

> Why not just have "layers" in general, with control over the layers (show, hide, move, lock etc) similar to most layout apps. Individual objects could still be hidden/unhidden on lock within each layer of course.

you know, it would be enough already if max patches would not always move the window content as soon as the window is smaller than the patching area - which makes me not using patches bigger than my monitor atm.

if stuff wouldnt jump to 0 0 position al the time i would not min d scrolling through patches which are 5 times bigger than my monitors.

Quote: johnpitcairn wrote on Sun, 29 July 2007 19:35
----------------------------------------------------
> Quote: Rui Caldas wrote on Mon, 30 July 2007 12:22
> ----------------------------------------------------
> > if possible, include a "user interface layer"
>
> Why not just have "layers" in general, with control over the layers (show, hide, move, lock etc) similar to most layout apps. Individual objects could still be hidden/unhidden on lock within each layer of course.
>
> Object groups would be handy too.
>
----------------------------------------------------

> Writing out this whole scenario, it seems like it'd be easier to simply 

> have a standalone app that could search and auto-download from the 

> various max externals sites and stick externals in the proper place on 

> your disk ("Cycling74/externals/auto-download"), instead of an 

> integrated solution. Unless, you pre-downloaded ALL externals (I wonder 

> how many MB of data that would be? A lot? They're not very big...)

I am always downloading any externals I come across. This piled up to 

2.9 GB on my harddrive over more than 15 years.

The size of externals I put into my search path is 2.6 MB or one 

The main problem is actually categorisation. Not availability or 

something like that. But that is a very personal thing, that is one of 

the reasons why I made my Max Overview patch. There I can do the 

evan.raskob [lists] schrieb:
> Writing out this whole scenario, it seems like it'd be easier to simply 
> have a standalone app that could search and auto-download from the 
> various max externals sites and stick externals in the proper place on 
> your disk ("Cycling74/externals/auto-download"), instead of an 
> integrated solution.  Unless, you pre-downloaded ALL externals (I wonder 
> how many MB of data that would be?  A lot?  They're not very big...)

I am always downloading any externals I come across. This piled up to 
2.9 GB on my harddrive over more than 15 years.
The size of externals I put into my search path is 2.6 MB or one 
thousandth of it...

The main problem is actually categorisation. Not availability or 
something like that. But that is a very personal thing, that is one of 
the reasons why I made my Max Overview patch. There I can do the 
categorisation in a personalised way...
Therefore Maxobjects is all I need...

max 5 interface wish item