Show Posts

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.

Messages - Arantor
1111
Test board / Re: Losers. Testing.
« on March 29th, 2013, 04:47 PM »
I don't like the fact that the legend now doesn't have w50 on it so it takes up all available space. Looks a bit daft having short items and a mahoosive legend.

Though the smaller pie chart works fine.
1112
Features / Re: Miscellaneous/WIP screenshots
« on March 29th, 2013, 04:31 PM »
Quote
Perhaps 200x200. This helps prevent the legend box from being shown on the bottom right (instead of the right) of the canvas.
Even with my ~1000px width it was working as expected :/

Easy fix, just change the size in PiePolls.php (since I put both the source and template in one file because I'm badass, though it's also for performance)
1113
Features / Re: New revs - Public comments
« on March 29th, 2013, 04:24 PM »
replace works as advertised, it replaces the contents of the layer, it just doesn't replace a given block. I didn't realise I was using the wrong function in that case.

The PiePolls plugin uses this to replace the poll template, which is how I discovered it since it needs to drop topic_poll_results and puts its own block in.
1114
Features / Re: Miscellaneous/WIP screenshots
« on March 29th, 2013, 04:21 PM »
Quote from Dragooon on March 29th, 2013, 06:08 AM
That's pretty nice, and kinda ironic. I am looking for a good PHP GD charting library ATM :P.
JpGraph. It's a bit big but it makes a nice job of it.
Quote from Nao on March 29th, 2013, 12:10 PM
hi im a forum admin i love wedge but it sucks because i installed the pie plugin on my website at wedge.org and dunno how to get it to work... helpz me!!!!!!!!!!!!!!!!!!§§§§§ §§§section
First, update the site to r2033 because the biggest part of r2033 was about providing support for this plugin. Yes, really.
1115
Off-topic / Re: Zend OPCache & APC
« on March 29th, 2013, 01:11 AM »
It's not a total replacement for APC, as the RFC even notes - https://wiki.php.net/rfc/optimizerplus - but having an opcoce cache as a core feature will, if properly implemented, be very worthwhile.

The problem is that I can actually see cruddier hosts not implementing it because OMG IT USES MORE MEMORY, without understanding what it's actually doing and why in all likelihood it would probably use less memory in sustained usage than the current model does.
1116
Features / Re: Plugin revs
« on March 28th, 2013, 11:59 PM »
(16 added, 58KB)

Revision: 81
Author: arantor
Date: 28 March 2013 22:58:03
Message:
! [Pie Polls] Initial checkin.
----
Added : /pie_polls
Added : /pie_polls/PiePolls.php
Added : /pie_polls/img
Added : /pie_polls/img/piepoll.png
Added : /pie_polls/img/piepoll_big.png
Added : /pie_polls/js
Added : /pie_polls/js/Chart.min.js
Added : /pie_polls/js/excanvas.compiled.js
Added : /pie_polls/lang
Added : /pie_polls/lang/PiePolls.english-uk.php
Added : /pie_polls/lang/PiePolls.english.php
Added : /pie_polls/piepolls.css
Added : /pie_polls/plugin-info.xml
Added : /pie_polls/readme
Added : /pie_polls/readme/readme.english-uk.txt
Added : /pie_polls/readme/readme.english.txt


Also
Quote
* Britishism. I'm leaving the ones in WedgeDesk, as it's got 'Pete' written all over it.
We actually made the executive decision that SimpleDesk would be British-English all over internally ;)
1117
Features / Re: New revs
« on March 28th, 2013, 11:53 PM »
(4 files, 8KB)

Revision: 2033
Author: arantor
Date: 28 March 2013 22:51:22
Message:
! Silly linktree bug of mine. Only occurred in rare circumstances. (Subs.php)
! Plugin permissions oddities from my removal of the simple view. (ManagePermissions.php)
! Poll display should be separated out a bit. (Display.php, Display.template.php)
----
Modified : /trunk/Sources/Display.php
Modified : /trunk/Sources/ManagePermissions.php
Modified : /trunk/Sources/Subs.php
Modified : /trunk/Themes/default/Display.template.php
1118
Features / Re: Miscellaneous/WIP screenshots
« on March 28th, 2013, 11:48 PM »
And now an updated version, which also includes the voter names if that's applicable (i.e. following the same visibility as normally enforced)
1119
Bug reports / add_plugin_css_file issues
« on March 28th, 2013, 11:08 PM »
I know I've reported the first before but this is to remind me to dig into it.

A call of add_plugin_css_file('Arantor:PiePolls', 'piepolls', true); will grab $plugindir/piepolls.css which is fine. (I seem to remember the last parameter being reversed, i.e. the default being to include the CSS file in the header, rather than having to explicitly indicate such)

The problem is that it generates:
Code: [Select]
<link rel="stylesheet" href="/wedge/css/pie_polls-chrome26-windows6.1-member-m1-b7-c2-admin-local-global-replace-505778.css.gz">

Now I know why this happens, add_plugin_css_file wasn't kept in step with add_css_file, but I'm not sure I want to touch add_plugin_css_file to bring it in line with add_css_file (since there's a *lot* of code for that by the looks of things)


Secondly, plugins can't use inline block. I'm sure I've brought this up before, but it just doesn't work. My file contains:

Code: [Select]
#pie_legend
div
margin-bottom: 4px
div
font-size: smaller
.pie mixes .inline-block
width, height: 16px
border-radius: 8px

The definition of inline-block is simply not pulled in because the plugin loader never pulls in anything other than the plugin. I'm aware this has always been the case - but until inline-block was a virtual class, it was never a problem. When inline-block was made a virtual class, I mentioned it then, and I mentioned it again about two-columns not being extensible in a plugin (since I wanted to make a three-columns class based on two-columns just with the width changed) but that's also not possible either.

Virtual classes and mixins are great but if plugins can't use them, I need to figure out something else entirely for them.
1120
Features / Re: Miscellaneous/WIP screenshots
« on March 28th, 2013, 10:12 PM »
This one's a bit unusual, given that it isn't a core feature (though it did require some overhaul in the core, but as it happened, that was no bad thing)

Simple enough and should be straightforward enough to understand what's going on ;)

Dragooon mentioned the ChartJS library to me recently, so I thought I'd give it a try and this is the result so far.
1121
Features / Re: New revs - Public comments
« on March 28th, 2013, 09:28 PM »
See... I figured you might ;)

Now, if only I could figure out why wetem::replace isn't working :/
Posted: March 28th, 2013, 09:09 PM

Never mind, I was misinterpreting what it was supposed to do... though whether it's behaving is another question entirely.

If you tell it to replace a layer, it'll work - the layer's content will be replaced. But if you tell it to replace a block on its own, it will do nothing. I'm not sure if this is intended behaviour or not.
1122
Features / Re: New revs - Public comments
« on March 28th, 2013, 08:54 PM »
* Arantor has happy thoughts in Nao's direction ;)
1123
Features / Re: New revs - Public comments
« on March 28th, 2013, 08:41 PM »
I know that feeling, heh :)

I'm currently attacking the polls template, separating the elements so I can make a fun plugin ;)
1124
Features / Re: New revs - Public comments
« on March 28th, 2013, 08:31 PM »
Also, after clicking on the Notifications option (now it's at the top), it's wrapped under the language icons rather than next to them where it currently is, plus there's no background.

* Arantor can provide screenshots if needed.
1125
Features / Re: New revs - Public comments
« on March 28th, 2013, 06:38 PM »
Quote
So may I leave everything to you on this..? It was quite a large patch, so I know it's not going to be fun...
Eh, it's a one line fix (and even tested)
Quote
Nope. It's the mission of Custom.template.php, where you can declare template_whatever_override() to replace a function.
We discussed it at length back in the day. Having template files inside skin folders is very doable, but it's not 'clean'. I'm always torn between the two sides of the problem, eh...
If you can replace a given template somewhere, that's cool. Though I can see one horrible situation.

master skin
  sub skin 1
    sub skin 2

If both sub skins declare a Custom template, in theory both would have to be included since sub skin 2 is inheriting from sub skin 1 - but if they replace the same things, you're going to get a function collision.
Quote
I didn't. I just noticed that adding line breaks manually in the string would add more physical line breaks to the thing. So I checked the code, and noticed the parse_bbc call. Which is why I decided to go for a 100% BBCode version. (Not that there's ANY BBCode in these strings, but... I mean the line breaks...)
But that's the thing... it's *not the same* as any other bbcode. Any other bbcode in the system will be a long one line string. This is the only area that's different.
Quote
Yeah but that's no reason to throw a hadōken at me in your previous post, buddy...
I'm sorry, I'm operating on something of a frustration level because I seem to be doing the rounds at the moment of explaining my point several times over and no-one's listening :(
Quote
Considering the amount of work we still have to finish, I don't see this happen in a realistic time frame. I'd rather we focus on more urgent matters -- translators can work on existing language files, if they're in such a hurry to have it done ;)
And they can even do what I did: edit it in the editor, the DB will give them a shiny preparsecode'd version of the content. I didn't manually translate anything - I just copied the original agreement.txt into a post and saved it, then grabbed it straight out the DB.
Quote
now that your Wedge copy is installed, download this separate file, Home.php and its related files, copy them to their respective folders, and point the homepage to Home, so you can have the Wedge.org homepage code on your site. Now you can modify it all you want (if you want!), because a Wedge upgrade will never overwrite it.
Then it's still a usability write-off. Only hardcore users are going to want to do that. The rest will just want a nice UI to play with and expect it to remain in place anyway (i.e. stored in the DB)
Quote
And working on these tools will deprive Wedge of other features that could be added to it, and that could be used by more people...
Having content management in the core will encourage more people to use it than not, IMHO.