Thanks so far about the IDE. I will check wheter some trial versions are available.
What strikes me most is the fact that there seems to be no clear strucutre of the software.
Seems that I have to spend some more time before I'll have an overview ;-}
Regards A. Cremer
"Dorozynski Janusz" dorozynskij@wampnm.webd.pl schrieb im Newsbeitrag news:31184.7716141076$1169416870@news.gmane.org...
| -----Original Message----- | From: ... Rolf Lampa | Sent: Sunday, January 21, 2007 8:26 PM / | Zend was already mentioned. Another #1 tool - with integrated (also | remote) debugging included - is Nusphere PhpED, more info here: | | http://www.nusphere.com/products/index.htm
for 390 $
but for 89 euro is phpEdit (http://www.waterproof.fr/) - with debugger, and for personal noncommercial works or education/training anybody can receive special licence for free (http://www.waterproof.fr/products/PHPEdit/buy-personal.php http://www.waterproof.fr/products/PHPEdit/buy-education.php).
Reg., Janusz 'Ency' Dorozynski
We're working on that.
For the database, you can have a look at http://www.mediawiki.org/wiki/Manual:Database_layout, which includes an overview of all the database tables currently used in MediaWiki. I've tried to make sure everything is more-or-less accurate (probably less), but it should be accurate for MW 1.8, 1.9 and 1.10alpha.
As for the class structure, does http://svn.wikimedia.org/doc/ help? I've found it to be useful many times.
Titoxd.
-----Original Message----- From: a. cremer [mailto:albert.cremer@online.de] Sent: Sunday, January 21, 2007 3:32 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] IDE for mediawiki
Thanks so far about the IDE. I will check wheter some trial versions are available.
What strikes me most is the fact that there seems to be no clear strucutre of the software.
Seems that I have to spend some more time before I'll have an overview ;-}
Regards A. Cremer
"Dorozynski Janusz" dorozynskij@wampnm.webd.pl schrieb im Newsbeitrag news:31184.7716141076$1169416870@news.gmane.org...
| -----Original Message----- | From: ... Rolf Lampa | Sent: Sunday, January 21, 2007 8:26 PM / | Zend was already mentioned. Another #1 tool - with integrated (also | remote) debugging included - is Nusphere PhpED, more info here: | | http://www.nusphere.com/products/index.htm
for 390 $
but for 89 euro is phpEdit (http://www.waterproof.fr/) - with debugger, and for personal noncommercial works or education/training anybody can receive special licence for free (http://www.waterproof.fr/products/PHPEdit/buy-personal.php http://www.waterproof.fr/products/PHPEdit/buy-education.php).
Reg., Janusz 'Ency' Dorozynski
On 22/01/07, Titoxd@Wikimedia titoxd.wikimedia@gmail.com wrote:
As for the class structure, does http://svn.wikimedia.org/doc/ help? I've found it to be useful many times.
Note that that URL contains all the generated documentation for the entire repo; to cut out the non-core stuff, do a checkout from trunk and run Doxygen on it yourself, otherwise it can get confusing.
Rob Church
Titoxd@Wikimedia wrote:
<snip>
For the database, you can have a look at http://www.mediawiki.org/wiki/Manual:Database_layout, which includes an overview of all the database tables currently used in MediaWiki. I've tried to make sure everything is more-or-less accurate (probably less), but it should be accurate for MW 1.8, 1.9 and 1.10alpha.
This really is of great help! This could fairly easy be drawn also with UML class diagrams with essential "views" of the classes like this (just a "demo page"):
http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text
As for the class structure, does http://svn.wikimedia.org/doc/ help? I've found it to be useful many times.
It definitely helps - if you don't get lost...
Also here it would help a lot to have simple diagrams showing things at different "levels" of complexity & abstraction. Diagrams should capture not only different "levels" but also how the same classes/tables are used within different "scopes" (like the text does in the very good database descriptions!). Daagrams should preferably illustrate "use cases", like "when deleting a page then it affects..." etc.
Such diagrams/views would give Context to the Details. This is important since Details without a meaningful Context is of lesser value to the newbie to Mediawiki (which I am one of).
Regards,
// Rolf Lampa
This one http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text is easy to understand because it shows how the tables are linked.
What is so confusing for me as someone who wants to dig into that world is that there is not one 'easy' approach.
One first has to learn all about the Doxygen's Apaches PHP and the others contributing to the game.
I guess that the key to success is persistence and some helpful people.
Regards Albert Cremer
"Rolf Lampa" rolf.lampa@rilnet.com schrieb im Newsbeitrag news:45B4F1FC.4070004@rilnet.com...
Titoxd@Wikimedia wrote:
<snip>
For the database, you can have a look at http://www.mediawiki.org/wiki/Manual:Database_layout, which includes an overview of all the database tables currently used in MediaWiki. I've tried to make sure everything is more-or-less accurate (probably less), but it should be accurate for MW 1.8, 1.9 and 1.10alpha.
This really is of great help! This could fairly easy be drawn also with UML class diagrams with essential "views" of the classes like this (just a "demo page"):
http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text
As for the class structure, does http://svn.wikimedia.org/doc/ help? I've found it to be useful many times.
It definitely helps - if you don't get lost...
Also here it would help a lot to have simple diagrams showing things at different "levels" of complexity & abstraction. Diagrams should capture not only different "levels" but also how the same classes/tables are used within different "scopes" (like the text does in the very good database descriptions!). Daagrams should preferably illustrate "use cases", like "when deleting a page then it affects..." etc.
Such diagrams/views would give Context to the Details. This is important since Details without a meaningful Context is of lesser value to the newbie to Mediawiki (which I am one of).
Regards,
// Rolf Lampa
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I would like to mention http://www.phpeclipse.de/ - eclipse plugin including possibility to attach a debugger, which works for me with a xampp installation. Don't miss the tutorial at http://docs.schuetzengau-freising.de/modules/xdocman/index.php?doc=xo-002&am... ng=en
Greetz, Bene
-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of a. cremer Sent: Monday, January 22, 2007 8:00 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] IDE for mediawiki
This one http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text is easy to understand because it shows how the tables are linked.
What is so confusing for me as someone who wants to dig into that world is that there is not one 'easy' approach.
One first has to learn all about the Doxygen's Apaches PHP and the others contributing to the game.
I guess that the key to success is persistence and some helpful people.
Regards Albert Cremer
"Rolf Lampa" rolf.lampa@rilnet.com schrieb im Newsbeitrag news:45B4F1FC.4070004@rilnet.com...
Titoxd@Wikimedia wrote:
<snip>
For the database, you can have a look at http://www.mediawiki.org/wiki/Manual:Database_layout,
which includes
an overview of all the database tables currently used in
MediaWiki.
I've tried to make sure everything is more-or-less
accurate (probably
less), but it should be accurate for MW 1.8, 1.9 and 1.10alpha.
This really is of great help! This could fairly easy be drawn also with UML class diagrams with essential "views" of the classes like this (just a "demo page"):
http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text
As for the class structure, does
http://svn.wikimedia.org/doc/ help?
I've found it to be useful many times.
It definitely helps - if you don't get lost...
Also here it would help a lot to have simple diagrams
showing things
at different "levels" of complexity & abstraction. Diagrams should capture not only different "levels" but also how the same classes/tables are used within different "scopes" (like the
text does
in the very good database descriptions!). Daagrams should
preferably
illustrate "use cases", like "when deleting a page then it
affects..." etc.
Such diagrams/views would give Context to the Details. This is important since Details without a meaningful Context is of lesser value to the newbie to Mediawiki (which I am one of).
Regards,
// Rolf Lampa
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Looks promising and IS FREE "DaBuum" dabuum@web.de schrieb im Newsbeitrag news:002301c73ef8$b8256b20$11b6a8c0@codysminimobile...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I would like to mention http://www.phpeclipse.de/ - eclipse plugin including possibility to attach a debugger, which works for me with a xampp installation. Don't miss the tutorial at http://docs.schuetzengau-freising.de/modules/xdocman/index.php?doc=xo-002&am... ng=en
Greetz, Bene
-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of a. cremer Sent: Monday, January 22, 2007 8:00 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] IDE for mediawiki
This one http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text is easy to understand because it shows how the tables are linked.
What is so confusing for me as someone who wants to dig into that world is that there is not one 'easy' approach.
One first has to learn all about the Doxygen's Apaches PHP and the others contributing to the game.
I guess that the key to success is persistence and some helpful people.
Regards Albert Cremer
"Rolf Lampa" rolf.lampa@rilnet.com schrieb im Newsbeitrag news:45B4F1FC.4070004@rilnet.com...
Titoxd@Wikimedia wrote:
<snip>
For the database, you can have a look at http://www.mediawiki.org/wiki/Manual:Database_layout,
which includes
an overview of all the database tables currently used in
MediaWiki.
I've tried to make sure everything is more-or-less
accurate (probably
less), but it should be accurate for MW 1.8, 1.9 and 1.10alpha.
This really is of great help! This could fairly easy be drawn also with UML class diagrams with essential "views" of the classes like this (just a "demo page"):
http://meta.rilnet.org/wiki/Mediawiki/Database/Tables/Text
As for the class structure, does
http://svn.wikimedia.org/doc/ help?
I've found it to be useful many times.
It definitely helps - if you don't get lost...
Also here it would help a lot to have simple diagrams
showing things
at different "levels" of complexity & abstraction. Diagrams should capture not only different "levels" but also how the same classes/tables are used within different "scopes" (like the
text does
in the very good database descriptions!). Daagrams should
preferably
illustrate "use cases", like "when deleting a page then it
affects..." etc.
Such diagrams/views would give Context to the Details. This is important since Details without a meaningful Context is of lesser value to the newbie to Mediawiki (which I am one of).
Regards,
// Rolf Lampa
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32)
iD8DBQFFthgjX96C8k2LhU8RAjjkAJ41ubpyQy2RD+YGSbjY0CfObeHGcgCfakoi HMtIPLs0tB7DRY/3gG2LUnY= =ydHn -----END PGP SIGNATURE-----
mediawiki-l@lists.wikimedia.org