api-file problems when calltip.*.parameters.start char not exists

hi,
i've created a api-file for javascript (attachment) and the following 
definition in SciteUser.properties:

api.*.js=\
$(SciteDefaultHome)\api\jscript.api;
calltip.javascript.ignorecase=1
calltip.javascript.end.definition=#
autocomplete.javascript.fillups=(
calltip.javascript.word.characters=$(chars.alpha)$(chars.numeric).
calltip.javascript.parameters.start=(
calltip.javascript.parameters.end=)
calltip.javascript.parameters.separators=,

this api-file contains functions (with brackets) and properties without 
brackets.
i think scite should first search for *.end.definition and then for 
parameters.start.

how to fix it?

regards Frank

length #Reflects the number of elements in an array/string. 
#array:
pop() #Removes the last element from an array and returns that element. 
push(element1,...,elementN) #Adds one or more elements to the end of an array and returns the new length of
the array. 
reverse() #Reverses the order of the elements of an array -- the first becomes the last, and the last becomes

Re: HTML/CSS Extra Commands for SciTE (David White)

> 	A color picker tool that returns the hex-color code

I've been looking for a while now for something close to this. Does
anyone know of a color picker which will also take a hex code on input
and select it? (Using this with CurrentWord would be very nice). I could
get my lazy butt to do it, but then it wouldn't be so lazy.

Oh, and another useful addition when using SciTE for HTML is setting it
as your browser's source editor.

_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest

Re: Re: HTML/CSS Extra Commands for SciTE (David White)

Gonzalo García Braschi wrote:
>> 	A color picker tool that returns the hex-color code
> 
> I've been looking for a while now for something close to this. Does
> anyone know of a color picker which will also take a hex code on input
> and select it? (Using this with CurrentWord would be very nice). I could
> get my lazy butt to do it, but then it wouldn't be so lazy.

There are so many nice free image editors around, I wonder why 
people are so enamored of the all-in-one uber IDE application 
model. I just use different applications for different tasks. 
*shrug* 

> Oh, and another useful addition when using SciTE for HTML is setting it
> as your browser's source editor.

--

-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia

Re: HTML/CSS Extra Commands for SciTE (David, White)

> There are so many nice free image editors around, I wonder why 
> people are so enamored of the all-in-one uber IDE application 
> model. I just use different applications for different tasks. 
> *shrug* 

I'm not looking for an all-in-one uber IDE, much less for an image
editor. What I was commenting was just a small external utility that
would let me simply visualize a color.

>*shrug*
Yeah, *shrug*

_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest

Re: HTML/CSS Extra Commands for SciTE

_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest

Re: Re: HTML/CSS Extra Commands for SciTE (David White)

Hello Everyone,

A very big thank you to all who responded!! I'm slowly working my way 
through all the suggestions and utils (Thanks for the en lang files)!

I am also a big fan of Irfanview but I could only get it to open a 
CurrentSelection in SciTE when IView is in fullscreen mode.

i gives you image specs and ctrl+r allows resizing, however...but access 
to IView's complete menu would be nice.

Best of Luck,
Dave White

Gonzalo García Braschi wrote:
>> 	A color picker tool that returns the hex-color code
> 
> I've been looking for a while now for something close to this. Does
> anyone know of a color picker which will also take a hex code on input
> and select it? 

I looked also...but no luck...great idea though!
I'll let you know if I find anything.

(Using this with CurrentWord would be very nice). I could
> get my lazy butt to do it, but then it wouldn't be so lazy.
> 
> 
> Oh, and another useful addition when using SciTE for HTML is setting it
> as your browser's source editor.
> 
> _______________________________________________
> Scite-interest mailing list
> Scite-interest <at> lyra.org
> http://mailman.lyra.org/mailman/listinfo/scite-interest

Re: api-file problems when calltip.*.parameters.start char not exists

Frank Wunderlich:

> i've created a api-file for javascript (attachment) and the following
> definition in SciteUser.properties:
>
> api.*.js=\
> $(SciteDefaultHome)\api\jscript.api;
> calltip.javascript.ignorecase=1

   There is no lexer called "javascript". The javascript language uses
the "cpp" lexer as specified in cpp.properties:
lexer.*.js=cpp

   Neil

Directory properties file

  Stefan Schwendeler implemented the directory properties feature
discussed in January. A single SciTEDirectory.properties file sets
options for the directory it is in and its subdirectories. A
simplified version of his code can be downloaded from

http://scintilla.sourceforge.net/scite.zip Source
http://scintilla.sourceforge.net/wscite.zip Windows executable

   To use this feature, it must first be turned on with
properties.directory.enable=1 (should probably be renamed to
properties.directory for consistency). Whenever a file is opened or
switched to, directory properties are read as well as local
properties. The directory properties file is called
SciTEDirectory.properties and is opened from the same directory as the
file being opened or switched to. If there is no
SciTEDirectory.properties file in that directory then the parent
directory is checked and so forth up the path until
SciTEDirectory.properties is found or the root is reached.

   I found the behaviour a little strange. If there is no active
directory properties file then the Open Directory Options File command
opens one in the same directory as the current file. This is the most
obvious behaviour but I normally expect that the file will go into a
parent directory.

   The code is not committed to CVS yet as I'm not certain about it.

   Neil

Re: api-file problems when calltip.*.parameters.start char not exists

Neil Hodgson, 02.03.2007 00:31:
> Frank Wunderlich:
> 
>> i've created a api-file for javascript (attachment) and the following
>> definition in SciteUser.properties:
>>
>> api.*.js=\
>> $(SciteDefaultHome)\api\jscript.api;
>> calltip.javascript.ignorecase=1
> 
>   There is no lexer called "javascript". The javascript language uses
> the "cpp" lexer as specified in cpp.properties:
> lexer.*.js=cpp

i've tried like this:

api.$(file.patterns.cpp)=\
$(SciteDefaultHome)\api\cpp.api;\
$(SciteDefaultHome)\api\c.api;

api.*.js=\
$(SciteDefaultHome)\api\jscript.api;

calltip.cpp.ignorecase=1
autocomplete.cpp.fillups=(
calltip.cpp.word.characters=$(chars.alpha)$(chars.numeric).
calltip.cpp.parameters.start=(
calltip.cpp.parameters.end=)
calltip.cpp.parameters.separators=,
calltip.cpp.end.definition=#

but also unsuccessful...

Frank

Re: Re: HTML/CSS Extra Commands for SciTE (David, White)

Gonzalo García Braschi wrote:
>> There are so many nice free image editors around, I wonder why 
>> people are so enamored of the all-in-one uber IDE application 
>> model. I just use different applications for different tasks. 
>> *shrug* 
> 
> I'm not looking for an all-in-one uber IDE, much less for an image
> editor. What I was commenting was just a small external utility that
> would let me simply visualize a color.
> 
>> *shrug*
> Yeah, *shrug*

Sorry, I was commenting about the previous postings in the thread, 
not your posting. Too much integration == hand-holding + tunnel 
vision.

--

-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia