Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kry]

Why is it again that we would be willing to drop support for a LOT of platforms, especially BSD, and reqork everything with a new framework, which so far I haven't seen an advantage about it, and has a lot of new problems for us?

Why spread FUD? Qt does support BSD. http://trolltech.com/developer/notes/changes/changes-3.3.4/ Which means, that ALL major platforms are supported (Linux, Win, OSX, BSD).

Qt as gui toolkit is times better that WX. You actually have a chance to rework GUI in minimal effort. And GUI should be reworked in many places. Don't you see an advantage? I do.

and has a lot of new problems for us

At least you don't have to instruct users to rebuild/reinstall WX because of random crashes.

As for the "FUD" I'm just quoting QT's website, which says Windows, Mac, Linux and embedded systems. No more, no less.

As for the "crashes", I don't see how it can be wx at fault that the packagers don't update or patch their versions.

[lfroen]

As for the "FUD" I'm just quoting QT's website, which says Windows, Mac, Linux and embedded systems. No more, no less.

Pleeeeeese.  Let me quote: from http://trolltech.com/products/qt/features:

Qt is available for the following platforms:
    * Qt/Windows (Microsoft Windows Vista™, Server 2003, XP, 2000, NT 4, Me/98)
    * Qt/Mac (Mac® OS X, 10.3 and 10.4)
    * Qt/X11 (Linux®, Solaris®, HP-UX, IRIX, AIX, many other Unix variants)
    * Qtopia Core - Learn more about the embedded Linux port of Qt.

As for the "crashes", I don't see how it can be wx at fault that the packagers don't update or patch their versions.

Why do you put "crashes" in quotation marks is beyond my comprehension. Wx really crashes. On left and right. In released versions. And this is versions that packages use. You can't expect them to compile CVS snapshots.

[Kry]

So QT never crashes?

[lfroen]

So QT never crashes?

Apparently every software crashes. However, according to my limited personal experience, Qt have order of magnitude less problems, compared to WX.

[Kry]

I see. Don't have much experience with it, but then again, didn't have that many crashes with wx either, save the url update one.


I do however doubt we could just switch a framework like that without TONS of work and free time, so I doubt it would be feasible at all.

[mulinex]

to estimate time and how much work it could be, i suggest a roadmap plan.
a basic version would be the best start.
So which maintabs has amule? and which are needed for QT? and which functions should be ported to QT ?
There are different approaches to work, from abstract to fine or from fine to the next part as well done fine.
I prefer the quick and dirty implementation, so from main Frames to the details,
We need only these frames:

Network (1) / Search (2)  / Transfer (3) / Filelist-Library (4) / Settings (5).

This means to drop in the first QT version of amule: Partial-Import, Messages, Statistics.

A swell in the 5 mentioned tabs we can drop several adjustments.
The gui design of preferencers was posted:
http://sourceforge.net/tracker/index.php?func=detail&aid=1814590&group_id=178712&atid=886242
( the suggestion was to make it left menue-tabbed, so copy paste the layout)

Network Imho does not need server settings, just one button to connect to one random server or not,
All other gui desings can be taken from here:
http://retroshare.svn.sourceforge.net/viewvc/retroshare/rs-Qt-gui/src/

the c++code has to be added and linked, of course,  the wxwidgets from core have to be removed.
All other adjustments, which are not in the new QT gui, then can be left as is ?! as they have all a default setting.

If a core wxwidget is lef in the code, a compilation with qt gui should not be harmed?


@wuische: which tab is yours ?


I suggest each one is taking a tab from 1-5.
Any volunteering?

[Kry]

I'm sorry but I would suggest you don't talk what you don't know about. You're jsut embarassing yourself in front of the people that actually know what this work entails.

[Kry]

Also, you might notice you're not an aMule developer if you look at the list.

[lfroen]

I do however doubt we could just switch a framework like that without TONS of work and free time, so I doubt it would be feasible at all.

Definitely true. That's why I'm not talking in terms of "let's do it now".

[wuischke]

@wuische: which tab is yours ?

Yesterday: The bar tab.

Fortunately we had cheap (but good) czech beer.
Unfortunately I've already forgotten all the Czech I've learned yesterday.

Regarding your actual question: DON'T EVEN THINK ABOUT ASKING AGAIN BEFORE THE RELEASE OF AMULE 2.2.0. (Sorry for shouting, but it seems like you didn't understand me the numerous times I tried to answer politely.)

[lfroen]

to estimate time and how much work it could be, i suggest a roadmap plan.

Should I quit my day job to keep up with suggested roadmap?

[Kry]

I think we all should, for the good of the Empire!

[mulinex]

(1) first, the discussion has rised to left the "no" for a QT-gui
(2) it is not about speed, not about beer, yes, not about coding, and not about "duck and cover".
http://www.youtube.com/watch?v=C0K_LZDXp0I
(3) because we do not want to quit day jobs, we (for kry: you) should coordinate the steps, that should be normal.
as wuischke needs one day+ after the bar, we wait until he has a focus of half and not double of the fun.
(4) leon, there is no roadmap plan, but if there is sparetime, can you make one with the steps?

[Kry]

Someone's not getting the hints.

[mulinex]

you mean leon not to do it? but what, if wuischke makes a frame  as well (after 2.2.0. of course)?