Re: [Amsn-devel] new WIKI
Hey !
It's me who port that
And it's a shit to port !
It's me who did all the job :p
It's not finished because I hadn't time...
I will try to finish that this evening...
Phil
Le Wednesday 21 June 2006 07:52, Youness Alaoui a écrit :
Hey, wow, I just saw this :
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
For sure it needs a lot of editing, but it's already good this way, it
shouldn't be that difficult to port it after all.
I just want to make a note, I see in the top of the page :
Frequently Asked Questions
Français - Swedish - Spanish (Incomplete) - Danish (Incomplete)
where Francais links to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions_F
rench Swedish to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions_S
wedish etc...
I would suggest you use mediawiki's internationalization support
instead... I think you only need to add in the end of the page something
like
{{fr}}
or something like that (refer to the manual, I don't know what it was
exactly), and you'd get a access to a french version of the text...
damn it.. I just tried on kakaroto.homelinux.net/wiki
it doesn't work!
http://en.wikipedia.org/w/index.php?title=SVNaction=edit
I can't understand what it is...
it seems {{ }} means you access a macro (a template), so if we do
{{howto}}
it will be replaced by Template:howto (in red), once we click on it, we
edit the 'template:howto' page with the content [[Category:How To]] then
the {{howto}} macro will be replaced on the fly by it scontent
([[Category:How to]] instead of the Template:howto)
I found some other examples :
http://www.mediawiki.org/wiki/Help:FAQ
Edit it and look at the end... you see the {{Lang:FAQ}} ? now look at the
last part of that link I gave...
then look here :
http://www.mediawiki.org/w/index.php?title=Template:Lang:FAQ
But I still don't know where the In other languages on the left panel
comes from!!!
Maybe it's a setting.. we'll have to look at that...
anyways, that's all for now, we're all happy to know we can have macros
(templates) with mediawiki! :)
KKRT
On Tue, 20 Jun 2006 18:26:16 -0400, GrdScarabe [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philippe Valembois - Phil wrote:
Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit :
btw, this whole thread wasn't about what to put in the new wiki, it was
about changing links to the old wiki so we can put this new wiki as
amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the old wiki
in
amsn.sf.net/devwiki
who's taking care of changing those links ?
I can do it but I would like the FAQ to be moved on the user WIKI...
Phil
I agree ... the FAQ is really user oriented and this way we will be able
to keep the more technical questions for a developer oriented FAQ.
The bad news is we cannot convert the FAQ from tikiwiki format to
mediawiki format (except if some filters exist somewhere ... I doubt
it). In this case, it would be in my opinion, a good thing to split the
FAQ. At least in categories :
- general FAQ
- technical FAQ
- Windows specific
- Linux specific
- Mac specific
because our FAQ is too big, it is difficult to make it clear with so
much information.
I don't have much time unfortunately to work on that ... moreover there
are some troubles with tikiwiki and some weired characters in the pages
such that I cannot save the pages anymore. If someone has an idea ?
Finally ... I already asked several times, but I'd like to have the
liste of pages (obtained from the database) that we have in our dev wiki
in order to try to find a better way to organize it. Maybe my
proposition is completly stupid, but what about setting up a new media
wiki for dev (prefixes in db for the tables) and migrate/reorganize in
this new wiki. I'm really pissed against tiki-wiki :S :)
Have a nice week anyway enjoy the sun :D
GrdScarabe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEmHYIPmfsnt4Id3wRAngJAKC5QlM42wM2R/rnDkLFLg6AmdWkLACg3IP4
MpyqyRLEFV7dbaglSQM7Z14=
=N2jV
-END PGP SIGNATURE-
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Erf...
I just see that many people worked on it since my first edition... And I saw
too that my log in hasn't been remembered... (I am the one who did the stub)
Phil
Le Wednesday 21 June 2006 20:10, Philippe Valembois - Phil a écrit :
Hey !
It's me who port that
And it's a shit to port !
It's me who did all the job :p
It's not finished because I hadn't time...
I will try to finish that this evening...
Phil
Le Wednesday 21 June 2006 07:52, Youness Alaoui a écrit :
Hey, wow, I just saw this :
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
For sure it needs a lot of editing, but it's already good this way, it
shouldn't be that difficult to port it after all.
I just want to make a note, I see in the top of the page :
Frequently Asked Questions
Français - Swedish - Spanish (Incomplete) - Danish (Incomplete)
where Francais links to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
_F rench Swedish to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
_S wedish etc...
I would suggest you use mediawiki's internationalization support
instead... I think you only need to add in the end of the page something
like
{{fr}}
or something like that (refer to the manual, I don't know what it was
exactly), and you'd get a access to a french version of the text...
damn it.. I just tried on kakaroto.homelinux.net/wiki
it doesn't work!
http://en.wikipedia.org/w/index.php?title=SVNaction=edit
I can't understand what it is...
it seems {{ }} means you access a macro (a template), so if we do
{{howto}}
it will be replaced by Template:howto (in red), once we click on it, we
edit the 'template:howto' page with the content [[Category:How To]]
then the {{howto}} macro will be replaced on the fly by it scontent
([[Category:How to]] instead of the Template:howto)
I found some other examples :
http://www.mediawiki.org/wiki/Help:FAQ
Edit it and look at the end... you see the {{Lang:FAQ}} ? now look at the
last part of that link I gave...
then look here :
http://www.mediawiki.org/w/index.php?title=Template:Lang:FAQ
But I still don't know where the In other languages on the left panel
comes from!!!
Maybe it's a setting.. we'll have to look at that...
anyways, that's all for now, we're all happy to know we can have macros
(templates) with mediawiki! :)
KKRT
On Tue, 20 Jun 2006 18:26:16 -0400, GrdScarabe
[EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philippe Valembois - Phil wrote:
Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit :
btw, this whole thread wasn't about what to put in the new wiki, it
was about changing links to the old wiki so we can put this new wiki
as amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the old
wiki in
amsn.sf.net/devwiki
who's taking care of changing those links ?
I can do it but I would like the FAQ to be moved on the user WIKI...
Phil
I agree ... the FAQ is really user oriented and this way we will be
able to keep the more technical questions for a developer oriented FAQ.
The bad news is we cannot convert the FAQ from tikiwiki format to
mediawiki format (except if some filters exist somewhere ... I doubt
it). In this case, it would be in my opinion, a good thing to split the
FAQ. At least in categories :
- general FAQ
- technical FAQ
- Windows specific
- Linux specific
- Mac specific
because our FAQ is too big, it is difficult to make it clear with so
much information.
I don't have much time unfortunately to work on that ... moreover there
are some troubles with tikiwiki and some weired characters in the pages
such that I cannot save the pages anymore. If someone has an idea ?
Finally ... I already asked several times, but I'd like to have the
liste of pages (obtained from the database) that we have in our dev
wiki in order to try to find a better way to organize it. Maybe my
proposition is completly stupid, but what about setting up a new media
wiki for dev (prefixes in db for the tables) and migrate/reorganize in
this new wiki. I'm really pissed against tiki-wiki :S :)
Have a nice week anyway enjoy the sun :D
GrdScarabe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEmHYIPmfsnt4Id3wRAngJAKC5QlM42wM2R/rnDkLFLg6AmdWkLACg3IP4
MpyqyRLEFV7dbaglSQM7Z14=
=N2jV
-END PGP SIGNATURE-
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical
Re: [Amsn-devel] new WIKI
hehe, ok, good job!
btw, I saw some inconsistencies in the page, we had some :
[#|back to top]
and we had some
[[#|back to top]]
I don't know the difference, but it's probably different.. anyways, I
changed all of them into {{top}}
so you can go edit this page :
http://amsn.sourceforge.net/userwiki/index.php?title=Template:Topaction=edit
to change this 'top' template and change all instances of 'back to top'..
also, I made it into :
[[#toc|Back to top]]
I found out that 'toc' is an existing label that refers to the table of
content... we could also use [[#top|Back to top]] where #top also exist
and refers to the top of the page, but not exactly the top, you won't see
the 'discussion' and 'edit' button in the top of the page, you'll be right
before the start of the introductory text.. I figured it's better not to
put that, so I used 'toc' instead of 'top'...
what do others think ?
KKRT
On Wed, 21 Jun 2006 14:15:41 -0400, Philippe Valembois - Phil
[EMAIL PROTECTED] wrote:
Erf...
I just see that many people worked on it since my first edition... And I
saw
too that my log in hasn't been remembered... (I am the one who did the
stub)
Phil
Le Wednesday 21 June 2006 20:10, Philippe Valembois - Phil a écrit :
Hey !
It's me who port that
And it's a shit to port !
It's me who did all the job :p
It's not finished because I hadn't time...
I will try to finish that this evening...
Phil
Le Wednesday 21 June 2006 07:52, Youness Alaoui a écrit :
Hey, wow, I just saw this :
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
For sure it needs a lot of editing, but it's already good this way, it
shouldn't be that difficult to port it after all.
I just want to make a note, I see in the top of the page :
Frequently Asked Questions
Français - Swedish - Spanish (Incomplete) - Danish (Incomplete)
where Francais links to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
_F rench Swedish to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
_S wedish etc...
I would suggest you use mediawiki's internationalization support
instead... I think you only need to add in the end of the page
something
like
{{fr}}
or something like that (refer to the manual, I don't know what it was
exactly), and you'd get a access to a french version of the text...
damn it.. I just tried on kakaroto.homelinux.net/wiki
it doesn't work!
http://en.wikipedia.org/w/index.php?title=SVNaction=edit
I can't understand what it is...
it seems {{ }} means you access a macro (a template), so if we do
{{howto}}
it will be replaced by Template:howto (in red), once we click on it,
we
edit the 'template:howto' page with the content [[Category:How To]]
then the {{howto}} macro will be replaced on the fly by it scontent
([[Category:How to]] instead of the Template:howto)
I found some other examples :
http://www.mediawiki.org/wiki/Help:FAQ
Edit it and look at the end... you see the {{Lang:FAQ}} ? now look at
the
last part of that link I gave...
then look here :
http://www.mediawiki.org/w/index.php?title=Template:Lang:FAQ
But I still don't know where the In other languages on the left
panel
comes from!!!
Maybe it's a setting.. we'll have to look at that...
anyways, that's all for now, we're all happy to know we can have
macros
(templates) with mediawiki! :)
KKRT
On Tue, 20 Jun 2006 18:26:16 -0400, GrdScarabe
[EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philippe Valembois - Phil wrote:
Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit :
btw, this whole thread wasn't about what to put in the new wiki,
it
was about changing links to the old wiki so we can put this new
wiki
as amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the
old
wiki in
amsn.sf.net/devwiki
who's taking care of changing those links ?
I can do it but I would like the FAQ to be moved on the user
WIKI...
Phil
I agree ... the FAQ is really user oriented and this way we will be
able to keep the more technical questions for a developer oriented
FAQ.
The bad news is we cannot convert the FAQ from tikiwiki format to
mediawiki format (except if some filters exist somewhere ... I doubt
it). In this case, it would be in my opinion, a good thing to split
the
FAQ. At least in categories :
- general FAQ
- technical FAQ
- Windows specific
- Linux specific
- Mac specific
because our FAQ is too big, it is difficult to make it clear with so
much information.
I don't have much time unfortunately to work on that ... moreover
there
are some troubles with tikiwiki and some weired characters in the
pages
such that I cannot save the pages anymore. If someone has an idea ?
Finally ... I already asked several times, but I'd like to have
Re: [Amsn-devel] new WIKI
Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit : btw, this whole thread wasn't about what to put in the new wiki, it was about changing links to the old wiki so we can put this new wiki as amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the old wiki in amsn.sf.net/devwiki who's taking care of changing those links ? I can do it but I would like the FAQ to be moved on the user WIKI... Phil KKRT On Mon, 19 Jun 2006 04:03:33 -0400, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] On Mon, 19 Jun 2006 01:41:53 -0400, NoWhereMan [EMAIL PROTECTED] wrote: I used apt as an example because a) I'm good with Ubuntu :P b) on another distro that would have been quite the same, excepted gentoo, I think; but if you can run Gentoo, then you can figure it out yourself ;) no judgement here, I also use apt :P sure, sure, this answer was for Max That's not a bad idea, but I wouldn't want that modularization became fragmentation. I agree with you, I'm also worried about fragmentation, which is why we need to find the best balance, fragmentation vs. modularity, try to do something in the middle. Ok :) me too, on the forums for example, on irc, on msn.. but for a 'guide', it should stay official/professional! sometimes small things could still be allowed to make the article less boring, but it shouldn't be too much ;) I'll force myself being less stupid :D (that'll be hard) Actually the Dev_Packages (typo: capital P, fixed) link tells him how to install *build dependencies* for tcl/tk8.4 but you're right I was not clear, there no, what I meant is that there are no build dependencies!!! so no need to talk about build-dep, it only makes the whole thing more complicated.. there is no dependency (apart from libc and xlibs as mentioned below, but those should be on any system!!! ) oh. I don't know, I did that long ago, so I don't remember what had been installed for Ubuntu (standard installation is quite light, there's not even gcc, you know...) is xft-dev required? I'm not sure... no idea, ask in #tcl channel maybe... stupid question; I already got the answer myself and forgot to remove it form the mail :P it's needed. bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philippe Valembois - Phil wrote: Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit : btw, this whole thread wasn't about what to put in the new wiki, it was about changing links to the old wiki so we can put this new wiki as amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the old wiki in amsn.sf.net/devwiki who's taking care of changing those links ? I can do it but I would like the FAQ to be moved on the user WIKI... Phil I agree ... the FAQ is really user oriented and this way we will be able to keep the more technical questions for a developer oriented FAQ. The bad news is we cannot convert the FAQ from tikiwiki format to mediawiki format (except if some filters exist somewhere ... I doubt it). In this case, it would be in my opinion, a good thing to split the FAQ. At least in categories : - general FAQ - technical FAQ - Windows specific - Linux specific - Mac specific because our FAQ is too big, it is difficult to make it clear with so much information. I don't have much time unfortunately to work on that ... moreover there are some troubles with tikiwiki and some weired characters in the pages such that I cannot save the pages anymore. If someone has an idea ? Finally ... I already asked several times, but I'd like to have the liste of pages (obtained from the database) that we have in our dev wiki in order to try to find a better way to organize it. Maybe my proposition is completly stupid, but what about setting up a new media wiki for dev (prefixes in db for the tables) and migrate/reorganize in this new wiki. I'm really pissed against tiki-wiki :S :) Have a nice week anyway enjoy the sun :D GrdScarabe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEmHYIPmfsnt4Id3wRAngJAKC5QlM42wM2R/rnDkLFLg6AmdWkLACg3IP4 MpyqyRLEFV7dbaglSQM7Z14= =N2jV -END PGP SIGNATURE- ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Hey, wow, I just saw this :
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions
For sure it needs a lot of editing, but it's already good this way, it
shouldn't be that difficult to port it after all.
I just want to make a note, I see in the top of the page :
Frequently Asked Questions
Français - Swedish - Spanish (Incomplete) - Danish (Incomplete)
where Francais links to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions_French
Swedish to
http://amsn.sourceforge.net/userwiki/index.php/Frequently_Asked_Questions_Swedish
etc...
I would suggest you use mediawiki's internationalization support
instead... I think you only need to add in the end of the page something
like
{{fr}}
or something like that (refer to the manual, I don't know what it was
exactly), and you'd get a access to a french version of the text...
damn it.. I just tried on kakaroto.homelinux.net/wiki
it doesn't work!
http://en.wikipedia.org/w/index.php?title=SVNaction=edit
I can't understand what it is...
it seems {{ }} means you access a macro (a template), so if we do
{{howto}}
it will be replaced by Template:howto (in red), once we click on it, we
edit the 'template:howto' page with the content [[Category:How To]] then
the {{howto}} macro will be replaced on the fly by it scontent
([[Category:How to]] instead of the Template:howto)
I found some other examples :
http://www.mediawiki.org/wiki/Help:FAQ
Edit it and look at the end... you see the {{Lang:FAQ}} ? now look at the
last part of that link I gave...
then look here :
http://www.mediawiki.org/w/index.php?title=Template:Lang:FAQ
But I still don't know where the In other languages on the left panel
comes from!!!
Maybe it's a setting.. we'll have to look at that...
anyways, that's all for now, we're all happy to know we can have macros
(templates) with mediawiki! :)
KKRT
On Tue, 20 Jun 2006 18:26:16 -0400, GrdScarabe [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philippe Valembois - Phil wrote:
Le Tuesday 20 June 2006 16:28, Youness Alaoui a écrit :
btw, this whole thread wasn't about what to put in the new wiki, it was
about changing links to the old wiki so we can put this new wiki as
amsn.sf.net/wiki instead of amsn.sf.net/userwiki and have the old wiki
in
amsn.sf.net/devwiki
who's taking care of changing those links ?
I can do it but I would like the FAQ to be moved on the user WIKI...
Phil
I agree ... the FAQ is really user oriented and this way we will be able
to keep the more technical questions for a developer oriented FAQ.
The bad news is we cannot convert the FAQ from tikiwiki format to
mediawiki format (except if some filters exist somewhere ... I doubt
it). In this case, it would be in my opinion, a good thing to split the
FAQ. At least in categories :
- general FAQ
- technical FAQ
- Windows specific
- Linux specific
- Mac specific
because our FAQ is too big, it is difficult to make it clear with so
much information.
I don't have much time unfortunately to work on that ... moreover there
are some troubles with tikiwiki and some weired characters in the pages
such that I cannot save the pages anymore. If someone has an idea ?
Finally ... I already asked several times, but I'd like to have the
liste of pages (obtained from the database) that we have in our dev wiki
in order to try to find a better way to organize it. Maybe my
proposition is completly stupid, but what about setting up a new media
wiki for dev (prefixes in db for the tables) and migrate/reorganize in
this new wiki. I'm really pissed against tiki-wiki :S :)
Have a nice week anyway enjoy the sun :D
GrdScarabe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEmHYIPmfsnt4Id3wRAngJAKC5QlM42wM2R/rnDkLFLg6AmdWkLACg3IP4
MpyqyRLEFV7dbaglSQM7Z14=
=N2jV
-END PGP SIGNATURE-
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
On Mon, 19 Jun 2006 01:41:53 -0400, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] yes, I agree, but what is simpler for the users : do 'apt-get install tcl8.4-dev tk8.4-dev' or go to this link http://debian.org/ and read about it to download tcl/tk dev packages Yes, I used apt as an example because a) I'm good with Ubuntu :P b) on another distro that would have been quite the same, excepted gentoo, I think; but if you can run Gentoo, then you can figure it out yourself ;) no judgement here, I also use apt :P but what I meant by the above is that, yes, we must give the commands to the users instead of just redirecting them to the guide for their packaging system... I think we should keep it modular as I said, yes, make it universal, but that's why article based is so great, you give generic instructions, with the 'install tcl/tk dev packages' being a link to another article that would explain how to do it per platform, That's not a bad idea, but I wouldn't want that modularization became fragmentation. If you can keep the most you can in the same article user would be less puzzled. Moreover he can see *how many* commands are needed to do what he wants I agree with you, I'm also worried about fragmentation, which is why we need to find the best balance, fragmentation vs. modularity, try to do something in the middle. or itself be a dispatch article that would dispatch you to the appropriate article for you distro... http://amsn.sourceforge.net/userwiki/index.php/Enabling_antialiasing -- many things to improve ? commands are with --enable-64bit ? I'm not on 64 bits, but that works ok, btw I took the commands from the guide I linked at the top of the page, compiling that way I never had problems... cool many typos... huh :P :P the '(yes, I copypasted here :p)' in Downloading Tk, might confuse some people into thinking they have to copy paste with 'nameofpackage.tar.gz' or something.. try to make it look professional, not 'familial'... huh. I like putting stupid comments :D me too, on the forums for example, on irc, on msn.. but for a 'guide', it should stay official/professional! sometimes small things could still be allowed to make the article less boring, but it shouldn't be too much ;) for the prerequesites, you say you need to install the dev packages for tcl/tk 8.4, but it's not true, if the user follows the link, he'll install dev packages OF tcl/tk 8.4, while he only needs the dependencies... Actually the Dev_Packages (typo: capital P, fixed) link tells him how to install *build dependencies* for tcl/tk8.4 but you're right I was not clear, there if the user follows the link, he might think he needs to read it all... that's what I mean by confusion... the best way to do it is to use 'apt-cache show tk8.4' and see what ARE those dependencies.. in Dev_Packages he's told to use build-dep, which will install all the build dependencies without any effort :) no, what I meant is that there are no build dependencies!!! so no need to talk about build-dep, it only makes the whole thing more complicated.. there is no dependency (apart from libc and xlibs as mentioned below, but those should be on any system!!! ) you'll see it's only libc, and xlibs (or libx11), so you could be pretty sure, there is no dependency, so this whole thing could be removed, leave only the xft thing, and as we just said above, make it 'Prerequisites' and 'you need to install xlibs and xft-dev' which would link to a how to install xft-dev... is xft-dev required? I'm not sure... no idea, ask in #tcl channel maybe... you talk about 'launching amsn with its usual name, amsn, will give you a segfault'... first, you don't need to say that... it makes our reputation bad... Well, that's what happens :D I didn't explain *why* this happens, which is quite normal; that could be completed explaining it's not a bad behaviour, just a consequence of binding amsn to tcl8.5 (I'm right here, aren't I?) I don't think it gives you a bad reputation; it just makes things clear. Moreover, when a user says oh, I have a segfault maybe he'll remember of the guide and will see he's forgot something... Anyway, if you really dislike it, just remove it ;) well, you could say might crash instead of segfault.. + most of the users who had this issue on the forums say that amsn never opens, not that it shows segfault.. rare are those who use the console... unfortunately :( secondly, I may have found a way to avoid this segfault.. I'm still testing it.. Well, once you have, we can safely remove the whole segfault thing... it's done! follow the ML, I announced it already (with a Added/Removed on it in the 0.96 TODO thread) this means it can be removed! :) bye :) ___ Amsn-devel mailing list
Re: [Amsn-devel] new WIKI
- Original Message - From: Youness Alaoui [EMAIL PROTECTED] On Mon, 19 Jun 2006 01:41:53 -0400, NoWhereMan [EMAIL PROTECTED] wrote: I used apt as an example because a) I'm good with Ubuntu :P b) on another distro that would have been quite the same, excepted gentoo, I think; but if you can run Gentoo, then you can figure it out yourself ;) no judgement here, I also use apt :P sure, sure, this answer was for Max That's not a bad idea, but I wouldn't want that modularization became fragmentation. I agree with you, I'm also worried about fragmentation, which is why we need to find the best balance, fragmentation vs. modularity, try to do something in the middle. Ok :) me too, on the forums for example, on irc, on msn.. but for a 'guide', it should stay official/professional! sometimes small things could still be allowed to make the article less boring, but it shouldn't be too much ;) I'll force myself being less stupid :D (that'll be hard) Actually the Dev_Packages (typo: capital P, fixed) link tells him how to install *build dependencies* for tcl/tk8.4 but you're right I was not clear, there no, what I meant is that there are no build dependencies!!! so no need to talk about build-dep, it only makes the whole thing more complicated.. there is no dependency (apart from libc and xlibs as mentioned below, but those should be on any system!!! ) oh. I don't know, I did that long ago, so I don't remember what had been installed for Ubuntu (standard installation is quite light, there's not even gcc, you know...) is xft-dev required? I'm not sure... no idea, ask in #tcl channel maybe... stupid question; I already got the answer myself and forgot to remove it form the mail :P it's needed. bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Humm.. I tried using the amsn display picture, resized to 135x135.. doesn't look that nice, but still better than the flower they had by default :P oh yeah, and btw.. Tom.. Lee.. if you create a logo for the wiki, it must be 135x135... KKRT On Sun, 18 Jun 2006 04:08:03 -0400, Youness Alaoui [EMAIL PROTECTED] wrote: Hi All, As it was discussed in here : http://amsn.sourceforge.net/forums/viewtopic.php?t=1177 A new WIKI for the users has been created. This means that we need to update all our links, the website link to the wiki, the redirect in faq.php, etc... What I did for now is move the current wiki (that we'll still use) to devwiki and have the new one in userwiki... now let me explain it better : the tikiwiki that we currently use will be kept for developers only, where only the developers can edit pages, its new URL will be http://amsn.sf.net/devwiki the mediawiki that I've just set up (same wiki as wikipedia) will be used and maintained by our users. It will mainly contain explanations on how to do stuff, which means that we'll have an article for almost anything we can think of, so no more search the forums, it will be a search the wiki which our super-power users (Elias, NoWhereMan, and soon Gus-Arg and Fenix-TX) will be able to answer.. Elias and NWM are ready to rewrite most of the things already answered, and we'll be able to have a real, huge FAQ where everyone can help, article-based, where our users will feel confortable! :) Now, that new wiki has been placed in http://amsn.sf.net/userwiki as you can see from http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url we can have a shorter name for the wiki, which means instead of having http://amsn.sf.net/wiki/index.php?title=Tcl we could have http://amsn.sf.net/wiki/Tcl for this, we need two dirs, one for the actual wiki, the other for the rewrite rule, which is why the wiki has been placed in htdocs/userwiki so the rewrite rule will rewrite /wiki into /userwiki Now, I didn't want to screw up our current system, so the htdocs/.htaccess file contains a rewrite rule for : http://amsn.sf.net/userwiki_short so, once everything has been set up, we'll just modify the .htaccess and put it into wiki/ remove the symlink from wiki/ to devwiki/ and we'll need to modify the wiki's article path so it doesn't get rewritten into userwiki/index.php?title= Now, if you'll notice, we have 3 new symlinks, the htdocs/wiki/ - htdocs/devwiki htdocs/userwiki/ -/tmp/persistent/amsn/mediawiki-1.6.7 wiki_sessions/ - /tmp/persistent/amsn/mediawiki-1.6.7/sessions the wiki_sessions symlinks are normal, I made them so we can actually log on and log out of the wiki (maybe that's why we can't log into tikiwki without the remember me option... the web server can't write the session files) but the other odd thing you'll find is that I made the whole mediawiki installation into /tmp/persistent instead of puttin it into /home/groups/a/am/amsn/htdocs and that's not because of a read/write permission issue, it's only because it allowed us to save 11MB of space from our 100MB limit on /home/groups/a/am/amsn :p so, in case you're lost, you know that the file's you're looking for are in /tmp/persistent/amsn/mediawiki-1.6.7 I made sure everyone has write permissions... btw, I kept the -1.6.7 in the dirname so we can easily know which version is installed and whether we need to upgrade... I also subscribed to the mediwiki release mailing list, so we should be fine... As you can see, as soon as you go into that new wiki.. we need a new logo so if Tom or Lee can make us a real nice logo that would blend in with the wiki (I tried to crop the logos we have on the website but the blue background makes it not blend at all), that would be terrific. Tell me when you've done the changes. Thanks! -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
I made one just based on the amsn web logo, can be changed if people want, seems to work quite nicely though :) Tom On 6/18/06, Youness Alaoui [EMAIL PROTECTED] wrote: Humm.. I tried using the amsn display picture, resized to 135x135.. doesn't look that nice, but still better than the flower they had by default :P oh yeah, and btw.. Tom.. Lee.. if you create a logo for the wiki, it must be 135x135... KKRT On Sun, 18 Jun 2006 04:08:03 -0400, Youness Alaoui [EMAIL PROTECTED] wrote: Hi All, As it was discussed in here : http://amsn.sourceforge.net/forums/viewtopic.php?t=1177 A new WIKI for the users has been created. This means that we need to update all our links, the website link to the wiki, the redirect in faq.php, etc... What I did for now is move the current wiki (that we'll still use) to devwiki and have the new one in userwiki... now let me explain it better : the tikiwiki that we currently use will be kept for developers only, where only the developers can edit pages, its new URL will be http://amsn.sf.net/devwiki the mediawiki that I've just set up (same wiki as wikipedia) will be used and maintained by our users. It will mainly contain explanations on how to do stuff, which means that we'll have an article for almost anything we can think of, so no more search the forums, it will be a search the wiki which our super-power users (Elias, NoWhereMan, and soon Gus-Arg and Fenix-TX) will be able to answer.. Elias and NWM are ready to rewrite most of the things already answered, and we'll be able to have a real, huge FAQ where everyone can help, article-based, where our users will feel confortable! :) Now, that new wiki has been placed in http://amsn.sf.net/userwiki as you can see from http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url we can have a shorter name for the wiki, which means instead of having http://amsn.sf.net/wiki/index.php?title=Tcl we could have http://amsn.sf.net/wiki/Tcl for this, we need two dirs, one for the actual wiki, the other for the rewrite rule, which is why the wiki has been placed in htdocs/userwiki so the rewrite rule will rewrite /wiki into /userwiki Now, I didn't want to screw up our current system, so the htdocs/.htaccess file contains a rewrite rule for : http://amsn.sf.net/userwiki_short so, once everything has been set up, we'll just modify the .htaccess and put it into wiki/ remove the symlink from wiki/ to devwiki/ and we'll need to modify the wiki's article path so it doesn't get rewritten into userwiki/index.php?title= Now, if you'll notice, we have 3 new symlinks, the htdocs/wiki/ - htdocs/devwiki htdocs/userwiki/ -/tmp/persistent/amsn/mediawiki-1.6.7 wiki_sessions/ - /tmp/persistent/amsn/mediawiki-1.6.7/sessions the wiki_sessions symlinks are normal, I made them so we can actually log on and log out of the wiki (maybe that's why we can't log into tikiwki without the remember me option... the web server can't write the session files) but the other odd thing you'll find is that I made the whole mediawiki installation into /tmp/persistent instead of puttin it into /home/groups/a/am/amsn/htdocs and that's not because of a read/write permission issue, it's only because it allowed us to save 11MB of space from our 100MB limit on /home/groups/a/am/amsn :p so, in case you're lost, you know that the file's you're looking for are in /tmp/persistent/amsn/mediawiki-1.6.7 I made sure everyone has write permissions... btw, I kept the -1.6.7 in the dirname so we can easily know which version is installed and whether we need to upgrade... I also subscribed to the mediwiki release mailing list, so we should be fine... As you can see, as soon as you go into that new wiki.. we need a new logo so if Tom or Lee can make us a real nice logo that would blend in with the wiki (I tried to crop the logos we have on the website but the blue background makes it not blend at all), that would be terrific. Tell me when you've done the changes. Thanks! -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
looks extremely nice, thanks ! :) On Sun, 18 Jun 2006 05:59:25 -0400, [EMAIL PROTECTED] wrote: I made one just based on the amsn web logo, can be changed if people want, seems to work quite nicely though :) Tom On 6/18/06, Youness Alaoui [EMAIL PROTECTED] wrote: Humm.. I tried using the amsn display picture, resized to 135x135.. doesn't look that nice, but still better than the flower they had by default :P oh yeah, and btw.. Tom.. Lee.. if you create a logo for the wiki, it must be 135x135... KKRT On Sun, 18 Jun 2006 04:08:03 -0400, Youness Alaoui [EMAIL PROTECTED] wrote: Hi All, As it was discussed in here : http://amsn.sourceforge.net/forums/viewtopic.php?t=1177 A new WIKI for the users has been created. This means that we need to update all our links, the website link to the wiki, the redirect in faq.php, etc... What I did for now is move the current wiki (that we'll still use) to devwiki and have the new one in userwiki... now let me explain it better : the tikiwiki that we currently use will be kept for developers only, where only the developers can edit pages, its new URL will be http://amsn.sf.net/devwiki the mediawiki that I've just set up (same wiki as wikipedia) will be used and maintained by our users. It will mainly contain explanations on how to do stuff, which means that we'll have an article for almost anything we can think of, so no more search the forums, it will be a search the wiki which our super-power users (Elias, NoWhereMan, and soon Gus-Arg and Fenix-TX) will be able to answer.. Elias and NWM are ready to rewrite most of the things already answered, and we'll be able to have a real, huge FAQ where everyone can help, article-based, where our users will feel confortable! :) Now, that new wiki has been placed in http://amsn.sf.net/userwiki as you can see from http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url we can have a shorter name for the wiki, which means instead of having http://amsn.sf.net/wiki/index.php?title=Tcl we could have http://amsn.sf.net/wiki/Tcl for this, we need two dirs, one for the actual wiki, the other for the rewrite rule, which is why the wiki has been placed in htdocs/userwiki so the rewrite rule will rewrite /wiki into /userwiki Now, I didn't want to screw up our current system, so the htdocs/.htaccess file contains a rewrite rule for : http://amsn.sf.net/userwiki_short so, once everything has been set up, we'll just modify the .htaccess and put it into wiki/ remove the symlink from wiki/ to devwiki/ and we'll need to modify the wiki's article path so it doesn't get rewritten into userwiki/index.php?title= Now, if you'll notice, we have 3 new symlinks, the htdocs/wiki/ - htdocs/devwiki htdocs/userwiki/ -/tmp/persistent/amsn/mediawiki-1.6.7 wiki_sessions/ - /tmp/persistent/amsn/mediawiki-1.6.7/sessions the wiki_sessions symlinks are normal, I made them so we can actually log on and log out of the wiki (maybe that's why we can't log into tikiwki without the remember me option... the web server can't write the session files) but the other odd thing you'll find is that I made the whole mediawiki installation into /tmp/persistent instead of puttin it into /home/groups/a/am/amsn/htdocs and that's not because of a read/write permission issue, it's only because it allowed us to save 11MB of space from our 100MB limit on /home/groups/a/am/amsn :p so, in case you're lost, you know that the file's you're looking for are in /tmp/persistent/amsn/mediawiki-1.6.7 I made sure everyone has write permissions... btw, I kept the -1.6.7 in the dirname so we can easily know which version is installed and whether we need to upgrade... I also subscribed to the mediwiki release mailing list, so we should be fine... As you can see, as soon as you go into that new wiki.. we need a new logo so if Tom or Lee can make us a real nice logo that would blend in with the wiki (I tried to crop the logos we have on the website but the blue background makes it not blend at all), that would be terrific. Tell me when you've done the changes. Thanks! -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
- Original Message - From: Youness Alaoui [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 12:24 PM Subject: Re: [Amsn-devel] new WIKI great! very good! :) I like the 'install svn' article, well done. [...] also, in the install SVN version, it would be best to just say how to do it, download, compile, install, launch... the You should now compile aMSN could link to an article on how to compile... it reminds me of programming, it has to be modular! :) but great work already! :) well, yes :) anyway, that's the text, it can be now splitted, teared into pieces, etc, etc :D as you like it :) bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Just noticed you've written aMsn throughout your articlesisn't the capitlisation aMSN? Or am I remembering wrong? :) Tom On 6/18/06, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 12:24 PM Subject: Re: [Amsn-devel] new WIKI great! very good! :) I like the 'install svn' article, well done. [...] also, in the install SVN version, it would be best to just say how to do it, download, compile, install, launch... the You should now compile aMSN could link to an article on how to compile... it reminds me of programming, it has to be modular! :) but great work already! :) well, yes :) anyway, that's the text, it can be now splitted, teared into pieces, etc, etc :D as you like it :) bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
You remember wrong :p (In fact you are right but I prefer aMsn :d) Phil Le Sunday 18 June 2006 12:37, [EMAIL PROTECTED] a écrit : Just noticed you've written aMsn throughout your articlesisn't the capitlisation aMSN? Or am I remembering wrong? :) Tom On 6/18/06, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 12:24 PM Subject: Re: [Amsn-devel] new WIKI great! very good! :) I like the 'install svn' article, well done. [...] also, in the install SVN version, it would be best to just say how to do it, download, compile, install, launch... the You should now compile aMSN could link to an article on how to compile... it reminds me of programming, it has to be modular! :) but great work already! :) well, yes :) anyway, that's the text, it can be now splitted, teared into pieces, etc, etc :D as you like it :) bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Hehe, I think Amsn looks ugly :P But that's probably because I'm english ;) btw,, NWM: I forgot to congratulate you on getting the wiki articles started! And I wasn't aware of the contribution you and Elias were making to the forums (I'm hardly ever on there now), so congrats on that too! Tom On 6/18/06, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: You remember wrong :p (In fact you are right but I prefer aMsn :d) Phil Le Sunday 18 June 2006 12:37, [EMAIL PROTECTED] a écrit: Just noticed you've written aMsn throughout your articlesisn't the capitlisation aMSN? Or am I remembering wrong? :) Tom On 6/18/06, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 12:24 PM Subject: Re: [Amsn-devel] new WIKI great! very good! :) I like the 'install svn' article, well done. [...] also, in the install SVN version, it would be best to just say how to do it, download, compile, install, launch... the You should now compile aMSN could link to an article on how to compile... it reminds me of programming, it has to be modular! :) but great work already! :) well, yes :) anyway, that's the text, it can be now splitted, teared into pieces, etc, etc :D as you like it :) bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
- Original Message - From: [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 12:42 PM Subject: Re: [Amsn-devel] new WIKI Hehe, I think Amsn looks ugly :P But that's probably because I'm english ;) btw,, NWM: I forgot to congratulate you on getting the wiki articles started! ehe, thanx :) And I wasn't aware of the contribution you and Elias were making to the forums (I'm hardly ever on there now), so congrats on that too! :) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
- Original Message - From: Philippe Valembois - Phil [EMAIL PROTECTED] You remember wrong :p (In fact you are right but I prefer aMsn :d) Lol, same for me :D ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
On Sun, 18 Jun 2006 06:28:27 -0400, [EMAIL PROTECTED] wrote: On 6/18/06, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 11:59 AM Subject: Re: [Amsn-devel] new WIKI I made one just based on the amsn web logo, can be changed if people want, seems to work quite nicely though :) Nice! I've already added a pair of articles :P Need to edit the main page to make a contents/index :) is it needed ? people can 'search' for stuff.. do you think people go through the index in wikipedia ? bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
On 6/18/06, Youness Alaoui [EMAIL PROTECTED] wrote: On Sun, 18 Jun 2006 06:28:27 -0400, [EMAIL PROTECTED] wrote: On 6/18/06, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 11:59 AM Subject: Re: [Amsn-devel] new WIKI I made one just based on the amsn web logo, can be changed if people want, seems to work quite nicely though :) Nice! I've already added a pair of articles :P Need to edit the main page to make a contents/index :) is it needed ? people can 'search' for stuff.. do you think people go through the index in wikipedia ? It might just be nice to havea friendly front. :) I'll do it anyway. BTW, I noticed file uploads are disabled... people might need to use screenshots etc, is there some way fo doing this without letting evrey Tom Dick and Harry upload crap? bye ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Just a thought, is there any chance the devwiki could be migrated to mediawiki at some point (I'd be willing to help) I dislike tiki-wiki... and mediawiki is so nice :) Tom On 6/18/06, Youness Alaoui [EMAIL PROTECTED] wrote: Hi All, As it was discussed in here : http://amsn.sourceforge.net/forums/viewtopic.php?t=1177 A new WIKI for the users has been created. This means that we need to update all our links, the website link to the wiki, the redirect in faq.php, etc... What I did for now is move the current wiki (that we'll still use) to devwiki and have the new one in userwiki... now let me explain it better : the tikiwiki that we currently use will be kept for developers only, where only the developers can edit pages, its new URL will be http://amsn.sf.net/devwiki the mediawiki that I've just set up (same wiki as wikipedia) will be used and maintained by our users. It will mainly contain explanations on how to do stuff, which means that we'll have an article for almost anything we can think of, so no more search the forums, it will be a search the wiki which our super-power users (Elias, NoWhereMan, and soon Gus-Arg and Fenix-TX) will be able to answer.. Elias and NWM are ready to rewrite most of the things already answered, and we'll be able to have a real, huge FAQ where everyone can help, article-based, where our users will feel confortable! :) Now, that new wiki has been placed in http://amsn.sf.net/userwiki as you can see from http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url we can have a shorter name for the wiki, which means instead of having http://amsn.sf.net/wiki/index.php?title=Tcl we could have http://amsn.sf.net/wiki/Tcl for this, we need two dirs, one for the actual wiki, the other for the rewrite rule, which is why the wiki has been placed in htdocs/userwiki so the rewrite rule will rewrite /wiki into /userwiki Now, I didn't want to screw up our current system, so the htdocs/.htaccess file contains a rewrite rule for : http://amsn.sf.net/userwiki_short so, once everything has been set up, we'll just modify the .htaccess and put it into wiki/ remove the symlink from wiki/ to devwiki/ and we'll need to modify the wiki's article path so it doesn't get rewritten into userwiki/index.php?title= Now, if you'll notice, we have 3 new symlinks, the htdocs/wiki/ - htdocs/devwiki htdocs/userwiki/ -/tmp/persistent/amsn/mediawiki-1.6.7 wiki_sessions/ - /tmp/persistent/amsn/mediawiki-1.6.7/sessions the wiki_sessions symlinks are normal, I made them so we can actually log on and log out of the wiki (maybe that's why we can't log into tikiwki without the remember me option... the web server can't write the session files) but the other odd thing you'll find is that I made the whole mediawiki installation into /tmp/persistent instead of puttin it into /home/groups/a/am/amsn/htdocs and that's not because of a read/write permission issue, it's only because it allowed us to save 11MB of space from our 100MB limit on /home/groups/a/am/amsn :p so, in case you're lost, you know that the file's you're looking for are in /tmp/persistent/amsn/mediawiki-1.6.7 I made sure everyone has write permissions... btw, I kept the -1.6.7 in the dirname so we can easily know which version is installed and whether we need to upgrade... I also subscribed to the mediwiki release mailing list, so we should be fine... As you can see, as soon as you go into that new wiki.. we need a new logo so if Tom or Lee can make us a real nice logo that would blend in with the wiki (I tried to crop the logos we have on the website but the blue background makes it not blend at all), that would be terrific. Tell me when you've done the changes. Thanks! -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
- Original Message - From: [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 2:10 PM Subject: Re: [Amsn-devel] new WIKI Just a thought, is there any chance the devwiki could be migrated to mediawiki at some point (I'd be willing to help) I dislike tiki-wiki... and mediawiki is so nice :) yes, I think that would be nice too... actually I don't see reasons for them to be splitted (safety? you can lock pages if you want) bye :) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
Op zondag 18 juni 2006 21:25, schreef Youness Alaoui: Humm.. I'm not sure, I also dislike tikiwiki but do we really want to redo all that work and migrate from one to another ? the syntax is not the same for one thing... also, developer stuff should be kept under developer access only, so we can use our tiki accounts to edit those pages... in mediawiki we can only say protect from unregistered or protect from unregistered and non-sysops... so what if we want to give the rights to some developers without giving them sysop status... anyways, I'd prefer devels to have their 'own space', where noone could bother us.. where we could write about amsn2 without getting tons of mails/reports/forum threads/edits of wiki/ asking ohh, I just read about amsn2, why not use this or this language instead or people knowing nothing trying to give their 'ideas' KKRT And what about the other way around? Just normal users would probably get lost in a wiki full of technical developer information. So giving them their own wiki where the information they need (how-to-use amsn) is is just perfect for them. Also, the userwiki will probably be a lot more helpful to our users than the forums, because looking for something in the forums is really searching for a needle in a haystack (even I usually can't find what I'm looking for, even if I KNOW it is somewhere in there!), and the wiki should have clear overview pages that guide the users to their information. So yes, there are reasons enough to have a devwiki and a userwiki. Also, I agree that moving the devwiki from tikiwiki to mediawiki would be a lot of work, and thus would take a lot of time that we can spend a better way. So, just keep it a tikiwiki for us. Harry On Sun, 18 Jun 2006 09:21:31 -0400, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] To: Mailing list for developers and everyone helping AMSN amsn-devel@lists.sourceforge.net Sent: Sunday, June 18, 2006 2:10 PM Subject: Re: [Amsn-devel] new WIKI Just a thought, is there any chance the devwiki could be migrated to mediawiki at some point (I'd be willing to help) I dislike tiki-wiki... and mediawiki is so nice :) yes, I think that would be nice too... actually I don't see reasons for them to be splitted (safety? you can lock pages if you want) bye :) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
On Sun, 18 Jun 2006 15:37:35 -0400, NoWhereMan [EMAIL PROTECTED] wrote: - Original Message - From: Youness Alaoui [EMAIL PROTECTED] anyways, I'd prefer devels to have their 'own space', where noone could bother us.. where we could write about amsn2 without getting tons of mails/reports/forum threads/edits of wiki/ asking ohh, I just read about amsn2, why not use this or this language instead are you thinking about someone in particular, here? :D not someone.. something... I know there were lengthy, annoying discussions on languages, but I'm too old to remember who said what (I also rarely see and remember who wrote an email, I'm only interested in its content).. so just to be clear, I'm not targetting anyone here! anyway, I see your point; I saw there was an hack to add user levels to mediawiki... but it was an hack... I prefer to avoid hacks for now, if the hack was good it would have been incorporated into the trunk/ no? an open to edit discussion function as seen in mediawiki would have been interesting, thought what ? bye :) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
I just would like to comment what i saw on the wiki... haden't time to contribute, my familly meeting turned into a business meeting in which i was both involved and interested (i now i got a new job :p) so i didn't had time to contribute : - we should use the category feature of mediawiki. To put an article in a category, simply add [[Category:Name]] at the end of the page.- we shouldn't make distro specific instructions : for example the how to remove tcl/tk with debian shoud be, imho, remove tcl/tk packages and distro specific links (internal or external) on how to use package management. We have to keep the wiki universal. If we go too much in specific details, we are going to miss some of the users (not every one is using debian and we cannot explain how to use apt-get/pacman/emerge/uprmi/yast/rpm and so on...)my 2 cents ! -- Maxime VERZIER (www.billets-orientes.com / www.verzier.info) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
On Sun, 18 Jun 2006 17:11:50 -0400, Max [EMAIL PROTECTED] wrote: I just would like to comment what i saw on the wiki... haden't time to contribute, my familly meeting turned into a business meeting in which i was both involved and interested (i now i got a new job :p) so i didn't had time to contribute : congrats - we should use the category feature of mediawiki. To put an article in a category, simply add [[Category:Name]] at the end of the page. sure, good idea.. I saw you or NWM on the test mediawiki I've set up, put a [[Category::How To]] in one of the pages... - we shouldn't make distro specific instructions : for example the how to remove tcl/tk with debian shoud be, imho, remove tcl/tk packages and distro specific links (internal or external) on how to use package management. We have to keep the wiki universal. If we go too much in specific details, we are going to miss some of the users (not every one is using debian and we cannot explain how to use apt-get/pacman/emerge/uprmi/yast/rpm and so on...) my 2 cents ! yes, I agree, but what is simpler for the users : do 'apt-get install tcl8.4-dev tk8.4-dev' or go to this link http://debian.org/ and read about it to download tcl/tk dev packages which would mean read pages and pages about apt-get, then how to search for tcl/tk devel packages using apt-cache, then do an apt-get on it, then try to figure out why it says tk-dev and tcl-dev are not real packages, only references, then they'll have to figure out that it was actually tk8.4-dev and tcl8.4-dev, etc... I think we should keep it modular as I said, yes, make it universal, but that's why article based is so great, you give generic instructions, with the 'install tcl/tk dev packages' being a link to another article that would explain how to do it per platform, or itself be a dispatch article that would dispatch you to the appropriate article for you distro... http://amsn.sourceforge.net/userwiki/index.php/Enabling_antialiasing -- many things to improve ? commands are with --enable-64bit ? many typos... the '(yes, I copypasted here :p)' in Downloading Tk, might confuse some people into thinking they have to copy paste with 'nameofpackage.tar.gz' or something.. try to make it look professional, not 'familial'... for the prerequesites, you say you need to install the dev packages for tcl/tk 8.4, but it's not true, if the user follows the link, he'll install dev packages OF tcl/tk 8.4, while he only needs the dependencies... the best way to do it is to use 'apt-cache show tk8.4' and see what ARE those dependencies.. you'll see it's only libc, and xlibs (or libx11), so you could be pretty sure, there is no dependency, so this whole thing could be removed, leave only the xft thing, and as we just said above, make it 'Prerequisites' and 'you need to install xlibs and xft-dev' which would link to a how to install xft-dev... you talk about 'launching amsn with its usual name, amsn, will give you a segfault'... first, you don't need to say that... it makes our reputation bad... secondly, I may have found a way to avoid this segfault.. I'm still testing it.. -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] new WIKI
- Original Message - From: Youness Alaoui [EMAIL PROTECTED] yes, I agree, but what is simpler for the users : do 'apt-get install tcl8.4-dev tk8.4-dev' or go to this link http://debian.org/ and read about it to download tcl/tk dev packages Yes, I used apt as an example because a) I'm good with Ubuntu :P b) on another distro that would have been quite the same, excepted gentoo, I think; but if you can run Gentoo, then you can figure it out yourself ;) I think we should keep it modular as I said, yes, make it universal, but that's why article based is so great, you give generic instructions, with the 'install tcl/tk dev packages' being a link to another article that would explain how to do it per platform, That's not a bad idea, but I wouldn't want that modularization became fragmentation. If you can keep the most you can in the same article user would be less puzzled. Moreover he can see *how many* commands are needed to do what he wants or itself be a dispatch article that would dispatch you to the appropriate article for you distro... http://amsn.sourceforge.net/userwiki/index.php/Enabling_antialiasing -- many things to improve ? commands are with --enable-64bit ? I'm not on 64 bits, but that works ok, btw I took the commands from the guide I linked at the top of the page, compiling that way I never had problems... many typos... huh :P the '(yes, I copypasted here :p)' in Downloading Tk, might confuse some people into thinking they have to copy paste with 'nameofpackage.tar.gz' or something.. try to make it look professional, not 'familial'... huh. I like putting stupid comments :D for the prerequesites, you say you need to install the dev packages for tcl/tk 8.4, but it's not true, if the user follows the link, he'll install dev packages OF tcl/tk 8.4, while he only needs the dependencies... Actually the Dev_Packages (typo: capital P, fixed) link tells him how to install *build dependencies* for tcl/tk8.4 but you're right I was not clear, there the best way to do it is to use 'apt-cache show tk8.4' and see what ARE those dependencies.. in Dev_Packages he's told to use build-dep, which will install all the build dependencies without any effort :) you'll see it's only libc, and xlibs (or libx11), so you could be pretty sure, there is no dependency, so this whole thing could be removed, leave only the xft thing, and as we just said above, make it 'Prerequisites' and 'you need to install xlibs and xft-dev' which would link to a how to install xft-dev... is xft-dev required? I'm not sure... you talk about 'launching amsn with its usual name, amsn, will give you a segfault'... first, you don't need to say that... it makes our reputation bad... Well, that's what happens :D I didn't explain *why* this happens, which is quite normal; that could be completed explaining it's not a bad behaviour, just a consequence of binding amsn to tcl8.5 (I'm right here, aren't I?) I don't think it gives you a bad reputation; it just makes things clear. Moreover, when a user says oh, I have a segfault maybe he'll remember of the guide and will see he's forgot something... Anyway, if you really dislike it, just remove it ;) secondly, I may have found a way to avoid this segfault.. I'm still testing it.. Well, once you have, we can safely remove the whole segfault thing... bye :) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
