Here the link http://sourceforge.net/p/amiblitz3/code/log/ it shows the always the up to date changelog.

Ok, here we go again.
This is another little Project from me to learn more about of the usage of Ntui

Have a look at the Screenshot:

[ATTACHMENT NOT FOUND]

• you can wrote or edit xmlfiles for/from Ntui
  
• you can always show what you are doing by clicking the Showbutton
  
• you can save your hard work.
  
• you can load new Files by a Filerequester or easy by Windrop
  
• you can start NtuiCreator also from Shell
  

ok, here is my Project for a new Gui to handel the svn-commands a little bit easyer...

Have a look at the Screenshot:
[ATTACHMENT NOT FOUND]

• You can use it to checkout a Workingcopy from a Repository
  
• Update a Workingcopy
  
• Cleanup a WorkingCopy
  
• Show the Status of the Workingcopy
  
• Add or Remove Files or Drawers to/from the Repository
  
• Let you show some infos of files of the Workingcopy
  
• Cleanup a locked Workingcopy

• Programmdocumentation
  
• Diff between Workingcopy and Repository
  
• Create a new Repository
  
• Commit filechanges
  
• and many more

Syntax Highlightning (or any other formatting of the text) in NTUI is called "styling".
This is how it works for now (Function names will change slightly in final NTUI), since don't want to expose newtypes.

[ab3]myStyleCallback:
Function.l myStyleCallback{*textBox.tuiTextBox,lpos.l,*tline.tline}

*tline\sclength = 0 ; reset the style information
cpos.l = 0 ; start at character position 0

While cpos<*tline\clength ; go through the whole line
c.b = Peek.b(*tline\text+cpos) : cpos+1 ; grab a character

Select c
Case @"a" ; if we see an "a"...

; make it bold and red
_tb_SetStyleCommand{*tline,cpos-1,#TUITBSC_BOLD,1}
_tb_SetStyleCommand{*tline,cpos-1,#TUITBSC_FGPEN,#TUITBPEN_RED}

; and return to normal
_tb_SetStyleCommand{*tline,cpos,#TUITBSC_BOLD,0}
_tb_SetStyleCommand{*tline,cpos,#TUITBSC_FGPEN,#TUITBPEN_TEXT}

Default
; nothing happens for other characters

End Select

Wend

*tline\flags|#TUITBLF_STYLED ; mark the line as styled
Function Return #TUISCB_DONE ; tell NTUI we are done

End Function
; this creates a global variable "*myStyleCallback" that points to our functions
; and tells AmiBlitz3 not to remove the function, since it is never called directly
!_MakeGlobalFuncPointer{myStyleCallback,{Null,0,Null}}

...
ntui_SetAttr{*textBox,#TUITBA_STYLECB,*myStyleCallback} ; attach the callback function to the textbox
...
ntui_SetAttr{*textBox,#TUITBA_STYLECB,Null} ; remove the callback function from the textbox[/ab3]

There are a few things to mention:
1. The example makes all "a"'s in the text bold and red.

2. You don't have to remove the callback when you free the textBox. This is only necessary if you want to make sure it will never called again, e.g. if your style callback allocated resources that you want to free before NTUI.

3. Between the label "myStyleCallback:" and the function declaration MUST NOT be any code.

4. It is allowed to write to the text buffer (Poke), but the length MUST be preserved. E.g. Casing can be altered. Note that you are actually changing the text buffer. If you just want to just format for display, you need "Style Commands" for this.

5. There are many "Style Commands", not only bold and colors. See TUITBSC_... for more. New commands can be easily added if necessary.

6. To style the text, you don't need a StyleCallback. You can also go through the whole text and style it. However, the style callback has so many advantages that you really want to use it. E.g., you don't need to parse the whole text, only the visible lines (=much faster). It also keeps track while editing the text line.

7. If you parse a line and the result may affect the next or previous line (e.g. multi-line comment), you need to return #TUISCB_NEXT or #TUISCB_PREV instead of #TUISCB_DONE. You can store the parser state as flags in *tline\flags. There are currently two flags, #TUITBLF_INCOMMENT and #TUITBLF_INTAG.

8. If the highlightning is more complex that just tracking a character, I highly recommend using a stack-based parser rather than a state machine.
99% of all programming languages can be parsed by a stack based parser with lookahead of 1 or 2 characters. I can give an example if there is interest.

Ich möchte in AB3 Labels erzeugen, die mir ermöglichen, an bestimmte Stellen zu springen. Im Optimalfall würde ich immer das gleiche benutzen, nämlich das Tape .o__o

Da man natürlich nicht mehrmals dasselbe Label verwenden kann, muß ich mein Tape immer etwas abwandeln.

Gibt es für diesen Fall eine elegantere Lösung?

edit
Hm. z.B. eine Direktive "Dummylabel = .o__o" oder so?

Hallo Thilo,

Wird denn bei der angabe im xml seit neuesten kein iconifygadget mehr im Window erzeugt, oder ging das noch nie ?
In AIDE machst du das ja per Menü...

Hallo Thilo,

Wäre es nicht cool wenn dein Tab auch ein Closegadget beinhalten würde ?

Amiforce ist wieder erreichbar. In einem Post teilt Franz mit woran es lag und wie es weitergehen soll mit der Seite.
http://www.Amiforce.de/thread.php?thread...&boardid=1

Hinter den Kulissen bin ich permanent dabei das Forum und die Site zu verbessern. Auf der ToDo stehen derzeit:

• anpassen der Farben für den Syntaxhighlighter an die original AB3 IDE Farben
  
• anpassen der Code-Farben für Blitz2 Chipset-Befehle
  
• anpassen des SyntaxHighlighter damit dieser auch Funktionen highlighted die auf {} hören
  
• anpassen der "Subsilver" Icons an die "AmiBlitz3 CI"
  
• Einbindung des SAE in die Website, so dass ihr in ferner Zukunft Eure Projekte auch Leuten zeigen könnt die keinen Amiga oder eine Emulation ihr Eigen nennen.

Hallo,

Wenn ich einen Text ins Textboxwidget einlese, warum wird das dann nicht automatisch refresht ?
Muß ich das selbst machen ?