nanogui: Thread: Pending patches/bug/requests ... list available on the FTP

Hi all,

in collaboration with Greg, we have made a list of all currently pending
issues / patches / features requests.
It is based on emails either directly sent to greg or to the mailing list
between the 0.90 release and now.
Everything is now available on the FTP server in a "patch-0.92" folder:
	ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/
The easiest way to browse them (all emails and attachment are stored in 
separate files) should be to first check the file: file_list.txt

With the release of all those things, a community work could start.
Most probably not everything will find its way in
Nano-X since there are also some very system / board
dependant stuffs which might probably not be of any help in a Nano-X
release. Still it contains lots of interesting stuffs and especially
a very big work on mwin from Gabriele Brugnoni.
If you notice that there are some missing stuffs (something important
patch that you've sent but which is not listed here) please report
it.
I think the mailing list should be the best place to discuss about those
patches for now on.

Regards,

Alain

	
	
		
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Hi...

nice to see bugs fixed which i`'ve found too but nobody on the list responded to e.g.

ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20041012-mwin_enhancement_fix_1.txt
and
http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?mss:8874:200408:gikaimjiefeoehkfooac


>in collaboration with Greg, we have made a list of all currently pending
>issues / patches / features requests.
But the reason for this mail is: Is the following bug also solved because i cannot find it on the list

Thread: http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?mss:9091:cgbfpkebpejpeekcjhgd

Kind regards,

Gerd	

Hi...

i'm responding to myself... ;-)

As it is 3:15 in the morning and i cannot sleep (or to sleepy to read files... :-( ) and after reading the files again i've found the first one as

ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20040801-Bug_in_MwDestroyWindow.txt

Maybe i'll find the second one too if i go to bed now and read the list again tomorrow. On monday/tuesday i'll compare at work my changes to 0.90 to the original 
files to see if i've reported all found "bugs".

Kind regards,

Gerd

PS: I'll try to go to bed now again... ;-)

> nice to see bugs fixed which i`'ve found too but nobody on the list responded to e.g.
> 
> ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20041012-mwin_enhancement_fix_1.txt
> and
> http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?mss:8874:200408:gikaimjiefeoehkfooac
> 

actually those data are still very ... RAW. Some problems have been reported
several times and then maybe be listed in several places in patch_0.92 
(most often
reported problem might be the selection.o problem of nxlib).
Some emails that may have been left without responce are also listed ...
your email is actually here:
ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20040801-Bug_in_MwDestroyWindow.txt

There is a big work to do to extract bug report from this list (and check if
they have already been fixed or not ... and provide fixes :D).

Help is of course always very welcome.

Regards,

Alain

	

	
		
_____________________________________________________________________________ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com

On Saturday 28 May 2005 02:04, Alain Volmat wrote:
> Hi all,
>
> in collaboration with Greg, we have made a list of all currently pending
> issues / patches / features requests.
> It is based on emails either directly sent to greg or to the mailing list
> between the 0.90 release and now.
> Everything is now available on the FTP server in a "patch-0.92" folder:
> 	ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/
> The easiest way to browse them (all emails and attachment are stored in
> separate files) should be to first check the file: file_list.txt
>
> With the release of all those things, a community work could start.
> Most probably not everything will find its way in
> Nano-X since there are also some very system / board
> dependant stuffs which might probably not be of any help in a Nano-X
> release. Still it contains lots of interesting stuffs and especially
> a very big work on mwin from Gabriele Brugnoni.
> If you notice that there are some missing stuffs (something important
> patch that you've sent but which is not listed here) please report
> it.
> I think the mailing list should be the best place to discuss about those
> patches for now on.
>
> Regards,
>
> Alain
 
ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20050427-optional_FBLIN_support.txt

I'd like to see this one go in, I was about to start writing the same kind of 
patch. Another option would be to have all drivers register themselves.
So in each driver file something like

static void register_me() __attribute__ ((constructor))
{
   global_driver_table_append(&my_driver_struct);
}

Then the driver selection code in fb.c would turn from a big switch to an 
iteration over the list of drivers and choose the matching one. This would 
get rid of the ifdefs in this file.

Would you consider this a better option ?

Bye
Alex
--
Work: ####@####.#### - http://www.jenoptik-los.de
Home: ####@####.####                - http://www.kde.org
      ####@####.####               - http://www.neundorf.net

> ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/20050427-optional_FBLIN_support.txt
> 
> I'd like to see this one go in, I was about to start writing the same kind of 
> patch.

Me too :D and that's basically the reason why I wrote it last month. :D

> Another option would be to have all drivers register themselves.
> So in each driver file something like
> 
> static void register_me() __attribute__ ((constructor))
> {
>    global_driver_table_append(&my_driver_struct);
> }
> 
> Then the driver selection code in fb.c would turn from a big switch to an 
> iteration over the list of drivers and choose the matching one. This would 
> get rid of the ifdefs in this file.
> 
> Would you consider this a better option ?

I have to admit that it is the first time I hear about this constructor
attribute ... after a bit of googling I understand what it does and it seems
to be quite good for this case. However does using such attribute will not
make problem on some platform ? (I lack of information about it so I can't
really judge) If no, then I think since solution if much better than the
dirty #ifdef solution.

Alain

> 
> Bye
> Alex
> --
> Work: ####@####.#### - http://www.jenoptik-los.de
> Home: ####@####.####                - http://www.kde.org
>       ####@####.####               - http://www.neundorf.net
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
</quote>

	

	
		
_____________________________________________________________________________ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com

On Saturday 28 May 2005 08:50, Alain Volmat wrote:
...
> I have to admit that it is the first time I hear about this constructor
> attribute ... after a bit of googling I understand what it does and it
> seems to be quite good for this case. However does using such attribute
> will not make problem on some platform ? (I lack of information about it so
> I can't really judge) If no, then I think since solution if much better
> than the dirty #ifdef solution.

Same here, that's why I'm not sure it's really better.
Is microwindows also used with compilers other than gcc ? If yes, then it's 
probably no option.

In C++ it would be easy to do, simply put the following in any object file:

class Fb8DriverInitializer
{
   public:
      Fb8DriverInitializer() 
{global_driver_table_append(&fb8_driver_struct);};
}

Fb8DriverInitializer fb8DriverInitializer;

When the program starts, the global variables will be initialized and this way 
automatically the constructors will be executed.

Bye
Alex
-- 
Work: ####@####.#### - http://www.jenoptik-los.de
Home: ####@####.####                - http://www.kde.org
      ####@####.####               - http://www.neundorf.net

> On Saturday 28 May 2005 08:50, Alain Volmat wrote:
> ...
> > I have to admit that it is the first time I hear about this constructor
> > attribute ... after a bit of googling I understand what it does and it
> > seems to be quite good for this case. However does using such attribute
> > will not make problem on some platform ? (I lack of information about it so
> > I can't really judge) If no, then I think since solution if much better
> > than the dirty #ifdef solution.
> 
> Same here, that's why I'm not sure it's really better.
> Is microwindows also used with compilers other than gcc ? If yes, then it's 
> probably no option.

There are still some borland, TC ... makefile in the source code. That's the
reason why I asked about other platform ... Even if I've not heared about
anybody using them recently, it might be a bit risky to use code that might
only work when compiled with gcc. Is that a new feature of gcc ? or is it 
already here from quite a long time ? Adding a dependency on very recent gcc
is probably not the right way to go.

> In C++ it would be easy to do, simply put the following in any object file:
> 
> class Fb8DriverInitializer
> {
>    public:
>       Fb8DriverInitializer() 
> {global_driver_table_append(&fb8_driver_struct);};
> }
> 
> Fb8DriverInitializer fb8DriverInitializer;
> 
> When the program starts, the global variables will be initialized and this way 
> automatically the constructors will be executed.

Yeah, I knew about C++ constructors/destructors and that's why I was surprised
to hear some similar feature in C. Thanks for pointing out this attribute. :D

Alain

> 
> Bye
> Alex
> -- 
> Work: ####@####.#### - http://www.jenoptik-los.de
> Home: ####@####.####                - http://www.kde.org
>       ####@####.####               - http://www.neundorf.net
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
</quote>

	

	
		
_____________________________________________________________________________ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com

Hello,

> I'd like to see this one go in, I was about to start writing the same kind of 
> patch. Another option would be to have all drivers register themselves.
> So in each driver file something like
> 
> static void register_me() __attribute__ ((constructor))
> {
>    global_driver_table_append(&my_driver_struct);
> }
> 
> Then the driver selection code in fb.c would turn from a big switch to an 
> iteration over the list of drivers and choose the matching one. This would 
> get rid of the ifdefs in this file.
> 
> Would you consider this a better option ?

In case portability is of concern, you can avoid the __attribute__ quite
easily:

  * Have each driver contain "DEFDRIVER(my_driver_struct)", where DEFDRIVER
    is a no-op macro.

  * At compile time, scan all the driver sources for DEFDRIVER() and have
    a tiny sed+awk/whatever script construct a .c file with the driver
    table.

That's what I do in a private project of mine, and it works reasonable
well. If people think this would be a good way, I'd volunteer to implement
it.

	Regards,
		-- Jachym Holecek

Alain Volmat wrote:

> Hi all,
> 
> in collaboration with Greg, we have made a list of all currently pending
> issues / patches / features requests.
> It is based on emails either directly sent to greg or to the mailing list
> between the 0.90 release and now.
> Everything is now available on the FTP server in a "patch-0.92" folder:
> 	ftp://microwindows.censoft.com/pub/microwindows/patch-0.92/
> The easiest way to browse them (all emails and attachment are stored in 
> separate files) should be to first check the file: file_list.txt

Maybe you want to change the name "file_list.txt" to something else so it 
will be the first file displayed when viewing the above URl. Like 
__file_list.txt or FILELIST.txt ...

--
Steven