FoxGUIb/FAQ - Revision history

Henon: /* How can I help? */

2009-06-10T18:26:12Z

How can I help?

← Older revision		Revision as of 18:26, 10 June 2009
Line 10:		Line 10:

	=== How can I help? ===		=== How can I help? ===
-	If you have written any useful extensions to foxGUIb / libGUIb or corrected any bugs ~~please send~~ in ~~the patches~~.	+	If you have written any useful extensions to foxGUIb / libGUIb or corrected any bugs you may fork [http://github.com/henon/foxguib/tree/master foxguib] on github. I will gladly merge in all your contributions and fixes.

	=== foxGUIb crashes! What should I do? ===		=== foxGUIb crashes! What should I do? ===

Henon: /* Is foxGUIb still actively developed? */

2009-06-10T18:22:57Z

Is foxGUIb still actively developed?

← Older revision		Revision as of 18:22, 10 June 2009
Line 7:		Line 7:

	=== Is foxGUIb still actively developed? ===		=== Is foxGUIb still actively developed? ===
-	No. At the time being the author is quite busy with other projects. Therefore there is no time left for foxGUIb. I try to answer questions and fix little bugs as quickly as possible, though. If you would like to push foxGUIb beyond what it is now please drop me a mail at <meinrad dot recheis at gmail dot com>.	+	No. At the time being the author is quite busy with other projects. Therefore there is no time left for foxGUIb. I try to answer questions and fix little bugs as quickly as possible, though. If you would like to push foxGUIb beyond what it is now please drop me a mail at <meinrad dot recheis at gmail dot com> or start working by forking [http://github.com/henon/foxguib/tree/master foxguib] on github. I will gladly merge in all your contributions and fixes.

	=== How can I help? ===		=== How can I help? ===

Henon: /* I found an annoying little bug */

2009-06-10T18:21:53Z

I found an annoying little bug

← Older revision		Revision as of 18:21, 10 June 2009
Line 16:		Line 16:

	=== I found an annoying little bug ===		=== I found an annoying little bug ===
-	Please fix it and send me the patch or if you are not able to do it you may send a bug report to <meinrad dot recheis at gmail dot com>.	+	Please fix it and send me the patch or if you are not able to do it you may send a bug report to <meinrad dot recheis at gmail dot com>. You may fork [http://github.com/henon/foxguib/tree/master foxguib] on github. I will gladly merge in all your contributions and fixes.

	=== Why does foxGUIb change my x, y, with or height values ===		=== Why does foxGUIb change my x, y, with or height values ===

Henon: /* I'm putting radios in a groupbox, but can't get mutex behaviour */

2008-05-27T15:18:57Z

I'm putting radios in a groupbox, but can't get mutex behaviour

← Older revision		Revision as of 15:18, 27 May 2008
Line 85:		Line 85:
	}		}

-	~~Annother~~ even better solution would be to make use of the '''RadioMutex''' class provided by libGUIb. It derives from FX::VerticalFrame and coordinates all RadioButtons that are its direct descendants in the widget tree.	+	Another even better solution would be to make use of the '''RadioMutex''' class provided by libGUIb. It derives from FX::VerticalFrame and coordinates all RadioButtons that are its direct descendants in the widget tree.

	=== What is the best way to reuse layouts? ===		=== What is the best way to reuse layouts? ===

Henon: /* I'm putting radios in a groupbox, but can't get mutex behaviour */

2008-05-27T15:18:25Z

I'm putting radios in a groupbox, but can't get mutex behaviour

← Older revision		Revision as of 15:18, 27 May 2008
Line 84:		Line 84:
	puts "#{radioName} has been selected"		puts "#{radioName} has been selected"
	}		}
		+
		+	Annother even better solution would be to make use of the '''RadioMutex''' class provided by libGUIb. It derives from FX::VerticalFrame and coordinates all RadioButtons that are its direct descendants in the widget tree.

	=== What is the best way to reuse layouts? ===		=== What is the best way to reuse layouts? ===

Henon: /* Is foxGUIb still actively developed? */

2008-05-20T15:34:55Z

Is foxGUIb still actively developed?

← Older revision		Revision as of 15:34, 20 May 2008
Line 7:		Line 7:

	=== Is foxGUIb still actively developed? ===		=== Is foxGUIb still actively developed? ===
-	No. At the time being the author is quite busy ~~trying to start his own business~~. Therefore there is no time left for foxGUIb. If you would like to push foxGUIb beyond what it is now please ~~send~~ a mail to <meinrad dot recheis at gmail dot com>.	+	No. At the time being the author is quite busy with other projects. Therefore there is no time left for foxGUIb. I try to answer questions and fix little bugs as quickly as possible, though. If you would like to push foxGUIb beyond what it is now please drop me a mail at <meinrad dot recheis at gmail dot com>.

	=== How can I help? ===		=== How can I help? ===

Henon at 13:14, 9 December 2007

2007-12-09T13:14:37Z

← Older revision		Revision as of 13:14, 9 December 2007
Line 7:		Line 7:

	=== Is foxGUIb still actively developed? ===		=== Is foxGUIb still actively developed? ===
-	No. At the time ~~beeing~~ the author is quite busy trying to start his own business. Therefore there is no time left for foxGUIb. If you would like to push foxGUIb beyond what it is now please send a mail to <meinrad dot recheis at gmail dot com>.	+	No. At the time being the author is quite busy trying to start his own business. Therefore there is no time left for foxGUIb. If you would like to push foxGUIb beyond what it is now please send a mail to <meinrad dot recheis at gmail dot com>.

	=== How can I help? ===		=== How can I help? ===
Line 44:		Line 44:
	No, it is not. However it is possible to do quite impressive design just with the color settings of widgets. foxGUIb's own GUI proves that		No, it is not. However it is possible to do quite impressive design just with the color settings of widgets. foxGUIb's own GUI proves that

-	=== What is the best way to ~~seperate~~ generated code from manual code? ===	+	=== What is the best way to separate generated code from manual code? ===
-	First of all, you should never make manual corrections to foxGUIb generated files because this would make regeneration of the code very destructive. The correct way is to ~~seperate~~ generated code and manual extensions in two different files. There are two main ways to do this in Ruby. Assume you have generated a class called ''DoneWithFoxGUIb'':	+	First of all, you should never make manual corrections to foxGUIb generated files because this would make regeneration of the code very destructive. The correct way is to separate generated code and manual extensions in two different files. There are two main ways to do this in Ruby. Assume you have generated a class called ''DoneWithFoxGUIb'':

	_done_with_foxguib.rb:		_done_with_foxguib.rb:
Line 74:		Line 74:

	=== I'm putting radios in a groupbox, but can't get mutex behaviour ===		=== I'm putting radios in a groupbox, but can't get mutex behaviour ===
-	Before fox12 the Groupbox widget was also a Radiobutton-mutex-controller. Since fox12 this has been changed. I wrote a handy RadioGroup ~~class~~ which is included in libGUIb ~~of course~~. It works like this:	+	Before fox12 the Groupbox widget was also a Radiobutton-mutex-controller. Since fox12 this has been changed. As a replacement I wrote a handy controller called '''RadioGroup''' which is included in libGUIb. It works like this:

	#suppose you have three radiobuttons which you want to be mutually exclusive: @radio1, @radio2, @radio3		#suppose you have three radiobuttons which you want to be mutually exclusive: @radio1, @radio2, @radio3
Line 97:		Line 97:

	=== What has been changed in all the facades (== sub-classed widgets) ===		=== What has been changed in all the facades (== sub-classed widgets) ===
-	FoxGUIb has ~~subclassed~~ most of the FXRuby widgets for easier code generation. The convention is that Fox::FXText is ~~subclassed~~ by FX::Text	+	FoxGUIb has sub-classed most of the FXRuby widgets for easier code generation. The convention is that Fox::FXText is sub-classed by FX::Text
-	and Fox::FXTextField by FX::TextField. What has been added by libGUIb are just convenience constructors and other convenience stuff. But the ~~subclassed~~ widgets of course expose the standard [http://www.fxruby.org/doc/api/ FXRuby API]. If you like to know what has been added have a look at the generated code or at libGUIb16.rb itself.	+	and Fox::FXTextField by FX::TextField. What has been added by libGUIb are just convenience constructors and other convenience stuff. But the sub-classed widgets of course expose the standard [http://www.fxruby.org/doc/api/ FXRuby API]. If you like to know what has been added have a look at the generated code or at libGUIb16.rb itself.

	=== May I redistribute libGUIb with my programs? ===		=== May I redistribute libGUIb with my programs? ===

Henon: /* I get thousands of warnings when foxGUIb starts */

2007-12-09T13:11:36Z

I get thousands of warnings when foxGUIb starts

← Older revision		Revision as of 13:11, 9 December 2007
Line 22:		Line 22:

	=== I get thousands of warnings when foxGUIb starts ===		=== I get thousands of warnings when foxGUIb starts ===
-	This is a bug which is exhibited by a specific combination of FXRuby nd Ruby version (FXRuby 1.6.?). The bug has already been fixed. It should not happen if you update to the latest Ruby / FXRuby version. If this is not possible you can work around by inserting the statement ''$VERBOSE=nil'' at the very first line in foxGUIb's source.	+	This is a bug which is exhibited by a specific combination of FXRuby and Ruby version (FXRuby 1.6.?). The bug has already been fixed. It should not happen if you update to the latest Ruby / FXRuby version. If this is not possible you can work around by inserting the statement ''$VERBOSE=nil'' at the very first line in foxGUIb's source.

	=== foxGUIb crashes when loading a layout ===		=== foxGUIb crashes when loading a layout ===

Henon: /* May I redistribute libGUIb with my programs? */

2007-12-09T13:09:36Z

May I redistribute libGUIb with my programs?

← Older revision		Revision as of 13:09, 9 December 2007
Line 102:		Line 102:
	=== May I redistribute libGUIb with my programs? ===		=== May I redistribute libGUIb with my programs? ===
	Yes. LibGUIb has been packed into only one file for exactly this purpose. You may place libGUIb-1x.rb together with your sources or redistribute the installable libGUIb package.		Yes. LibGUIb has been packed into only one file for exactly this purpose. You may place libGUIb-1x.rb together with your sources or redistribute the installable libGUIb package.
		+
		+
		+	=== I got another question ===
		+	No problem. Send your question to meinrad dot recheis at gmail dot com.

Henon: /* What is libGUIb? */

2007-12-09T13:06:33Z

What is libGUIb?

← Older revision		Revision as of 13:06, 9 December 2007
Line 95:		Line 95:
	=== What is libGUIb? ===		=== What is libGUIb? ===
	[[LibGUIb]] is the library behind foxGUIb which is needed by the generated sources. LibGUIb contains facades (less complicated interfaces) for every widget, extends widgets with convenience methods and adds some handy tools.		[[LibGUIb]] is the library behind foxGUIb which is needed by the generated sources. LibGUIb contains facades (less complicated interfaces) for every widget, extends widgets with convenience methods and adds some handy tools.
		+
		+	=== What has been changed in all the facades (== sub-classed widgets) ===
		+	FoxGUIb has subclassed most of the FXRuby widgets for easier code generation. The convention is that Fox::FXText is subclassed by FX::Text
		+	and Fox::FXTextField by FX::TextField. What has been added by libGUIb are just convenience constructors and other convenience stuff. But the subclassed widgets of course expose the standard [http://www.fxruby.org/doc/api/ FXRuby API]. If you like to know what has been added have a look at the generated code or at libGUIb16.rb itself.

	=== May I redistribute libGUIb with my programs? ===		=== May I redistribute libGUIb with my programs? ===
	Yes. LibGUIb has been packed into only one file for exactly this purpose. You may place libGUIb-1x.rb together with your sources or redistribute the installable libGUIb package.		Yes. LibGUIb has been packed into only one file for exactly this purpose. You may place libGUIb-1x.rb together with your sources or redistribute the installable libGUIb package.