Hi

Execellent!

Yes upon doing a fresh install I also found that it was necessary to use the 
cpp lexer  for flash. However,the style.flash.* definitions seemed to work 
already without changig them to style.cpp.*... I also posted the following the 
scite-instreset mailing list:
-------------------------
I want to edit flash/actionscript in Linux (Ubuntu 6.06). The  scite 
installation in the package manager is 1.67. I have used the discontinued 
Scite|Flash distribution for windows and would like to incorporate some of its 
features into the linux version. Sorry for the long mail, but I've been 
struggling with this for a couple of days so I'll explain my problems in detail.

The first thing I'm unsure about is the extent of built in flash support in the 
Linux version. Falsh(actionscript) is listed as a supported language for scite. 
When I open a .as file I get correct syntax highlighting and code folding, but 
there is no properties file and no language selection option (even amongst the 
commented ones in the global properties file). I would like to edit the compile 
and build commands to use a makefile, but since there is no properties file, I 
don't know how to proceed.

I have  copied the flash.properties, flash.api, API.flashcommClient, 
API.flashcommServer files from the scite|flash windows distribution into my 
/usr/share/scite directory where all the other properties files are located. 
After adding 'import flash' to the sciteglobal.properties all code highlighting 
disappears.
I assume this is because of the command 

lexer.$(file.patterns.flash)=flash

in flash.properties and that there is no lexer named flash outside of 
scite|flash. If I change this to 

lexer.$(file.patterns.flash)=cpp

, I get the correct syntax highlighting in the style specified by 
flash.properties. I can also edit the compile options in flash.properties to my 
liking with the correct effect. I can also successfully add flash to the 
language selection menu.

However, code I cant get auto completion and call tips working properly. If I 
add "autocompleteword.automatic=1" to my sciteuser.properties I get auto 
completion on keywords and functions the second time I use them in a file. Is 
this normal?  Also  call tips are not functioning at all, in spite of the 
inclusion of flash.api and the following lines in flash.properties

####################### 
#    Load the Flash API 
#######################    
api.$(file.patterns.flash)=$(SciteDefaultHome)\flash.api;$(SciteDefaultHome)\API.custom;API.flashcommClient;API.flashcommServer;
 
    autocomplete.flash.ignorecase=1 

The only reference to call tips in sciteglobal.properties is 
#calltip.back=#FFF0FE which doesn't activate call tips if I uncomment it.

To summerise:
    1) Is there a different lexer i should use instead of cpp (a built in flash 
lexer)?
    2) Is there a way to get the auto completion to give all the options listed 
in the flash.properties file without having used them in the file being edited?
    3)How do I get call tips working?
------------------------
Cheers
Izak


Zárate <[EMAIL PROTECTED]> wrote: Hi there,

I've contacted Ale who is the original creator of SciteFlash. He has
kindly accepted helping us figure out what's going on. Here's a quick
translation of his emails:

---------------------

First thing to do replace in flash.properties:

lexer.$(file.patterns.flash)=flash
lexer.$(file.patterns.flash2)=flash

with

lexer.$(file.patterns.flash)=cpp
lexer.$(file.patterns.flash2)=cpp

To use default C++ lexer.

Then, in flash.properties look for lines starting with style.flash.*.
Those are keywords for each lenguage lexer. Changing them to
style.cpp.* will bring highlights again [because we've changed to C++
lexer].
---------------------------

And that's it for now. For the time being this is what we have to
start looking at the problem. Nevertheless, I'll chase him up because
i'm really interested in bringing SciteFlash up to life again so we
have a decent lightweight IDE for Flash in Linux.

Cheers!

Juan

On 7/18/07, izak marais  wrote:
> Hi Zárate
>
> Hmm, something is strange. I got the same behaviour you describe on my home
> ubuntu box. But on my office ubuntu works it fine. I'll have to check and
> figure out what the differences between the two setups is.
>
> On my home box, after adding "import.flash" to the global sicte properties
> file, it definitely reads flash.properties since the 'compile' and 'build'
> menu options change to those specified in flash.properties, but the color
> highlighting disappears. My guess is that something in the lexer
> specification is stopping it from being read. But comparing flash.properties
> to the other language.properties files it appears the same.
>
> Like Matt said, AS syntax is similar to JS and also close to C/C++, so I
> assume that's why there is some syntax highlighting and code folding
> initially.
>
> No, I code completion will not work for your own classes, since it loads the
> information from flash.api. If you edit API.custom to include them, it might
> work. But for that the other more basic stuff must work first! Perhaps we
> should seek help on the scite mailing list, if there is one.
>
> I'll let you know when I figure something out.
>
> Matthias: from the osflash tutorials conclude that ASDT does not support the
> natural entry point method? I might try it again in the future, but since I
> already use scite for my python and c needs, and I find eclipse to be slow,
> I currently prefer scite. I'll try to file a bug report on that ASDT file
> opening problem soon.
>
> Cheers
> Izak
>
> Zárate  wrote:
>  It doesn't work for me ¬¬
>
> I'm using Scite version 1.71-1 (from Synaptic in Ubuntu) and the very
> moment I import flash.properties in SciteGlobalProperties, it just
> stops colour highlighting.
>
> I've been messing around a lot installing and unstalling, trying to
> tweak config files but no luck. Did you even manage to get
> autocompletition for your own classes?
>
> Thanks
>
> Juan
>
> On 7/17/07, Zárate wrote:
> > Hello!
> >
> > I'm using Scite too in Ubuntu for Flash development and i managed to
> > do some of the work you described above but didn't go that far. THANKS
> > a lot :)
> >
> > On 7/17/07, izak marais wrote:
> > > Ok, I've tested the scite setup I descibed in my previous mail and it
> also
> > > jumps to the line where mtasc spesifies an error. Happy coding.
> > >
> > >
> > >
> > > ________________________________
> > > Be a better Heartthrob. Get better relationship answers from someone who
> > > knows.
> > > Yahoo! Answers - Check it out.
> > >
> > >
> > > _______________________________________________
> > > osflash mailing list
> > > [email protected]
> > > http://osflash.org/mailman/listinfo/osflash_osflash.org
> > >
> > >
> >
> >
> > --
> > Juan Delgado - Zárate
> > http://zarate.tv
> > http://dandolachapa.com
> > http://loqueyosede.com
> >
>
>
> --
> Juan Delgado - Zárate
> http://zarate.tv
> http://dandolachapa.com
> http://loqueyosede.com
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>
>  ________________________________
> Luggage? GPS? Comic books?
>  Check out fitting gifts for grads at Yahoo! Search.
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>


-- 
Juan Delgado - Zárate
http://zarate.tv
http://dandolachapa.com
http://loqueyosede.com

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org


       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to