From: 李祐棠 <lc...@gm...> - 2015-01-11 17:14:06
|
Hello Qucs-devel: I just search "qucs" on Github, and I found this repository. https://github.com/damiansimanuk/qucs-qt4 It already port most qucs function into Qt4 two years ago. He seems to be a skilled programmer. It's curious that the contribution didn't merge into main repository. Maybe we can ask him to join the qucs team and merge his contributions? Or at least, ask about the permission to use his code in main repository. Best Regard Yodalee 20150112 |
From: Guilherme B. T. <gui...@gm...> - 2015-01-11 21:19:15
|
Hello Yodalee, There is more to it. On our old_svn in SF there is a version related to that code you found, see: https://sourceforge.net/p/qucs/code/HEAD/tree/branches/ This is probably the same code you found: https://gitorious.org/qucs-qt4 And there is also this one: http://git.tuxfamily.org/qucsqt4dev/qucsqt4.git I don't know about their willingness to contribute, but the work is derivative of Qucs and the license is still GPL. Gopala Krishna was active in the Qt4 port. Perhaps Bastien was also involved (?). Tracing the qucs-devel archives, Gopala went to work with another project and the port stalled. He used to maintain a blog about the port: http://krishnaggk.blogspot.be/2007/07/qucs-and-what-i-am-doing-in-it.html If I recall correctly they did not quite *ported* to QGraphicsView. They instead bypassed the Qt3Support step and went straight to a new UI using to QtSVG and QtXML and other technologies. It seems that they even used a different file format for schematic and and component symbols. The code diverged significantly. At the moment the fork looks incompatible with Qucs. So, it probably did not merge back because it was unfinished and/or incompatible. I wrote down some notes had about these attempts to port. I will try to dig out them out. Speaking about Qt4. The support for Qt4 series was extended one more year: http://blog.qt.digia.com/blog/2014/11/27/qt-4-8-x-support-to-be-extended-for-another-year/ It would be nice if we could finish the port to Qt4 in this year, release a stable version and then move on to Qt5. Regards, Guilherme On 1/11/15 6:13 PM, 李祐棠 wrote: > Hello Qucs-devel: > > I just search "qucs" on Github, and I found this repository. > https://github.com/damiansimanuk/qucs-qt4 > It already port most qucs function into Qt4 two years ago. He seems to be a > skilled programmer. > > It's curious that the contribution didn't merge into main repository. Maybe > we can ask him to join the qucs team and merge his contributions? Or at > least, ask about the permission to use his code in main repository. > > Best Regard > Yodalee > |
From: Gopala K. <kri...@gm...> - 2015-01-12 18:32:34
|
Happy new year Qucs folks! You folks are right - a bunch of us (Pablo, Bastien, myself) made progress with Qt4 port back then at different intervals. We were ambitious and pursued big ideas like defining components via SVG and XML. GraphicsView was used for diagramming but the components themselves were loaded dynamically via SVG & XML files. We were successful to good extent. A framework evolved and we felt it was nicely decoupled but not inline with Qucs - so the GUI was split into its own project called caneda - http://qt-apps.org/content/show.php/Caneda?content=134437 . Pablo added features like project management, PCB layout support etc. As I reached closer towards final year of my college, I got occupied with other projects. I got into a software development job right after college in a new place and never found a window to comeback to qucs. IMHO, I feel achieving Qt3Support free code first and making the code compatible with Qt5 with stability would be better goal. Big hairy ideas like generalizing GUI using SVG etc require great amount of effort - the main challenge would be in achieving stability. The port can definitely not be merged directly, but may be some ideas/code can be adopted. Loving the discussions that go over qucs-devel@ - hope to see a completed Qt4 port this year :) On Mon, Jan 12, 2015 at 2:49 AM, Guilherme Brondani Torri < gui...@gm...> wrote: > Hello Yodalee, > > There is more to it. > > On our old_svn in SF there is a version related to that code you found, > see: > https://sourceforge.net/p/qucs/code/HEAD/tree/branches/ > > This is probably the same code you found: > https://gitorious.org/qucs-qt4 > > And there is also this one: > http://git.tuxfamily.org/qucsqt4dev/qucsqt4.git > > I don't know about their willingness to contribute, but the work is > derivative of Qucs and the license is still GPL. > > Gopala Krishna was active in the Qt4 port. Perhaps Bastien was also > involved (?). > Tracing the qucs-devel archives, Gopala went to work with another > project and the port stalled. > He used to maintain a blog about the port: > http://krishnaggk.blogspot.be/2007/07/qucs-and-what-i-am-doing-in-it.html > > If I recall correctly they did not quite *ported* to QGraphicsView. They > instead bypassed the Qt3Support step and went straight to a new UI using > to QtSVG and QtXML and other technologies. It seems that they even used > a different file format for schematic and and component symbols. The > code diverged significantly. At the moment the fork looks incompatible > with Qucs. > > So, it probably did not merge back because it was unfinished and/or > incompatible. > > I wrote down some notes had about these attempts to port. I will try to > dig out them out. > > Speaking about Qt4. The support for Qt4 series was extended one more year: > > http://blog.qt.digia.com/blog/2014/11/27/qt-4-8-x-support-to-be-extended-for-another-year/ > > It would be nice if we could finish the port to Qt4 in this year, > release a stable version and then move on to Qt5. > > Regards, > Guilherme > > On 1/11/15 6:13 PM, 李祐棠 wrote: > > Hello Qucs-devel: > > > > I just search "qucs" on Github, and I found this repository. > > https://github.com/damiansimanuk/qucs-qt4 > > It already port most qucs function into Qt4 two years ago. He seems to > be a > > skilled programmer. > > > > It's curious that the contribution didn't merge into main repository. > Maybe > > we can ask him to join the qucs team and merge his contributions? Or at > > least, ask about the permission to use his code in main repository. > > > > Best Regard > > Yodalee > > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Qucs-devel mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-devel > -- Cheers, Gopala Krishna A |
From: Guilherme B. T. <gui...@gm...> - 2015-01-12 21:24:58
|
Hello Gopala, Thank you for the update and the work you did for Qucs. I appreciate your advice about "Qt3Support free" and "compatible with Qt5" (Qt4 first). I hope it will help shape the ongoing effort towards the GraphicsView implementation. I totally agree that the *port* comes first and major *refactoring* is second. Small refactoring is inevitable, but the focus should be stability and the task at hand which is to move away from Qt3Support. I did not know about Caneda. It also looks inactive thou. Best wishes, Guilherme On 1/12/15 7:32 PM, Gopala Krishna wrote: > Happy new year Qucs folks! > > You folks are right - a bunch of us (Pablo, Bastien, myself) made > progress with Qt4 port back then at different intervals. We were > ambitious and pursued big ideas like defining components via SVG and > XML. GraphicsView was used for diagramming but the components > themselves were loaded dynamically via SVG & XML files. We were > successful to good extent. A framework evolved and we felt it was > nicely decoupled but not inline with Qucs - so the GUI was split into > its own project called caneda - > http://qt-apps.org/content/show.php/Caneda?content=134437 . Pablo > added features like project management, PCB layout support etc. > > As I reached closer towards final year of my college, I got occupied > with other projects. I got into a software development job right after > college in a new place and never found a window to comeback to qucs. > > IMHO, I feel achieving Qt3Support free code first and making the code > compatible with Qt5 with stability would be better goal. Big hairy > ideas like generalizing GUI using SVG etc require great amount of > effort - the main challenge would be in achieving stability. The port > can definitely not be merged directly, but may be some ideas/code can > be adopted. > > Loving the discussions that go over qucs-devel@ - hope to see a > completed Qt4 port this year :) > > > On Mon, Jan 12, 2015 at 2:49 AM, Guilherme Brondani Torri > <gui...@gm... <mailto:gui...@gm...>> wrote: > > Hello Yodalee, > > There is more to it. > > On our old_svn in SF there is a version related to that code you > found, see: > https://sourceforge.net/p/qucs/code/HEAD/tree/branches/ > > This is probably the same code you found: > https://gitorious.org/qucs-qt4 > > And there is also this one: > http://git.tuxfamily.org/qucsqt4dev/qucsqt4.git > > I don't know about their willingness to contribute, but the work is > derivative of Qucs and the license is still GPL. > > Gopala Krishna was active in the Qt4 port. Perhaps Bastien was also > involved (?). > Tracing the qucs-devel archives, Gopala went to work with another > project and the port stalled. > He used to maintain a blog about the port: > http://krishnaggk.blogspot.be/2007/07/qucs-and-what-i-am-doing-in-it.html > > If I recall correctly they did not quite *ported* to > QGraphicsView. They > instead bypassed the Qt3Support step and went straight to a new UI > using > to QtSVG and QtXML and other technologies. It seems that they even > used > a different file format for schematic and and component symbols. The > code diverged significantly. At the moment the fork looks incompatible > with Qucs. > > So, it probably did not merge back because it was unfinished and/or > incompatible. > > I wrote down some notes had about these attempts to port. I will > try to > dig out them out. > > Speaking about Qt4. The support for Qt4 series was extended one > more year: > http://blog.qt.digia.com/blog/2014/11/27/qt-4-8-x-support-to-be-extended-for-another-year/ > > It would be nice if we could finish the port to Qt4 in this year, > release a stable version and then move on to Qt5. > > Regards, > Guilherme > > On 1/11/15 6:13 PM, 李祐棠 wrote: > > Hello Qucs-devel: > > > > I just search "qucs" on Github, and I found this repository. > > https://github.com/damiansimanuk/qucs-qt4 > > It already port most qucs function into Qt4 two years ago. He > seems to be a > > skilled programmer. > > > > It's curious that the contribution didn't merge into main > repository. Maybe > > we can ask him to join the qucs team and merge his > contributions? Or at > > least, ask about the permission to use his code in main repository. > > > > Best Regard > > Yodalee > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot > Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and > more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Qucs-devel mailing list > Quc...@li... > <mailto:Quc...@li...> > https://lists.sourceforge.net/lists/listinfo/qucs-devel > > > > > -- > Cheers, > Gopala Krishna A |