From: Bastien R. <rou...@gm...> - 2007-11-04 16:11:38
|
Le dimanche 4 novembre 2007, Oswald Buddenhagen a =E9crit=A0: > On Sun, Nov 04, 2007 at 08:02:20PM +0530, Gopala Krishna wrote: > > <schematic type=3D"external" filename=3D"resistor.svg"/> > > <ports> > > <port name=3D"1" position=3D"0,0"> > > <port name=3D"1" position=3D"4.5,0"> > > <ports/> > > this looks wrong. the ports should be defined inside the svg. Why ? Give me some argument... Actually port are separed in tjhe C++ code from drawing. Moreover we do=20 notwant to parse svg file each time we need to get port position for wiring. I agree that port need to be defined in the svg file. But is a only graphic= al. BTW if you user commit a mistake copying port cordinate between svg file an= d=20 xml file it is his problem. A little bit like you do rm -rf / as root :-) > > There are some components which implement the netlist method, verilog > > method and vhdl method. If we xmlize the components, how can we > > represent these in the xml ? > > Or should these components need to reimplemented as c++ code itself ? > > i see no alternative to implenting the device models in c++. > you can try to make the models pluggable, so the xml would name a > library that implements the model. you could also have a second library > that implements the gui to parametrize a part of the given type. > btw, consider making xml files and plugins possible that implement > multiple components, and group the standard components logically - if > you need to load two or more files for each component, startup time sill > suffer significantly. It is not about performance. Early optimization is evil (Donald knuth). It = is=20 about correctness. We do not say device model are not implemented is C++ . = We=20 are saying that implementing gui component in C++ is not scalable and quite= =20 boring for core team.** Unix philosophy is one program, one goal. The goal of the gui is to offer a= =20 gui nothing more, we do not want to add C++ file each time we add a compone= nt=20 in core. To be simple we will implement one file one component in a first time. Beca= use=20 we prefer (Gopala and me) a slow thing but correct and scalable. The medium term goal is to implement a auxilarry program that will group al= l=20 the component database in a single file. But we prefer to concentrate in a= =20 simple but working thing ** BTW I think a lot of component will be implemented using equation block= =20 instead of C++. And moreover I use regulary Sparam (s2p) pure text file=20 model. Therefore it is not true that you implement model in C++ =2D-=20 "ROUCARIES Bastien" roucaries.bastien+qucs@gmail.= com =2D------------------------------------------------------------------------= =2D----- DO NOT WRITE TO rou...@gm... OR BE BLACKLISTED |