[zakky]

Yep, unless you actually want to change the search locations

you manage to make me feel stupid

Also, be aware that if you're going to hack config files like this, Awasu must not be running when you do it.

well not really cool but understandable.. hmm.. well

[zakky]

Yep, unless you actually want to change the search locations

you manage to make me feel stupid

Also, be aware that if you're going to hack config files like this, Awasu must not be running when you do it.

well not really cool but understandable.. hmm.. well

[support]

you manage to make me feel stupid

The Australian sense of humour is like its countryside: very dry.

[support]

you manage to make me feel stupid

The Australian sense of humour is like its countryside: very dry.

[kevotheclone]

zakky wrote:

Step 1: User sets up search channels in Awasu, without providing query string

I've tried this and my version (2.3 Pro) of Awasu's UI won't let me create a Search Channel without specifying a search term, and when the "Advance Syntax" setting is enabled I can't specify just the "*" wildcard character (as documented in Awasu's Help file). So you may have to specify some placeholder text that will be replaced by your script.

Search Channel file names seem to be sequentially numbered and it appears that you can simply clone an existing "n.channel" file and save it with the next sequential number and Awasu will load it the next time it is run, but Taka will have to confirm if this is a good practice, as I don't know if the cloned channel get indexed by Awasu's search engine, etc.

If cloning a Search Channel's "n.channel" file is a viable option then new possibilities open up: such as maintaining a Search Channel "template" file that you populate with your search criteria from text files or a database query and then save an updated copy of the "template" file to Awasu's "Channels" directly with the next sequential number. A simple 3 table database with a UI for your users to manage many "word lists" linked to many Awasu Search Channel files.

[kevotheclone]

zakky wrote:

Step 1: User sets up search channels in Awasu, without providing query string

I've tried this and my version (2.3 Pro) of Awasu's UI won't let me create a Search Channel without specifying a search term, and when the "Advance Syntax" setting is enabled I can't specify just the "*" wildcard character (as documented in Awasu's Help file). So you may have to specify some placeholder text that will be replaced by your script.

Search Channel file names seem to be sequentially numbered and it appears that you can simply clone an existing "n.channel" file and save it with the next sequential number and Awasu will load it the next time it is run, but Taka will have to confirm if this is a good practice, as I don't know if the cloned channel get indexed by Awasu's search engine, etc.

If cloning a Search Channel's "n.channel" file is a viable option then new possibilities open up: such as maintaining a Search Channel "template" file that you populate with your search criteria from text files or a database query and then save an updated copy of the "template" file to Awasu's "Channels" directly with the next sequential number. A simple 3 table database with a UI for your users to manage many "word lists" linked to many Awasu Search Channel files.

[support]

Search Channel file names seem to be sequentially numbered and it appears that you can simply clone an existing "n.channel" file and save it with the next sequential number and Awasu will load it the next time it is run, but Taka will have to confirm if this is a good practice, as I don't know if the cloned channel get indexed by Awasu's search engine, etc.

Search channels get numeric names because they have to be called something when they are created and generating a name based on the search query itself is not a good idea.

When Awasu starts up, it processes every <tt>.CHANNEL</tt> file it finds in the <tt>Channels</tt> sub-directory, regardless of name, and figures out what kind of channel it is based on its contents. So, if you want to create a new search channel, just create a new file with a <tt>.CHANNEL</tt> extension with the appropriate <tt>QueryString</tt> setting and Awasu will load it the next time it starts.

Copying an existing </tt>.CHANNEL</tt> file is a seriously Bad Idea - channels get assigned a unique ID for internal purposes and copying the file will duplicate this ID.

[support]

Search Channel file names seem to be sequentially numbered and it appears that you can simply clone an existing "n.channel" file and save it with the next sequential number and Awasu will load it the next time it is run, but Taka will have to confirm if this is a good practice, as I don't know if the cloned channel get indexed by Awasu's search engine, etc.

Search channels get numeric names because they have to be called something when they are created and generating a name based on the search query itself is not a good idea.

When Awasu starts up, it processes every <tt>.CHANNEL</tt> file it finds in the <tt>Channels</tt> sub-directory, regardless of name, and figures out what kind of channel it is based on its contents. So, if you want to create a new search channel, just create a new file with a <tt>.CHANNEL</tt> extension with the appropriate <tt>QueryString</tt> setting and Awasu will load it the next time it starts.

Copying an existing </tt>.CHANNEL</tt> file is a seriously Bad Idea - channels get assigned a unique ID for internal purposes and copying the file will duplicate this ID.

[kevotheclone]

Copying an existing .CHANNEL file is a seriously Bad Idea - channels get assigned a unique ID for internal purposes and copying the file will duplicate this ID.

That's right, there's the "ChannelGuid" entry that needs to be unique. Ok zakky, scratch that whole "clone channel templates" idea, which is kind of what I suspected, that's why I immediately asked for Taka's input.

Well you can still manually setup the Search Channels in Awasu with some placeholder text that will be replaced by your script, and that's a pretty fast way to update multiple channels with varying large query strings.

[kevotheclone]

Copying an existing .CHANNEL file is a seriously Bad Idea - channels get assigned a unique ID for internal purposes and copying the file will duplicate this ID.

That's right, there's the "ChannelGuid" entry that needs to be unique. Ok zakky, scratch that whole "clone channel templates" idea, which is kind of what I suspected, that's why I immediately asked for Taka's input.

Well you can still manually setup the Search Channels in Awasu with some placeholder text that will be replaced by your script, and that's a pretty fast way to update multiple channels with varying large query strings.

[support]

That's right, there's the "ChannelGuid" entry that needs to be unique.

IIRC, that's only used for sync'ing channels. The one I was referring to is <tt>LocalChannelId</tt>.

Cloning an existing channel is not really necessary since it's pretty easy to create new channels. Just set up a <tt>.CHANNEL</tt> file as I described above, with any other fields included as necessary e.g. channel name, update interval, etc.

[support]

That's right, there's the "ChannelGuid" entry that needs to be unique.

IIRC, that's only used for sync'ing channels. The one I was referring to is <tt>LocalChannelId</tt>.

Cloning an existing channel is not really necessary since it's pretty easy to create new channels. Just set up a <tt>.CHANNEL</tt> file as I described above, with any other fields included as necessary e.g. channel name, update interval, etc.

[zakky]

can you list the required parameter lines that are a must-have in the channel file?

if, as you say, i just create a new .channel file won't i have to provide a unique ID for ChannelGuid and LocalChannelID?

I would need detailed instructions on what must be included in the channel file.

thank you,

[zakky]

can you list the required parameter lines that are a must-have in the channel file?

if, as you say, i just create a new .channel file won't i have to provide a unique ID for ChannelGuid and LocalChannelID?

I would need detailed instructions on what must be included in the channel file.

thank you,

[support]

can you list the required parameter lines that are a must-have in the channel file?

As I described above.

if, as you say, i just create a new .channel file won't i have to provide a unique ID for ChannelGuid and LocalChannelID?

Awasu automatically assigns one if it's not there.

[support]

can you list the required parameter lines that are a must-have in the channel file?

As I described above.

if, as you say, i just create a new .channel file won't i have to provide a unique ID for ChannelGuid and LocalChannelID?

Awasu automatically assigns one if it's not there.

[zakky]

So, if you want to create a new search channel, just create a new file with a .CHANNEL extension with the appropriate QueryString setting and Awasu will load it the next time it starts.

awasu is able to work with a one-line .channel file? and the other settings are random? i don't get it but I will waste my time trying to figure it out myself.

[zakky]

So, if you want to create a new search channel, just create a new file with a .CHANNEL extension with the appropriate QueryString setting and Awasu will load it the next time it starts.

awasu is able to work with a one-line .channel file? and the other settings are random? i don't get it but I will waste my time trying to figure it out myself.

[support]

and the other settings are random?

Random?! Sigh...

Awasu will use sensible defaults for values that are not present. Once the channel has been created, take a look at the <tt>.CHANNEL</tt> file to see what they are.

[support]

and the other settings are random?

Random?! Sigh...

Awasu will use sensible defaults for values that are not present. Once the channel has been created, take a look at the <tt>.CHANNEL</tt> file to see what they are.

[zakky]

seriously now. i like your product. i also appreciate your fast responses. however if you make it a habbit of replying with one sentence per question you musn't wonder that people get angry at your responces. and dry australian humor is maybe also easily misunderstood, especially if only read.

so... instead of answering:

As I described above.

I would have expected an answer like:

As I described above. Awasu will automatically populate the other parameter with its default parameters. you only have to provide the query line. the GUIs will also be assigned automatically.

such a reply would have saved my next question which was obvious to come.

anway, i had a bad day.

i like your product!

[zakky]

seriously now. i like your product. i also appreciate your fast responses. however if you make it a habbit of replying with one sentence per question you musn't wonder that people get angry at your responces. and dry australian humor is maybe also easily misunderstood, especially if only read.

so... instead of answering:

As I described above.

I would have expected an answer like:

As I described above. Awasu will automatically populate the other parameter with its default parameters. you only have to provide the query line. the GUIs will also be assigned automatically.

such a reply would have saved my next question which was obvious to come.

anway, i had a bad day.

i like your product!

[kevotheclone]

@support
"sensible defaults" are a beautiful thing! I try use "sensible defaults" in my programming at work too. Config file not found? Create a new one with "sensible defaults". Why display a "show stopper" error message, when you can continue to operate using "sensible defaults". Taka, is there anything you haven't though of to make our jobs easier?

@zakky
If you work with Awasu enough and you'll "love" it. And the "fast responses" are priceless, worth every penny you've paid. Absolutely amazing support.

Now if we could only get some MP3s of Taka playing jazz...

[kevotheclone]

@support
"sensible defaults" are a beautiful thing! I try use "sensible defaults" in my programming at work too. Config file not found? Create a new one with "sensible defaults". Why display a "show stopper" error message, when you can continue to operate using "sensible defaults". Taka, is there anything you haven't though of to make our jobs easier?

@zakky
If you work with Awasu enough and you'll "love" it. And the "fast responses" are priceless, worth every penny you've paid. Absolutely amazing support.

Now if we could only get some MP3s of Taka playing jazz...