SciTE4D text editor 0.10 released

(will commit when Brad get setup for it)

People on the D News Group started looking at many editors to see which one was the most useful editor for D. We found SciTE!

The "Package" grew to what it is today with lots of integrated utilities written by D programming language community. Read on for all the details...

Quote Neil Hodgson:"SciTE is a SCIntilla based Text Editor. Originally built to demonstrate Scintilla, it has grown to be a generally useful editor with facilities for building and running programs."

Scite4D contains SEATD for SciTE, D programming language help CHM and build tool ybud.

Enjoy :)

== functionality ==

* Customized Syntax highlighting.

* AutoComplete D keywords, Phobos module name and Tango module name automatically (suggest the option in a dropdownbox while typing), just hit ENTER or TAB to Autocomplete.)

* Code folding for easy code viewing.

* Auto indentation while typing.

* F1 - open D programming language Helpfile on the keyword were the cursor is located.

* Ctrl + Alt + F1 - MSDN search on the keyword were the cursor is located.

* F7 - Debug build.

* Ctrl + F7 - Release build.

* Ctrl + Alt + Shift + D - Build documentation.

* Ctrl + Alt + Shift + T - Run unittest.

* Alt + D - pops up a list of the declarations in the current file.

* Alt + M - pops up a list of modules.

  Selecting a declaration or module in such a list jumps to the first line of the declaration or module.

* F12 - search for a declaration with an identifier equal to the one under the cursor and jump there if successful.

  If you move the cursor over the module name of an import declaration, it will jump to that module.


== Configuration ==

=== Include path ===

SEATD for SciTE has minimal configuration requirements. It only needs an include path to find D source files that correspond to the module names that appear in import statements. If no explicit include path is given, it tries to figure it out by itself.

In order to do so, the path of the current file and it's module name (if available) is used. For example, from a D file "/project/src/pak/bla.d" with a module declaration "module pak.bla;", SEATD for SciTE will extract "/project/src/pak/" and "/project/src/". To specify include paths that are outside of the project's source directory, you can set a global and a local include path.

SEATD for SciTE is configured through SciTE's properties files. To be able to have different settings on installation-, user- and project-level, SciTE allows global-, user- and directory option files. Usually, you only change the user- and directory options.

The global include path is supposed to be set in scite4d\SciTEGlobal.properties, the first line contain the include paths for libraries that all of your projects use (like Phobos or Tango). It is a list of paths separated by ';', for example:

seatd.global.include=c:\dmd\src\phobos;c:\tango\import

To change it, modify the line above accordingly and include it in your user options file.

More details of SEATD for SciTE, please visit: [http://seatd.mainia.de/doc.html SEATD doc]


== ybud usage ==

    ybud use DSSS to build anything.

    ''' 1 ''' Download and install DSSS from:
    [http://www.dsource.org/projects/dsss DSSS]

    Be sure dsss.exe in your environment path variable.

    ''' 2 ''' configurate dsss.conf for your project.

    e.g. to build ybud.exe, assume ybud.d at D:\d\scite4d\ybud.d

    D:\d\scite4d\dsss.conf :
    {{{
    [*]
    buildflags=-explicit -SD:\d\dmd\tango\lib;D:\d\dm\lib -lltango;dwin
    postbuild=del *.obj *.map dsss.last

    [ybud.d]
    debugflags=-g -w -debug=UnitTest -unittest -version=ybudVerbose
    releaseflags=-O -release -inline
    target=ybud
    }}}


    ''' 3 ''' Press F7 or Ctrl + F7 to build your project

    Click scite4d\Sc1.exe to run SciTE4d

    open ybud.d in scite4d

    Press F7 to debug build.

    Press Ctrl + F7 to release build.



== Authors ==

=== 1. SEATD for SciTE 0.01.2 ===

    By Jascha Wetzel [firstname]@mainia.de

    home [http://seatd.mainia.de/ SEATD]

=== 2. D Programming Language 2.001 CHM help ===

    By Vladimir Panteleev <thecybershadow at gmail.com>

    [http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=52020 NG Topic]

    [http://thecybershadow.net/d/docs/d.chm download]

=== 3. simple build tool ybud 0.10 ===

    By yidabu



== Forums ==

Make suggestions and ask questions in the :

[http://bbs.yidabu.com/forum-10-1.html Chinese Forum]


== Home ==



== Maintainer ==

 * yidabu at g m a i l dot com


 == Chinese Version ==


是关于SciTE4D工具的整合.

功能有:

代码高亮

自动完成成D关键词, Phobos, Tango模块名

F1 打开光标所在D关键词的CHM帮助

Ctrl + Alt + F1 搜索MSDN

F7 Debug模式编译

Ctrl + F7 release模式编译

Ctrl + Alt + Shift + D 文档生成

Ctrl + Alt + Shift + T 运行单元测试

Alt + D 弹出声明列表

Alt + M 弹出导入模块列表, 选择并按Enter打开对应模块

F12 打开光标所在标识符定义所在文件，并滚动所在行

一键编译基于DSSS, 你要预先写好dsss.conf, 定义好debugflags和releaseflags。 特别是编译库时比较方便， 打开库里的任意文件， 就可实现一键编译。

目前可以在这里下载

http://svn.dsource.org/projects/dwin/tools/scite4d/

以后可能转移到 http://svn.dsource.org/projects/scite4d





-- 
yidabu <yidabu.nospam@gmail.com>
D Programming Language China:
http://bbs.yidabu.com/forum-10-1.html

Reply to yidabu,

> SciTE4D text editor 0.10 released
> 
> (will commit when Brad get setup for it)
> 
> People on the D News Group started looking at many editors to see
> which one was the most useful editor for D. We found SciTE!
> 
> The "Package" grew to what it is today with lots of integrated
> utilities written by D programming language community.  Read on for
> all the details...
> 
> Quote Neil Hodgson:"SciTE is a SCIntilla based Text Editor. Originally
> built to demonstrate Scintilla, it has grown to be a generally useful
> editor with facilities for building and running programs."
> 
> Scite4D contains SEATD for SciTE, D programming language help CHM and
> build tool ybud.
> 
> Enjoy :)
> 


how do I install?

A lot of people will "just keep looking" if they can't figure this out in about 2 min.

BCS Wrote:

> how do I install?
> 
> A lot of people will "just keep looking" if they can't figure this out in about 2 min.

you are right.

only thing to do is modify includepath at scite4d\SciTEGlobal.properties first line.

If you want to press F7 or Ctrl F7 to build  library or binary ..., be sure configuate dsss.conf first.

Reply to yidabu,

> BCS Wrote:
> 
>> how do I install?
>> 
>> A lot of people will "just keep looking" if they can't figure this
>> out in about 2 min.
>> 
> you are right.
> 
> only thing to do is modify includepath at
> scite4d\SciTEGlobal.properties first line.
> 
> If you want to press F7 or Ctrl F7 to build  library or binary ..., be
> sure configuate dsss.conf first.
> 

that doesn't answer my question. What programs do I need to install (Assume I'm stating with a clean XP install) What file do I need to download? What plugins? Is it a plugin or a stand alone app? I have heard about the things you mention, but only in this NG and I haven't ever even looked into using them before.

What would work well is something like this

""
download this: http://link.to.thing/download/somthing.zip
unzip and run install.exe
download this: http://cool.plug.in/link.blah
install it using command ABC
start program
.
.
.
""

I'm not looking for a full tutorial, or instructions for idiots. But instructions for the ignorant would go a long way.

On Sat, 27 Oct 2007 18:45:00 +0000 (UTC)
BCS <ao@pathlink.com> wrote:

> Reply to yidabu,
> > BCS Wrote:
> 
> that doesn't answer my question. What programs do I need to install (Assume I'm stating with a clean XP install) What file do I need to download? What plugins? Is it a plugin or a stand alone app? I have heard about the things you mention, but only in this NG and I haven't ever even looked into using them before.
> 
> What would work well is something like this
> 
> ""
> download this: http://link.to.thing/download/somthing.zip
> unzip and run install.exe
> download this: http://cool.plug.in/link.blah
> install it using command ABC
> start program
> .

> 
> I'm not looking for a full tutorial, or instructions for idiots. But instructions for the ignorant would go a long way.
> 

Thanks! , BCS

How about this:


== Getting started ==

SciTE4d is a stand alone application. you can figure this out in about 2 min.

1 dowload this:

http://svn.dsource.org/projects/dwin/tools/scite4d/scite4d.zip

2 unzip to ..\scite4d\

3 Click scite4d\Sc1.exe to start program.

4 open scite4d\SciTEGlobal.properties, modify seatd.global.include to fit your libraries path.

If you want to press F7 or Ctrl F7 to build  library or binary ..., be sure configurate dsss.conf first, SciTE4D just find the
dsss.conf and pass command to DSSS.

Enjoy :)

-- 
yidabu <yidabu.nospam@gmail.com>
D Programming Language China:
http://bbs.yidabu.com/forum-10-1.html

yidabu wrote:
> SciTE4D text editor 0.10 released
> 
> (will commit when Brad get setup for it)
> 
> People on the D News Group started looking at many editors to see which one was the most useful editor for D. We found SciTE!
> 
> The "Package" grew to what it is today with lots of integrated utilities written by D programming language community. Read on for all the details...
> 
> Quote Neil Hodgson:"SciTE is a SCIntilla based Text Editor. Originally built to demonstrate Scintilla, it has grown to be a generally useful editor with facilities for building and running programs."
> 
> Scite4D contains SEATD for SciTE, D programming language help CHM and build tool ybud.
> 
> Enjoy :)
> 
> == functionality ==
> 
> * Customized Syntax highlighting.
> 
> * AutoComplete D keywords, Phobos module name and Tango module name automatically (suggest the option in a dropdownbox while typing), just hit ENTER or TAB to Autocomplete.)
> 
> * Code folding for easy code viewing.
> 
> * Auto indentation while typing.
> 
> * F1 - open D programming language Helpfile on the keyword were the cursor is located.
> 
> * Ctrl + Alt + F1 - MSDN search on the keyword were the cursor is located.
> 
> * F7 - Debug build.
> 
> * Ctrl + F7 - Release build.
> 
> * Ctrl + Alt + Shift + D - Build documentation.
> 
> * Ctrl + Alt + Shift + T - Run unittest.
> 
> * Alt + D - pops up a list of the declarations in the current file.
> 
> * Alt + M - pops up a list of modules.
> 
>   Selecting a declaration or module in such a list jumps to the first line of the declaration or module.
> 
> * F12 - search for a declaration with an identifier equal to the one under the cursor and jump there if successful.
> 
>   If you move the cursor over the module name of an import declaration, it will jump to that module.
> 
> 
> == Configuration ==
> 
> === Include path ===
> 
> SEATD for SciTE has minimal configuration requirements. It only needs an include path to find D source files that correspond to the module names that appear in import statements. If no explicit include path is given, it tries to figure it out by itself.
> 
> In order to do so, the path of the current file and it's module name (if available) is used. For example, from a D file "/project/src/pak/bla.d" with a module declaration "module pak.bla;", SEATD for SciTE will extract "/project/src/pak/" and "/project/src/". To specify include paths that are outside of the project's source directory, you can set a global and a local include path.
> 
> SEATD for SciTE is configured through SciTE's properties files. To be able to have different settings on installation-, user- and project-level, SciTE allows global-, user- and directory option files. Usually, you only change the user- and directory options.
> 
> The global include path is supposed to be set in scite4d\SciTEGlobal.properties, the first line contain the include paths for libraries that all of your projects use (like Phobos or Tango). It is a list of paths separated by ';', for example:
> 
> seatd.global.include=c:\dmd\src\phobos;c:\tango\import
> 
> To change it, modify the line above accordingly and include it in your user options file.
> 
> More details of SEATD for SciTE, please visit: [http://seatd.mainia.de/doc.html SEATD doc]
> 
> 
> == ybud usage ==
> 
>     ybud use DSSS to build anything.
> 
>     ''' 1 ''' Download and install DSSS from:
>     [http://www.dsource.org/projects/dsss DSSS]
> 
>     Be sure dsss.exe in your environment path variable.
> 
>     ''' 2 ''' configurate dsss.conf for your project.
> 
>     e.g. to build ybud.exe, assume ybud.d at D:\d\scite4d\ybud.d
> 
>     D:\d\scite4d\dsss.conf :
>     {{{
>     [*]
>     buildflags=-explicit -SD:\d\dmd\tango\lib;D:\d\dm\lib -lltango;dwin
>     postbuild=del *.obj *.map dsss.last
> 
>     [ybud.d]
>     debugflags=-g -w -debug=UnitTest -unittest -version=ybudVerbose
>     releaseflags=-O -release -inline
>     target=ybud
>     }}}
> 
> 
>     ''' 3 ''' Press F7 or Ctrl + F7 to build your project
> 
>     Click scite4d\Sc1.exe to run SciTE4d
> 
>     open ybud.d in scite4d
> 
>     Press F7 to debug build.
> 
>     Press Ctrl + F7 to release build.
> 
> 
> 
> == Authors ==
> 
> === 1. SEATD for SciTE 0.01.2 ===
> 
>     By Jascha Wetzel [firstname]@mainia.de
> 
>     home [http://seatd.mainia.de/ SEATD]
> 
> === 2. D Programming Language 2.001 CHM help ===
> 
>     By Vladimir Panteleev <thecybershadow at gmail.com>
> 
>     [http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=52020 NG Topic]
> 
>     [http://thecybershadow.net/d/docs/d.chm download]
> 
> === 3. simple build tool ybud 0.10 ===
> 
>     By yidabu
> 
> 
> 
> == Forums ==
> 
> Make suggestions and ask questions in the :
> 
> [http://bbs.yidabu.com/forum-10-1.html Chinese Forum]
> 
> 
> == Home ==
> 
> 
> 
> == Maintainer ==
> 
>  * yidabu at g m a i l dot com
> 
> 
>  == Chinese Version ==
> 
> 
> 是关于SciTE4D工具的整合.
> 
> 功能有:
> 
> 代码高亮
> 
> 自动完成成D关键词, Phobos, Tango模块名
> 
> F1 打开光标所在D关键词的CHM帮助
> 
> Ctrl + Alt + F1 搜索MSDN
> 
> F7 Debug模式编译
> 
> Ctrl + F7 release模式编译
> 
> Ctrl + Alt + Shift + D 文档生成
> 
> Ctrl + Alt + Shift + T 运行单元测试
> 
> Alt + D 弹出声明列表
> 
> Alt + M 弹出导入模块列表, 选择并按Enter打开对应模块
> 
> F12 打开光标所在标识符定义所在文件，并滚动所在行
> 
> 一键编译基于DSSS, 你要预先写好dsss.conf, 定义好debugflags和releaseflags。 特别是编译库时比较方便， 打开库里的任意文件， 就可实现一键编译。
> 
> 目前可以在这里下载
> 
> http://svn.dsource.org/projects/dwin/tools/scite4d/
> 
> 以后可能转移到 http://svn.dsource.org/projects/scite4d
> 
> 
> 
> 
> 

Thanks!

Reply to yidabu,

> On Sat, 27 Oct 2007 18:45:00 +0000 (UTC)
> BCS <ao@pathlink.com> wrote:
>> Reply to yidabu,
>> 
>>> BCS Wrote:
>>> 
>> that doesn't answer my question. What programs do I need to install
>> (Assume I'm stating with a clean XP install) What file do I need to
>> download? What plugins? Is it a plugin or a stand alone app? I have
>> heard about the things you mention, but only in this NG and I haven't
>> ever even looked into using them before.
>> 
>> What would work well is something like this
>> 
>> ""
>> download this: http://link.to.thing/download/somthing.zip
>> unzip and run install.exe
>> download this: http://cool.plug.in/link.blah
>> install it using command ABC
>> start program
>> .
>> I'm not looking for a full tutorial, or instructions for idiots. But
>> instructions for the ignorant would go a long way.
>> 
> Thanks! , BCS
> 
> How about this:
> 
> == Getting started ==
> 
> SciTE4d is a stand alone application. you can figure this out in about
> 2 min.
> 
> 1 dowload this:
> 
> http://svn.dsource.org/projects/dwin/tools/scite4d/scite4d.zip
> 
> 2 unzip to ..\scite4d\
> 
> 3 Click scite4d\Sc1.exe to start program.
> 
> 4 open scite4d\SciTEGlobal.properties, modify seatd.global.include to
> fit your libraries path.
> 
> If you want to press F7 or Ctrl F7 to build  library or binary ..., be
> sure configurate dsss.conf first, SciTE4D just find the dsss.conf and
> pass command to DSSS.
> 

Fantastic!! Just right. I;m giving it a try now.

> Enjoy :)
> 

OK, I'm trying scite4d and playing with the F12 feature

given this (and a /little/ more content):

========= module main

char[] generateSummary(Task tasks)
{
	auto distribution = generate.distribution(tasks);  // F12 here
}
========= module generate
void distribution(Task tasks)
{
}
=========
resluts in nothing but "access Violation" being printed in the status window.

Both files are open and what not. If it then go and fix the import settings (as described in your wunderful short how-to) it works.

I'm guessing that access Violations shouldn't happen even if things are set wrong. Also I would think that it should work fine for sibling modules no matter what global.include is set to.

Besides that, SWEEET!!!

BCS wrote:
> OK, I'm trying scite4d and playing with the F12 feature
> 
> given this (and a /little/ more content):
> 
> ========= module main
> 
> char[] generateSummary(Task tasks)
> {
>     auto distribution = generate.distribution(tasks);  // F12 here
> }
> ========= module generate
> void distribution(Task tasks)
> {
> }
> =========
> resluts in nothing but "access Violation" being printed in the status window.
> 
> Both files are open and what not. If it then go and fix the import settings (as described in your wunderful short how-to) it works.
> 
> I'm guessing that access Violations shouldn't happen even if things are set wrong. Also I would think that it should work fine for sibling modules no matter what global.include is set to.
> 
> Besides that, SWEEET!!!
> 
> 

that is a bug in SEATD, could you send me everything i need to reproduce this, please?

Reply to Jascha,

> BCS wrote:
> 
>> OK, I'm trying scite4d and playing with the F12 feature
>> 
>> given this (and a /little/ more content):
>> 
>> ========= module main
>> 
>> char[] generateSummary(Task tasks)
>> {
>> auto distribution = generate.distribution(tasks);  // F12 here
>> }
>> ========= module generate
>> void distribution(Task tasks)
>> {
>> }
>> =========
>> resluts in nothing but "access Violation" being printed in the status
>> window.
>> Both files are open and what not. If it then go and fix the import
>> settings (as described in your wunderful short how-to) it works.
>> 
>> I'm guessing that access Violations shouldn't happen even if things
>> are set wrong. Also I would think that it should work fine for
>> sibling modules no matter what global.include is set to.
>> 
>> Besides that, SWEEET!!!
>> 
> that is a bug in SEATD, could you send me everything i need to
> reproduce this, please?
> 

========= module main
import generate;

char[] generateSummary(Task tasks)
{
auto distribution = generate.distribution(tasks);  // F12 here
}
========= module generate
void distribution(Task tasks)
{
}
=========
I thikn that will do it. If not (I'l chek later) I'll figure out what does and sen it in.