<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
<title></title>
</head>
<body>
<p style="margin: 0px;"><span> </span></p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
Alexander Klenin <klenin@gmail.com> hat am 16. März 2011 um 12:14 geschrieben:<br/>
<br/>
> 2011/3/16 Mattias Gaertner <nc-gaertnma@netcologne.de>:<br/>
> >> > Write a package TAChartAggPas, that depends on AggPasLcl and<br/>
> >> > tachartlazaruspkg and has a unit implementing the aggpas backend for<br/>
> >> > TAChart.<br/>
> >> I considered that. But it will be one package per dependency -- so +3<br/>
> >> packages right now.<br/>
> >> Is it ok from user interface point of view?<br/>
> ><br/>
> > I think yes. The project requires only one dependency instead of two<br/>
> > (TAChart+AggPas). So this might actually be an advantage.<br/>
> ><br/>
><br/>
> I was rather wondering about how easy it would be for the user<br/>
> to discover the need for that one dependency.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Like any other option. Just add hints/comments to the right places.</p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
><br/>
> >> Is there a notion of "package group" in the IDE?<br/>
> >> If not, maybe it is a good idea to create one?<br/>
> > What should that be?<br/>
> ><br/>
> > Packages are shown alphabetically, so if you use the same prefix they are<br/>
> > listed close together.<br/>
><br/>
> I was thinking about the following:<br/>
><br/>
> 1) Let "sub-package" be a special kind of package with the additional<br/>
> "Parent" field<br/>
> 2) In the IDE package list, display only a parent packages (maybe<br/>
> display sub-packages<br/>
> in a treeview-like manner)<br/>
> 3) Automatically install sub-packages if all their dependencies are installed<br/>
> (that, naturally, includes parent packages).
</div>
<p style="margin: 0px;"> </p>
The 'install' is only for the IDE and independent of the project. Think about the IDE as another project.<br/>
That means 'soft' dependencies can be satisfied by the IDE and/or the project.<br/>
Which means the package might have different search paths for the IDE and for the project, which might increase confusion. <br/>
And you need more IDE knowledge to understand the package.<br/>
<br/>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
><br/>
> The end result would be, if the user installs TAChart and OpenGL, he will<br/>
> automatically have opengl back-end, without the need to worry about<br/>
> TAChartOpenGL package.<br/>
><br/>
> But may be it is overkill. To this moment, I am aware of a single user<br/>
> interested in AggPas back-end.
</div><br/>
Yes. To summarize:<br/>
- There exists another solution, which is not that bad.<br/>
- The proposed solution has some drawbacks.<br/>
- So far only one request, which makes maintaining/testing difficult.<br/>
<br/>
My conclusion: a good day work better spent elsewhere.<br/>
<br/>
<br/>
Mattias<br/>
<br/>
</body>
</html>