This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »
1111
Announcements / Re: News points
« on: March 20, 2012, 02:09:52 pm »
I'm sorry, but it was just waaaaay too homo to read in that voice.
1112
Announcements / Re: News points
« on: March 20, 2012, 10:57:34 am »
Fixed.
Now I'ma break it all again.
[bubble=red]So I broke it.[/bubble]
[bubble=green]But then I fixed it.[/bubble]
[bubble=blue]And now it's much cleaner.[/bubble]
[snip=cpp]I also fixed these tags' CSS[/snip].
[snip=perl]Now they are less ugly when[/snip] squeezed together.
Everything works with them now.
[bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]A[/bubble][bubble=violet]B[/bubble][/bubble][bubble=purple][bubble=violet]C[/bubble][bubble=violet]D[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]E[/bubble][bubble=violet]F[/bubble][/bubble][bubble=purple][bubble=violet]G[/bubble][bubble=violet]H[/bubble][/bubble][/bubble][/bubble][bubble=green][bubble=blue][bubble=purple][bubble=violet]I[/bubble][bubble=violet]J[/bubble][/bubble][bubble=purple][bubble=violet]K[/bubble][bubble=violet]L[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]M[/bubble][bubble=violet]N[/bubble][/bubble][bubble=purple][bubble=violet]O[/bubble][bubble=violet]P[/bubble][/bubble][/bubble][/bubble][/bubble][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]Q[/bubble][bubble=violet]R[/bubble][/bubble][bubble=purple][bubble=violet]S[/bubble][bubble=violet]T[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]U[/bubble][bubble=violet]V[/bubble][/bubble][bubble=purple][bubble=violet]W[/bubble][bubble=violet]X[/bubble][/bubble][/bubble][/bubble][bubble=green][bubble=blue][bubble=purple][bubble=violet]Y[/bubble][bubble=violet]Z[/bubble][/bubble][bubble=purple][bubble=violet]A[/bubble][bubble=violet]B[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]C[/bubble][bubble=violet]D[/bubble][/bubble][bubble=purple][bubble=violet]E[/bubble][bubble=violet]F[/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble]
Now I'ma break it all again.
[bubble=red]So I broke it.[/bubble]
[bubble=green]But then I fixed it.[/bubble]
[bubble=blue]And now it's much cleaner.[/bubble]
[snip=cpp]I also fixed these tags' CSS[/snip].
[snip=perl]Now they are less ugly when[/snip] squeezed together.
Everything works with them now.
[bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]A[/bubble][bubble=violet]B[/bubble][/bubble][bubble=purple][bubble=violet]C[/bubble][bubble=violet]D[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]E[/bubble][bubble=violet]F[/bubble][/bubble][bubble=purple][bubble=violet]G[/bubble][bubble=violet]H[/bubble][/bubble][/bubble][/bubble][bubble=green][bubble=blue][bubble=purple][bubble=violet]I[/bubble][bubble=violet]J[/bubble][/bubble][bubble=purple][bubble=violet]K[/bubble][bubble=violet]L[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]M[/bubble][bubble=violet]N[/bubble][/bubble][bubble=purple][bubble=violet]O[/bubble][bubble=violet]P[/bubble][/bubble][/bubble][/bubble][/bubble][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]Q[/bubble][bubble=violet]R[/bubble][/bubble][bubble=purple][bubble=violet]S[/bubble][bubble=violet]T[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]U[/bubble][bubble=violet]V[/bubble][/bubble][bubble=purple][bubble=violet]W[/bubble][bubble=violet]X[/bubble][/bubble][/bubble][/bubble][bubble=green][bubble=blue][bubble=purple][bubble=violet]Y[/bubble][bubble=violet]Z[/bubble][/bubble][bubble=purple][bubble=violet]A[/bubble][bubble=violet]B[/bubble][/bubble][/bubble][bubble=blue][bubble=purple][bubble=violet]C[/bubble][bubble=violet]D[/bubble][/bubble][bubble=purple][bubble=violet]E[/bubble][bubble=violet]F[/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble]
Code: (edl) [Select]
global int a; ///< A random global
variant b = "Mary had a little lamb"; // I LOVE THAT SONG
with (instance_nearest(x,y,obj_0)) x = 50; /* weeeeeeeeee */
return 0 + 'a'; /** Random documentation **/ /* weeee */ /*! more docs */
1113
Proposals / Re: New ENIGMA Implementers' API; this concerns all developers
« on: March 20, 2012, 09:15:59 am »
I moved your post here because it seemed more appropriate. And yes; the reason I posted this topic at this stage is because I wanted input on precisely how varargs overloads would be resolved. I think it will be a lot easier on everyone if I resolve them like this:
1) Check if an exact overload exists.
2) Check if a castable overload exists.
3) Check if a varargs overload exists which would encompass it.
That way, max(double,double) is still used for max(int,int), but max(1,2,3) gets the varargs overload.
Also, the above makes it possible to extend a JDI method for the job.
While I am on the subject... Would anyone be interested in [snip=cpp]int function(int a, varargs bcdwxy, int z)[/snip] being a valid overload?
1) Check if an exact overload exists.
2) Check if a castable overload exists.
3) Check if a varargs overload exists which would encompass it.
That way, max(double,double) is still used for max(int,int), but max(1,2,3) gets the varargs overload.
Also, the above makes it possible to extend a JDI method for the job.
Code: (cpp) [Select]
function* get_overload(args) {
function *r = jdi::get_overload(args);
if (!r) {
for (overload *o in r) {
// Magically check for varargs overloading
}
}
return r;
}
While I am on the subject... Would anyone be interested in [snip=cpp]int function(int a, varargs bcdwxy, int z)[/snip] being a valid overload?
1114
Announcements / Re: News points
« on: March 20, 2012, 01:52:28 am »
Well, this has been a productive night.
Syntax highlighting works, if you can't tell.
a2h, if you delete it this time, I swear to GOD...
Also, added languages to snip tag. [snip=cpp]this->test(c++);[/snip] Was a pain in the ass because GeSHi insists on using <div> or <pre>. Wasn't even that rewarding, because you can't even tell anything in that snippet is being highlighted. <_<"
Syntax highlighting works, if you can't tell.
a2h, if you delete it this time, I swear to GOD...
Code: (php) [Select]
array(
'tag' => 'code',
'type' => 'unparsed_content',
'content' => '$1',
// !!! Maybe this can be simplified?
'validate' => isset($disabled['code']) ? null : create_function('&$tag, &$data, $disabled', '
global $txt;
$data = \'<div class="codeheader">\' . $txt["code"] . \': <a href="javascript:void(0);" onclick="return smfSelectText(this);" class="codeoperation">\'
. $txt["code_select"] . \'</a></div>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'<pre style="margin: 0; padding: 0;">\' : "")
. \'<code class="bbc_code">\' . $data . \'</code>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'</pre>\' : "");
'),
'block_level' => true,
),
array(
'tag' => 'code',
'type' => 'unparsed_equals_content',
'content' => '$1',
// !!! Maybe this can be simplified?
'validate' => isset($disabled['code']) ? null : create_function('&$tag, &$data, $disabled', '
global $txt;
global $context;
$lang = $data[1];
$geshi = new GeSHi(rtrim(html_entity_decode(preg_replace("/\ \;/"," ",preg_replace("/\<br \/\>/","\n",$data[0])),ENT_QUOTES|ENT_HTML5)), $lang);
echo "<style type=\"text/css\">".$geshi->get_stylesheet( false )."\n.$lang { margin: 0; overflow-x: auto; }</style>";
if($geshi->error() == GESHI_ERROR_NO_SUCH_LANG) {
$data[0] = \'<div class="codeheader">\' . $txt["code"] . \': (\' . $data[1] . \') <a href="javascript:void(0);" onclick="return smfSelectText(this);" class="codeoperation">\'
. $txt["code_select"] . \'</a></div>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'<pre style="margin: 0; padding: 0;">\' : "")
. \'<code class="bbc_code">\' . $data[0] . \'</code>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'</pre>\' : "");
}
$hrname = $geshi->get_language_name();
$ndata = \'<div class="codeheader">\' . $txt["code"] . \': (\' . $hrname . \') <a href="javascript:void(0);" onclick="return smfSelectText(this);" class="codeoperation">\'
. $txt["code_select"] . \'</a></div>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'<pre style="margin: 0; padding: 0;">\' : "")
. \'<code class="bbc_code" style="color:black;">\';
$geshi->set_encoding("UTF-8");
$geshi->enable_classes();
$geshi->set_overall_class("source-$lang");
$geshi->enable_keyword_links(false);
$geshi->enable_line_numbers(false);
// $geshi->start_line_numbers_at($args["start"]);
$out = $geshi->parse_code();
$err = $geshi->error();
if($err)
$ndata .= $data[0];
else
$ndata .= preg_replace("/[\r\n]/","<br />",$out);
$ndata .= \'</code>\' . ($context["browser"]["is_gecko"] || $context["browser"]["is_opera"] ? \'</pre>\' : "");
$data[0] = $ndata;
'),
'block_level' => true,
),
Also, added languages to snip tag. [snip=cpp]this->test(c++);[/snip] Was a pain in the ass because GeSHi insists on using <div> or <pre>. Wasn't even that rewarding, because you can't even tell anything in that snippet is being highlighted. <_<"
1115
Announcements / Re: News points
« on: March 19, 2012, 11:32:29 pm »
Okay, so maybe that isn't all. Going to try for syntax highlighting.
Code: [Select]
Basic code. Nothing special.
Code: (cpp) [Select]
// C++ code
#include <iostream>
using namespace std;
int main(int argc, char *argv[]) {
cout << "hi world";
return 0;
}
Code: (yaml) [Select]
%YAML
---
yaml: aint
markup: language
1116
Announcements / Re: News points
« on: March 19, 2012, 10:27:16 pm »
One quick rule:
[bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]None of this faggotry.[/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble]
That is all.
[bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]None of this faggotry.[/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble]
That is all.
1117
Announcements / News points
« on: March 19, 2012, 10:25:46 pm »
Greetings, all; I have a few small pieces of news to report.
First and foremost, recent parse progress is here. Lines 2-110 were read in by the program as input; lines 114 and forward are complete program output. It should be a completely capable C parser by the end of tomorrow. Note: I said "C" parser, not "C++" parser. The difference being massive.
Second off, Gary is working on our mailserver issues. New members can't register at the moment because the server is incapable of sending mail. For those of you who have attempted to register, please hold tight, we will resend your emails once the mailserver is back up.
Lastly, I have added two BBCode tags.
The first is called "bubble." [bubble]This is the default bubble[/bubble]. You can also specify your own color [bubble=red]for maximum overkill[/bubble].
The second is called "snip." I introduced this tag in the past in a custom BBParser, but now I added it to SMF. The snip tag allows you to put snippets of code inline with the rest of your sentence. To demonstrate, I will give usage.
The code [snip][bubble]Hello, world![/bubble][/snip] gives this: [bubble]Hello, world![/bubble]
The code [snip][bubble=green]Hello, world![/bubble][/snip] gives this: [bubble=green]Hello, world![/bubble]
The code [snip][snip]Hello, world![/snip ][/snip] gives this: [snip]Hello, world![/snip]
And now you know everything.
Perhaps later I will add syntax highlighting again and we can all live happily ever after. Perhaps.
First and foremost, recent parse progress is here. Lines 2-110 were read in by the program as input; lines 114 and forward are complete program output. It should be a completely capable C parser by the end of tomorrow. Note: I said "C" parser, not "C++" parser. The difference being massive.
Second off, Gary is working on our mailserver issues. New members can't register at the moment because the server is incapable of sending mail. For those of you who have attempted to register, please hold tight, we will resend your emails once the mailserver is back up.
Lastly, I have added two BBCode tags.
The first is called "bubble." [bubble]This is the default bubble[/bubble]. You can also specify your own color [bubble=red]for maximum overkill[/bubble].
The second is called "snip." I introduced this tag in the past in a custom BBParser, but now I added it to SMF. The snip tag allows you to put snippets of code inline with the rest of your sentence. To demonstrate, I will give usage.
The code [snip][bubble]Hello, world![/bubble][/snip] gives this: [bubble]Hello, world![/bubble]
The code [snip][bubble=green]Hello, world![/bubble][/snip] gives this: [bubble=green]Hello, world![/bubble]
The code [snip][snip]Hello, world![/snip ][/snip] gives this: [snip]Hello, world![/snip]
And now you know everything.
Perhaps later I will add syntax highlighting again and we can all live happily ever after. Perhaps.
1118
Proposals / Re: New ENIGMA Implementers' API; this concerns all developers
« on: March 18, 2012, 09:19:28 pm »
1) Yes.
2) No. varargs uses only variant. I will see about supporting varargs<typename>.
3) It will more than likely be a static array, as the compiler will know the exact space to allocate. It will still offer quicksort and reverse functions.
2) No. varargs uses only variant. I will see about supporting varargs<typename>.
3) It will more than likely be a static array, as the compiler will know the exact space to allocate. It will still offer quicksort and reverse functions.
1119
Proposals / Re: Edit Image/subimage... Button?
« on: March 17, 2012, 09:03:44 am »
Oh, in that case, I'll be happy to load you up some keylogger functions. As long as it's for benevolent or educational purposes.
1120
Proposals / Re: New ENIGMA Implementers' API; this concerns all developers
« on: March 16, 2012, 02:16:15 pm »
There is no more overhead than using the old system. In fact, there might be less, since this is probably somewhere close at all times.
1121
Proposals / Re: New ENIGMA Implementers' API; this concerns all developers
« on: March 16, 2012, 09:48:11 am »1122
Proposals / New ENIGMA Implementers' API; this concerns all developers
« on: March 15, 2012, 09:16:17 pm »
As the new parser approaches completion, it is time to start considering the implications. I have already made the executive decision of implementing half of this in the past, but what has been implemented will need some recoding, and the new parser allows for marvelous new extensions I would like to take advantage of. As such, I figure it would be good of me to draw up this proposal both to inform developers and open the floor for comments before they are implemented.
Developers heretofore have used the global [bubble]enigma::instance_event_iterator[/bubble] to determine the current instance and interface with its locals. At first glance, there's nothing wrong with this, but when we really consider its implications, we start to see its limitations:
This is similar to the mechanism with which you are likely already familiar, the [bubble]varargs[/bubble] type, which allows you to request an stdargs-like overload which you can treat like an array of parameters. It is similar in that each of these are semantics that can be declared in C++, but only used in EDL via the intervention of the parser.
The proposal, then, is as follows:
The lexical stipulations should be my concern rather than yours. Basically, don't assume you can do anything stupid. For instance, the following is a set of legal overloads:
The reason, of course, is that if you pass it two doubles, both functions are equally logical choices. Now, I could choose to give weight to the concrete matches precedence, but I'm asking for your opinions on that, first.
Now, as for the [bubble]_E_SELF[/bubble] parameter, if you think you have a better method of unambiguous identification for this which corrects issue (2) given above, let me know. Or, if you prefer a different name, such as just SELF, let me know as well. Otherwise, this will be the new format for the prototype:
So, post suggestions, or be aware that these two modifications mean changes to the API, including existing functions.
Floor's open. Be informed. Feel free to contribute.
Developers heretofore have used the global [bubble]enigma::instance_event_iterator[/bubble] to determine the current instance and interface with its locals. At first glance, there's nothing wrong with this, but when we really consider its implications, we start to see its limitations:
- Threads cannot manipulate this variable concurrently.
- Sideways casts between virtual ancestors cannot be made correctly in other files.
- Functions which change scope must synchronize their use of this variable.
- This variable does not, in itself, affect the scoping of scripts and functions called therein.
This is similar to the mechanism with which you are likely already familiar, the [bubble]varargs[/bubble] type, which allows you to request an stdargs-like overload which you can treat like an array of parameters. It is similar in that each of these are semantics that can be declared in C++, but only used in EDL via the intervention of the parser.
The proposal, then, is as follows:
- Any parameter with the type [bubble]enigma::varargs[/bubble] will be allowed to be passed an infinite number of parameters, as an array. The parser will handle packing the parameters given into the array in an efficient manner.
- Any parameter with the name [bubble]_E_SELF[/bubble] and a pointer-to type will be invisible to the user and filled in by the compiler with a pointer to the instance in question, meaning [snip=edl]this[/snip] in events and member scripts, and [snip=edl]with->inst[/snip] in [snip=edl]with[/snip] statements.
The lexical stipulations should be my concern rather than yours. Basically, don't assume you can do anything stupid. For instance, the following is a set of legal overloads:
Code: (cpp) [Select]
int max(double, double);
int max(double, double, varargs);
While the following is ambiguous:Code: (cpp) [Select]
int max(double, double);
int max(varargs);
The reason, of course, is that if you pass it two doubles, both functions are equally logical choices. Now, I could choose to give weight to the concrete matches precedence, but I'm asking for your opinions on that, first.
Now, as for the [bubble]_E_SELF[/bubble] parameter, if you think you have a better method of unambiguous identification for this which corrects issue (2) given above, let me know. Or, if you prefer a different name, such as just SELF, let me know as well. Otherwise, this will be the new format for the prototype:
Code: (cpp) [Select]
void instance_destroy(enigma::object_basic* _E_SELF);
So, post suggestions, or be aware that these two modifications mean changes to the API, including existing functions.
Floor's open. Be informed. Feel free to contribute.
1123
Proposals / Re: Edit Image/subimage... Button?
« on: March 15, 2012, 02:19:08 pm »
I'm mostly trolling, but...
1124
Proposals / Re: Edit Image/subimage... Button?
« on: March 15, 2012, 09:54:54 am »
So it's a keylogger?
Games use WM_KEYDOWN. Applications use the hotkey API. Keyloggers use hardware scan functions.
Games use WM_KEYDOWN. Applications use the hotkey API. Keyloggers use hardware scan functions.
1125
Proposals / Re: Edit Image/subimage... Button?
« on: March 12, 2012, 11:53:54 am »
It is pretty different, isn't it. I think DarkAceZ wants a button with the little pencil and paper icon ("edit") between the paper with the star ("new") and the big X ("delete").
Also, I'd move that "wrap" checkbox on its own somewhere where it's more noticeable and less hideous. Like under that scroll pane with the subimage thumbs. Then right-align the arrows.
While we're proposing features, I'd like to see a button myself, with the icon you use for the effects tile. It should have options to quickly invert all subimages (255 - channel), flip/rotate all, reverse order, add reverse order, and if you're feeling jumpy, any of GM6's stock effects (fade from one subimage to another, rotate by a fraction of a given angle each subimage, shrink from a given subimage, grow to a given subimage, etc). Depending on just how jumpy you feel, I'm personally in the market for a "color to alpha" and "alpha to color" function--the former does some math on the color channels to determine the alpha channel (probably comp<alphacolor.red,alphacolor.green,alphacolor.blue>(<pixel.red,pixel.green,pixel.blue>)), the latter just renders the image over a background of that color.
Also, I'd move that "wrap" checkbox on its own somewhere where it's more noticeable and less hideous. Like under that scroll pane with the subimage thumbs. Then right-align the arrows.
While we're proposing features, I'd like to see a button myself, with the icon you use for the effects tile. It should have options to quickly invert all subimages (255 - channel), flip/rotate all, reverse order, add reverse order, and if you're feeling jumpy, any of GM6's stock effects (fade from one subimage to another, rotate by a fraction of a given angle each subimage, shrink from a given subimage, grow to a given subimage, etc). Depending on just how jumpy you feel, I'm personally in the market for a "color to alpha" and "alpha to color" function--the former does some math on the color channels to determine the alpha channel (probably comp<alphacolor.red,alphacolor.green,alphacolor.blue>(<pixel.red,pixel.green,pixel.blue>)), the latter just renders the image over a background of that color.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »