A new kit will be posted this week, probably today.

Yes, you ARE missing something. On the Server Explorer view there is a small downwards point triangle. Select that and choose 'customize view'. They turn OFF the generated files filter

This is really an ISC internal issue but I would ensure that %Studio.SourceControl.ISC is compiled on the server. 

Tim is right, all classes require a package name. The clue is in the fact that myclass is underlined and colored in Red. In future versions of Atelier will be implementing 'code hints' and 'smart fixes' which will be able to help you resolve these sorts of problems quickly. Thank you!

This all makes sense. I've asked for there to be scheduled a thorough review of those places in Atelier where a project needs to be selected so that we can implement a consistent selection strategy. Thanks for bringing this to our attention

1) The git issue you raise is VERY interesting, the problem stems from git swapping one branches code out from underneath you and replacing it in the same structure. This is clearly different from many other source control systems where branches are placed in distinct trees in the file system (this is what we are used to at Intersystems, as we use Perforce). Addressing this issue will require some careful thought and I think working in a disconnected mode ( something which we are working on ) will only partially solve the issue.  So the answer here is we hear you loud and clear, we are working on disconnected mode but need a little time to think about all the ramifications.

2) You will be able to SYNC no Cache files to the server when CSP support is completed. We are still working on this aspect.

3) We were not planning on Atelier being a deployment tool, I know Bill McCormick has strong views on this subject and I will let him answer this particular issue

4) Again what you see in Atelier is a work in progress, syntax coloring is a very high priority for us but as you can appreciate its a significant task. We wanted to get Atelier into users hands so we could get valuable feedback such as yours so we couldn't wait for a perfect syntax coloring experience. We promise to deliver that. It will just take some time

The content available in the repository has to be signed ( we we do ) to prove that what you have downloaded has been created by ISC. When Atelier downloads it, it checks to see if it's been signed appropriately by calling the platforms cryptographic apis. This is what 'CheckTrust' is doing. We will investigate, I can't hazard a guess as to the exact problem at this moment in time

The intent is that we always use the internal web-kit browser and NOT use the default installed browser. Development is looking at this issue and it's being treated as a matter of urgency. 

This feature is called (in eclipse terminology) the 'edit strategy'. This is planned work .

Investigating

Both issues are confirmed, the drop down box should NOT be gray when there are connections already defined. This behavior is discrepant from that of the Mac so may be a windows only problem. The 'no namespaces reported' is definitely a bug. Developer informed. Thanks for the detailed report

You can turn on the network activities log for Atelier with Window->Show View->Other->Atelier->Network Activities

When starting Atelier and periodically ,Atelier queries the server for server info. This info includes which namespaces are available. It's worth looking in the log and grabbing the JSON response for the /api/atelier call. (You can format this JSON easily at www.jsonlint.org, though we plan to pretty print this at a later stage). 

Ref: the JVM shared library "/Library/internet plug ins/javaappletplugin.plugin/contents/home/bin/../lib/server/libjvm.dylib" 

This problem can be mitigated by installing the Java 1.8 JDK. Oracle states that the JRE does NOT update the symbolic links appropriately whereas the JDK does. Thus for MacOSX only we will now REQUIRE that the JDK be installed. We are sorry for any inconvenience this may cause but these are circumstances beyond our control. Thank you.

he JVM shared library "/Library/internet plug-ins/javaappletplugin.plugin/contents/home/bin/../lib/server/libjvm.dylib" 

We recognize the need to let you organize your whole source tree as you like within your project.

For example if you are a web developer, this would include all your HTML and JS files etc, etc. Unlike Studio where files in CSP directories needed to be manually copied to the server we will be providing the facility within Atelier to do this. 

When creating files in your project you are free to lay them out in what ever structure you want.

When copying or importing files to the project will will provide options for reasonable defaults, a flat structure in a specified root directory, a structure according to package and also a scriptable custom facility which lets you determine exactly where a file should go and how it should be named according to directory, filename and type.

These features are currently under development.

We (ISC) cannot distribute the java virtual machine due to Oracles licensing restrictions. We ARE working on code-signing however, in order to be a good citizen, though the practicalities of that are challenging.