It was a great gsoc session with PMA last time. I could not contribute it
for last few months(after gsoc) because I had my final year exam at
university. I'm willing to continue my contribution to phpMyadmin as a non
gsoccer. Are there any remaining ideas to continue with ajaxification of
the PMA. If so I like to open a discussion on them and continue with them.
L G Thilanka Kaushalya
Computer Science & Engineering,
University of Moratuwa,
Connect with me at,
Gmail : lgtkaushalya(a)gmail.com
Twitter : @thilanka_k
Facebook : Thilanka Kaushalya
Yahoo : lgtkaushalya(a)yahoo.com
Blog : http://coders-view.blogspot.com/
As you might recall from the PHPExcel licensing discussion
Fedora people were investigating a possible licensing concern with the
tcpdf library we bundle. Nothing has come of that with Fedora, but
apparently the SuSE people have found something they don't like. The
user ChrisWi asked about it in the IRC channel and provided a link to
their bugtracker: https://bugzilla.novell.com/show_bug.cgi?id=736698 --
which requires a login, so he also provided the following text summary:
** begin paste **
phpMyAdmin 22.214.171.124 (and presumably many earlier versions as well) contains
tcpdf. This package claims to be LGPL-3.0+ licensed but contains the
YOU CAN'T REMOVE ANY TCPDF COPYRIGHT NOTICE OR LINK FROM THE
GENERATED PDF DOCUMENTS.
As the LGPL-3.0+ incorporates by reference the GPL-3.0+, sections 7 and
the GPL-3.0+ are relevant:
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
Accordingly, it may be possible to point out to tcpdf upstream that the
additional term that they apply may be viewed as a 'non-permissive
and that you wish to exercise your rights under the GPL-3.0+ to remove that
term from downstream distributions.
If upstream are unwilling to engage in meaningful discussion or take the
that the additional restriction is per se not part of the license
because it is
above the license and not incorporated into it, tcpdf should be dropped.
** end paste **
Now again, as I'm sure you're aware, we're not responsible for making
the distributions happy, but it's also in our best interest to try to
resolve these things. Looks to my non-lawyer eye like this is something
to push back on the tcpdf folks. Again, if I'm understanding correctly,
the problem is the additional line added that "YOU CAN'T REMOVE ANY
TCPDF COPYRIGHT NOTICE OR LINK FROM THE GENERATED PDF DOCUMENTS."
Additionally, Google provides a lot of results of people questioning
seems to be the best discussion. A discussion regarding the inclusion in
went so far as to bring up the dubious legal position of putting a
(tcpdf) copyright notice on the work of others.
From the tcpdf forums link, it appears the author has no interest in
changing this. To be fair to tcpdf, the only place I see his notice in
the generated PDF is the "PDF Producer" field of the file properties. I
think that's reasonable, but I think the part that concerns the SuSE
folks is the having a non-OSI-endorsed clause appended to a license; if
every project would do that it would be a nightmare to maintain. But
that's just my interpretation.
I've signed up for a Novell account, but I'm still not authorized to
view the bug report directly. At the moment, aside from the gentleman in
IRC, we have no line of communication to them or way of getting updates
on their internal discussion.
Thanks for your thoughts on this...
Try this on sakila.actor:
1. edit the PRIMARY index and add first_name to it
2. edit it again and remove first_name
3. edit it again: first_name is shown as being part of the index
On 11 Dec, 2011, at 7:37 PM, Marc Delisle <marc(a)infomarc.info> wrote:
> Le 2011-11-14 10:58, Aris Feryanto a écrit :
>> Hi all,
>> On 12 Nov, 2011, at 2:29 AM, Piotr Przybylski<piotr.prz(a)gmail.com>
>>> 2011/11/11 Marc Delisle<marc(a)infomarc.info>:
>>>> Piotr Przybylski a écrit :
>>>>> 2011/11/11 Marc Delisle<marc(a)infomarc.info>:
>>>>>> Dieter Adriaenssens a écrit :
>>>>>>> Kind regards, Dieter Adriaenssens. Op 11 nov. 2011 16:00
>>>>>>> schreef "Marc Delisle"<marc(a)infomarc.info
>>>>>>> <mailto:firstname.lastname@example.org>> het volgende:
>>>>>>>> Hi, when grid editing a TEXT column, hitting ENTER
>>>>>>>> transmits my change instead of inserting a new line.
>>>>>>> It makes sense that in this case a new line is added, but
>>>>>>> how should the entry be submitted in the database? If I'm
>>>>>>> not mistaken there is no submit button at the moment.
>>>>>> Dieter, by default, $cfg['SaveCellsAtOnce'] is set to false,
>>>>>> thus not showing a submit button.
>>>>>> When setting it to true, a submit button appears but the
>>>>>> field closes as soon as ENTER is hit.
>>>>>> If we want to support grid editing + newlines, a possible
>>>>>> solution would be to ask the user to click outside the input
>>>>>> field but it's less efficient.
>>>>> How about ignoring Shift+ENTER for submitting? This way ENTER
>>>>> would submit form and Shift+ENTER would just insert a newline.
>>>> Yes but is Shift+Enter intuitive enough or do we need to -
>>>> advertise it on the page - explain it in Documentation.html
>>> I've seen it used in a few places, but it's not common - some
>>> "Press Shift+Enter for newline" message under text field would be
>> Yes. I agree to use Shift+Enter and display a hint for that. I'll try
>> to fix this and the RTL alignment on this weekend.
> Hi Aris,
> any progress on this?
I've added the shift+enter handling in my repo .
I also added OK and Cancel button in the editing area.
But, I haven't finished fixing the RTL alignment.
If you have some time, you may test the shift+enter and the buttons in my repo.