From Fedora Project Wiki
Line 35: Line 35:
''Order and content of windows is not finished yet and can be changed''
''Order and content of windows is not finished yet and can be changed''


1) Selection what language tool will be installed / configured including project
* Selection what language tool will be installed / configured including project


2) User can select what IDE will be configure (like checkboxes)
* User can select what IDE will be configure (like checkboxes)


3) Select where will be installed language tool including / examples. Selection what will be installed is under discussion.
* Select where will be installed language tool including / examples. Selection what will be installed is under discussion.


4) Buttons with creating structure, button with creating RPM.
* Buttons with creating structure, button with creating RPM.
 
* Git integration (Creating / uploading / modification)


== Some hints for editors ==
== Some hints for editors ==


[http://sontek.net/blog/detail/turning-vim-into-a-modern-python-ide http://sontek.net/blog/detail/turning-vim-into-a-modern-python-ide]
[http://sontek.net/blog/detail/turning-vim-into-a-modern-python-ide http://sontek.net/blog/detail/turning-vim-into-a-modern-python-ide]

Revision as of 08:10, 21 February 2013

This page will be used for feature DevelopersAssistant

Repository for that feature is: DevelopersAssistant

Command line arguments (not official)

-m ... means which modules will be included in source tar ball as example, (file operation, thread processes, Django / Rails application) this will be defined by each language and will not be common

-t ... what type of application will used that language (Rails, Django, apache, PHP, ...)

-d ... means dependencies. What packages are needed for that language. We will use dbus connection. Usage will be -d "glibc-devel @development"

-c ... will update configuration files of IDE tool (like vim, Eclipse, ...). After configuration user will have fully configured IDE.

-a ... this will be used for autotools. Each language script can define what will be created and provided by RPM package. E.g. manual pages? Some documentation? Who will create that type of documents???

-p ... will call command for creating package (rpm)

-n ... name of the application where will be stored on filesystem. Either as relative path (like ../<application_name>) or as absolute path (as /home/<user_name>/test/<application_name>)

-l ... will turn on some logging operations (this has small priority)

We need to thank about issue how the source files will be named and delivered to autotools binary.

a) Definition as a parameter -a like -a <files.c> -a <setup.py> etc.

b) autotools.py script will automatically select all files in src directory with specific extension???

Some notes for GUI

GUI Tool will be developed so that it will looks like wizard.

It will be used for beginners to help them understand briefly language structure and coding styles

Order and content of windows is not finished yet and can be changed

  • Selection what language tool will be installed / configured including project
  • User can select what IDE will be configure (like checkboxes)
  • Select where will be installed language tool including / examples. Selection what will be installed is under discussion.
  • Buttons with creating structure, button with creating RPM.
  • Git integration (Creating / uploading / modification)

Some hints for editors

http://sontek.net/blog/detail/turning-vim-into-a-modern-python-ide