[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3203 [Pluggable transport]: obfsproxy will probably need a GUI on Windows
#3203: obfsproxy will probably need a GUI on Windows
---------------------------------+------------------------------------------
Reporter: asn | Owner: asn
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by asn):
Replying to [comment:6 chiiph]:
> Replying to [comment:5 asn]:
> >
> > The original ETA of this - looking at my application - was "June 17th
> > - July 1st".
> >
> > Replying to [comment:3 chiiph]:
> > > 2) Make a plugin for this. If the idea is to just fork another
process with obfsproxy, and have a couple of buttons and simple lineedits
for config, this won't be a problem as a plugin. The only thing is that
I'm planning on putting the design behind the plugin framework for review
this week, and from there to a usable stage, it might take a while (a
month may be?).
> > >
> >
> > Hm, alright. I'm most probably gonna start with this in at least 3
> > weeks from now. Do you think I could use your plugin framework for
> > this?
> > How hard do you think it will be? GUIs terrify me!
>
> It shouldn't be really hard. But I guess it depends, if it terrifies you
then you could say it's really hard :)
>
> So, today I've pre-finished the structure to support plugins in Vidalia.
It's not ready for comments yet though, but it should be by this weekend
or so.
> The idea for the API is to provide the exact same interface to widgets
like Qt does in C++.
> Since Qt is really big, I've got to prioritize certain parts, so what I
could do is to think what you'd need according to what you wrote, and code
that part first.
> You'd have to have in mind that you'll be coding over something that
hasn't been really really tested yet. If you are ok with that, then we
should sync in terms of deadlines.
>
Hi!
I still think I prefer doing it with the experimental plugin API.
Since I'm gonna get my feet wet with Qt/C++ I might as well go the whole
way and integrate it cleanly with Vidalia; it might also help the plugin
API mature.
I can't predict my deadline with great precision, but I'll probably start
coding for this somewhere around 17th of June and have the very first days
of July as my deadline.
> Otherwise, a standalone Qt app would be almost as straight forward (in
terms of coding) as the plugin, so that shouldn't be a problem either.
> You'd have to work with something like qmake, and stuff like that (which
you wouldn't need as a plugin), and it won't be integrated with Vidalia.
But you could do the plugin equivalent later on.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3203#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs