Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
We have two separate tags:
https://stackoverflow.com/tags/oxygene/info
https://stackoverflow.com/tags/delphi-prism/info
They read like those are different products, more so like Prism is a superset of Oxygen and the latter is "just compiler" and Prism to Oxygene is like Lazarus to FPC.
Maybe that was the picture somewhen. But looking at Prism withdrawal, i wonder if there still are some things in Prism that are missed from Oxygene ?
If not, then there is probably a time to make oxygene the One True Tag and make delphi-prism just an alias to Oxygene ?
We're in the process of getting the two tags merged, yes. fwiw, Prism is not and never has been a super-set to Oxygene. Prism is/was the exact same thing as Oxygene for .NET.
(that said, this discussion would really belong on meta?)
It is actually the other way around. Prism was just the .NET "flavor" of the Oxygene compiler. Oxygene includes everything that Prism did, plus a whole lot more. Oxygene also includes the Java flavor (for Android development) as well as the soon to be released "Cocoa" edition which is currently code named "Nougat" (for Mac and iOS development).
When Delphi Prism was first released there was some existing .NET resources that were bundled with it, but they deprecated and removed shortly after. Most of the Delphi Prism and Prism releases were solely a subset of Oxygene.
The difference you read in the descriptions comes down to branding. Technically there is none.
In an unrelated note, if you find yourself doing both Oxygene for .NET and Delphi development then you should check out Hydra too.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Yes, while i'm working on node.js, i still love perl, :)
The old web product is based on old perl CGI, i'm looking to the simplest way to fix XSS/Sql injection/etc. web security holes, within a week including testing, :(
So for
Catalyst
Dancer
Mason
Maypole
Mojolicious
which one should i use in the ARM platform ?
Thank you !
You have fallen foul of the primarily opinion-based off-topic categorisation, and your question will probably be closed very soon. However I think it's worth offering a few guidelines here
First of all you should absorb what is written in CGI::Alternatives as it is a reasonable summary of the subject
Next you should separate the HTML generation functionality of your existing CGI code from the interface itself, and consider replacements for each of them separately. If you were to use HTML::Tiny together with CGI::Simple then your code would have to change very little and you would have achieved better partitioning of functionality
Ideally you will move on to one of the many templating systems such as Template Toolkit, together with one of the frameworks, which is the topic of your question. In the end you will need to do a lot of research and many trials to discover how well each framework fits your requirement, in terms of both the feature list and the convenience and clarity of the API
All I can do here is say that I am very fond of the Mojolicious suite and suggest that it may be a good starting point. The API focuses on command chaining in a way similar to Ruby, and there is a Mojolicious::Plugin::CGI accessory which will allow you to execute CGI scripts unchanged during your migration
Note however that all of the frameworks that you mention, as well as several others, will have their proponents. That is why you must make the selection yourself, as such recommendations will be influenced primarily by familiarity, and without your own knowledge of the requirements of your project
Unfortunately I cannot speak to the security issues of the various options, but I hope that has helped a little
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I program in Objective-C and Swift primarily and understood Apple's announcing Open Source Swift by end of year as a move to make it available for backend programming as well. To quote Craig Federighi (SVP Engineering) in the keynote “We think Swift is the language we'll be doing application and systems programming”. The mention to systems programming and the mention that there will be libraries for Linux seems a clear indication on the path to using as a backend development language as well.
So my question relates to two possible paths that could take. On the one hand, Swift's page says that “Using the incredibly high-performance LLVM compiler, Swift code is transformed into optimized native code that gets the most out of modern hardware.” This would mean that it would have to be compiled for each target hardware I assume. Is this assumption correct?
On the other hand, if Swift was compiled to the JVM I assume it would make Swift's adoption much wider and faster because it could take advantage of the JVM's hardware independence.
I guess the point of my question is: are these two assumptions above correct? Would it even be possible to compile Swift to the JVM? If so, what advantages and disadvantages would it have over native code to each target hardware.
I am curious to understand if this is on the ballpark on how to think about this development for Swift.
LLVM IR can be used as a platform-agnostic binary distribution method. Google does exactly this with PNaCl. http://www.chromium.org/nativeclient/pnacl/introduction-to-portable-native-client
I don't know if JVM provides advantages over LLVM IR but it's not the same as locking into one exact binary format.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am searching for an Eclipse plugin which supports drag and drop functionality to build a GUI
and
supports immediate and automatic embedding within a MVC (model view controller) structure. Any ideas?
WindowBuilder is free, simple and not cumbersome. It also supports binding and synchronization of model pojo objects taking some of the MVC pains away.
I find it quite pleasant to work with as it does not places itself at toe forefront like most other similar editors will. It does not embed strange files that serve no other purposes than to serve the editor, rather it uses directly the java source file as it's backing persistence and it does so in a very clean way compared to say visual Studio with an MFC project.
It does have some quirks though, especially with Maven as some of the dependencies are sometimes hard to find. Personnaly I package them as a single jar and added it dynamically to the build through some clever hacks inspired largely by other members of the present community :-)
Give it a try, may not be the uber cadillac with shiny chromed everything but it does work well and stays out of the way when you don't need it.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm thinking about starting to develop a plugin for AutoCAD, but I have absolutely no knowledge of the field. How does the plugin system work? What are the licensing terms? What programming platforms are available?
I'd really appreciate if somebody could give me a primer, or, even better, link to some resources for the total beginner I am.
Thanks!
Prior to AutoCAD 2014, there were three basic plugin types for AutoCAD:
AutoLisp
.Net
ObjectARX
AutoCAD 2014 also provides:
4. Javascript API. You can find a link to the documentation at the AutoCAD DevBlog.
AutoLisp can be used with DIESEL scripts/macros to accomplish and automate basically anything that a user can due through the UI, and a maybe a little bit more, but .Net and ObjectARX are much more powerful, allowing you to create your own entities and more advanced behavior.
ObjectARX is a C++ interface, and the .NET classes are actually wrappers to the ObjectARX interface. The .Net interface abstracts things fairly well, but you still have to be concerned with the threading and possibly some other things as you develop more complex applications.
As previously mentioned, Through the Interface is a great blog for .NET stuff.
For ObjectARX, there is a good introduction at ObjectARX & Dummies, but for the deeper material the Developers Forums are a good resource.
If you are developing anything for people other than yourself, you should also seriously consider getting a registered developer symbol to prevent conflicts among different plugins. You can do that at the Symbols Registration page on the AutoDesk website.
Depending on your resources, you may also want to join the AutoDesk Developers Network (ADN), which provides access to software technical support, and early and beta access to upcoming AutoDesk products and APIs.
What type of application are you thinking of writing? I've written a couple WPF user controls that communicate with AutoCad. To do so, I used the AutoCad .NET Developers Guide found here:
http://docs.autodesk.com/ACD/2010/ENU/AutoCAD%20.NET%20Developer's%20Guide/index.html
This is a great blog to with some good video tutorials on it too.
This is a GREAT video if you just want to get started!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I was wondering how people think about using productivity tools like Coderush or Resharper in live demos. Is it a don't and should someone only use the most default settings of the IDE? Or is it ok to speed things up a little during the demo? Also, should you explain you are using this tool during the demo?
I've seen a lot of presentations where people use these tools and personally I don't mind.
Make sure you tell people that are going to be using the tool and then announce the action that you are about to take. e.g. "I'll use Resharper to extract this method into the Foo class"
It really depends on what you want to demonstrate. This kind of productivity tool are usefull even for demos in order to avoid loosing time on basic technical problems. You may also take advantages of such demos to introduce the features of these tools...
I tend to use DevExpress Refactor! Pro, and GhostDoc, when I do code-related presentations. I try to make sure the audience knows what I'm doing by saying out loud what I'm going to do, but I have also built my own custom tool for this, which you can find a beta of here: LVK.ScreenKeys.
Basically the tool will pop up, in the upper right corner of the screen, yellow tooltip/toast-like windows showing the key stroke/sequence I invoked, and also a textual description of what it means, depending on the software it was invoked in.
Before I started using such a tool, I invariably had questions like "what did you do now", and if you don't want to use such a tool (there are others besides mine), I would consider not using more than a few functions of such tools.