nanogui: Thread: updated source available

Hi -
    The Nano-X system CVS has been placed on a commercial
server with backup power protection, same name:

cvs.microwindows.org

There are two CVS trees, microwin and nxlib.

For those without CVS access, I have placed a current
source tree (matching current CVS) on the web ftp site:

ftp://microwindows.censoft.com/pub/microwindows/microwindows-src-snapshot.tar.gz

If you know the project fairly well and want CVS write access,
let me know.  If anybody would like to nominate another, please do.

I will update the home page shortly, and would like to release the
current CVS as version 0.91.   Is anybody willing to try the
newer make system beforehand?  I would like to hear comments.

Next, I will catalogue the received patches and publish them,
along with the plan to include (most of them) into 0.92.
There have been a couple of major submissions/enhancements to the
win32 API portion.  After that, a community discussion and decision
for future enhancements and testing is in order.

The nanogui mailing list problem is not solved - those that use
spamassasin will need to explicitly whitelist Alex's servers in order
to receive nanogui mail.  I do not think this is a good enough solution
yet.  Please comment.

Regards,

Greg

Hi Greg,

> I will update the home page shortly, 

this is really a not important request but since you
are going to update the homepage, could you remove (or
maybe move to another page) the detailed changelog of
each release. I don't think such information is needed
on the main page and it would avoid to loading more
than 140K for the main page.

> and would like to release the current CVS as version
> 0.91.   Is anybody willing to try the
> newer make system beforehand?  I would like to hear
> comments.

it works :D .. (I'm not sure that's exactly the kind
of comment you are really expecting). I've tried the
config.x11 and another configuration derivated from
config.x11.
By the way, the Object Framework (mwin/mobject)
doesn't compile (don't know if it was the same before
since I have almost always been using nanox instead of
mwin).

More general comment about the this 'new' make system
is that ... well to me it seems quite similar to the
previous one. Well of course it has some new features
like the possibility to compile in different directory
(as discussed recently on the ML) and also lots of
things from Makefile have been moved to Objects.rules
and some other files ... but ... as discussed recently
I would prefer having a kconfig like make system. It
would allow to have clean/simple makefile, avoid
things like
  ifeq ....
  CFLAGS := ...
  endif
since we can automatically create the include file
based on the configuration  (like /include/autoconf.h
for the kernel) and some other interesting things ...
anyway that's a bit out of topic right now since it is
a project for future versions.

alain

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Greg Haerr wrote:
> The nanogui mailing list problem is not solved - those that use

That's news to me. The ETRN/RDNS name of my server was changed several 
days ago to something without an IP address in it, so if your 
SpamAssassin setup is still blocking messages it must be hitting a 
different rule this time. Please send me a copy of the Spamassassin 
report from one of the blocked messages.

-- 
------------ Alex Holden - http://www.alexholden.net/ ------------
If it doesn't work, you're not hitting it with a big enough hammer

Alex Holden wrote:
> That's news to me. The ETRN/RDNS name of my server was changed several 

I meant HELO not ETRN of course :-/

-- 
------------ Alex Holden - http://www.alexholden.net/ ------------
If it doesn't work, you're not hitting it with a big enough hammer

>  could you remove (or
> maybe move to another page) the detailed changelog of
> each release. I don't think such information is needed
> on the main page and it would avoid to loading more
> than 140K for the main page.

Yes - I'll change that.


> By the way, the Object Framework (mwin/mobject)
> doesn't compile (don't know if it was the same before
> since I have almost always been using nanox instead of
> mwin).

Perhaps we should remove the default compile for this,
since few folks if any use this C++ wrapper for nano-X.



> More general comment about the this 'new' make system
> is that ... well to me it seems quite similar to the
> previous one. Well of course it has some new features
> like the possibility to compile in different directory
> (as discussed recently on the ML) and also lots of
> things from Makefile have been moved to Objects.rules

Jonathan Foster contributed this, it's intent wasn't to
introduce some wholly new make method, but rather
to allow the tree to be able to be built for different
architectures without having to copy files around and
still use the existing config file format.  This newer make
system allows the config file, BIN and OBJ directories
(and of course the architecture) to be specified in a
command line to build the entire microwindows system.

Regards,

Greg