Event, GUi and other...

[GeoVah]

So i'm the first on the liist !!!

First, hello, word ands BygFoot is realy really good !
I have lot of idea, so I just write it in case of it's interest you..

There is two part :

On one hand, some idea for GUI :
- Improve history window for result :
One for the manager, One for the current team
Each time you won a cup or finish first, you receive a cup. All cup you have receive are show in the result window. In order to do this, you may implement "event" : <em>"Monaco" won the Chamopion ligues !<em> and behind an image with the cup· or <em>"Thierry Henry"</em> is the best player of the year, also if Thierry Henry is not in you club... And add the image in your gallery...

- Maybe you can add "fanion" (it's the french word for the image associated with a team") in team definition ? This image can also be use and display in the event.

On other hand, on "code" side :
Maybe use XHTML+CSS for text data instead of plain text for history, reasult, etc... -I have a fast look on your code and don't seems to use this-.

Start to separate -really- GUI from data : In variables.c we found data for the user and Gtk stuff. The idea is to split you code in two part, the functions for play (maybe lib?) and the GUI.

I don't know GTK (only QT ) but maybe I start to use GTK for help you, if I have the time ...



-

[gyboth]

hello,

So i'm the first on the liist !!!

that's because i just put the forum online i'm in fact currently announcing the forum on the homepage. and i haven't filled the developer forums yet.

On one hand, some idea for GUI :
- Improve history window for result :
One for the manager, One for the current team
Each time you won a cup or finish first, you receive a cup. All cup

yes, that's a nice idea, to have a separate history for the manager. in fact, there is one already (Figures -> History), but it's a rather old part of the code and not very well done.

you may implement "event" : <em>"Monaco" won the Chamopion ligues !<em> and behind an image with the cup· or <em>"Thierry Henry"</em> is the best player of the year, also if Thierry Henry is not in you club... And add the image in your gallery...

yes, i'm planning to make Events. also ones like "Arsenal crushes ManU 4:0 at home!". but it's still a long way to go.

- Maybe you can add "fanion" (it's the french word for the image associated with a team") in team definition ? This image can also be use and display in the event.

that's not possible the club emblems (badges) are copyrighted. this is also why i can't use official club names in the official Bygfoot packages.

Maybe use XHTML+CSS for text data instead of plain text for history, reasult, etc... -I have a fast look on your code and don't seems to use this-.

yes. no. in 1.9 i'll be switching to XML. but what do you mean for 'history' and 'result'? to store the data on the hard disk instead of in the memory?

Start to separate -really- GUI from data : In variables.c we found data for the user and Gtk stuff. The idea is to split you code in two part, the functions for play (maybe lib?) and the GUI.

you mean to separate variables like 'teams' and 'main_window'? that's a good idea. but i believe that the other parts of the code are more or less well separated.

I don't know GTK (only QT ) but maybe I start to use GTK for help you, if I have the time ...

i'd be glad

gyozo

P.S.: You should change your post title to something more meaningful. 'I wish' (wish is written with only one 'h' ) doesn't really tell us what you wish for.

[GeoVah]

Maybe use XHTML+CSS for text data instead of plain text for history, reasult, etc... -I have a fast look on your code and don't seems to use this-.

yes. no. in 1.9 i'll be switching to XML. but what do you mean for 'history' and 'result'? to store the data on the hard disk instead of in the memory?

I'm idea is for the GUI, in order to display the hsitory text and result text :
Instead of display plain text in a edit widget, use a Browser widget and use XHTML/CSS for formatting the text.

[gyboth]

I'm idea is for the GUI, in order to display the hsitory text and result text :
Instead of display plain text in a edit widget, use a Browser widget and use XHTML/CSS for formatting the text.

ah, i didn't know there was a browser widget. i mean, there obviously is one in QT, but are you sure there's an equivalent in GTK? i didn't find one in the index of the reference manual.

gyözö

[GeoVah]

Yes, there is one extra lib call GtkHTML.
I found it whis my friend google. See http://primates.ximian.com/~rodo/progra ... uadec.html

For my first try, i'm wanted to use it for the documentation :
Menu help->information show the HTML file which represent the documentation, so we can
use HTML syntax for doc and you can also provide this file up to date on web site ... . Formatting text (color, bold/italic, menu, ...) could be more easier with HTML instead of plain text.

It's just a try, for me to understand GTK, and to see if it can be used in BygFoot (dependency, already develop,etc...)

[gyboth]

Yes, there is one extra lib call GtkHTML.
I found it whis my friend google. See http://primates.ximian.com/~rodo/progra ... uadec.html

hm... the lib seems to depend on gnome. i'm not sure i'd like to have such a dependancy in Bygfoot. not everybody has gnome installed, let alone gnome headers.

gyözö

[GeoVah]

hm... the lib seems to depend on gnome. i'm not sure i'd like to have such a dependancy in Bygfoot. not everybody has gnome installed, let alone gnome headers.

Yes it depends on gnome .
So my idea for rendering text in HTML is not good ...
Other idea will be to use the text widget with color (look gtkdemo) but need rework help file for add some formatting data.

[gyboth]

Other idea will be to use the text widget with color (look gtkdemo) but need rework help file for add some formatting data.

i'm not sure working on the help file would be rewarding. the current help file is very out-of-date (did i mention that i don't like writing documentation? ); besides, the game is really rather simple.

as Bygfoot has a wiki now (http://mec-symonds.eng.monash.edu.au/cg ... ot/WebHome), i'd rather use the wiki as the game documentation database (we could maybe use a snapshot of the wiki pages as in-game documentation). at any case we should agree on a common documentation format, e.g. html or text or whatever.

gyözö

[GeoVah]

Other idea will be to use the text widget with color (look gtkdemo) but need rework help file for add some formatting data.

i'm not sure working on the help file would be rewarding. the current help file is very out-of-date (did i mention that i don't like writing documentation? ); besides, the game is really rather simple.

as Bygfoot has a wiki now (http://mec-symonds.eng.monash.edu.au/cg ... ot/WebHome), i'd rather use the wiki as the game documentation database (we could maybe use a snapshot of the wiki pages as in-game documentation). at any case we should agree on a common documentation format, e.g. html or text or whatever.

gyözö

I agree with the idea on a common documentation format, and don't forget : an offline documentation must be provide.
More over if work are made in formatting text data, iI think this "text widget improve" can (and must ?) be use to display history and other text base data. This is why i have proposed a html render widget.

[vector]

I agree that a common documentation medium is required and that its best if its available"offline" ie part of the game. HTML is a very common format which is a much better extension of simple text and lends itself to collaboration. However as you say we dont want yet another dependancy (Gnome) and Im not aware gtk will support it any other way.

Also note, that the twiki doc is a pit where things can be tossed in. the idea would be to eventually weed the good ones back out again reformat and produce a proper doc. There is no exact Twiki Page to HTML doc converter that I know of but I dont think it would be too hard to make a parser. So its not a dead end. I generally just cutn paste out what i need. The twikis formatting isnt exactly tantelising, so its not as if you need the formatting info anyway.

I vote for HTML.
Is there some way we can simply launch the "systems" browser from within bygfoot to look at a "manual.html" file in the /home/bygfoot folder. Everyone has a browser of some sort? We just point it to the file. ie the manual doesnt reside within the bygfoot game. I know of a few apps that do this and as a user Im happy with it.

[gyboth]

let me summarize then:

• we'd like to have the docs in html format
• the wiki isn't an appropriate replacement for the in-game docs
• as there's no browser widget in GTK proper, we could start the system browser from within the game

the question that remains to be answered is, who's going to write the docs? i'm not really satisfied with the current documentation at the home page. on the other hand, i don't like writing docs at all, but i don't see who else could do it

gyözö

[vector]

the question that remains to be answered is, who's going to write the docs?

Indeed the author is better poised to write the docs but as long as you dont mind me/us asking questions anyone can complete them. At least with html anyone, from any OS, can add their bit. It will however still rely on you to make sure:
* We are not "giving the game away" ie explaining too much
* Obvious misenterpretations of game code.

I have started trawling thru your code in an attempt to understand how it goes (wow there is alot of it But im not a "c" person and strugling. You could provide some insight by putting even more comments in the code. Allowing me to simply lift out and "reformat" (make readable and expand etc) the coments. (This is how I write my python docs, as I go, inside the code) I have a code parser which pulls out all the comment lines and dumps to a text file I then just go thru and reformat it, deleting any techo stuff.

As mentioned b4 Im happy to do this but lack the ability to read the "c" fluently.
Adding stuff from the twiki or forum posts is fine and I have been doing this but its a bit like bolting the gate after the horse gone.

* I can do it but I aint brilliant.
* Untill someone better comes along.

Mind you i said that once to a band i was mixing for when they asked me to pick up a bass guitar. Its 14 years on and im still playing bass for the same band. Am I a good bassist? NO but then the band aint Rammstein.

[gyboth]

Indeed the author is better poised to write the docs but as long as you dont mind me/us asking questions anyone can complete them. At least with html anyone, from any OS, can add their bit. It will however still rely on you to make sure:
* We are not "giving the game away" ie explaining too much
* Obvious misenterpretations of game code.

i'd be tremendously grateful if anyone could take on the docs. i'd answer any questions of course. and great parts of the old docs can be reused, too (i'm just not satisfied with their structure).

I have started trawling thru your code in an attempt to understand how it goes (wow there is alot of it But im not a "c" person and strugling. You could provide some insight by putting even more comments in the code. Allowing me to simply lift out and

i believe it's too late for 1.7 it'd be a lot of work to do the comments right. but i'm doing this doxygen trick for 1.9, so there should be nice comments for that version at least.
besides, i believe that the most important part of the docs are not the code comments but simply a manual on how to play and what possibilities there are.

As mentioned b4 Im happy to do this but lack the ability to read the "c" fluently.
Adding stuff from the twiki or forum posts is fine and I have been doing this but its a bit like bolting the gate after the horse gone.

it's not necessary to document the code (i mean, not for the users). we'd only need things like 'getting started', 'how to handle transfers' and the likes. if you could do it, i'll give you 20% of the donations that would make 0 $ up to now...

gyözö