Developers

developers@phpmyadmin.net

7004 discussions

[Phpmyadmin-devel] Fix against bug #586230
by Lo�c 25 Jul '02

25 Jul '02

Hi List! I've suggested a patch against bug #586230 (Table comments not parsed for HTML) in the bug tracker. Can anybody test it and commit it if it works? Thanks, Loïc ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif

1 0

[Phpmyadmin-devel] Re: RE: [Phpmyadmin-devel] RE: [Phpmyadmin-devel] suggestion for Documentation after 2.3
by Robin Johnson 24 Jul '02

24 Jul '02

On Wed, 24 Jul 2002, [utf-7] Beck, Mike wrote: > +AD4- I would actually go against that idea. Have XML master files > +AD4- instead, as > +AD4- those can be kept in CVS a lot easier than a database. Each translator > +AD4- would just open up the XML file in his editor, and update it directly, > +AD4- then post a patch to the tracker. To keep track of when > +AD4- changes are made > +AD4- to the english documentation and not the translations, I > +AD4- suggest having > +AD4- small tag in them that is noted as out of date when the > +AD4- english is updated > +AD4- and the translation isn't. > > well as has been noticed, i am not at all firm with XML yet, so i possibly i > really thought too complicated there. Trust me, writing documents in XML directly is even easier than writing HTML by hand. Since you have control over your own elements and attributes, the language is usually a lot simpler. A list might be: <list type='dot'> <item>foo</item> <item>bar</item> <list> Paragraph: <para>I'm a little paragraph. (This is actually SGML compliant I think)</para> > possibly it is even ok when we just > add the new parts to the docu at the end of the file as it is done with the > language now and when the xml is converted to html, pdf or whatever there is > a possibility to order the stuff using some tags there? can this be done > with a XSLT? Yes, that is definetly doable, but not very common. As for keeping things straight and easier to edit, the document frequently gets re-arranged to keep all of the code in the order it will come out. It is a lot easier to edit when it is already in order. But it wouldn't be too hard in our language scripting for new sections being added to be placed at the end of the master files, and then we can run another script to re-order the XML file via XSLT. The only skill/knowledge that is needed for doing hard code XML is for creating your own XSLT and XML Schema documents. Once you have those, and I can create them when I have a bit of time, you can feed them to existing tools, and use WYSIWYG XML editors. -- Robin Hugh Johnson E-Mail : robbat2(a)orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639

1 0

[Phpmyadmin-devel] RE: [Phpmyadmin-devel] suggestion for Documentation after 2.3
by Beck, Mike 24 Jul '02

24 Jul '02

> While that may be true of most people that install phpMyAdmin > themselves, > it is not true if they are installing it for an ISP type > setting, where > there are other users besides the one that installed it. exactly > There are quite a few anchors already, and it would not be > too hard to add > more. jup, it will just need a lot of patience... > <?php > function PMA_HelpLink($ref) > { > globals $cfg; > if ($cfg['Display_HelpLinks']) { > $str = '<a href="Documentation.php#'.$ref.'" > onclick="..."><sup>?</sup></a>'; > } else { > $str = ''; > } > > return $str; > } // end of the "PMA_HelpLink()" function > ?> something like that. Only if Js is enabled it should only point to # and if there is no js than we don't need to add the onClick. Do we allready have some js-checking? after all we are using some js every now and then. And of course we will have to give the section (=filename) as well, and the function might have to add the language. > I have the configuration variable there on purpose, as in > some cases I run > with limited screen space, and I would want to turn off the > help links, as > I know what I am doing. agreed. though what i am thinking of is a graphic of 10*10 pixels (because i want to also have it on the side of inputs) and just a text ? is not really obvious enough (that's for the alt in case you also switched off graphics ;-) > > 2) wasn't there some thought on having the docu in a > different format? > > (sgml, xml or whatever) > Yes. No format was decided on. I'd be in favour of having the master > document in SGML/XML, split up into little sections. > Possible directory structure: ... > I think XML masters would be ideal, as with XSLT stylesheets on our > master side when we are rolling a package, we can build all the > documentation easily. There would also be room to produce more formats > easily from the XML, such as Info, LaTeX and PDF. I don't > know if one can > do this from SGML or not. yes, there even i agree XML would be a good move *lol* well i wanted to do some reading on this topics anyway.. > > 3) i expect nobody ever really hoped we could get the whole docu > > translated, or? > It will be a slow process for documentation, but it can be done in the > long term. at least then we should think of having the files for different languages. (allthough i expect it would be ok to have the install only in english). but then there is two problems: the whole doku in all the languages would be quite a package, so i'd suggest that the documentation would be split from the main package and is downloaded seperately in the language the user wants (this also spares us to have 30 or 40 copies of the english text at the beginning while there is no translation for some language and we need a file with that name ;-) and we'd have to think of a way to handle the translations .... what i could imagine would be to have all strings in a database and do a script that would enable the translators to translate them online and creating their languagefile out of it? simple draft: table docu str_id section_id[enum] place_id string 0000001 tbl_qbe 1 Heading 1 0000002 tbl_qbe 1.2 <dt><dd>bla bla.... table transl_chines str_id translation 0000002 asdfhlsajfh so when creating the languagefile the script would not find 0000001 in the transl so it takes it from the table docu (which can be done with a simple left join transl_chines where str_id is null) and the other from the translation. additionally a script like that could of course easily provide the text in all needed charactersets. hm.... once again something which might be an idea for a splitted project - there might be other people apart from PMA that might have a use for that. -- Mike Beck mike.beck(a)users.sourceforge.net

2 1

[Phpmyadmin-devel] Re(2): Function
by Lo�c 24 Jul '02

24 Jul '02

Hi List! >I can extrapolate all of the other functions except >PMA_INFO_getDB() from this. >Got any ideas on the last function ? Since we pass the current db name by url/form everywhere, I don't think this kind of function inside the current code. Sorry... Loïc ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif

3 2

RE: [Phpmyadmin-devel] Function
by Robin Johnson 24 Jul '02

24 Jul '02

> > Could somebody please help me with: > > // returns current database name as string > > PMA_INFO_getDB() > > //returns array of table names in given database > > PMA_INFO_getTables($DBName) > > //returns array of tables names in current database > > PMA_INFO_getTables() > > //returns array of column names in given table > > PMA_INFO_getColumns($TableName) > > //returns array of column names in given table inside given database > > PMA_INFO_getColumns($DBName,$TableName) > > all of these allready exist in mysql_wrappers.lib do you need to change > them? Thanks Mike. Hmm, I hadn't noticed those before, and didn't see them when I looked. Glancing quickly in the file, I see PMA_mysql_list_tables (like my PMA_INFO_getTables($DBName)) PMA_mysql_list_fields (like my PMA_INFO_getColumns($DBName,$TableName)) I can extrapolate all of the other functions except PMA_INFO_getDB() from this. Got any ideas on the last function ? It wouldn't surprise me if we actually had a variable with it already in PMA. -- Robin Hugh Johnson E-Mail : robbat2(a)orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639

1 0

[Phpmyadmin-devel] Function
by Robin Johnson 23 Jul '02

23 Jul '02

In writing my SQL parser, I need some functions written that get some information from MySQL, and I'm not sure of the best way to go about them. Could somebody please help me with: // returns current database name as string PMA_INFO_getDB() //returns array of table names in given database PMA_INFO_getTables($DBName) //returns array of tables names in current database PMA_INFO_getTables() //returns array of column names in given table PMA_INFO_getColumns($TableName) //returns array of column names in given table inside given database PMA_INFO_getColumns($DBName,$TableName) Thanks in advance -- Robin Hugh Johnson E-Mail : robbat2(a)orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639

1 0

[Phpmyadmin-devel] Re: new parser
by Robin Johnson 23 Jul '02

23 Jul '02

On Tue, 23 Jul 2002, Marc Delisle wrote: > Hi Robin, > > when do you plan to merge it? The PMA_STR_* stuff is about to be merged. PMA_SQP_* later on tonight, I need to rewrite a function again. So that people can give me a hand in updating the existing codebase to use the new parser, here is an outline of it. The basic procedure for using the new SQL parser: On any page that needs to extract data from a query or to pretty-print a query, you need code like this up at the top: ($sql contains the query) $parsedSQL = PMA_SQP_Parse($sql); If you want to extract data from it then, you just need to run $SQLinfo = PMA_SQP_Analyze($parsedSQL); (returned structure of this function is being rewritten presently); If you want a pretty-printed version of the query, do: $string = PMA_SQP_FormatHTML($parsedSQL); (note that that you need to have syntax.css.php3 included somehow in your page for it to work, I recommend '<link rel="stylesheet" type="text/css" href="syntax.css.php3" />' at the moment.) -- Robin Hugh Johnson E-Mail : robbat2(a)orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639

1 0

[Phpmyadmin-devel] Re(2): Adding query box on the structure page
by Lo�c 23 Jul '02

23 Jul '02

Hi List! Marc wrote: > What about adding the whole contents of the SQL page, > on the Structure page, after "propose table structure"? I agree this idea. Alexander wrote: > What about letting the user open a small query window > via JS by clicking on a link in the left frame? This > would allow him to use the query box from anywhere. > I'll build a patch tomorrow. Good idea as soon it can also work with a browser that can't parse js (it can be easilly done). Loïc ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif

4 5

[Phpmyadmin-devel] Marc offline tomorrow
by Marc Delisle 23 Jul '02

23 Jul '02

Hi, I will be without e-mail tomorrow, due to a server maintenance. -- Marc Delisle

1 0

[Phpmyadmin-devel] Fix against bug #574620
by Lo�c 23 Jul '02

23 Jul '02

Hi again! I've suggested a fix against this bug (tables not linked are missing in PDF) in the bug tracker. It would be nice if someone can test it and maybe submit it in the CVS tree. Thanks, Loïc ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers