February 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Looking for developers to add GUI toolkit to XEmacs and/or InfoDock. 24 years, 3 months

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > > FYI, there is a BeOpen.com-sponsored project at SourceXchange for paid > > > work to integrate an Open Source GUI toolkit with XEmacs and InfoDock > > Bob, thanks for doing this! I think it will be very worth while. When > did you add this project? I was contemplating spending some of my time > in the probably coming temporary unemployment trying out SourceXchange > but I cannot remember seeing this before? Unfortunately I cannot > commit myself to anything at the moment because I am not sure if, > when and for how long I would be available for this. > > > Just an FYI for other people on the list... I think I'm going to submit a > > proposal later this week. > > Good luck and success! I would love to see this happening! > > > using vacation / comp-time to do it. The 4-5 week timeframe is based on > > using Qt, since it already has the easy ability to work with Xt-based > > Does that include convincing XEmacs major copyright holders (i.e. > including Sun and the FSF) to add a Qt exception clause? :-( Will see what stallman has to say... if the clause in there about needing to replace the current lwlib widgets wasn't there, I could do it completely as a module (would just be a bit harder). > > applications, and I have more experience with it than gtk. Qt also works > > better on win32 at the moment. > > But surely it isn't open source on that platform. No, but you can also use it under cygwin & an X server. Although I suppose the same holds true for gtk. Not that big a deal for me, since I have a windows license or two. Someone could also pony up the $1500 and distribute binaries for windows - you could then just redistribute the Qt dll, just like we do for our commercial apps. > > I also just noticed that the deadline was yesterday... > > That seems a mistake to me. > > Jan (who is wondering whether Andy will be charging consulting fees to > whoever takes this up) Heh... my main concern would be how hard it would be to convert _all_ the widgets to use Qt or gtk. It looks hopeless trying to get gtk to talk with an Xt application. -Bill P.

1 participants
0 comments

Re: patch to fix rect.el like GNU rect.el 24 years, 3 months

Jan Vroonhof

Didier Verna <didier(a)xemacs.org> writes: > 1/ I believe that in XEmacs, we use `####' and not `###'. I even believe that > somebody (Martin ?) recently made a global replace in the sources. Note > that personally, I've always used three #, not four, and I don't like using > four. Why not a hundred, while we're at it. I'm wondering where this > convention comes from. Rumour has it it comes from C-u # Jan

1 participants
0 comments

Re: Looking for developers to add GUI toolkit to XEmacs and/or InfoDock. 24 years, 3 months

Jan Vroonhof

[Message resent with corrected headers] Bob Weiner <weiner(a)beopen.com> writes: > P.S. If you want me to respond to something, mail me directly as I rarely get > the luxury to read these lists. If you have other *very specific* project > ideas surrounding XEmacs or InfoDock, tell us about them, including > development timeframes so we can consider sponsoring them. Here is some very specific areas that XEmacs could do with improvements, including some that can be done by people with non-programming skills. Most of these are smaller projects than adding a whole new Widget set. The times are guesstimates. - Update the New User manual to reflect version 21, including major usability improvements for Newbies such as customize. [2 weeks] - Write a graphical version of the tutorial. This is much more doable with the new widgets. [1.5 weeks] - Paint an Open Source set of high-color icons for XEmacs (including Gnus, VM, W3 and TeX-toolbar). [<1 week for a skilled artist] - Interface XEmacs with a fast C/C++ parser (gcc with precompiled headers?) to provide the equivalent of the Intellisense features contained in Visual Studio. (c.f. Eric Ludlam's work, eldoc, ilisp JDK and your own oobrowser). [1 month] Alternatively find out whether XEmacs-NT can call on Visual Studio to provide the needed information and if so, implement it. [1 week] - Provide true unicode support for XEmacs (I believe this one might be already taken). These are all projects that directly improve the (apparent) usability of XEmacs to various groups of new and older users. Apart from the last one I feel they can performed by one committed person in isolation and then be integrated. Jan P.S. To close of with a really hard problem (that to me seems inappropriate for SourceXchange) that is becoming more and more relevant. - Design and implement a clean way of allowing "multiple major modes" as embedded scripts, ditto HTML, and ditto documentation is becoming more and more popular. AFAIK there currently isn't an editor that does this really well.

1 participants
0 comments

21.2-b30 NT native fails to build 24 years, 3 months

Damon Lipparelli

After updating to the latest CVS, I can't build NT native anymore. The build gets as far as: ..\src\temacs.exe -batch -l ..\src\..\lisp\update-elc.el and then dies with the following: runtime error R6027 - not enough space for lowio initialization Has anyone else seen this? -lipp ps: I'm building with this command line: ＠nmake -nologo -f xemacs.mak %1 %2 %3 %4 %5 %6 \ INSTALL_DIR="d:/win32app/xemacs-21.2" \ MAKEINFO="d:\win32app\utils\makeinfo.exe" \ PACKAGE_PREFIX="d:/win32app/xemacs-21.2/lib/xemacs" \ HAVE_MSW=1 HAVE_X=0 HAVE_MULE=0 HAVE_MSW_C_DIRED=1 \ GUNG_HO=1 DEBUG_XEMACS=0 HAVE_XPM=1 \ XPM_DIR=d:/src/xemacs-beta/libdist/ilib HAVE_GIF=1 HAVE_JPEG=1 \ JPEG_DIR=d:/src/xemacs-beta/libdist/ilib HAVE_TIFF=1 \ TIFF_DIR=d:/src/xemacs-beta/libdist/ilib HAVE_PNG=1 \ PNG_DIR=d:/src/xemacs-beta/libdist/ilib \ ZLIB_DIR=d:/src/xemacs-beta/libdist/ilib

1 participants
0 comments

Re: Use a more modern HTML DTD by default 24 years, 3 months

Jan Vroonhof

torkel(a)hpc2n.umu.se (Bj?rn Torkelsson) writes: > What are the PC way to comment on patches sent to xemacs-patches if you > are not a member of the review board? xemacs-beta? Yep. Although if you think a patch can cause a thermonuclear reaction it is a good idea to CC xemacs-review (you are allowed to write to it). Most actual discussion should occur here. > Why not using 4.01 then? > > +(defcustom html-helper-htmldtd-version "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">\n" I'm all for it. I just copied our site wide settings (which should be updated I guess). Jan

1 participants
0 comments

Re: Looking for developers to add GUI toolkit to XEmacs and/or InfoDock. 24 years, 3 months

William M. Perry

Olivier Galibert <galibert(a)pobox.com> writes: > On Tue, Feb 22, 2000 at 10:24:07AM -0500, William M. Perry wrote: > > Just an FYI for other people on the list... I think I'm going to submit a > > proposal later this week. I think after a design document is done that it > > would take about a month of full-time coding, and I was planning on just > > using vacation / comp-time to do it. The 4-5 week timeframe is based on > > using Qt, since it already has the easy ability to work with Xt-based > > applications, and I have more experience with it than gtk. Qt also works > > better on win32 at the moment. > > Qt's license (even the OpenSource(sm) one) and the GPL are well known to > be non-compatible. Bad karma. >From everything I have heard, stallman has relented on the Qt 2.x front. I could be mistaken though. Anyone? I'll send him some email directly. -Bill P.

1 participants
0 comments

Re: Newbie Beta Tester Questions 24 years, 3 months

Jan Vroonhof

Welcome! Jake Colman <colman(a)ppllc.com> writes: > series. So, having downloaded and built the 21.2.29 release, I have some > newbie questions: Martin has already addressed the specifics. It would be nice if you kept small notes about glitches, missing documentation and annoyances you notice as you become familiar. For long time beta testers it sometimes hard to remember that they actually spent a desperate night finding out how to make X work or to disable Y. Jan

1 participants
0 comments

Re: Looking for developers to add GUI toolkit to XEmacs and/or InfoDock. 24 years, 3 months

William M. Perry

Bob Weiner <weiner(a)beopen.com> writes: > FYI, there is a BeOpen.com-sponsored project at SourceXchange for paid > work to integrate an Open Source GUI toolkit with XEmacs and InfoDock > (BeOpen.com's Open Source IDE built atop XEmacs). The code developed > under the project will be GPLed and broadly distributed. Just an FYI for other people on the list... I think I'm going to submit a proposal later this week. I think after a design document is done that it would take about a month of full-time coding, and I was planning on just using vacation / comp-time to do it. The 4-5 week timeframe is based on using Qt, since it already has the easy ability to work with Xt-based applications, and I have more experience with it than gtk. Qt also works better on win32 at the moment. Bonus points if it can be abstracted enough to work with other toolkits eventually. :) I also just noticed that the deadline was yesterday... Urk. I was stuck in transit from seattle to indiana during most of the weekend. I assume that since nobody got a proposal in that more will be accepted? > Visit www.sourceXchange.com and browse the RFPs section for specific > details on the project which is titled Graphical InfoDock/XEmacs. It > should be a fun and highly useful piece of work as well as a way to earn > some side income. Was planning on emailing you about this today bob... finally recovered from my week in purgatory (seattle) and weekend in hell (airports). :) -Bill P.

2 participants
1 comments

Re: More tab fixes 24 years, 3 months

Nick V. Pakoulin

Andy Piper <andy(a)xemacs.org> writes: > [1 <text/plain; us-ascii (7bit)>] > This should fix the color problems people are seeing and also fixes > properly the original resizing problem. Every time I fixed a bug it > revealed another one, that's why it took so long. At least I understand the > code better now. No, this patch does not work -- at least, it hides the names of the buffers on tabs. > > Please try this if you have applied my other tabs fix. If it works 21.2.30 > should go out soon. And what about hiding ispell choices window? It is still present. > andy Nick.

2 participants
1 comments

Re: Need DNS/Web expert - http://xemacs.org 24 years, 3 months

Hrvoje Niksic

<nic(a)niss.ac.uk> writes: > Martin Buchholz wrote on 22-February-2000: > > ->People these days expect entering `xemacs.org' into their web browser > ->to do something useful. Does anyone know the (presumably trivial) > ->incantation to our /etc/named/xemacs/xemacs.db file to make `xemacs.org' go to > ->`http://www.xemacs.org'? > -> > ->Martin > > Put in an A record for xemacs.org, and make www.xemacs.org a CNAME > of xemacs.org. Won't the browser still insist on using just `xemacs.org' as the host name? Maybe what you want is an additional redirect in the web server configuration, redirecting http://xemacs.org/foo to http://www.xemacs.org/foo for any foo.

3 participants
2 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta February 2000