website rev 832
en: edit devel/forge
author | Paul Issott <paul@slitaz.org> |
---|---|
date | Thu Apr 28 22:47:01 2011 +0100 (2011-04-28) |
parents | c179925b46d5 |
children | de9b09114bc3 |
files | en/devel/forge.php en/devel/index.php |
line diff
1.1 --- a/en/devel/forge.php Thu Apr 28 16:08:37 2011 +0200 1.2 +++ b/en/devel/forge.php Thu Apr 28 22:47:01 2011 +0100 1.3 @@ -186,29 +186,29 @@ 1.4 <h2>GUI - Pure C/GTK, Yad, Vala/Genie and CGI/web</h2> 1.5 1.6 <p> 1.7 - We have many way to create user interface in the open source world. From 1.8 - the start of the project until 3.0 we mainly used a tool called Gtkdialo 1.9 - who let us create nice and quiet complex interfaces in GTK but with a 1.10 - scripting language, no compilation, just run. But gtkdialog in unmaintained 1.11 - and lack about new GTK features, so we switched to Yad for simple GUI boxes. 1.12 - For all the admin, packages and configuration tools we switched to TazPanel, 1.13 - a CGI/web interface with all the gui in xHTML 5 and CSS 3. 1.14 + There are many ways to create user interfaces in the open source world. From 1.15 + the start of the project until 3.0 we mainly used a tool called Gtkdialog 1.16 + which let us create quite nice and complex interfaces in GTK, but using a 1.17 + scripting language that just run without having to be compiled. But gtkdialog is 1.18 + unmaintained and lacks many new GTK features, so we switched to Yad for simple GUI boxes. 1.19 + For all the administration, packages and configuration tools we switched to TazPanel, 1.20 + a CGI/web interface with a gui coded in xHTML 5 and CSS 3. 1.21 </p> 1.22 <p> 1.23 - Now we Yad is very simple and dont allow us to create complex interface even 1.24 - if we just need 2 or 3 entry with label and a few buttons, so an other way 1.25 - must be used. The advantage of a scripting language is the fact we dont need 1.26 - to compile and can code in relatime, but it produce a slower applications. 1.27 - All in C is complex and we got less contributor since SHell script are easier 1.28 - to understand, so the guide line now is to keep and continue improving our 1.29 - cmdline tools and provide frontend in GTK or CGI/web. 1.30 + Yad is very simple but doesn't allow us to create complex interfaces even if we 1.31 + only need 2 or 3 entries with labels and a few buttons, so another way 1.32 + must be found. The advantage of a scripting language is the fact that it doesn't need 1.33 + to be compiled and can be coded in realtime (but it produces slower applications). 1.34 + Writing tools in C is complex and gets less contributions since SHell scripts are easier 1.35 + to understand, so the guidelines are now to keep and continue to improve our 1.36 + cmdline tools and provide frontends in GTK or CGI/web. 1.37 </p> 1.38 <p> 1.39 - They is many new languages who let use GTK such as Genie, Vala or GTKaml. 1.40 - But keep in mind ther are not so popular than C and GTK and finaly not realy 1.41 - easier to learn and use, at least for simple fronted you finally use SHell 1.42 - scripts to perform tasks. Use can use Vala if you like but look at a pure 1.43 - GTK single window, it only 14 lines: 1.44 + There are many new languages that use GTK such as Genie, Vala or GTKaml. 1.45 + But keep in mind that they are not as popular as C and GTK and not really 1.46 + easier to learn and use (for simple frontends you can use SHell 1.47 + scripts to perform tasks). You can use Vala but look at a pure 1.48 + GTK single window, it uses only 14 lines: 1.49 </p> 1.50 <pre> 1.51 #include >gtk/gtk.h< 1.52 @@ -228,19 +228,19 @@ 1.53 } 1.54 </pre> 1.55 <p> 1.56 - If you not sure about the language to use, discuss it on the mailing list. 1.57 + If you are not sure about which language to use, discuss it on the mailing list. 1.58 If you just want a small GUI function, look at tazbox in the slitaz-tools 1.59 - repo, it have tiny desktop tools such as a logout box. By the way the first 1.60 - SliTaz sub-project all written in pure GTK is TazWeb and you may learn 1.61 - some way to use system() to include system commands in your frontend. For 1.62 - example TazWeb use wget for downloads and sed to add bookmarks. 1.63 + repo, it has tiny desktop tools such as a logout box. The first 1.64 + SliTaz sub-project written in pure GTK is TazWeb and you can use it to learn 1.65 + ways to use system() to include system commands in your frontend. For 1.66 + example TazWeb uses wget for downloads and sed to add bookmarks. 1.67 </p> 1.68 <p> 1.69 Yad scripts should follow TazYad guidelines: 1.70 <a href="http://hg.slitaz.org/slitaz-dev-tools/raw-file/tip/tazyad/README"> 1.71 README</a> and 1.72 <a href="http://hg.slitaz.org/slitaz-dev-tools/raw-file/tip/tazyad/tazyad"> 1.73 - exmaple code</a> 1.74 + example code</a> 1.75 </p> 1.76 1.77 <a name="iconv"></a>
2.1 --- a/en/devel/index.php Thu Apr 28 16:08:37 2011 +0200 2.2 +++ b/en/devel/index.php Thu Apr 28 22:47:01 2011 +0100 2.3 @@ -76,11 +76,11 @@ 2.4 2.5 <ul> 2.6 <li><a href="forge.php">Forge</a> - Collaborative management, KISS, 2.7 - guideline, Mercurial repo, website and other services</li> 2.8 - <li><a href="../../i18n.php">Internationalisation project</a> - 2.9 - Translation, goals and management.</li> 2.10 + guidelines, Mercurial repos, website and other services.</li> 2.11 + <li><a href="../../i18n.php">Internationalization project</a> - 2.12 + Translation, goals and management.</li> 2.13 <li><a href="http://hg.slitaz.org/" >Mercurial Repositories</a></li> 2.14 - <li><a href="http://bts.slitaz.org/">SliTaz Bugs Tracker</a></li> 2.15 + <li><a href="http://bts.slitaz.org/">SliTaz Bug Tracker</a></li> 2.16 </ul> 2.17 2.18 <a name="devel"></a>