I need assistance in publishing Symbian port
Veon
I do to publish this piece of code.
Vadim Zeitlin
V> I have a Symbian fork of wxWidgets (2.8.7). What exactly steps should
V> I do to publish this piece of code.
Hello,
This is excellent news! Is your port a new/independent one or it somehow
related to the wxSymbian port which was discussed/started before by someone
whose name I unfortunately forgot[*]? Also, what is -- approximately -- its
level of completeness?
Anyhow, the first step would be to make the changes which you have apply
to the current svn trunk sources as this is where all the new development
happens. This will probably need some work as Unicode handling was changed
in the trunk (http://docs.wxwidgets.org/trunk/overview_changes_since28.html)
and while it shouldn't make much difference to the user code using wx, it
probably does/will for a wx port itself.
We'd also need some documentation about the new port, notably how to build
it (this is non trivial for Symbian AFAIR). Maybe you already have it but
if not it would really need to be written for anybody else to be able to
use it -- and help with developing it.
And once this is done we should simply apply your changes to svn. And if
you are willing to continue working on it and maintain it we'd give you
write access to wxSymbian part of the repository, of course.
Let us know if you have any questions or if you run into any problems
while trying to make it work with svn trunk.
Thanks in advance and good luck!
VZ
[*] Amazing but true (and very sad): Google Groups search is just
completely non functional, it doesn't find any mention of wxSymbian
although there were plenty in the archives), see
http://groups.google.com/group/wx-dev/search?group=wx-dev&q=wxsymbian&qt_g=Search+this+group
Андрей М
On Thu, 13 Aug 2009 05:24:10 -0700 (PDT) Veon <veon.ua@gmail.com> wrote:
V> I have a Symbian fork of wxWidgets (2.8.7). What exactly steps should
V> I do to publish this piece of code.
Hello,
This is excellent news! Is your port a new/independent one or it somehow
related to the wxSymbian port which was discussed/started before by someone
whose name I unfortunately forgot[*]? Also, what is -- approximately -- its
level of completeness?
yes, this port is extension and update of wxSymbian you sent me as archive.
Anyhow, the first step would be to make the changes which you have apply
to the current svn trunk sources as this is where all the new development
happens. This will probably need some work as Unicode handling was changed
in the trunk (http://docs.wxwidgets.org/trunk/overview_changes_since28.html)
and while it shouldn't make much difference to the user code using wx, it
probably does/will for a wx port itself.
We'd also need some documentation about the new port, notably how to build
it (this is non trivial for Symbian AFAIR). Maybe you already have it but
if not it would really need to be written for anybody else to be able to
use it -- and help with developing it.
which form of documentation? do you have any templates?
I have Google Docs document describing full unroll procedure for my project, that using wxWidgets as library. (But it must be translated)
Build procedure is quite simple. But before that there are a lot of prerequisites are necessary/recommend. Some of them are common (eg. JRE, ActivePerl), some are specific (compiler update, plug ins). GCCE-compiler update is highly recommend, since linking errors (section overlapping) occurs even in simple projects. more about this http://wiki.forum.nokia.com/index.php/How_to_use_GCCE_4_with_Symbian_SDKs
Vadim Zeitlin
АМ> On Thu, Aug 13, 2009 at 3:41 PM, Vadim Zeitlin <va...@wxwidgets.org> wrote:
АМ>
АМ> > This is excellent news! Is your port a new/independent one or it somehow
АМ> > related to the wxSymbian port which was discussed/started before by someone
АМ> > whose name I unfortunately forgot[*]?
АМ>
АМ> yes, this port is extension and update of wxSymbian you sent me as archive.
Good to know that the initial work was finally useful!
АМ> > Also, what is -- approximately -- its level of completeness?
Just out of curiousity, could you please describe what is capable of right
now?
АМ> > Anyhow, the first step would be to make the changes which you have apply
АМ> > to the current svn trunk sources as this is where all the new development
АМ> > happens. This will probably need some work as Unicode handling was changed
АМ> > in the trunk (
АМ> > http://docs.wxwidgets.org/trunk/overview_changes_since28.html)
АМ> > and while it shouldn't make much difference to the user code using wx, it
АМ> > probably does/will for a wx port itself.
АМ>
АМ> ok, I'll review sources in the near future.
Please do post here if you have any questions!
АМ> > We'd also need some documentation about the new port, notably how to build
АМ> > it (this is non trivial for Symbian AFAIR). Maybe you already have it but
АМ> > if not it would really need to be written for anybody else to be able to
АМ> > use it -- and help with developing it.
АМ>
АМ> which form of documentation?
Nothing terribly formal, just some pointers to the build tools you need
and how should you use them to build it.
АМ> I have Google Docs document describing full unroll procedure for my project,
АМ> that using wxWidgets as library. (But it must be translated)
Maybe this is already enough, do you have a (publicly available) link to
it?
АМ> Build procedure is quite simple. But before that there are a lot of
АМ> prerequisites are necessary/recommend. Some of them are common (eg. JRE,
АМ> ActivePerl), some are specific (compiler update, plug ins). GCCE-compiler
АМ> update is highly recommend, since linking errors (section overlapping)
АМ> occurs even in simple projects. more about this
АМ> http://wiki.forum.nokia.com/index.php/How_to_use_GCCE_4_with_Symbian_SDKs
If it can be built under Linux, this is great as this makes it much easier
to test it (installing Symbian build chain under Windows drove me mad with
its weird requirements (Perl had to be 5.6 AFAIR and not 5.10 that I
already had; something had to reside on C: drive, ...) the previous times I
tried it). It should also make it possible to set up a build bot for it to
ensure that it's not broken by the changes elsewhere once it's integrated
in svn -- this is a real danger for less often used ports.
Regards,
VZ
Veon
wxchar.cpp. I can't to find changelog for this. And wxWidgets still
have header include/wxchar.h. what's happend with this source?
>> Also, what is -- approximately -- its level of completeness?
> Just out of curiousity, could you please describe what is capable of right
now?
processes, logger, etc.
There is no UI, because Symbian have the very poor one, it's not more
than iconic lists on main view, and buttons in menu.
The current application have Model-view-controller architecture. And
wxWidgets is on model&controller levels. View generally is a native
code. It provides good performance and usability as well as
application core is still cross-platform.
Unfortunately, the code doesn't include networking. AFAIK POSIX
sockets are not currently supported in Symbian OS. Networking
subsystems in wxWidgets and Symbian are too different. And I'm unable
to fill this gap.
>> If it can be built under Linux,
Vadim Zeitlin
V> I'm trying to merge files now. I have an additional file src/common/
V> wxchar.cpp. I can't to find changelog for this. And wxWidgets still
V> have header include/wxchar.h. what's happend with this source?
I think the closest analogue to this old file is wxcrt.cpp. But mostly the
old wxchar.cpp contents is in the headers now.
V> There is no UI, because Symbian have the very poor one, it's not more
V> than iconic lists on main view, and buttons in menu.
V>
V> The current application have Model-view-controller architecture. And
V> wxWidgets is on model&controller levels. View generally is a native
V> code. It provides good performance and usability as well as
V> application core is still cross-platform.
I see, thanks. I guess it's useful in its own right but I hoped to be able
to do UI too.
V> Unfortunately, the code doesn't include networking. AFAIK POSIX
V> sockets are not currently supported in Symbian OS. Networking
V> subsystems in wxWidgets and Symbian are too different. And I'm unable
V> to fill this gap.
Unfortunately I don't know anything about Symbian sockets so I can't
comment on this.
Regards,
VZ
Alessandro Rossi
See
http://www.newlc.com/en/forum/how-make-symbian-socket-calls
Alessandro
Veon
I've prepare(99%) the symbian pack. There are some changes in common
headers. e.g. platform definitions, constants.
What is the next step?
Vadim Zeitlin
V> Symbian env deployment instructions at http://docs.google.com/View?id=dtf8ddb_103g5rzr5gh.
Thanks, this is really nice, I remember I had a lot of troubles because I
was using Perl 5.8 (and it's even worse than 5.10) instead of 5.6 for
example and had to change some headers too...
I guess it's also going to be useful for setting up Symbian build under
Linux if anybody is interested in trying this.
V> I've prepare(99%) the symbian pack. There are some changes in common
V> headers. e.g. platform definitions, constants.
V>
V> What is the next step?
I guess we need to check this in svn. The patch is probably going to be
too big to put in Trac so please feel free to send it to me. Please read
http://trac.wxwidgets.org/wiki/HowToSubmitPatches if you haven't done it
yet.
TIA!
VZ
Veon
proposed me to post the patch to the trac directly.
But when I try to create a new ticket, I get permission error.
Your assistance in this matter is very much appreciated.
On Oct 18, 3:00 pm, Vadim Zeitlin <va...@wxwidgets.org> wrote:
> On Sun, 18 Oct 2009 05:26:10 -0700 (PDT) Veon <veon...@gmail.com> wrote:
>
> V> Symbian env deployment instructions athttp://docs.google.com/View?id=dtf8ddb_103g5rzr5gh.
> Thanks, this is really nice, I remember I had a lot of troubles because I
> was using Perl 5.8 (and it's even worse than 5.10) instead of 5.6 for
> example and had to change some headers too...
>
> I guess it's also going to be useful for setting up Symbian build under
> Linux if anybody is interested in trying this.
>
> V> I've prepare(99%) the symbian pack. There are some changes in common
> V> headers. e.g. platform definitions, constants.
> V>
> V> What is the next step?
>
> I guess we need to check this in svn. The patch is probably going to be
> yet.
>
> TIA!
> VZ
>
> application_pgp-signature_part
> < 1KViewDownload
Vadim Zeitlin
V> ok, I've send a diff to You, Vadim. And since you are busy you
V> proposed me to post the patch to the trac directly.
V> But when I try to create a new ticket, I get permission error.
Hello,
I really don't know what's going on, sorry... Can you login successfully?
What is your Trac user name?
Regards,
VZ
Андрей М
new ticker url - http://trac.wxwidgets.org/newticket
error: Forbidden - TICKET_CREATE privileges are required to perform this operation
Vadim Zeitlin
АМ> login: veon
АМ> new ticker url - http://trac.wxwidgets.org/newticket
АМ> error: Forbidden - TICKET_CREATE privileges are required to perform this
АМ> operation
I still have no idea unfortunately. I checked and your login is not
assigned any special permissions so it should inherit those of the
"authenticated" group to which all logged in users belong. And it does have
TICKET_CREATE permissions.
If Robin doesn't see anything wrong in the logs I can only advise trying
logging out and in again. Also, if you use a proxy to access the site, try
accessing it without it, sometimes buggy proxies break authentication.
Regards,
VZ
Андрей М
Logging and proxies aren't connected to this issue.
I've change my acc. password, it is the same as a log-in name. Try this using my credentials.
Or may be I should post patches via e-mail instead?
Vadim Zeitlin
АМ> I have successful authentication, but still haven't enough permissions to
АМ> create a new ticket.
АМ> Logging and proxies aren't connected to this issue.
АМ>
АМ> I've change my acc. password, it is the same as a log-in name. Try this
АМ> using my credentials.
Hello,
When I log in using your credentials I get a big yellow warning at the
top:
Warning: Your permissions have been limited until you verify your email address
with "verify" being a link to http://trac.wxwidgets.org/verify_email
I even took the liberty to follow it and it told me that it sent an email
with authentification token to Veon.UA at gmail. Please enter the token
when you get it at the above URL, I think it should fix your problems.
АМ> Or may be I should post patches via e-mail instead?
Trac is really much more convenient, both for reviewing patches and,
especially, for not losing them...
Regards,
VZ
Андрей М
I tried to verify my e-mail.
Since I haven't got the first letter, I've click on "resend" button but I still haven't get any token.
Already passed more than 2 hours, and there is no letter even in spam folder.
Any thoughts?
Veon
Regarding build S60 apps on Linux, as I understand it's unofficial and
almost inapplicable but still see http://www.martin.st/symbian/ ,
http://discussion.forum.nokia.com/forum/showthread.php?t=186041 (in
Russian)
Comments about the patch
>1. Removed the change to wxConsoleAppTraits as it would have broken non-
> Symbian ports compilation. You need to do whatever this is for in
> Symbian-specific part.
It is in Symbian-specific part, but for any new or unhandled platform
wxConsoleAppTraits interface _must_ be such as I described.
>2. I didn't understand what was the extra explicit cast to "const char*"
> in filename.cpp for so I didn't apply this. Could you please explain
> what was this for?
wxCharBuffer buf(path.fn_str()); - call of overloaded 'wxCharBuffer
(const wxChar*)' is ambiguous
path.fn_str() returns wxWX2WCbuf == wxChar*
wxCharBuffer have no wxChar* constructor, but defined as
wxCharTypeBuffer<char>
another decision is calling path.c_str(), wxCharBuffer have
wxCStrData& constructor.
Vadim Zeitlin
V> Regarding build S60 apps on Linux, as I understand it's unofficial and
V> almost inapplicable but still see http://www.martin.st/symbian/ ,
Thanks, I did setup a Symbian tool-chain under Linux using this and was
even able to build (and run on my phone) the SDK hello world example. I
didn't try to do anything more involved yet...
V> >1. Removed the change to wxConsoleAppTraits as it would have broken non-
V> > Symbian ports compilation. You need to do whatever this is for in
V> > Symbian-specific part.
V>
V> It is in Symbian-specific part, but for any new or unhandled platform
V> wxConsoleAppTraits interface must be such as I described.
Sorry, I must have misread the patch.
V> >2. I didn't understand what was the extra explicit cast to "const char*"
V> > in filename.cpp for so I didn't apply this. Could you please explain
V> > what was this for?
V>
V> wxCharBuffer buf(path.fn_str()); - call of overloaded 'wxCharBuffer
V> (const wxChar*)' is ambiguous
V>
V> path.fn_str() returns wxWX2WCbuf == wxChar*
V> wxCharBuffer have no wxChar* constructor, but defined as
V> wxCharTypeBuffer<char>
V>
V> another decision is calling path.c_str(), wxCharBuffer have
V> wxCStrData& constructor.
The first question I have is whether filename APIs under Symbian use
Unicode or not. And if they don't use Unicode, what encoding (UTF-8,
current locale, latin-1, ...) do they use?
Thanks,
VZ
Андрей М
> Unicode or not. And if they don't use Unicode, what encoding (UTF-8,
> current locale, latin-1, ...) do they use?
Symbian use so-called descriptors ( http://descriptors.blogspot.com/ )
in the majority of cases it is 16bit Unicode
but using Open C (stl-plug in) also provides ability to use non
Unicode file names. Telling the truth I didn't try create non latin
file using this stl.
Vadim Zeitlin
АМ> > The first question I have is whether filename APIs under Symbian use
АМ> > Unicode or not. And if they don't use Unicode, what encoding (UTF-8,
АМ> > current locale, latin-1, ...) do they use?
АМ>
АМ> Symbian use so-called descriptors ( http://descriptors.blogspot.com/ )
АМ> in the majority of cases it is 16bit Unicode
АМ>
АМ> but using Open C (stl-plug in) also provides ability to use non
АМ> Unicode file names. Telling the truth I didn't try create non latin
АМ> file using this stl.
This is probably not very important but it would be still nice to know
what kind of strings do the emulation functions like mkstemp() take. We can
easily just about any sane choice (although I have a suspicion that this
might not be enough for Symbian...) but we do need to know what are we
doing.
Regards,
VZ
Andrew Matuk
char functions.
Vadim Zeitlin
AM> Nokia's OpenC based on UC, Berkley sources, and use UTF8 for narrow
AM> char functions.
Then we should make fn_str() synonymous with utf8_str() for wxSymbian and
not use the casts, shouldn't we?
Thanks,
VZ
Andrew Matuk
using wide strings, e.g.
inline FILE *wxFopen(const wxString& path, const wxString& mode)
{ return wxCRT_Fopen(path.fn_str(), mode.fn_str()); }
wxCRT_Fopen = wfopen
but not for mkstemp, this func. have only narrow string implementation
Vadim Zeitlin
AM>
AM> I don't think so. Because other file-related functions defined as
AM> using wide strings, e.g.
AM>
AM> inline FILE *wxFopen(const wxString& path, const wxString& mode)
AM> { return wxCRT_Fopen(path.fn_str(), mode.fn_str()); }
AM>
AM> wxCRT_Fopen = wfopen
AM>
AM> but not for mkstemp, this func. have only narrow string implementation
Ok, I give up, I don't know how to handle this elegantly. We probably need
an #ifdef __WXSYMBIAN__ here and use utf8_str() inside it.
Thanks for the explanations,
VZ
Veon
have anything to say about this pack? Suggestions, problems, blockers
etc.
What is the next step to bring code to the repository?
Vadim Zeitlin
V> I've published Symbian specific files more than a week ago. Do you
V> have anything to say about this pack? Suggestions, problems, blockers
V> etc.
Sorry, I didn't notice that the ticket was updated somehow. I'll apply it
in a moment.
After a quick look the only small detail I see is that the files in
build/symbian have a copyright notice with "All right reserved" in it but
no licence information. Could you please add "Licence: wxWindow licence" to
the header to remove the ambiguity?
And another small thing: #pragma interface (for GCC) are unneeded since a
long time and can actually be harmful sometimes so it would be better to
remove them.
Final remark is that ideally we'd avoid (almost?) duplicating some Unix
files such as tls.h or sockunix.h in wxSymbian. Couldn't they be reused
instead?
Thanks,
VZ
Andrew Matuk
And I prefer this files were in the repository before I'll change
another issues, because it's quite difficult to assemble full,
well-structured archive for sending. I have to do a lot of manual
manipulations.
Vadim Zeitlin
AM> I've refresh the pack, change license information, and delete equal files.
Thanks!
AM> And I prefer this files were in the repository before I'll change
AM> another issues
Err, but they are. I've committed the changes to wxSYMBIAN branch (r62838)
when I wrote my previous reply, didn't you notice them?
Regards,
VZ
Andrew Matuk
> Err, but they are. I've committed the changes to wxSYMBIAN branch (r62838)
> when I wrote my previous reply, didn't you notice them?
I am switching to this branch, further patches will applicable to it.
Kind regards,
Andrew
Andrew Matuk
I set predefines in dirty way - just copied "setup.h" in includes.
What is the right way to do this?
Predefines in project file are not allowed in Symbian (anyhow I can
not do this well) so this file is necessary.
There are some changes to build successful, should I create a new
ticket for them or just update the old one?
Vadim Zeitlin
AM> I set predefines in dirty way - just copied "setup.h" in includes.
I don't think there is anything particularly dirty about having
include/wx/symbian/setup.h. However this file
a) is supposed to be editable by user so if some settings can't be enabled
at all under Symbian they should be forcefully disabled in
wx/symbian/chkconf.h
b) should be generated automatically by ./build/update-setup.h so you need
to add a line "update_common_setup_h include/wx/symbian/setup.h" to the
end of this file
AM> There are some changes to build successful, should I create a new
AM> ticket for them or just update the old one?
Please open new tickets, when an existing one is reopened it's easy to
miss it.
Thanks,
VZ