This question is just out of curiosity, I own a P1i and it would be nice to play with it :)
A link to some documentation would be fine :)
It isn't officially supported, but apparently you can get it to work:
http://www3.symbian.com/faq.nsf/7b5405edb1250e7c802569ee005d054e/30398b3e9500a24d80256c7f00693a91?OpenDocument
Plus there are some 3rd party solutions out there if you google
Yes you can - using older versions (VC++.NET 2003) and Carbide.vs
Don't forget the VS supports makefile based projects as well so you can pretty much develop anything as long as there's a CLI based compiler for it. Sometimes, if you're lucky, Intellisense can pick up the headers and do autocompletion.
EDIT: To do this in VS2K5, do the following:
Select File->New->Project...
In the dialog, select the General type under Visual C++ branch of the left hand tree view. The right hand list should have a 'Makefile Project'. Highlight that, select a project name and then OK. You now get a wizard that allows you to set up the build command lines (what version of make and so on).
You have to manually create and update the makefile with the source files but everything else works as if it were a native VS project (F7 to build, etc).
Related
I really enjoy Xamarin Studio and I'm looking for a template solution to start developing a cross devices application with MvvmCross.
But I can't find how to set a project to work with PCL and MvvmCross with Xamarin Studio.
If anyone can give me a link where I can find a tutorial to make it, it would be awesome.
I would be very pleased to contribute to this community by giving my feedback and providing some tutorial about how to start using Xamarin Studio, PCL MvvmCross and get rid of Visual Studio :D
As #duDE's answer pointed out, for working in Visual Studio on the PC in the pre-Xamarin2.0 world, there were quite detailed instructions available on http://slodge.blogspot.de/2012/12/cross-platform-winrt-monodroid.html
As various releases of Xamarin 2.0 have been released over the last month, these type of instructions have become more and more difficult to keep up to date... and this situation is likely to continue for a little while yet as Xamarin are currently adding:
.Net 4.5 (Mono 3) support
async/await support
PCL support
This work is being done with some urgency, but without any official target date - so I'm afraid there isn't any easy way to predict dates for Alpha, Beta or final availability.
For the current OSX setup, I think you can use:
the current XamarinStudio/MonoDevelop - 4.0.2
the current stable Xamarin.iOS/MonoTouch and Xamarin.Android/MonoDroid - do not use the Aplha channel
For the current PC setup, I think you can cannot use Xamarin.iOS, but you can use:
VS2010 or VS2012
the current stable Xamarin.Android/MonoDroid - do not use the Aplha channel
with just a couple of changes:
you need to add two supported framework xml files - one for Android and one for MonoTouch - you can find these on http://slodge.blogspot.co.uk/2013/03/xamarinios-with-mvvmcross-in-vs2012.html
For discussions on getting things building and running, don't use StackOverflow - instead use one of:
http://forums.xamarin.com/discussion/1549/pcls-and-mvvmcross-in-the-new-tools#latest
as a backup you can also try https://jabbr.net/#/rooms/mvvmcross
Don't even think about trying to get an MvvmCross app built - on the free version of Xamarin - it's limits are way too low for any app I've tried to build.
If you are looking for some starting app templates, use: https://github.com/slodge/MvvmCross-Templates
If you are looking for some pre-built binaries, use one one of the folders on: https://github.com/slodge/MvvmCross-Binaries - please note that portable libraries built on the Mac are not portable across to the PC (or vice versa) - they will be 'soon' but not yet.
Sorry for the fact that we don't have a neater, finished solution... we've now been fighting to hack PCLs into Xamarin for a year. However, the good news is that really soon that battle will be over and we can all get on with the apps :)
I guarantee this answer is out of date inside a week...
Xamarin.Studio 4.2 allows you to create PCL projects.
Take a look at this article: http://slodge.blogspot.de/2012/12/cross-platform-winrt-monodroid.html
Many information about using PCLs as well as some special infos about MVVMCross
I'm currently trying to compile an old program (made with C++ builder 2 or 3) with the "current" Embarcadero RAD Studio XE2.
So, I was wondering whether there is an easy way to use the old code, as Borland once claimed to be fully compatible to lower versions... however I couldn't find a "project-file", only source-code (.cpp, .h, .res, etc.).
I tried to "add to project" the main .cpp, however there seem to be some wrong include-paths... it also seem to use the OWL-package and includes its important source-files...
I'm a bit confused which type of main project I have to open first, since you need to open a new project before adding the source to it. As the running .exe has a GUI, I tried a Form-Window first, but it may be better to use a console or service as the real form is produced within the code as far as I understand.
So, after installing OWL and correcting the include-paths, do you think it should be running fine? Or is there something else to take care of?
If your old project was using OWL, you're probably well outside of the supported upgrade path.
That being said, valid C++ code should still compile and work and I've heard of people using OWL with recent versions of C++Builder. (via OWLNext)
Regarding your confusion as to which type of project to use, I believe a console application would be your best bet. A forms application is completely wrong, that will bring in the VCL and give you no end of problems trying to reconcile the different windowing systems. A service application is a completely different beast as well, and isn't meant for GUI applications. A console application should work, but you'll need more. The OWLNext project has a wiki that should help quite a bit.
I am a javascript/html developer that hasn't ventured into visual studio much, so this might be a trivial question.
I am currently developing a Windows Store app (winJS), that will likely turn into several apps. And it would be highly likely that I will be reusing code, so I have made a js library with the common code.
The question is, how can I develop on this lib in visual studio, so that the apps that I am developing will use the latest version of it (i.e without me having to copy the files in again manually).
Best thing I can think of is, create a new project for the lib, and include it in the applications solutions, but what type of project would it have to be, and how to you expose the files?
Hope that makes sense!
Thanks!
I usually solve this by having the project copy the JS files I want to a common location, and add that file to the target project using a LINK to the file I want to include, rather than just adding it -- this is on the "Add Existing File" dialog, under the little arrow on the "Add" button.
VS 2012 doesn't have a JavaScript library project type. You'll have to manage your library as loose files.
The easiest thing would probably be to create a nuget package. That way it would be easy to pull into other projects and have the tool help keep you up to date. It does have the downside of needing to put your stuff into a nuget feed, which is not something you want for private stuff.
I absolutely love the Source Code Ouliner power toy that I use in VS2005 but am upgrading to 2010 and it seems they haven't yet released a new version. Is there anything similar that shows you a basic outline of the file you are currently navigating?
ReSharper, amongst many other features, has a File Structure window which does the same as Source Outliner.
For a free one, try the Solution Navigator in the Microsoft Productivity Power Tools.
Like you, I found this a totally great plug in that saved on the order of minutes per day. No more searching for functions! Luckily Source Outliner has been re-created for VS2010 and is still free. However, sbohlen updated it and it now runs on the (free) DXCore environment. I have been using it ever since I upgraded to VS2010.
You can read along as I got this set up, downloaded all the parts and got it running.
http://unhandled-exceptions.com/blog/index.php/2010/05/23/plugins-for-dxcorecoderushxpresscoderushrefactor-pro-201014-rtm-available/
The download is here:
http://code.google.com/p/dxsourceoutliner/downloads/list
You will also need the DXCore community installer from http://www.devexpress.com
But as a ReSharper user for years now, I will use the File Structure - same sort of view and already built in to R#.
Does anyone know of an alternative IDE for Sybase Powerbuilder? It feels pretty clunky, after working with VS2008 and Eclipse.
If not, has anyone successfully worked with this language outside the IDE? I'm not against using a simple text editor, but I find edit-import-regenerate-test-export-edit is clunkier than simply using the Powerbuilder editor.
To date, the only tools I have had any success with are:
PowerGen, for builds (with NUnit and CruiseControl.NET)
ConTEXT, which has syntax highlighting for Powerbuilder
PBL Peeper, which has some interesting features not present in the IDE
EDIT: I added a bounty to draw some wider attention to the question. It would be a very nice thing to have, if it exists.
EDIT: Well that was disappointing. The bounty apparently did not cause even 1 new person to look at the question.
None that I'm aware of, although you could probably use a source control tool, edit in your source control repository, and Get Latest Version from the PB IDE to shorten your text editor cycle. Be warned that there are hacks required to edit anything over 128 ASCII. (My guess is that this is to allow everything Unicode to be source controlled in the most restrictive source control tools.)
As Paul said, PB12 is coming with based on the Visual Studio shell, and will include things like collapsible code blocks, Intellisense, etc.... However, for PB12, this will only be used for WPF targets and a few .NET-type targets (like assemblies), last I heard. Win32 targets will continue to use the "classic" IDE.
Good luck,
Terry.
P.S. Thanks for the PBL Peeper compliment.
The PowerBuilder IDE is clunky, but I don't think developing completely outside the PowerBuilder IDE is a good idea. I think there are just too many dependencies right now.
However, the IDE for PowerBuilder 12 will be built using Microsoft's Visual Studio Isolated Shell so it ought to be much better when that is released. Also, I believe they'll be doing away with the PBL format which ought to make source control much easier to work with.
Certainly something to watch.
What I do is right-click the object and edit source. Then I copy the text and paste it into Notepad++ to edit. I copy and paste back to PowerBuilder, then I can save and see any errors. I've got a fairly decent User Defined Language for PowerScript if anyone's interested.
Added:
Please be aware that I've seen the PB Source editor corrupt DataWindows. They were all large DataWindows. To be safe always export DataWindows to edit.
One tool that will most probably make your PB experience way better is Visual Expert, which provides a good source browser. Such a tool should have been integrated into the PB IDE a long time ago, IMHO. Only problem is that it's not free, as opposed to the other tools you mention.
Regarding using external source editors, you can probably take advantage of OrcaScript, which is a scripting language that lets you perform actions such as export and import of PB objects from outside of the IDE. It will require some effort, but you can setup a basic dev env using batch files with ORCA scripts and some additional external tools. However, this setup will lack any visual editing capabilities, which means no (feasible) GUI or DW work. If you're mostly into NVOs, it could work. But then if that's the case, why use PB in the first place?...
I too have heard PB12's use of VS will be limited to some .NET stuff, which will probably benefit only a very small portion of the PB programmers community. I'm afraid the rest of us are stuck with the awful IDE for years to come.
Other than exporting the source and editing it I don't know of another IDE for PB. One problem you may have is that the exported source contains a lot of syntax that is not documented in the manuals. The PB IDE generates this code but there is no support for creating it by hand. I think you are stuck with the PB IDE
In my modest five Years of experiences starting with Powerbuilder 5/6, now using PB 10, I tempt to :
build my own browser from the classdefinition object based on Powerbuilder
tried to use autohotkey in order to open datawindows comfortable (we have several thousands in the project and i am two-finger-driven)
truly investigated in the idea using an external editor/IDE suppoted by an autohotkey script which is undermined by sybase allowing only mouse-click-usage of PB
using Visual Expert which is neither a truly integration in the IDE, nor is really worth in analyzing datwindow/powerscript interaction
ending by build hopes on PB12 Visual Studio, which lacks - depending on compatibility issues - ...
... i came to the conclusion that there will be no chance in improving Powerbuilder to an state-of-the-art language
In my philosophy - I obtained during those years - I distinguish between two types of OOP-oriented languages:
the one that award using object-orientation like C#, Python, Ruby (C++) etc. and very much the Java-Eclipse/Netbeans-Universe does
the other one that punish using object-orientation like Powerbuilder and the old Visual Basic, for example (which is causative the OOP-Idea comes afterwards and is "plugged in").
Especially the demand that all object should always be compiled (regenerated) and that you could't work with ancestors and descandants concurrently makes it painful to use real OOP.
...In memory of the good old Unix(Solaris)/C++ days...
I was researching a replacement solution that would be similar to PowerBuilder and I came across two that caught my eye.
The first was 'React Studio' https://reactstudio.com/ which I found via Alternativeto.net .
And the second was from an ad at the top of some Google searches but it was similar enough and looked good enough at first glance for me to want to take a closer look at it, and it's called 'Servoy' https://servoy.com/ .
Still researching but I currently have React Studio at the top of our list.
The TextPad editor has a syntax definition file for PowerBuilder 6.x contributed by anr#aon.at that I downloaded for free and customized several years ago. It works fine for later versions (including 8), doing keyword color highlighting on PowerScript srx files. Editing large source files in PB could get it to crash so it's usually safer, faster and more convenient to export to srx file, edit outside the IDE then re-import.