hey tim!

Tim Blechmann wrote:
> hi niklas,
>
>   
>> coding a extensible-browser (most of the skeletton is already done) that 
>> will support the following features:
>>     
>
> i am not sure, if i am understanding correctly, what you mean with the
> term "browser" ... 
> are you speaking of a gui object for the nova language or of a widget of
> the gui?
>   

a "widget" for the gui. well it has to be a tad more than that :)
>   
>> - show nova-objects installed with info (nearly done (hey, i am still 
>> new to all that python stuff and the nova-code :) )
>>     
>
> that is definitely pretty important to figure out, which objects are
> installed ...
>   
well i just wrote some wrapper stuff that builds a list which is then
exportet to python. i have to add the author and lateron the instance_name
field. btw. the isDSP reports always true here, can that be changed once
the descriptions+hints for the objects are added?
>   
>> - show known patches, with additional tagging and a list of recently 
>> opened and saved ones (in progress (needs a db))
>>     
>
> ... useful, too ...
>
> in both cases, in both cases ... i would guess you are talking about gui
> widgets (?)
>   
yes.
>
>
>   
>> planned:
>>     
>
> i guess, it is not that bad to steal some ideas from other systems ...
>
>
>   
>> - simple file browser to allow importing new data to the various 
>> browser-"handlers"
>> - show known samples with additional info like playtime etc and 
>> additional tagging
>>     
>
> max provides a file-browser gui object, ubumenu, that iirc can either be
> filled with messages, or directly accesses the file system (with support
> for extension filtering)
>
>   
like that, yes :)
>> - project browser for easy patch&referenced samples/general 
>> objects-handling and info about the used nova-objects+editing the names
>> (eg. for dynamic patching) & project specific actions (more below)
>> - repository browser for importing patches from a remote repository to 
>> the local library
>> - extensible search function to search patches/samples etc.
>>     
>
> should be plain gui features, no?
>   
yep. but one could also add a query message to the browser-object
for the nova language so you can search the known stuff db-style
with nova objects.
>   
>> - nova-browser object(s) that outputs specific messages accordingly to 
>> their gui events:
>> eg. the sample browser would just output a message with the file-path to 
>> the currently selected sample+bang when the sample should be 
>> played/stoped+simple volume float. messages can be stored in the 
>> action-browser like [store "name" message-content(-[browser.action]
>> - action browser that allows storing such messages, retrieving&editing 
>> them and sending them through the [browser.action] when clicked
>>     
>
> you should definitely have a look at the ubumenu documentation ...
> cycling provides pdf manuals at the site for most of their products
> (http://www.cycling74.com/twiki/bin/view/ProductDocumentation)
>
> cheers, tim
>   

ok, i have a look.

so long...
niklas
> --
> [EMAIL PROTECTED]    ICQ: 96771783
> http://tim.klingt.org
>
> A paranoid is a man who knows a little of what's going on.
>   William S. Burroughs
>   

_______________________________________________
nova-dev mailing list
[email protected]
http://klingt.org/cgi-bin/mailman/listinfo/nova-dev
http://tim.klingt.org/nova

Reply via email to