Closed
Bug 89330
Opened 25 years ago
Closed 25 years ago
Remove Motif port from tree
Categories
(SeaMonkey :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla0.9.6
People
(Reporter: zuperdee, Assigned: netscape)
Details
Attachments
(1 file)
|
13.59 KB,
patch
|
bryner
:
review+
|
Details | Diff | Splinter Review |
I admit, this may seem a little funny, considering I once wanted to ressurect
the Motif port, but I think it should now be removed... I see absolutely no
reason to keep it around anymore. Nobody uses it... Nobody builds it...
Nobody owns it anymore (that I know of)... Nobody maintains it... Nobody CARES
about it...
Motif is generally a dying toolkit. I don't think the Linux/Unix market would
mind if it were removed, especially since even HP/Sun include GNOME/GTK in their
Unices.
If nobody minds and everyone approves, I'd hereby like to request an opportunity
to remove the Motif port from the tree. I'd LOVE to be the one that does it.
Let us hereby save Mozilla some lines of code in the tree. :-)
hrm, i'd like to see it kept alive. i was working at one point to fix the
string problems you reported, others seem to be doing the same work now so
hopefully things will get better.
if you do decide to remove it, please tag the motif code
MOTIF_RIGHT_BEFORE_IT_WAS_KILLED or something so that people can ressurrect it.
Comment 2•25 years ago
|
||
I would like to see Motif port alive, too.
Most code can be reused from Xlib-toolkit except some minor stuff:
- use Motif DND API
- use Motif clipboard API
- use Xt/Motif "color management" API
- use Motif/CDE datatyping for mimetype-->application mapping. CDE has a full
database with this... it may be nice to use that
- Motif Mozilla widget... :-)
- ... etc. etc.
| Reporter | ||
Comment 3•25 years ago
|
||
Goodness. Sounds like there is still a little support for it. I still don't
understand *why*, however. Could someone explain this to me? I mean, is there
ANYTHING feature-wise that the Motif port could potentially do that the other
three Unix ports (Xlib, GTK, and Qt) cannot? Is there ANY Unix platform, be it
proprietary OR open source, that the Xlib, GTK, or Qt ports will not run on at
this point? Then, on those platforms that support all four, is there ANY reason
whatsoever to pick Motif instead of Xlib, GTK, or Qt? In considering these
questions, I would keep in mind that even some of the strongest original
supporters of Motif/CDE, including HP, Sun , and The Open Group, are slowly
deprecating the CDE/Motif duo in favor of the two major Unix desktop
environments out there on the market today that are rapidly replacing CDE/Motif,
like GNOME/GTK, or KDE/Qt. I happen to think even the Qt port makes more sense
to support at this point than Motif. However, even then, since Mozilla has its
very own XPWidget set at this point, what is the point of supporting ANY widget
toolkit? Why bother using a full-fledged widget set, when Mozilla is now doing
this all ITSELF?? Why not simply use raw Xlib, and bypass the extra layer of
widgets? It would simplify things tremendously, and I think we have proven that
Xlib has greater speed, performance, and code-size potential than any of the
others, given that Mozilla has its own XPWidgets.
If the support for Motif is really this strong however, then I am certainly
willing to re-consider, and mark this bug WONTFIX, or even INVALID. If that is
the case however, then bug 22266 (which is assigned to NOBODY) should be
re-examined, as should bug 38637 (Roland, that will cover your Motif embedding
widget), bug 77984 (DnD support), bug 78653, and last but not least, bug 89329.
I will even be willing to check in patches for the Motif port, if you folks wish.
| Assignee | ||
Comment 4•25 years ago
|
||
So here we are months later and the motif port is still dead. I posted a last
call for motif to the newsgroups a few weeks ago and sentiment seemed to mainly
be that motif was already dead. The code is bitrotten and those who have
bothered to hack it enough to get it to compile, state that it still doesn't
run and those hacks have never made their way back into the tree. Since there
has been no active work on the motif port for the better part of 2 years now,
it's time for it to finally leave the building. I've got a patch to remove the
build references to motif and the following directories will be cvs removed:
config/mkdetect
gfx/src/motif
widget/src/motif
widget/timer/src/unix/motif
webshell/embed/xlib/motif
webshell/embed/xlib/xt
webshell/tests/viewer/unix/motif
| Assignee | ||
Comment 5•25 years ago
|
||
Comment 6•25 years ago
|
||
Comment on attachment 53185 [details] [diff] [review]
Kiss motif good bye
r=bryner
Attachment #53185 -
Flags: review+
| Assignee | ||
Comment 7•25 years ago
|
||
Taking the bug.
Assignee: zuperdee → seawood
Severity: normal → minor
Priority: -- → P4
Target Milestone: --- → mozilla0.9.6
Comment 8•25 years ago
|
||
rs=pavlov. check this in. :)
| Assignee | ||
Comment 9•25 years ago
|
||
The tree was tagged with MOTIF_LAST_RITES before the removal.
RIP Motif.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 10•25 years ago
|
||
Hooray!! Thanks guys.
I am now marking all Motif-related bugs WONTFIX. :-)
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•