<br><br><div class="gmail_quote">On Wed, Jan 5, 2011 at 7:29 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 01/05/2011 07:35 AM, Mariano Martinez Peck wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I would not include 'Seaside-Tools' at all in the Core group and I would<br>
not put is as default.<br>
I would create another group, that incldues the Core + Seaside-Tools +<br>
rest of the sutff and would put that group as default. This fixes the<br>
two problems:<br>
<br>
- newbies do not need to know which group to load and just the default<br>
will load the Seaside-Tools and all the necessary packages (probably all<br>
of them)<br>
- Advanced guys that need core, probably know how to use metacello, and<br>
they can just load Core for their images (even maybe only for production<br>
images)<br>
<br>
Cheers<br>
<br>
mariano<br>
</blockquote>
<br></div>
Mariano, <a href="http://et.al" target="_blank">et.al</a>.,<br>
<br>
Seaside30 has so many packages and so many possible _valid_ combinations of packages that it didn't make a lot of sense to try to define groups for all of the possible combos...<br></blockquote><div><br>yes, that's true!!!<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
It was decided over a long series of emails to create a 'Base' group that was the absolute minimum usable chunk of Seaside.<br>
<br>
The 'Core' group was then defined as everything else that came with Seaside excluding the tests. Note that the core group includes all of the development tools as well...<br></blockquote><div><br>Hi Dale. This is what is misleading for me. I mean, from my point of view, development tools are not core. Just watching it form outside, I may call 'core' to what you call now 'base' and try to find a better name for what it is now in 'Core'. <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
The 'OneClick' group was added later to match the content of the 'OneClick' image (which basically excluded the LGPL packages) and included many tests.<br>
<br>
Now that there are folks who have some real needs it probably makes sense to take another look at creating some finer grained groups.<br>
<br>
So, if you run the following expression in a Pharo image, with the latest ConfigurationOfSeaside30:<br>
<br>
| version |<br>
version := ConfigurationOfSeaside30 project<br>
version: '3.0.3-commonBaseline'.<br>
((version packages collect: [:each | each name ]) asSet<br>
difference: ((version groups detect: [:each |<br>
each name = 'Base']) includes) asSet)<br>
reject: [:each | each includesSubString: '-Tests-' ]<br>
<br>
You'll get the list of basic packages that are not included in the 'Base' group and are not test packages:<br>
<br>
'RSS-Core' 'Seaside-InternetExplorer' 'Seaside-Welcome'<br>
'Seaside-Email' 'Scriptaculous-Core' 'Seaside-Swazoo'<br>
'Javascript-Core' 'Seaside-Adaptors-Swazoo' 'JQuery-UI'<br>
'Seaside-Development' 'JQuery-Core' 'Seaside-HTML5'<br>
'Seaside-Examples' 'Scriptaculous-Components'<br>
'Seaside-Tools-Web' 'Seaside-Tools-OmniBrowser'<br>
'Prototype-Core' 'RSS-Examples'<br>
<br>
If reasonable groups can be defined for these packages then we can start taking a look at the dependencies involved and go from there.<br>
<br>
If you want to look at the dependencies of the various packages (without parsing configurations), you can try printing the results of expressions like the following:<br>
<br>
(ConfigurationOfSeaside30 project version: '3.0.3')<br>
record: #('Seaside-Tools-OmniBrowser')<br>
<br>
You'll get a list of the packages that would have been loaded if you did a load and the list is in load order...<br><font color="#888888">
<br>
Dale<br>
</font></blockquote></div><br>