El Mi=E9rcoles 18 Abril 2007 12:00, escribi=F3:
> > Why? :-)
> > I do considere it as a part of porting qucs to qt4, it's part of adding
> > the new features that qt4 offers. Else, it will run in Qt4 but the Qt3
> > way :-)
> > My reasons:
> > * If we continue with the separate icons:
> > ** each time the application is loaded the hard drive has to seek for
> > the specific file and load it into memory. Repeat that for _every_ icon.
> - Do you know readahead (even dark side OS do readahead) ?=20
Yes, I forgot this part.
> Moreover we=20
> could put all the svg files and model description in one single file
> (xml in xml)
As I said in the IRC, while botter to do that when you already have it=20
implemented in a similar-working fashion?
I guess pasting the log will be helpful to others to understand :-)
<BastienN7> - for hard drive seeking we could put all the files in one big=
file thanks to xml
<BastienN7> Moreover OS we do readahead
<lisandrop> ok, and why will you take the time to do that if it's allready=
implemented in a convenient way?
<BastienN7> And For qucs-core teams it will be easier to decouple qucs-gui =
<lisandrop> because, resources will end doing the same thing
<BastienN7> For quick and dirty testing of new components
<lisandrop> there's nothing in resources that will get in between qucs-core=
<BastienN7> With file we need to only add a new file
<BastienN7> But with ressource we need to do a new compile cycle
<lisandrop> easy, add a 1-port, 2-port,... images for non-known components
<lisandrop> after all, you are testing it
<lisandrop> and, by the way, how do you associate the components with the=20
<lisandrop> moreover, you do not have to put the components in the resources
Yes, it was in the line above that I realized that most of you are thinking=
adding the component's files to the resources. Bastien explained to me:
[12:09:43] <lisandrop> just the icons
[12:09:58] <BastienN7> Yes but the goal is to create a component xml file
OK, I do realize that, for components, it would be much easier to use xml, =
not for the rest of the icons (think about the toolbars, for example).
> > ** we have to care during the installation process (ok, when coding
> > the installer, be it autotools based or nsi based) that the correct pat=
> > for _each_ OS is right, take care of file permissions, etc.
> - Not really a problem. Moreover with the file approach each user
> could use its own icons and model (we could begin to search in $HOME).
> Something that is not possible with ressource
Agree with the components side of the discussion.
> > * If we use resources:
> > ** the application loads only one file, the binary, with the icons
> > emmbeded. Only one hard drive access has to be done. The files
> > would be stored in a sequential array optimized by Qt's resources
> > compiler. More than that, it is _possible_ that memory consumption will
> > decrease due to such compilation (no separate files in memory).
> - It a gui we do not care about memory usage
Put it in another perspective: the qucs-gui-qt4 team is porting and trying =
use the new Qt4's features that fits in the design. We do care about the gu=
So, less memory consumption and/or more speed are important variables to us.
"So long, and thanks for all de fish!"
The Hitchhickers guide to the Galaxy
Lisandro Dami=E1n Nicanor P=E9rez Meyer