From Fedora Project Wiki
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
== Command line arguments (not official)==
== 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
There are several commands which can be run for building / installation / running project
./develassistant c -n <project_name>


-t ... what type of application will used that language (Rails, Django, apache, PHP, ...)
This will create project in current directory like subdirectory <project_name>.


-d ... means dependencies. What packages are needed for that language. We will use dbus connection. Usage will be '''-d "glibc-devel @development"'''
Command also automatically checks / installs RPM dependencies need by C / C++ programming.


-c ... will update configuration files of IDE tool (like vim, Eclipse, ...). After configuration user will have fully configured IDE.
Another commands under C Assistants are:


-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. Input to that should be file names stored in src directory which are needed by configure.ac and Makefile structures
./develassistant c -n <project_name> --build


-p ... will call command for creating package (rpm)
which creates RPM and SRPM packages


-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>)
./develassistant c -n <project_name> --github <GH_username>
 
which uploads local git repository to GitHub
 
./develassistant c -n <project_name> --eclipse
 
which imports project to eclipse environment. Afterwards user can develop application under eclipse environment


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


== Some notes for GUI==
== Some notes for GUI==
Line 29: Line 36:
''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
 
* 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)
 
 
It would be good to have GUI for creating own assistants (base on YAML configuration file)


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


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


4) Buttons with creating structure, button with creating RPM.
* specify git commands and order


== 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]

Latest revision as of 11:20, 6 March 2013

This page will be used for feature DevelopersAssistant

Repository for that feature is: DevelopersAssistant

Command line arguments (not official)

There are several commands which can be run for building / installation / running project 

./develassistant c -n <project_name>

This will create project in current directory like subdirectory <project_name>.

Command also automatically checks / installs RPM dependencies need by C / C++ programming.

Another commands under C Assistants are: 

./develassistant c -n <project_name> --build

which creates RPM and SRPM packages 

./develassistant c -n <project_name> --github <GH_username>

which uploads local git repository to GitHub 

./develassistant c -n <project_name> --eclipse

which imports project to eclipse environment. Afterwards user can develop application under eclipse environment


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)


It would be good to have GUI for creating own assistants (base on YAML configuration file)

  • specify RPM dependecies
  • specify building operations
  • specify git commands and order

Some hints for editors

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

Retrieved from "https://fedoraproject.org/w/index.php?title=User:Phracek/DevelopersAssistant&oldid=325307"