Looking fantastic

[macgapproject]

Looking fantastic

[jeff-h]

Just found this, in case it's helpful... https://help.github.com/articles/how-to-transfer-a-repository

[jeff-h]

Oh man, I am so sorry — I just deleted the MacGapProject/MacGap2 repo because as per the details in the link above you can't transfer a repo if there is one in the destination with the same name. Only after that did I realise you'd spent time yesterday putting the wiki together. How much have I lost? :(

[rawcreative]

Doesn't really matter to me when it's transferred, I was just waiting until I had the majority of it completed, or at least to the point when it's ready to start being tested (which could arguably be now). Not a big deal about the wiki, it just had a checklist for the api..

The only things left to port to MG2 are the user defaults and sound api (haven't done growl yet but I really don't see the point in doing it since the notification center does everything growl does). I think there's some random commands that were left out as I was porting things since I did it pretty sporadically so we'll want to go through and doublecheck things.. Might be best just to open issues for everything left to do.

I'd also like to get a wish-list of features going either on the new repo or on the current one for people to chime in on stuff they want to see. I have a few ideas of things I was thinking about integrating but they're pretty complex and I don't want to take on implementing them if it's not something people want in the project e.g. things like persistent data storage

[jeff-h]

Whenever you're ready, moving this over to MacGapProject will certainly get some extra eyes on it.

In the meantime, let me know if you'd like me to go through and start documenting the new API. I haven't yet as I wasn't sure if it had stabilised. I'll put that stuff in the wiki right here if that's ok with you, since when you transfer the project, the wiki will go with it.

The wish list is great — I have a few ideas myself :)

[rawcreative]

For the most part the API has stabilized, I don't plan on modifying anything at this point. I may however add some convenience type stuff to various commands, i.e. ability to pass objects or individual params as arguments etc.

If you want to start going through the API and documenting it, that would be great. Wherever it was feasible to do so, I consolidated command arguments (and in a couple cases whole commands) so that they were easier to use on the JS side. For instance the Path command was consolidated to the App class, which on the js side is the base macgap object i.e. macgap.app.hide() is now just macgap.hide() Everything from the Path command is now just a property of the macgap object.. so instead of having to call macgap.path.application() to get the app path, now it's just macgap.applicationPath

I've tried to keep this consistent throughout, so any getters that do not require parameters are just properties of their respective objects, i.e. macgap.acommand.aproperty vs the old macgap.acommand.aproperty()

If I get a chance today I'll go through and just make a quick list of the commands and their arguments so you have a jumping off point.

[rawcreative]

I've written up some notes on the added and changed commands in the main readme..

I think we're pretty much good to go to transfer this to the organization, however since I'm not an owner, only a member of the org and transferred repos automatically have no teams assigned, as soon as I transfer ownership, I'll immediately lose admin/write access to the repo.

[jeff-h]

any getters that do not require parameters are just properties of their respective objects

This is a really nice improvement. Thanks again for your incredible work throughout.

since I'm not an owner

Fixed :)

[gobijan]

Yes nice work! I vote for removing growl since apple doesn't allow apps that bundle growl or better said that use notification services other than the native osx one :)

[desduvauchelle]

+1 for @tschundeee