i’d love to get involved with this one, especially for adding/providing support for Oyxgene/Delphi Prism (http://remobjects.com/oxygene) as inline language.
Any involvement would be welcomed. Eric has been working on adding support for <asp:> controls and I have been adding basic support for syntax highlighting in VB as well as codesense completions for keywords etc.. At some point I also hope to be able to add completions for .Net’s built in classes but have yet to find a definitive list of these (I hope to be be able to parse the XML files from the framework using XSLT to do this) but at present I am working on putting together good solid support for the syntax.
I have no experience with Oxygene itself (although I do have a little with Delphi a few years ago) but adding as much support would be very welcome. I have found the JavaScript to be sugar an excellent starting place for my VB work in terms of understanding how the syntaxes and codesense works etc.
not having looked at the actual sugars yet myself, would you recommend i start by getting a plain Oxygene sugar working (need that anhhow , and we later integrate that with the ASPX one, or would that be radically differet from whats needed to have Oxygene integrated with the APSX one?
is the current work-in-progress on yours available someplace? if not, i’d be happy to set up a public SVN space on one of our servers that we can use…
My knowledge of Oxygene is practically non existent other then some quick reading this morning. I know that Eric has been working on the ASPX side of things and I on the VB and so far these are separate sugars only because I started independently of him really. Eric has set up a repo over at beanstalk and would probably be worth PMing him for access. It would probably be worth working on a separate Oxygene sugar for the in-line code stuff but to also integrate with Eric’s ASPX work for the controls etc.
I will be more than happy to post what I have done so far for you to have a look at - it is far from complete and there are still a few bits that I am trying to figure out but it may help point you in the right direction. I sans power supply for my laptop currently but as soon as I get that sorted I’ll put it up for you.
One of the things I had wanted to implement as part of this sugar was document parsing such that user function could be displayed as part of the code completions - similar to the way that visual studio works. According to Jan (See PHP Sugar post) this is not going to be possible in version 1.0 and I wanted to clarify that here. However through the magic of itemizers it will be possible to display the hierarchy of a document including namespaces, classes, regions, functions and subs etc which is something the VS doesnt do.
So I really don’t have any way to have ASP .NET code highlighting in Espresso? I hate to pull the inevitable Coda comparison, but at my workplace .NET is the standard and Espresso’s missing functionality is increasingly becoming a problem. Anyone have any suggestions?
Language Sugars are simple XML with some regex to define the various parts of the language. Since no one has created an ASP.sugar up to now, your best option if you need one is to create it yourself.
Respectfully, I understand that you’re limited in what responses you can provide, but “make one yourself” is mildly insulting—sugar creation is based on the rules of the particular language, which is exactly what I’m asking assistance for in the first place! Another option would be to use a competing program that provides this functionality out-of-the-box.
I am sorry to hear you are insulted, but that is the most constructive suggestion I can offer. You could alternatively try to set a bounty on an ASP.sugar, but so far as I know that has not been terribly successful for other people.
We are more than happy to help people with Sugar development because offering first-party support for every language is not currently possible for us. If you are uninterested in that, there is not much else we can offer at this point in time. :-\
Only mildly insulted. I think that you have a very courteous tone here in the forums and I’m probably just frustrated that I haven’t seen more development progress on Espresso and CSSEdit. Sorry to get all complainy on you.
, and we later integrate that with the ASPX one, or would that be radically differet from whats needed to have Oxygene integrated with the APSX one?
I think that you have a very courteous tone here in the forums and I’m probably just frustrated that I haven’t seen more development progress on Espresso and CSSEdit. Sorry to get all complainy on you.