go to post Fred Gustafsson · Mar 23, 2020 No worries, I got it working after a fresh reinstall. Probably did something wrong the first time around
go to post Fred Gustafsson · Mar 20, 2020 It generates tons of JSON looking data. Is there a trick to getting the GraphiQL to get to the schema? Any settings or such?
go to post Fred Gustafsson · Mar 20, 2020 This looks very promising. I've got the testing shell up and running returning data from the Sample namespace but how do i "generate a schema for all classes in the namespace" as mentioned in your instructions? My Documentation Explorer just reports "NO SCHEMA AVAILABLE"
go to post Fred Gustafsson · Oct 1, 2019 Mutations, mainly. Is GraphQL support, or will it become, an official part of the product?
go to post Fred Gustafsson · Sep 30, 2019 Really interesting stuff that I would like to introduce but there seem to be no new developments for a long time now. Has this development fizzled out?
go to post Fred Gustafsson · Jan 7, 2019 |I agree with Guillaume. We have been using this model (together with Git Flow) for more than a year now. It works very well.
go to post Fred Gustafsson · Jan 7, 2019 I strongly believe that the best approach to this problem is to use the "Git Flow" branching model. See https://nvie.com/posts/a-successful-git-branching-model/
go to post Fred Gustafsson · Oct 18, 2018 I suggest using local development environment for atelier and using the GitFlow workflow for managing your branches and merges. All the merged code can then be moved, manually or automatically, to your test server and the live server. It works well for us.
go to post Fred Gustafsson · Sep 13, 2018 Hi,We switched to Atelier late last year, mostly to be able to use Git and GitHub. We follow a strict GitFlow workflow. Versioning is working well as long as you follow the workflow. We release every third week (plus occasional hotfixes) using Jenkins via a test server and a staging server.We have 7 developers working on the same code base but merge conflicts are very rare and GitHub/Git does a fine job of solving them.Switching branches is not a problem but you need to reload and recompile your entire code base every time (we have upgraded our dev machines seriously to be able to do this quickly).Regarding workspaces/projects: we only have one workspace but have split the application some 50 projects. ISC recommended us to keep the projects small but given the CPU power we now have, I think we would have been better off with just having one project.I can't say Eclipse is the best editor in the word and the Atelier code completion is nowhere near as slick as Studio but it is worth it.Hope that helps.
go to post Fred Gustafsson · May 23, 2018 I agree with Scott, it is so slow that is close to useless. I can't see any reason for being this slow, it's just a simple lookup.
go to post Fred Gustafsson · May 16, 2018 We decided to split them each top level package into separate projects (approx 50) but I'm starting to regret that. I think it is better to have all code in one project and in one repo.
go to post Fred Gustafsson · Oct 19, 2017 This issue has now been identified. It turns out that there is a bug in the CSP importer, it ignores any trailing CRLF at the very end of the file and this leads to sync conflict. The issue can solved by either removing any CRLF at the end of the file or by creating a different directory for the source CSPs and the CSP application path. The reply I got from the developers was: 'This behavior is observed because the server and Atelier are competing. Pointing the "CSP Files Physical Path" to the Atelier workspace is not supported at this time. We will further investigate and plan to improve user experience.'
go to post Fred Gustafsson · Oct 16, 2017 But the F3 does the wrong thing, it goes to the server version of the class, not to the source code.
go to post Fred Gustafsson · Jul 26, 2017 One aspect of punycode encoding is that Chrome is (since v56) encoding data submitted from input type='email' fields with punycode. Not a big deal, you might think but consider people signing up for you service using chrome, data gets stored as punycode and the user will never be able to login from any other browser because the submitted value will not match the stored value! See https://justmarkup.com/log/2015/02/input-type-email-better-dont-use-it/ Fred
go to post Fred Gustafsson · Jul 4, 2017 Jochen,We are also working on implementing GitHub and Atelier. I have been spending a lot of time researching various options. I think you will have to get use to the fact that all code in a repo will always be present, I don't see why this is an issue at all, just use package names to separate them.The bigger issue I have come across is the actual workflow between Github, Atelier, Cache. Checking out code from git will place the class files in the workspace directory but it will not push them into cache and compile it. I think we will have to write some kind of hook in Git to trigger a full import and compilation. Also, I find that the Git integration in Eclipse is hard to work with, it's not very clear and they are using non-standard terms. I recommend SourceTree instead.BTW, I also recommend looking into Git-Flow , it solves some of the trickier version control issues.Fred
go to post Fred Gustafsson · Jun 22, 2017 Thanks for that. It worked fine but it leads on to the next question. How do get it into my Atelier project automatically?
