profiles and config files
7 views
Skip to first unread message
Adam Goucher
Apr 24, 2013, 1:13:27 PM4/24/13
to sau...@googlegroups.com
The next release of Py.Saunter and SauntePHP are now a week over
schedule and likely won't be until next week. The big thing in the
release is going to be custom Firefox profile support. It ends up the FF
profiles are not actually as portable as they would like you to
believe... especially if you don't control the environment, like say
when it exists in something like Sauce's cloud.
After that the release will be primarily be about changing how the
configuration information is captured. Right now Py.Saunter uses an INI
based format and SaunterPHP uses just raw PHP. Both will be moving to a
YAML based config structure and the configs will actually be
interchangeable (though I don't really know why you would want to). Not
only will there be consistency between implementations but it will allow
for multiple concurrent browsers in a script (not parallel execution,
but for when a particular script needs more than one browser open). That
functionality is planned for the release after next.
The exact format is still in flux, but
https://github.com/Element-34/py.saunter/wiki/ConfigFormat is a first
stab at what it will look like.
Now the survey question is... do you want;
1) nice instructions like the wiki page on how to convert the various
configs to the new yaml one, or
2) a --convert flag to the saunter script which will read the existing
formats to yaml
Of course I am biased towards the first option, but am open to the
second. But, that also means the release will be much longer since it is
more to write and debug.
-adam
schedule and likely won't be until next week. The big thing in the
release is going to be custom Firefox profile support. It ends up the FF
profiles are not actually as portable as they would like you to
believe... especially if you don't control the environment, like say
when it exists in something like Sauce's cloud.
After that the release will be primarily be about changing how the
configuration information is captured. Right now Py.Saunter uses an INI
based format and SaunterPHP uses just raw PHP. Both will be moving to a
YAML based config structure and the configs will actually be
interchangeable (though I don't really know why you would want to). Not
only will there be consistency between implementations but it will allow
for multiple concurrent browsers in a script (not parallel execution,
but for when a particular script needs more than one browser open). That
functionality is planned for the release after next.
The exact format is still in flux, but
https://github.com/Element-34/py.saunter/wiki/ConfigFormat is a first
stab at what it will look like.
Now the survey question is... do you want;
1) nice instructions like the wiki page on how to convert the various
configs to the new yaml one, or
2) a --convert flag to the saunter script which will read the existing
formats to yaml
Of course I am biased towards the first option, but am open to the
second. But, that also means the release will be much longer since it is
more to write and debug.
-adam
Carol Mirakove
Apr 24, 2013, 1:18:08 PM4/24/13
to sau...@googlegroups.com
My survey response:
1) nice instructions like the wiki page on how to convert the various configs to the new yaml one
Thanks, Adam! Exciting stuff.
Carol
-adam
--
You received this message because you are subscribed to the Google Groups "Saunter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to saunter+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Dakota Smith
Apr 24, 2013, 1:21:47 PM4/24/13
to sau...@googlegroups.com
I also would prefer just a wiki description of how to convert the configs.
To unsubscribe from this group and stop receiving emails from it, send an email to saunter+u...@googlegroups.com.
Dave Tung
Apr 24, 2013, 1:53:10 PM4/24/13
to sau...@googlegroups.com
Option 1
Reply all
Reply to author
Forward
0 new messages