From: Stefan J. <st...@gr...> - 2007-04-18 10:31:26
|
Am Mi, 18.04.2007, 10:10, schrieb roucaries bastien: Hello! >> > For this week I implemented a filter, which filters components >> > based on name typed in line edit in sidebar. This really helps to >> > locate components at faster rate instead of navigating through all >> > types of sources. >> > Please do give me feedback about this feature! >> >> I will look at it. Thanks. >> >> > One good news. Ruso (or Martin) , friend of Lisandrop helped me >> > by implementing slots corresponding to zoom and also some few other >> > slots. >> >> Good to hear that. :-) >> >> > Oh yeah, theres one more big change. Hence forth we thought of using >> > Qt's resource system to store icons in binary format in platform >> > independent way. Ruso did that and I commited that too. You can have a >> > look at this link for more info >> > http://doc.trolltech.com/4.2/resources.html >> > >> > Please do give feedback. >> >> Actually I don't like the idea. I don't see an advantage for now. It's >> not related to "porting Qucs" and also not a conceptional change. With >> the bitmaps as seperate files it is easier to change them even with the >> application compiled and installed... Anyway, please don't feel >> bothered. >> If you really require the change you can leave it as is. > > Here I agree with Stephan. It will be better to keep the icons as files. Thanks. > It will be also better to describe each component in the gui by an xml > file, that will include the number of port, the name of the component, > the path to an icon file (preferably in vector graphics format) and a > regexp (or a printf like string) for creating the simulation file. > If we could do this, qucs core and qucs will be fully decoupled, ie we > do not need to recompile qucs-gui if we add a new components to > qucs-core. But I suppose it is a mid term goal. This I also had it mind already. It would be something like the description of library elements. There is already a Symbol, Ports and Netlist description contained... Also it would be a step towards loadable add-on modules for components which is (I agree) a mid term goal. But also not related to actually porting Qucs to Qt4. Cheers, Stefan. |