Who are intrested in Nokia Symbian Series60 mobile phone development using VC++
-
hi , This thread is for all those developers who want to write application for Nokia and other small mobile phones using VC++, every body intrested can share views here and post problems and suggestion regarding it , cauz it might help many ppl who r new to this kind of development. Waiting for ure participations No Worries!
-
hi , This thread is for all those developers who want to write application for Nokia and other small mobile phones using VC++, every body intrested can share views here and post problems and suggestion regarding it , cauz it might help many ppl who r new to this kind of development. Waiting for ure participations No Worries!
For all those developers who are willing to write Symbian software, my suggestion is to stay away from Nokia's SDK for Visual Studio. This SDK is just a bunch of command-line driven scripts, and are EXTREMELY clumsy. Borland is about to release it's mobile development environment, called Borland Mobile Studio. I would wait for it before really starting to build Symbian apps with C++. If you can't wait, learn Java. It's development tools are much more convinient. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.
-
For all those developers who are willing to write Symbian software, my suggestion is to stay away from Nokia's SDK for Visual Studio. This SDK is just a bunch of command-line driven scripts, and are EXTREMELY clumsy. Borland is about to release it's mobile development environment, called Borland Mobile Studio. I would wait for it before really starting to build Symbian apps with C++. If you can't wait, learn Java. It's development tools are much more convinient. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.
-
For all those developers who are willing to write Symbian software, my suggestion is to stay away from Nokia's SDK for Visual Studio. This SDK is just a bunch of command-line driven scripts, and are EXTREMELY clumsy. Borland is about to release it's mobile development environment, called Borland Mobile Studio. I would wait for it before really starting to build Symbian apps with C++. If you can't wait, learn Java. It's development tools are much more convinient. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.
Who has said u it is just bunch of command line driven script , u can integrate SDK in VC6.0 and VS.NET,There is also series 60 appwizard available for VC6.0. I Know it is hard but you can program it with little effort. as far as borland c concerns u can wait for it but i can't . also Java might be a preferable tool for you , but as a VC guy when it comes to performence I wont see jave my first choice. One last thing this offer was only for those who like to take up the challenge instead of worrying about the difficulties. Atif Mushtaq No Worries!
-
Thanx for this information but i said ppl Who are intrested in Nokia Symbian Series60 mobile phone development using VC++ not using Java. Atif Mushtaq No Worries!
-
Who has said u it is just bunch of command line driven script , u can integrate SDK in VC6.0 and VS.NET,There is also series 60 appwizard available for VC6.0. I Know it is hard but you can program it with little effort. as far as borland c concerns u can wait for it but i can't . also Java might be a preferable tool for you , but as a VC guy when it comes to performence I wont see jave my first choice. One last thing this offer was only for those who like to take up the challenge instead of worrying about the difficulties. Atif Mushtaq No Worries!
The SDK consists of tools, that are ran by Perl scripts. It requires a specific version of Java Runtime Environment in order to run, it even has an authentic 'if' check to ensure this, which can be happily ignored by hacking the registry a bit. Several attempts on Nokia's behalf to alter the SDK to support a newer version of JRE have not succeeded: the only way to use a newer version of JRE properly is to fool the scripts to think that you're running an older version. The integration of the SDK with the VS environment allows you to create the emulator versions of your applications. These files, strangely, are compiled for the x86 processor, and further suggest that you cannot use them directly on a target mobile device, but must use the command-line tool to compile, for example, an ARM4 version. Another oddity in the SDK, and especially in the design of the emulator. From what I know about emulators, you should be able to build an ARM4-version, then run the emulator with that version in order to test it, and finally move the version directly over to the phone. Naturally, this creates difficulties in the debugging phase (because cross-processor debugging is hard to implement), so that is probably why they chose the "alternative" approach in the first place, putting the emulator run x86 code. The documentation for the Avkon framework is outright poor. In order to effectively do something with Avkon, you must browse through numerous example codes and header files. Creating docs with an automated documentation generator is fast, agreed, but leaving documentation to a this type of state is just about unacceptable. The Symbian framework (Eikon/Uikon) documentation is much more better off, you can actually perform lots just by reading it. From my point of view, the C++ SDK provided by Nokia is very poor compared to the J2ME tools that one of the posters mentioned. Java might have poorer performance, but when running on a mobile phone environment, the speed is not always the most important thing. The performance gain provided by C++ is, of course, a natural plus, but the lacks in the SDK drag it below Java's level. Perhaps you don't have time to wait for Borland to release their tool. That is okay: it's completely possible to develop Symbian software for Nokia mobile devices by using the tools currently available. But in order to become a major hit, so that lots and lots more people would take up the challenge and write competitive software for Nokia's phones, a clean-up of their act with the SDK is definite
-
The SDK consists of tools, that are ran by Perl scripts. It requires a specific version of Java Runtime Environment in order to run, it even has an authentic 'if' check to ensure this, which can be happily ignored by hacking the registry a bit. Several attempts on Nokia's behalf to alter the SDK to support a newer version of JRE have not succeeded: the only way to use a newer version of JRE properly is to fool the scripts to think that you're running an older version. The integration of the SDK with the VS environment allows you to create the emulator versions of your applications. These files, strangely, are compiled for the x86 processor, and further suggest that you cannot use them directly on a target mobile device, but must use the command-line tool to compile, for example, an ARM4 version. Another oddity in the SDK, and especially in the design of the emulator. From what I know about emulators, you should be able to build an ARM4-version, then run the emulator with that version in order to test it, and finally move the version directly over to the phone. Naturally, this creates difficulties in the debugging phase (because cross-processor debugging is hard to implement), so that is probably why they chose the "alternative" approach in the first place, putting the emulator run x86 code. The documentation for the Avkon framework is outright poor. In order to effectively do something with Avkon, you must browse through numerous example codes and header files. Creating docs with an automated documentation generator is fast, agreed, but leaving documentation to a this type of state is just about unacceptable. The Symbian framework (Eikon/Uikon) documentation is much more better off, you can actually perform lots just by reading it. From my point of view, the C++ SDK provided by Nokia is very poor compared to the J2ME tools that one of the posters mentioned. Java might have poorer performance, but when running on a mobile phone environment, the speed is not always the most important thing. The performance gain provided by C++ is, of course, a natural plus, but the lacks in the SDK drag it below Java's level. Perhaps you don't have time to wait for Borland to release their tool. That is okay: it's completely possible to develop Symbian software for Nokia mobile devices by using the tools currently available. But in order to become a major hit, so that lots and lots more people would take up the challenge and write competitive software for Nokia's phones, a clean-up of their act with the SDK is definite
Yes it is right u need JRE1.3.1 and perl 8.5 to make this SDK work , it is also right that to run the examples come with this SDK , need some command line work to convert in visual c++ workspace. no dought help is very poor ,code generated by appwizard is difficult to understand but above all these things it is only choice if u use C++,i seen features in Borland Mobile Studio , it has minimum support for C++ ,what it does provide all SDK under one hood , some wizards but ultimately u will have to use same SDK.(no Form builder ) so what a c++ guy can do either migrate to J2ME , or stay with it. One important thing u have bundle of c++ code , which u might convert to run on mobile devices , what would u do with that translate all that in java. so no way i can migrate to jave cauz i dont have much time , can u suggest some third option like new Mobile WebServices in .NET 2003 as i have only heared about it.or some other better solutions.thanx Atif Mushtaq No Worries!