|
#1
|
||||
|
||||
|
Whilst I realise that TechView is pretty much unsupported, and probably considered deprecated at this stage, has anyone attempted to build a working ROM containing it, using components available in a PDK?
I was thinking of attempting to build one, although I'm unsure of where to start, as far as deciding which components are necessary, and I don't know if any prerequisite components are missing yet. (Although I envisage getting to a stage where I discover that a ton of stuff is missing, fairly early on in the process). Still, if it's considered a total dead-end, I'm willing to wait for whatever additional components are necessary to build an S60-based image, or for the NGA/Orbit/New UI stuff, for what it's worth... Thanks, Tyson |
|
#2
|
||||
|
||||
|
There are some hassles with building both Eikon (Techview) and Avkon (S60) at the same time - they both want to generate uiklaf.dll, they both want to provide the startup sequence resource files, .... We therefore don't build Techview in the platform builds.
The problems aren't insuperable, but the most straightforward fix would be to build from scratch with the appropriate changes to the System Model. Unfortunately, the sf/app/techview package is still under SFL so you can't get it and build it yourself. PDK 3.0.c is getting closer, and I'm hopeful that PDK 3.0.d will have the OpenWF solution for the NGA graphics issue, and we will crack the S60 UI ROMs as well. Stay tuned to this channel, and we will bring you more information as it comes in... |
|
#3
|
||||
|
||||
|
That's really good news. I was thinking we were going to have to wait for 4.0.a next year for a working graphical environment.
Would it be possible to simply change the build targets for the various files in techview that conflict with their S60 replacements, such that both could be built at once? Since it is unlikely that people are going to care about winscw for much longer, any name changes could be made good in the IBY files and it would be possible to build ROMs for either environment. Certainly it'd be a reasonable way to ensure it at least still builds with whatever changes are being made to the platform. |
|
#4
|
||||
|
||||
|
Thanks for the update on this.
|
|
#5
|
||||
|
||||
|
Is it still possible to build a working Techview ROM with PDK 3.0.c? Is it unsupported as I don't see related files in the package (e.g. techview.oby)?
If this package is unsupported or deprecated so far, could anybody point me to the official announcement? or who is the key person to confirm this? Thanks in advance, Osvaldo |
|
#6
|
||||
|
||||
|
Its worth considering doing a mini gui configuration:
http://developer.symbian.org/main/do...v.minigui.over There is no specific documentation on how to do this in relation to Syborg. If you were to investigae this approach, lots of people in the community would like to see the details - perhaps in a wiki page. |
|
#7
|
||||
|
||||
|
Hi faimemon,
I've been trying to build a minigui ROM without success, I guess it is not supported so far either and we will have to wait until NGA has been brought up. Cheers! Osvaldo |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|