Hi all,
Do you know how I could provide feedback for the new repository? Maybe
the web admins mailing list? I am wondering, because I think the old
OpenOffice repository already looks very good feature-wise and in my
opinion a clone would be the best option.
Kind regards
Alex
--
Hi Nate,
Welcome to the team :)
Alex
Am 14.09.2011 17:39, schrieb Nathaniel Schultz:
Heh, I joined the lists a month or two back, but work got hairy, and
then it ended. Suffice it to say, I was distracted.
My applicable background is primarily user-interface design and
programming. (I'm
Hi Alex, Nathaniel!
Somehow missed to respond to this mail ... thanks for the reminder,
Alex ;-)
Nathaniel, welcome to the team ... if you have any questions or
comments, then please go ahead :-)
Cheers,
Christoph
Am Freitag, den 16.09.2011, 22:02 +0200 schrieb Alexander Wilms:
Hi Nate,
Hi Loic, all!
Am Freitag, den 16.09.2011, 00:07 +0200 schrieb Loic Dachary:
Hi,
As an additional note - do we get the source code to work on further
refinements / changes after the challenge is over?
I will provide the deliverables as a layered XCF file and it will be under
GPLv3+ as
On 09/16/2011 11:11 PM, Christoph Noack wrote:
Rationale: Bugs aren't funny, but for our website it would help to have
a visual anchor that tells the user bug this way, please. Furthermore,
a hiqh quality graphic lets us appear more professional ... although it
is still the same product (note:
Hi all,
after my rather lengthly explanation yesterday, here is an structural
example (based on See's design) of how it could look like:
https://picasaweb.google.com/lh/photo/PLZvWTs1NiL_w3auPyfUjA?feat=directlink
Cheers,
Christoph
Am Freitag, den 16.09.2011, 00:40 +0200 schrieb Christoph
Hi all,
just wanted to share my first ideas regarding the icon for the
bug-report pages. It's simply a LibreOffice icon with red borders and a
little warning sign containing an exclamation mark. Its not based on the
tango guidelines or the LO color-palette, only a draft. SVG:
Principle: Users shouldn't have to map their thinking process to the
computer. A good UI will map the data to intent to allow (as much as
possible) refinement in any order.
Styles:
Beginning and ending tags of manual formatting versus styles are
clumsy to edit, and some of the rules can
