Wiki: suggest improvements
Posted: 01 November 2008 05:26 PM   [ Ignore ]
Administrator
RankRankRankRank
Total Posts:  106
Joined  2008-10-27

The Espresso wiki is still very much a work in progress, and some parts probably need much more attention. If you think the wiki needs more info on a particular subject, or you have other suggestions: post here!

Profile
 
 
Posted: 01 November 2008 06:39 PM   [ Ignore ]   [ # 1 ]
Moderator
RankRankRankRank
Total Posts:  1249
Joined  2008-10-28

I think a file-by-file explanation of how a Sugar works would be a really good idea.  The overall explanation of sugars was a little too high-level for me to figure out what the heck it was talking about when I read it.  I had to take a really close look at the existing sugars before I started to get a feel for how things interconnected.

If you’re interested in user contributions for the wiki, I could start this topic (I think I have a half-way decent understanding of what’s going on in a Sugar after playing with them last night).  However, you’ve got the full story so it might just be easier for you to write it yourself.

Some way to navigate between articles (without needing to jump back to the index page) would also be really helpful.

 Signature 

Ian Beck
MacRabbit Support

Follow us on Twitter, or try my custom themes: Quiet Light & Earthworm

Profile
 
 
Posted: 02 November 2008 02:52 PM   [ Ignore ]   [ # 2 ]
Member
RankRankRank
Total Posts:  81
Joined  2008-10-28

A bit more information on the scope selectors (storage.type, constant.language, etc) would be nice. I’m basically just looking at what TextMate does ATM.

Profile
 
 
Posted: 02 November 2008 08:40 PM   [ Ignore ]   [ # 3 ]
Newbie
Rank
Total Posts:  10
Joined  2008-10-28

You could of course give us something about code formatters, i have been trying to do that for some time. And why on earth there isn’t a formatter rule for <in zone>, only after and before?

 Signature 

Which one comes first, Espresso with CodeSense or xCode for PHP?

Profile
 
 
Posted: 05 November 2008 07:50 AM   [ Ignore ]   [ # 4 ]
Sr. Member
RankRankRankRank
Total Posts:  232
Joined  2008-11-05

I’m very confused about how the current names map to highlighting. Is that something internal, or is that just how your current (only) ‘theme’ chooses to highlight? For instance, I had to mark class definitions in Ruby as a “storage.type” to get them to highlight, which seemed so very, very wrong. A wiki page describing naming conventions would be nice — especially if anybody could edit it! I’d really like to see some conventions laid down by Sugar developers and Theme (or whatever they will eventually be called) developers, so that most Themes work well with most Sugars and vice-versa.

 Signature 

Ruby.sugar | Rails.sugar? | Haml.sugar | SASS.sugar | Sugar Manager.sugar | Git.sugar | Regex.sugar | ERb.sugar | RSpec.sugar

http://elliottcable.name/contact.xhtml

Profile
 
 
Posted: 11 November 2008 07:05 PM   [ Ignore ]   [ # 5 ]
Moderator
RankRankRankRank
Total Posts:  1249
Joined  2008-10-28

I’ve added the file-by-file thing I requested to the SugarBasics article; definitely people should give it a once-over and make changes where appropriate.  Goal of it was to establish the relationships between the files a bit better right off the bat, along with making it explicitly clear what each file is doing.

For anyone who wants to edit the wiki, we appear to be using Textile for formatting along with ExpressionEngine’s pMCode and wiki link sytnax.

 Signature 

Ian Beck
MacRabbit Support

Follow us on Twitter, or try my custom themes: Quiet Light & Earthworm

Profile
 
 
Posted: 12 November 2008 12:03 PM   [ Ignore ]   [ # 6 ]
Newbie
Rank
Total Posts:  10
Joined  2008-10-28

Something about CodeSenseLibraries and CodeSenseProviders (CodeSense is a… well a bit misleading name since codesense usually means that the code is parsed, sensed)

 Signature 

Which one comes first, Espresso with CodeSense or xCode for PHP?

Profile
 
 
Posted: 14 November 2008 10:46 PM   [ Ignore ]   [ # 7 ]
Administrator
RankRankRankRank
Total Posts:  106
Joined  2008-10-27
George the Flea - 11 November 2008 07:05 PM

I’ve added the file-by-file thing I requested to the SugarBasics article; definitely people should give it a once-over and make changes where appropriate.  Goal of it was to establish the relationships between the files a bit better right off the bat, along with making it explicitly clear what each file is doing.

For anyone who wants to edit the wiki, we appear to be using Textile for formatting along with ExpressionEngine’s pMCode and wiki link sytnax.

Ian, awesome!
Profile
 
 
Posted: 20 November 2008 01:57 AM   [ Ignore ]   [ # 8 ]
Administrator
RankRankRankRank
Total Posts:  106
Joined  2008-10-27

As of now the Wiki should have documentation on everything Sugars offer. I’m sure some articles could still use some clarification though—so suggestions are still welcome! You can also edit the Wiki if you think a crucial part of info is missing and you know just what to say.

Profile
 
 
Posted: 01 December 2008 04:18 AM   [ Ignore ]   [ # 9 ]
Member
RankRankRank
Total Posts:  76
Joined  2008-11-04

Just wondering if CodeSense providers can use start/end-selector?

This would mean it would be easy to add codesense to particular items, rather then just single selectors.

Profile
 
 
Posted: 02 March 2009 03:07 AM   [ Ignore ]   [ # 10 ]
Moderator
RankRankRankRank
Total Posts:  1249
Joined  2008-10-28

I’d love to see the Actions section of the wiki expanded.  In particular:

- Need descriptions of the new sorting capabilities of beta3
- Need descriptions of the completion and keyboard equivalent tags (I think I have these pretty well figured out, but am leery of writing what I’ve figured out as fact since I don’t know whether you’ve finalized the specs for these tags)
- A link to a page with some details about what Textmate features for text snippets you support would also be very helpful
- I also discovered action-aliases in the default Sugars, but couldn’t quite figure out what their capabilities were; this would be another helpful tidbit of info for the wiki

 Signature 

Ian Beck
MacRabbit Support

Follow us on Twitter, or try my custom themes: Quiet Light & Earthworm

Profile
 
 
Posted: 31 October 2009 11:26 PM   [ Ignore ]   [ # 11 ]
Newbie
Rank
Total Posts:  6
Joined  2009-10-25

I don´t now if this is the right thread but I must say that there is a very big thing missing in expresso sugars an that is autocomplete feature for class properties and methods.

Bellow is some code sample of actionscript 3 code I could illustrated it with a php class to but I think you get what looking for:

package
{
  
public class foo
  {
      
public str:string "test";
      public function 
output():string
      {
          
return "Im a string";
      
}
  }

var c = new foo();
c.  <—- pressing . should give me an autocomplete list of all public methods / properties in my “foo” class.

—- str:String
—- output returns String

Im wondering is there anything inside the sugar api to do this ?

This is for me truly the missing feature that is standard in modern code editors plz don´t overlook this as it is needed.

Best regards

Nic

Profile
 
 
Posted: 01 November 2009 06:02 AM   [ Ignore ]   [ # 12 ]
Moderator
RankRankRankRank
Total Posts:  1249
Joined  2008-10-28

Hey Nic,

There isn’t anything in the Sugar API to allow for this kind of thing; it pretty much has to come from MacRabbit because the only way to populate autocomplete is via XML.  That said, it’s a very commonly requested feature, so hopefully it will show up eventually.

 Signature 

Ian Beck
MacRabbit Support

Follow us on Twitter, or try my custom themes: Quiet Light & Earthworm

Profile