Difference between revisions of "Projects/KNS2/Packager"

< Projects‎ | KNS2
Jump to: navigation, search
(The Packager)
Line 1: Line 1:
 
{{warning|Names are just temporary. Infos can be as well. Please don't trust this page as probably most of the things are going to heavily change during this 1 month developement marathone.}}
 
{{warning|Names are just temporary. Infos can be as well. Please don't trust this page as probably most of the things are going to heavily change during this 1 month developement marathone.}}
  
= The Packager =
+
== The Packager/Uploader ==
 
The syntax I'd like to came up with is:
 
The syntax I'd like to came up with is:
 
<div class="codebox">
 
<div class="codebox">
Line 17: Line 17:
  
 
This task is mostly done, this is the API I came out with:
 
This task is mostly done, this is the API I came out with:
=== Packaging control API ===
+
== Proposed API (packaging section) ==
 
* '''Plasmagik::PackageType''' -> Predefined list of package types. See packaging.txt for the complete list.
 
* '''Plasmagik::PackageType''' -> Predefined list of package types. See packaging.txt for the complete list.
 
* '''setPackageType(Plasmagik::PackageType, bool clearFirst)''' If clearFirst == true, clearProgrammingLanuages() will be called.
 
* '''setPackageType(Plasmagik::PackageType, bool clearFirst)''' If clearFirst == true, clearProgrammingLanuages() will be called.
Line 31: Line 31:
 
* '''setText(Plasmagik::Label label, QString text)''' You can customize GUI strings with that function
 
* '''setText(Plasmagik::Label label, QString text)''' You can customize GUI strings with that function
  
==== Improvements proposed ====
+
==== Improvements proposed for this section ====
 
* Rename ProgrammingLanguages --> packageType, or such
 
* Rename ProgrammingLanguages --> packageType, or such
 
* setPackageExtension(QString extension) with mimetype instead of string?
 
* setPackageExtension(QString extension) with mimetype instead of string?
  
=== Networking control API ===
+
== Proposed API (networking section) ==
 
* '''TODO!'''
 
* '''TODO!'''

Revision as of 11:01, 14 March 2007

noframe
 
Warning
Names are just temporary. Infos can be as well. Please don't trust this page as probably most of the things are going to heavily change during this 1 month developement marathone.


Contents

The Packager/Uploader

The syntax I'd like to came up with is:

Code

Plasmagik packager; packager.setPackageType(...); packager.setSomething(); packager.show();

or something like that --Ruphy 18:14, 12 March 2007 (CET).

Plasmagik inherits QDialog

This task is mostly done, this is the API I came out with:

Proposed API (packaging section)

  • Plasmagik::PackageType -> Predefined list of package types. See packaging.txt for the complete list.
  • setPackageType(Plasmagik::PackageType, bool clearFirst) If clearFirst == true, clearProgrammingLanuages() will be called.
  • setProgrammingLanguages(QString/QStringList languages) If languages is QString, languages are separated by '|'. It will call clearProgrammingLanguages().
  • QString/QStringList programmingLanguages()
  • addProgrammingLanguages(QString/QStringList languages) Same as setProgammingLanguages, but it won't call clearProgrammingLanguages() first, and will add languages to the end.
  • clearProgrammingLanguages() It will remove any language previously set.
  • setIcon(QIcon icon) Sets the icon for the dialog
  • setPackageExtension(QString extension) Sets the provided extension as the one used when saving the package. It will be passed as-is to KFileDialog.
  • setText(Plasmagik::Label label, QString text) You can customize GUI strings with that function

Improvements proposed for this section

  • Rename ProgrammingLanguages --> packageType, or such
  • setPackageExtension(QString extension) with mimetype instead of string?

Proposed API (networking section)

  • TODO!

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal