1 (edited by Stefan 2012-01-15 21:59:05)

Topic: Siren 3.00 alpha - General discussion thread

Siren 3.00 alpha 1 ( read more at >> http://scarabee-software.net/forum/view … hp?id=273)


Quick downloaded and first test:

- starts good on Win XP SP3, did just an lookaround, no renaming till now
- looks like the old one (Siren 2), fine.


- "Environment variables supported" is helpful. The expanded examples in the 'Completion Window' are nifty.
(maybe this can be done too for other variables like the one on the 'Base' and 'Date' tab?)

- i noticed the 'Completion Window' button, helpful.

- Hey, there is an wizard!  Just playing around with it.

- "A favourite expression can be "included" in an expression:" ,  Fine, i can see an use for this.

- to be continue...


EDIT:  if you need more tester i can post the beta release on an freeware forum?

Re: Siren 3.00 alpha - General discussion thread

Sorry, I missed your "Edit".
(thanks to Pierre for pointing out your post)

Speaking about testers giving feedbacks, there are few of them for the Windows version and none for the GNU/Linux one.
I didn't get any report about the metadata extraction and I'm sure there are bugs/problems there.
If you've got time to recruit interested people, it could help.

Thanks for your support

3 (edited by Stefan 2012-01-15 20:36:33)

Re: Siren 3.00 alpha - General discussion thread

Siren 3.00 alpha 2 build 805
+ Variables can be used as a expression parameters
   For example :
               %b("title",%At).%e
               %b("title",%Rs{10}(1,%Rn{1})).%e
               %T{%fc}

Thank you, just on testing  on Windows XP SP3 (without renaming, expression field only right now).

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

Example 1:

%T{%f}(%Rn{1}).*


Since "%Rn{n}" can result to zero too, the computed file name is often "nothing"

I am not saying getting an '0' is bad at all. Maybe sometime that's exactly what we need.
I just mention it here for reverence.

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

Hmm, i am sure "%T{%fc}" worked on more then one file an minute ago,
but now only the first selected file get computed and shows the first line from that file.
If i deselect that first file, the second selected file get now computed.

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

Example 2:

%b("Spongebob",%Rs{10}(1,%Rn{2})).%e

works fine.

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

Max value for
%Rs{n}
and
%Rn{n}
seems to be '50'

Values greater then 50 fall back to default '8'

I have not really counted the amount of signs, but you see it if you use %Rn{50} and %Rn{51}.

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

Example 3

%Rs{25}(1,%Rn{2}).%lRa{3}

gives nice random file name from random length.

aNGETd1zDtR8GCLdYgZ2STy3u.lhw
al.lak
bYBHOIsXIBoy5RwQbSj.wpw


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

Question: The "%Rs{n,m}" syntax was to much to implement?

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

Re: Siren 3.00 alpha - General discussion thread

Hello,

%T{%f}().*
Since "%Rn{n}" can result to zero too, the computed file name is often "nothing"
I am not saying getting an '0' is bad at all. Maybe sometime that's exactly what we need.

There may be different solutions to this.
Replace 0 with 1 :
%T{%f}(%Rn{1}(s/^0$/1/)).*
Increment the random number by 1 :
%Rn{1}-%f;%T{%f[2]}(%N{1,1}).*

Quite complicated but maybe at the "height" of the problem  wink

Hmm, i am sure "%T{%fc}" worked on more then one file an minute ago,
but now only the first selected file get computed and shows the first line from that file.
If i deselect that first file, the second selected file get now computed.

%T{%fc} with return the nth line of the current evaluate file. n being the selection number of the file.
If you want the first line of the file you should use : %T1{%fc}

Values greater then 50 fall back to default '8'
I have not really counted the amount of signs, but you see it if you use %Rn{50} and %Rn{51}.

You're right. I've decided to max out the length to 50 and the default length of random strings is defined in the Preferences. By default it is 8.
I can easily change these in the next build if needed.

Question: The "%Rs{n,m}" syntax was to much to implement?

I imagine you meant "%Rn{n,m}". This feature would only be meaningful for numbers.
I thought the last syntax evolution was enough.
I'll have a look on this for the next build.
Maybe the syntax might be : %R{size,mix,max}"

Thanks for your feedback.

PS : It seems there may be a typo in the title of the thread (threat/thread)

Re: Siren 3.00 alpha - General discussion thread

S> Since "%Rn{n}" can result to zero too, the computed file name is often "nothing"

R> Replace 0 with 1 :
R> %b(1,%Rn{1}(s/^0$/1/)).*

Hey, that really works ;-)
Good solution. I have found my way too, see last paragraph.

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

R> you should use : %T1{%fc}

Upps, you are right of course.

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

R> I've decided to max out the length to 50
R> I can easily change these in the next build if needed.

Good to know. I think greater values are not really needed.
We can also use that variable more then once. %Rs{50}%Rs{50}%Rs{50}%Rs{50}
But since i use explicitly the {n} modifier i should get what i want and the limit should be 255.
But I can live with the current behaviour.

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

R> I imagine you meant "%Rn{n,m}". This feature would only be meaningful for numbers.

Oh yes, since it is used now with the substr() feature only, only digits are meaningful.
(I had thought above about my first silly idea to have that min/max for all  that  %Rx   separately)
It is ok. I only want to know.

I found an way to get this min/max length i was after:
To be sure to have 4 signs at least i use
%Rs(1,4)%Rs{9}(1,%Rn{1}).%lRa{3}

I can live with this current behaviour too.

At least for the moment. Lets see what further test will discover smile

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

R> typo

Always the same roll

Re: Siren 3.00 alpha - General discussion thread

Hello,

I'll try to implement the %Rn{size,min,max} modifier.

Regards,

Remi

Re: Siren 3.00 alpha - General discussion thread

%Rn{size,min,max} has been added in the last build (811).

Thanks for your support.

Remi