My latest patchset of UI tweaks is ready: http://github.com/klazuka/factor/tree/ui (the 7 most recent commits)
Nearly all of the changes are purely cosmetic. The only significant change that affects downstream is the renaming of 'border-width' in the io.styles vocab to "inset". This new "inset" style does the same thing, except that it now takes a pair of numbers, one specifying the horizontal inset, and the other specifying the vertical inset. This allows greater flexibility, plus the name "border-width" was confusing as many people would construe it to mean the actual width of the border stroke, not an internal margin/padding. What is the policy for preparing a branch to be merged? I did a phase 2 bootstrap, ran relevant unit tests and ran the help-lint tool. Should I also rebase my branch against the upstream master? Or should I merge in upstream master and then send out the pull request? -keith ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
