Jump to content

Kexi/Getting Started: Difference between revisions

From KDE Community Wiki
Jstaniek (talk | contribs)
Jstaniek (talk | contribs)
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Welcome! This is a ''Getting Started'' page for Kexi on the community.kde.org -- a wiki for developers and by developers. It's like a notepad and a planning board in one. You can create account there even now.
Welcome! This is a ''Getting Started'' page for KEXI on the community.kde.org -- a wiki for developers and by developers. It's like a notepad and a planning board in one. You can create account there even now.


Good start is to visit Calligra page [[Calligra/First_Contact|First Contact]]. This page is for entire Calligra Suite, but there are lots of general knowledge useful for Kexi development too.  
A great starting point is to visit the Calligra [[Calligra/First_Contact|First Contact]] page, which provides an overview of the entire Calligra Suite. This page also includes a wealth of general information that is valuable for KEXI development.


{{Note|If you're still looking for a cool task, just contact us! Many tasks are not documented here and we can adjust to your interests, capabilities and needs!}}
{{Note|If you're still looking for a cool task, just contact us! Many tasks are not documented here and we can adjust to your interests, capabilities and needs!}}
Line 17: Line 17:
*What does testing mean?
*What does testing mean?
**Identifying crashes or misbehaviour
**Identifying crashes or misbehaviour
**Locating places where Kexi is inefficient (e.g. for large data sets) or hangs
**Locating places where KEXI is inefficient (e.g. for large data sets) or hangs
**Checking particular functionality and proposing extensions, e.g. data importing functions
**Checking particular functionality and proposing extensions, e.g. data importing functions
**Comparing the application to the competition and identify the most desired features that Kexi currently lacks
**Comparing the application to the competition and identify the most desired features that KEXI currently lacks
**Testing for usability, e.g. identifying functions that are hard to use or locate
**Testing for usability, e.g. identifying functions that are hard to use or locate
**Testing for accessibility, e.g. identify areas of the application that are not clearly visible on non-default color settings or cannot be used without mouse
**Testing for accessibility, e.g. identify areas of the application that are not clearly visible on non-default color settings or cannot be used without mouse
Line 28: Line 28:
*[[Calligra/FAQ#I_am_developer.2C_how_to_contribute_a_patch.3F|Contributing a Patch]] (applies to all Calligra apps, '''but note: Kexi uses phabricator.kde.org, not reviewboard''')
*[[Calligra/FAQ#I_am_developer.2C_how_to_contribute_a_patch.3F|Contributing a Patch]] (applies to all Calligra apps, '''but note: Kexi uses phabricator.kde.org, not reviewboard''')
*[http://api.kde.org/ Calligra API reference]
*[http://api.kde.org/ Calligra API reference]
*[[Calligra/Building|Building Kexi as part of Calligra]] (other Calligra apps can be built or only Kexi)
*[[Calligra/Building|Building KEXI as part of Calligra]] (other Calligra apps can be built or only KEXI)
*[[../Junior Jobs/]]
*[[../Junior Jobs/]]


==Specific for non-Developers==
==Specific for non-Developers==
Are you non-developer or just don't wish to develop for us but want to help in other way? Good!
*Starting: [[Calligra/FAQ#I_am_developer.2C_how_to_contribute_a_patch.3F|"I am not developer, I cannot or do not like to program. How can I help?"]]
*Starting: [[Calligra/FAQ#I_am_developer.2C_how_to_contribute_a_patch.3F|"I am not developer, I cannot or do not like to program. How can I help?"]]
*For testing, possibly the newest Kexi version should be used  
*For testing, possibly the newest KEXI version should be used  
*After starting Kexi for the first time, a new empty database can be created. [http://docs.kde.org/stable/en/koffice/kexi/index.html Handbook (old)] can be used to get information how to do this.
*After starting KEXI for the first time, a new empty database can be created. [http://docs.kde.org/stable/en/koffice/kexi/index.html Handbook (old)] can be used to get information how to do this.
*To test support for server databases, access to a server is needed. It can be the same computer as the used desktop or laptop machine, but database server software have to be installed on it. Users that lack knowledge on how to do this should ask someone (e.g. a network administrator) to do so.
*To test support for server databases, access to a server is needed. It can be the same computer as the used desktop or laptop machine, but database server software have to be installed on it. Users that lack knowledge on how to do this should ask someone (e.g. a network administrator) to do so.
*Example databases on a database server (MySQL, PostgreSQL) useful to test server connections '''will be provided later''' after contributor provides a server space.  
*Example databases on a database server (MySQL, PostgreSQL) useful to test server connections '''will be provided later''' after contributor provides a server space.  
*Beginner users may also want to use [http://kde-files.org/content/show.php/Simple+Database?content=23137 example database] as a reference.
*Beginner users may also want to use [http://kde-files.org/content/show.php/Simple+Database?content=23137 example database] as a reference.
*Marketing and education: spread the word about KEXI:
**Publish a link to KEXI project on your web page or social page or other publications
**Subscribe to [email protected] (link) and you'll be informed about KEXI news worth to spread.
**Write articles about KEXI for websites, newspapers or as college/studies paper.
**Let us know about your publications so we can coordinate.
**Put the software in distributed software bundles and inform users about its availability.
**Any other promotional action


==Other information==
==Other information==
*General [[Calligra/FAQ|Calligra FAQ]]
*General [[Calligra/FAQ|Calligra FAQ]]
*[http://techbase.kde.org/Contribute Contribution options described on KDE Techbase]
*[https://community.kde.org/Get_Involved Contribution options described on KDE Community wiki]
*Kexi 1.x has a wiki at http://kexi-project.org/wiki/wikiview/ - you may be directed there somehow (e.g. via google search or other links) but just note that knowledge published there may a bit outdated be at places. And we're trying to migrate fresh to this wiki.

Latest revision as of 21:28, 29 November 2024

Welcome! This is a Getting Started page for KEXI on the community.kde.org -- a wiki for developers and by developers. It's like a notepad and a planning board in one. You can create account there even now.

A great starting point is to visit the Calligra First Contact page, which provides an overview of the entire Calligra Suite. This page also includes a wealth of general information that is valuable for KEXI development.

Note

If you're still looking for a cool task, just contact us! Many tasks are not documented here and we can adjust to your interests, capabilities and needs!

Ways to contribute

  • Tester
  • Developer
  • Promoter

Communication channels

See Contact.

Common activity

  • Reporting issues, wishes or bugs (quick link: Report bug or wish for Kexi)
  • Download Calligra to run it
  • What does testing mean?
    • Identifying crashes or misbehaviour
    • Locating places where KEXI is inefficient (e.g. for large data sets) or hangs
    • Checking particular functionality and proposing extensions, e.g. data importing functions
    • Comparing the application to the competition and identify the most desired features that KEXI currently lacks
    • Testing for usability, e.g. identifying functions that are hard to use or locate
    • Testing for accessibility, e.g. identify areas of the application that are not clearly visible on non-default color settings or cannot be used without mouse
    • Testing for localisations issues, including support for right-to-left languages, etc. (note: errors in translations to other languages should be reported to a particular translation team)
    • Locating errors in Documentation, Tutorials and Samples, report unclear or incomplete paragraphs, outdated or missing screen shots (the above note about translation teams also apply to translated documentation)

Specific for Developers

Specific for non-Developers

Are you non-developer or just don't wish to develop for us but want to help in other way? Good!

  • Starting: "I am not developer, I cannot or do not like to program. How can I help?"
  • For testing, possibly the newest KEXI version should be used
  • After starting KEXI for the first time, a new empty database can be created. Handbook (old) can be used to get information how to do this.
  • To test support for server databases, access to a server is needed. It can be the same computer as the used desktop or laptop machine, but database server software have to be installed on it. Users that lack knowledge on how to do this should ask someone (e.g. a network administrator) to do so.
  • Example databases on a database server (MySQL, PostgreSQL) useful to test server connections will be provided later after contributor provides a server space.
  • Beginner users may also want to use example database as a reference.
  • Marketing and education: spread the word about KEXI:
    • Publish a link to KEXI project on your web page or social page or other publications
    • Subscribe to [email protected] (link) and you'll be informed about KEXI news worth to spread.
    • Write articles about KEXI for websites, newspapers or as college/studies paper.
    • Let us know about your publications so we can coordinate.
    • Put the software in distributed software bundles and inform users about its availability.
    • Any other promotional action

Other information