Search results
From Free Pascal wiki
Jump to navigationJump to search
Page title matches
- {{GUI design guidelines}}4 KB (503 words) - 09:54, 12 January 2014
- {{GUI design guidelines}}3 KB (382 words) - 11:47, 2 August 2006
- {{GUI design guidelines}}4 KB (720 words) - 08:27, 23 February 2017
- {{GUI design guidelines}}7 KB (72 words) - 18:37, 26 January 2016
- {{GUI design guidelines}} These guidelines apply to the Lazarus IDE but may be used for other projects as well.3 KB (526 words) - 08:09, 19 November 2020
Page text matches
- == Coding Guidelines for Lazarus == See [[GUI design guidelines]]2 KB (343 words) - 09:09, 15 April 2020
- ==Guidelines==2 KB (272 words) - 05:30, 19 July 2021
- ...s and ensure the clarity of dialogs. This article tries to summarize these guidelines to help you designing. There is also a buch of screenshots, artwork and dia * [[GUI design guidelines]]3 KB (542 words) - 16:07, 10 August 2014
- ===Guidelines for the Icons===2 KB (242 words) - 08:17, 9 February 2020
- ...human-interface-guidelines/macos/windows-and-views/sheets/ Human Interface Guidelines], you should only use a sheet when a window has a frame. Sheets should alwa ...UserExperience/Conceptual/OSXHIGuidelines/index.html macOS Human Interface Guidelines].3 KB (361 words) - 07:53, 29 November 2020
- ...f leeway is granted to the client application and/or parser to enforce the guidelines. As usual when writing code: この実装は、This implementation adheres strictly to the RFC 4627 guidelines above and does not allow deviation from the specification.7 KB (290 words) - 05:11, 4 May 2017
- * [[GUI_design_guidelines/de|GUI design guidelines]]1 KB (190 words) - 14:41, 5 April 2013
- There are a few rules and guidelines that define the JSON syntax (see RFC 4627): ...f leeway is granted to the client application and/or parser to enforce the guidelines. As usual when writing code:5 KB (473 words) - 23:48, 24 February 2017
- ==Guidelines==5 KB (752 words) - 15:37, 23 March 2017
- ...s. To make a finished application that adheres to the respective GUI style guidelines (and even the requirements of app stores) warrants additional steps, howeve { Adapts Menus and Shortcuts to the interface style guidelines13 KB (1,699 words) - 21:56, 23 February 2021
- Simple and short guidelines:1 KB (170 words) - 07:07, 27 March 2021
- There are a few rules and guidelines that define the JSON syntax (see RFC 4627): ...f leeway is granted to the client application and/or parser to enforce the guidelines. As usual when writing code:5 KB (685 words) - 03:13, 8 June 2021
- ...UserExperience/Conceptual/OSXHIGuidelines/index.html macOS Human Interface Guidelines].4 KB (466 words) - 03:34, 8 May 2021
- {{GUI design guidelines}} These guidelines apply to the Lazarus IDE but may be used for other projects as well.3 KB (526 words) - 08:09, 19 November 2020
- [[Category:Guidelines/af]]2 KB (390 words) - 21:20, 27 October 2015
- [[Category:Guidelines]]2 KB (314 words) - 16:27, 1 February 2019
- {{GUI design guidelines}}3 KB (382 words) - 11:47, 2 August 2006
- See the Lazarus coding guidelines: [[DesignGuidelines]] * [[DesignGuidelines|Coding Guidelines for Lazarus]]5 KB (743 words) - 11:37, 7 January 2022
- ...o van de Voort: Development Tutorial (a.k.a Build FAQ)] – general building guidelines ...arco van de Voort: Creating a portable Pascal codebase.] – general porting guidelines5 KB (736 words) - 07:48, 1 April 2021
- ...lopment. Details of implementation may change, as well as adherence to GUI guidelines. ...an-interface-guidelines/macos/user-interaction/keyboard/ ''Human Interface Guidelines''] for system reserved shortcuts.6 KB (818 words) - 01:51, 18 June 2020
- См. [[GUI design guidelines]]4 KB (83 words) - 19:12, 22 January 2016
- ...ws/desktop/uxguide/vis-icons Microsoft: Windows Icons] Design Concepts and Guidelines.3 KB (459 words) - 11:57, 4 March 2020
- ...used by the OS, there are no menu Alt shortcuts and there are substantial guidelines (contrary to Linux and Windows where only a few keys are standardised to wo ...an-interface-guidelines/macos/user-interaction/keyboard/ ''Human Interface Guidelines'' - keyboard section] deals with key bindings for macOS.8 KB (1,230 words) - 06:22, 11 August 2020
- *[[GUI design]] - Notes on guidelines when designing the lazarus GUI *[[Moderating the bug tracker]] - Guidelines for lazarus developers and moderators for using the [http://www.lazarus.fre10 KB (1,443 words) - 03:30, 29 March 2020
- * [[GUI design guidelines/de|Richtlinien für das GUI-Design]] Hinweise / Richtlinien für das Design4 KB (519 words) - 23:44, 8 May 2014
- ''This page contains some useful notes and guidelines specific to the Russian translation of the Lazarus IDE. Since such informat5 KB (189 words) - 00:39, 9 December 2019
- Keep in mind that Cocoa design guidelines suggest the Icon defines a type of the document opened in the Window.3 KB (450 words) - 19:05, 5 December 2023
- ...face-guidelines/macos/app-architecture/preferences/ Apple: Human Interface Guidelines - Preferences]6 KB (558 words) - 06:27, 28 December 2021
- {{GUI design guidelines}}4 KB (503 words) - 09:54, 12 January 2014
- ...eaturesincerow|v0.9.4 (and prior, 2004 and earlier)|Designer|form designer guidelines (June 2002)}} == form designer guidelines (June 2002) ==18 KB (2,609 words) - 14:49, 7 January 2019
- === Object Design guidelines ===13 KB (1,961 words) - 13:06, 28 December 2020
- Once you've created the package, you can check it follows the guidelines with the command '''lintian''': The -9 -n options are necessary for the package to follow the guidelines.12 KB (1,728 words) - 19:39, 2 January 2022
- |Per macOS design guidelines, Push buttons should only have labels on them, and no Icons. This is exactl In macOS guidelines, the style that should be used for a button depends on the placement/usage9 KB (1,374 words) - 09:41, 26 August 2020
- * [https://developer.apple.com/app-store/resources/ Apple Guidelines and Resources]5 KB (670 words) - 06:49, 5 February 2021
- ...apps/hh465362 Guidelines for scaling] Windows Dev Center - User experience guidelines for scaling Metro style apps9 KB (1,447 words) - 10:29, 19 August 2022
- ...ys are used by the OS, there are no menu Alt shortcuts and there are large guidelines (contrary to linux and windows where only a few keys work the same under al The apple human interface guidelines for key bindings can be seen here:12 KB (1,478 words) - 09:41, 29 February 2020
- {{GUI design guidelines}}4 KB (720 words) - 08:27, 23 February 2017
- There are a few rules and guidelines that define the JSON syntax (see RFC 4627):5 KB (594 words) - 23:09, 28 September 2015
- ...emaining name of the test is freely chosen, however there are some general guidelines for this as well:7 KB (1,108 words) - 22:13, 24 June 2018
- * NSToolbar support - TToolbar doesn't correspond to macOS UI guidelines5 KB (698 words) - 02:14, 14 December 2019
- {{GUI design guidelines}}7 KB (72 words) - 18:37, 26 January 2016
- This document contains some guidelines for moderating the Lazarus [https://gitlab.com/freepascal.org/lazarus/lazar5 KB (807 words) - 23:20, 8 July 2023
- ...rface-guidelines/macos/windows-and-views/window-anatomy/ ''Human Interface Guidelines''] document on window anatomy. ...loper.apple.com/design/human-interface-guidelines/macos/ ''Human Interface Guidelines'']12 KB (1,847 words) - 11:33, 13 December 2021
- *[[GUI design]] - Notes on guidelines when designing the lazarus GUI *[[Moderating the bug tracker]] - Guidelines for lazarus developers and moderators for using the [http://www.freepascal.20 KB (3,053 words) - 20:27, 31 May 2022
- ...apps/hh465362 Guidelines for scaling] Windows Dev Center - User experience guidelines for scaling Metro style apps16 KB (396 words) - 08:42, 22 June 2022
- This document contains some guidelines for using the FPC / Lazarus [https://gitlab.com/freepascal.org/ bug tracker6 KB (1,014 words) - 23:29, 19 April 2023
- ...rmance/Conceptual/power_efficiency_guidelines_osx/ Apple: Power Efficiency Guidelines].6 KB (885 words) - 10:37, 13 March 2022
- ...//developer.apple.com/app-store/review/guidelines/ Apple: App Store Review Guidelines]7 KB (1,077 words) - 08:32, 11 April 2021
- ...FPC JVM compiler and the Jasmin assembler for which you should follow the guidelines written [[FPC_JVM|here]]. ''Note:'' You should also follow the guidelines written on the [http://developer.android.com/guide/publishing/app-signing.h19 KB (2,871 words) - 03:52, 3 August 2020
- ...bug reports it soon becomes apparent that it is easy to deviate from these guidelines.8 KB (1,474 words) - 06:01, 17 September 2020
- '''Guidelines:''' '''Guidelines:'''21 KB (2,698 words) - 22:55, 6 June 2021
- ...n control that has an animation effect according to Google Material Design guidelines. It supports custom color for background and for the circle animation, also8 KB (1,171 words) - 21:27, 13 August 2023
- ...riendly place, you'll have a better experience if you follow the following guidelines, incomplete as they are.9 KB (1,666 words) - 16:24, 24 July 2022
- [[Category:Coding guidelines]]8 KB (1,168 words) - 20:19, 2 October 2022
- *[[GUI design]] - Notes on guidelines when designing the lazarus GUI10 KB (1,431 words) - 03:31, 29 March 2020
- ...nes/macos/visual-design/color/#dynamic-system-colors Apple Human Interface Guidelines - Dynamic System Colors]12 KB (1,758 words) - 18:08, 31 May 2022
- ...m/documentation/UserExperience/Conceptual/OSXHIGuidelines/index.html Apple Guidelines]9 KB (1,244 words) - 23:41, 17 December 2019
- Some guidelines for the usage of the format() function11 KB (1,794 words) - 01:52, 9 April 2021
- [[Category:Coding guidelines]]9 KB (1,277 words) - 21:05, 2 October 2022
- *[[Material Design]]: Google material design guidelines based UI components.14 KB (2,013 words) - 09:00, 3 April 2024
- ...gn/human-interface-guidelines/macos/overview/themes/ macOS Human Interface guidelines].16 KB (2,611 words) - 02:09, 27 January 2020
- Some guidelines for the usage of the format() function12 KB (1,860 words) - 12:25, 16 February 2020
- ...y using directories common to other systems, you should carefully read the guidelines about the file system layout [http://developer.apple.com/library/mac/#docum32 KB (5,086 words) - 22:17, 20 November 2023
- *[[Cocoa Internals/Memory Management]] - guidelines of memory management tactics, whenever writing/understanding Cocoa code. (p17 KB (2,307 words) - 05:31, 15 January 2022
- The translated headers follow some simple guidelines. First all translated declarations remain at the exact same position as the20 KB (3,017 words) - 08:10, 18 March 2020
- :* [[German localization notes|German]] - Notes and guidelines for translating the Lazarus IDE to German, including a small dictionary to23 KB (1,194 words) - 06:07, 29 March 2020
- ''This page contains some useful notes and guidelines specific to the German translation of the Lazarus IDE. Since such informati17 KB (2,349 words) - 21:13, 25 July 2015
- The output on macOS 10.14.5 with FPC 3.0.4 (violates Apple Guidelines - see [[#macOS|below]] for the correct macOS file locations): ...config files in the user directory is a violation of the Apple programming guidelines. See the [[Locating macOS app support, preferences folders]] article for co43 KB (6,443 words) - 12:24, 27 January 2022
- - Guidelines31 KB (4,690 words) - 20:47, 12 January 2012
- - Guidelines28 KB (3,985 words) - 01:01, 1 June 2022
- - Guidelines26 KB (3,526 words) - 00:54, 19 February 2020
- ''The translated headers follow some simple guidelines. First all translated declarations remain at the exact same position as the31 KB (3,200 words) - 17:22, 13 May 2015
- * '''Reason''': This is in accordance with Microsoft guidelines for setting file locations.32 KB (4,698 words) - 13:24, 3 March 2020
- - Guidelines27 KB (3,914 words) - 00:55, 19 February 2020