Hi,
I got a question from a student I am mentoring, about using many feature
branches in his tree. Here is the answer that apply (at least) to the
two students I mentor.
Because the sub-projects on the schedule are linear, my opinion is that
it will be simpler to just use the master branch, completing one feature
before starting the next one.
Of course, the student has to frequently merge origin/master (origin
being [0]) to his master branch or to all of his feature branches, to
keep up with what happens in the "common" tree.
Moreover, if the student has many branches and modifies the same file in
more than one branch, cross-merging between his branches has to be done
and this require more planning.
There won't be a "final" merging at the end of GSoC. From the student
guide [1], "Push every change you've done so that we can track your
progress. GSoC has few deadlines, but we want to see and merge your code
continuously! "
[0] git@github.com:phpmyadmin/phpmyadmin.git
[1] http://wiki.phpmyadmin.net/pma/GSoC_2012_Student_Guide
--
Marc Delisle
http://infomarc.info
Hi,
As discussed on the team meeting in February, I started creating a
wiki page with some guidelines for avoiding security bugs [0].
The page is not finished yet, I just set out some ideas, that I will
work out in the next few days. Feel free to comment, improve or add
guidelines as you see fit.
[0] http://wiki.phpmyadmin.net/pma/Security_pitfalls
--
Kind regards,
Dieter Adriaenssens
> -----Original Message-----
> From: SourceForge.net [mailto:noreply@sourceforge.net]
> Sent: Saturday, April 28, 2012 12:36 AM
> To: SourceForge.net
> Subject: [Phpmyadmin-trk-featreq] [ phpmyadmin-Feature Requests-3522109 ]
> Inline editing by double click
>
> Feature Requests item #3522109, was opened at 2012-04-27 14:23
> Message generated for change (Comment added) made by arcadius-radius
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=377411&aid=3522109&group_i
> d=23067
>
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: Interface Improvements
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: arcadius (arcadius-radius)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Inline editing by double click
>
> Initial Comment:
> Currently (pma 3.5.0) grid editing in browse mode is started on click.
> This can be annoying for some users, f.e., they fear important table data can be
> accidentally damaged.
> Another bad thing is unexpected starting edit mode when trying to select some
> text in grid (to copy it to clipboard).
>
> It would be good to support 3 configuration modes of Grid editing:
> - On click (current behavior),
> - On double click,
> - Disable.
>
> While there's no this useful setting, I replaced in /js/makegrid.js:
> $(g).find("td.data").click
> .. with:
> $(g).find("td.data").dblclick
>
> ----------------------------------------------------------------------
>
> >Comment By: arcadius (arcadius-radius)
> Date: 2012-04-27 15:36
>
> Message:
> Usual action on double click is selecting all text, on 3-click –
> selecting all line...
> So ideal shortcut for starting inline editing would be Ctrl+Click, if it
> possible.
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=377411&aid=3522109&group_i
> d=23067
Would introducing a new configuration option, as suggested by arcadius, be a good idea?
IMHO changing the click behavior for 4.0 would consist a rather big change for people used to 3.5, wouldn't it?
--
Jo Michael
Hi there,
Just spotted an issue with the new "move columns" functionality.
After you add or drop a column, if you click on the "Move columns" link,
you will be shown a dialog with the old columns instead of the new ones.
Bye,
Rouslan
Hi
I've created tuned coding style checks for phpcs, which is now being
used on http://ci.phpmyadmin.net/. As you can see we got rid of 2000
useless warnings (mostly about missing @author/@copyright/@link, which
we don't use).
However we still have more than 10000 violations. Some are simply not
fixable or hard to fix, but some are easy (like adding documentation).
Anyway please try not to introduce new violations if possible :-). We
want nice code base that is easy to understand and following coding
standard helps here a lot.
--
Michal ÄŒihaÅ™ | http://cihar.com | http://blog.cihar.com