Wedge

(14 files, 20KB)

Revision: 59
Author: arantor
Date: 18 November 2012 15:53:06
Message:
! [Calendar] Many many changes. It's still completely broken, but at least it displays the form items when it's supposed to, and the distinct calendar forms have been harmonised somewhat. And the holiday management stuff got some security it didn't have before, oops. And live627's dateinput is also included, not that the server-side processing works, it's still expecting the old date. But this is still progress. It's just not enough progress to be usable, but enough that I wanted it committed! :P (all files)
----
Modified : /calendar/Calendar.php
Modified : /calendar/Calendar.template.php
Modified : /calendar/CalendarDisplay.php
Modified : /calendar/CalendarIntegration.template.php
Modified : /calendar/CalendarPost.php
Modified : /calendar/ManageCalendar.php
Modified : /calendar/ManageCalendar.template.php
Added : /calendar/css
Added : /calendar/css/dateinput.css
Added : /calendar/js
Added : /calendar/js/dateinput.js
Modified : /calendar/lang/Calendar.english.php
Modified : /calendar/plugin-info.xml
Modified : /calendar/readme.english.txt

(7 files, 2KB)

Revision: 1780
Author: arantor
Date: 18 November 2012 15:41:37
Message:
! Missing likes image. (likes.png)

! The list of fields that should be called for entity-saving should be extensible in most cases now. (Class-Editor.php, PersonalMessage.php, Post.php, PersonalMessage.template.php, Post.template.php)

! Harmonised entity handling between quick reply and main reply. (Display.template.php)
----
Modified : /trunk/Sources/Class-Editor.php
Modified : /trunk/Sources/PersonalMessage.php
Modified : /trunk/Sources/Post.php
Modified : /trunk/Themes/default/Display.template.php
Modified : /trunk/Themes/default/PersonalMessage.template.php
Modified : /trunk/Themes/default/Post.template.php
Added : /trunk/Themes/default/images/admin/likes.png

Yup, although I know the reason why that's the case - and it has a lot to do with the design of the calendar/post linkage. I find it interesting that IPB's calendar does not link to forum topics but instead maintains its own post + comments structure outside the forum. Doing the same would actually cut most of the performance hit right out straight away.

I understand where you're coming from, but in all honesty that's not going to happen. Wedge and its plugins represent something for me that I don't expect many other people here to understand, but it's going to be the culmination of my contributions to communities. It should be clear to most people watching that I'm not happy about writing code for free and giving to communities so once Wedge is out and has everything that I want to see Wedge have, I'll be disappearing. Having a decent calendar is one of those core things that the ecosystem needs, IMNSHO.

Let me put it a bit more simply. I don't want to see Wedge compete with phpBB/MyBB/SMF. I want to see it able to compete with IPB. As a minimum it needs the same breadth of facilities as IPB offers. Once that's in place, there's very little extra that I feel I need to do.

Establishing Wedge has done something I swore I'd never do after my experiences with SMF: giving people expectations. I don't like feeling like I owe people, and we've already had enough trolls for that around here. So once my obligation is fulfilled, I'm gone. In the meantime, I work on what I feel I can and what I choose to spend my free time on. Right now, I've already put my other projects on hold to make this happen, and while I respect what you're saying, I don't like being told that I'm wasting my free time on a project that I've chosen to take on.

It sort of explains why the calendar is the lame duck, it's like even its original developers didn't really care about it.

I'm having lots of fun tonight, now that I'm actually making all the post code tie up. Then I realise that there is a fun condition, even in SMF, whereby you can elect to tie an event to a topic but cause the topic to be created without the event as well, though it's a bit harder to trigger in SMF (but still entirely possible)

I feel a little like I've bitten off more than I can chew.

I know, I wrote the plugin version, but I wrote it long before the other stuff was added, it certainly predates the m, b, c and other prefixes. Given that it basically just acts as a wrapper to wedge_cache_css(), I had sort of hoped that it would 'just work'... :/

I also realise that my temper got the better of me in this thread (and I'm sorry, because you're the one who's going to be getting that, and that's wrong). Figuring out the many skeins of why the calendar is broken is not a pleasant task and in some ways I might just have been quicker building it from scratch, and it has felt like every single time I tried to do something, everything else seemed to break, and I know if I'm encountering these errors, others will as well.This actually brings me back to the original point I made when creating this thread - while it is nice to segregate like that, it does mean that a plugin not only can't share from the core, it also can't share with other plugins, though if you can't extend the core, you can't extend other plugins' stylesheets anyway.

I understand about the total burnout and was actually quite pleased to see you taking a break :)

Ignore the specifics of generateDays, it doesn't really matter. What does matter is that if you update the values in a select through whatever means, and then call .sb(), it won't work properly.

Of course it could work... which is why one is currently under development :P