Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 1 and Version 2 of GSoC2009/WindowsGUI


Ignore:
Timestamp:
Jun 25, 2009, 4:53:02 PM (15 years ago)
Author:
utopianheaven
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC2009/WindowsGUI

    v1 v2  
     1== What is this project? ==
     2
    13Google's GSoC Proposal: http://socghop.appspot.com/student_project/show/google/gsoc2009/pidgin/t124024197245
    24
    35
    46This page will maintain a public view of the progress of my side of the Windows GUI (generally "higher level" than the other GUI project that looks to be done in native win32 or MFCs).
     7
     8
     9== Compiling libpurple with Visual Studio ==
     10
     11Status: '''Done'''
     12
     13A 'proof-of-concept' implementation was done of the nullclient, compiled and linked entirely in Visual Studio (including glib, libxml2, and the AIM prpl). This shows the ability to compile libpurple visual studio, communicate across CLI boundaries, and the feasibility of the project.
     14
     15
     16== Wrapping libpurple's API in a CLI wrapper ==
     17
     18Status: '''In Progress'''
     19
     20The simple 'proof-of-concept' implementation of the nullclient showed that each and every function in libpurple must be wrapped by a [DllImport(...)] in C#. Currently, a parser and generator is being developed to provide a C# wrapper that generates all required function calls to create a CLI wrapper around libpurple.
     21
     22Current generated code can be found at: /libpurple/wrapper/*.cs in the im.pidgin.soc.2009.penguin.visualstudio mtn branch.
     23
     24The program used to generate the code can be found at: /libpurple/wrapper/generator/*.cs in the same branch.
     25
     26
     27== Writing a Native GUI for Windows using C# ==
     28
     29Soonish. :)
     30
     31
     32
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!