« first day (947 days earlier)      last day (4005 days later) » 

6:25 AM
@Rarst WP are hoping that Yahoo's purchase of Tumblr will be similar in effect to their purchase of Flickr, they want to grab as much market share from Tumblr as possible. This is problem with post formats crap, which is executed poorly imo. If they just approach the architecture in my thought out process, they'd have better result. But that's just my opp...
 
 
2 hours later…
8:48 AM
They want to be the new tumblr so that they can get invited to swankier parties in Silicon Valley
Which considering the commercial, all over the place nature of wordpress.com is unlikely to happen anytime soon, post formats or not
 
9:26 AM
@TomJNowell if that were true, I'll run for the hills... and we can create that CMS that we keep talking about but never do anything about :P
 
quite a lot of people are building their own cms from scratch as a hobby
there're plenty of WordPress competitors slowly being built, getting launched, and killed before they reach maturity
it's not so much a case of build it and they will come
as to what to do once v1 is released and nobody knows about it yet
for ultimate traction we'd need to compromise it with WordPress API wrappers
 
that's essentially the current puzzle. you can't build something technically modern and popular at the same time. sacrifice one or another. maybe that's why WP isn't so quick to progress on PHP version and kicking hosts forward? level the playing field and suddenly you compete against modern systems that can run on same range of environments as you
it's like perverted reverse evolution where creature evolves environment to be most stuitable for it :)
 
9:44 AM
@TomJNowell As @kaiser said it should be similar to that of WP to make the transition easy for people. Personally everytime I have written a half assed skeleton attempt at my own CMS it has been Wordpress-esque; basically just righting all the wrongs.
 
what they should be really afraid then is leap in static site generators from "nerd" realm.
 
I think if trac had a more positive uptake to patch submissions my opinion would be different
@Rarst I don't think you'll ever see stat generators cause much of any trouble tbh
 
@userabuser they keep coming back recurrently. and every time they come back they have more intricate range of programming tools and languages to play with.
 
My thoughts are build a core cms and a blog plugin, and release that as a distribution
As if WordPress implemented blog posts in a plugin and bundled it akismet style activated by default
should probably do the same with WordPress APIs
minus some notable bugaboos like query_posts
 
@Rarst people like us, yeah we'd use them, but for mainstream solution, unless that staticness gets a whole lot of automagical love then mainstream people won't use it... but hey time will tell.
 
9:47 AM
imagine desktop app that is diary-like and can at push of a button publish your blog to everything from dropbox to any site that has FTP to Amazon S3 to affordable (few $) custom-tailored hosted service
 
PHPCR?
 
@TomJNowell as a separate project or as a plugin of WP?
 
no database to deal with, no server requirements, no dying under anything but most extreme traffic
 
@Rarst ooo you should email me for top secret stuff on this :)
 
something to look at, undecided if its something that should be used or not
 
9:49 AM
we can scoff at static site generators now because it's technical mess for nerds for the sake of running anywhere, but it is almost exactly what people scoff at WP - technical mess for the sake of running anywhere
 
essentially i think posts and terms are the way to go, albeit taxonomies should be implemented more like scribus posts 2 posts plugin
or whomever maintains that now
@Rarst if we can get a PHP runtime + sqlite working locally and just have a basic 'push' mechanism as you mentioned earlier it's a nonissue
 
@TomJNowell Already messing with this on TideSDK
 
@TomJNowell yeah, WP itself is very close to achieveing this. pieces are out there already, just not coherent and robust enough
 
@Rarst could you add a way of tagging API functions on query posts as recommended, then a page to list them all out?
stuff like the core base APIs everything else wraps around, the essentials
i'd guess a non-heirarchical taxonomy would do the job
 
I have plans for better organizaing and relevance logic, but parser change is damn kryptonite for it
 
10:04 AM
@Rarst I'm using PHPReflect for this purpose and it does what you need, consider changing if so..
 
I was thiiiis close to move to WP-Parser then got stuck again and its development has consistency of dice roll
 
@Rarst noo.. seriously stay away from wp-parser, so much better to use PHPReflect or PHP-Parser directly I found
 
but does it do hooks?
 
No you need to extend the parser to capture hooks, essentially you are extended base class to scan strings within start-end lines of functions/methods.
 
thus WP-Parser...
 
10:08 AM
yah but aren't you having problems with wp parser like you said last time?
 
it's minor problem. which I hoped to be quickly resolved by smarter people than me after I open issue about it. two months later...
 
end-line problem right?
 
yeah... so I ended up doing other things meanwhile like Laps and Fragment Cache
 
lol
something good come of it at least
 
not for QP...
 
10:11 AM
progress is still progress no matter where it is...
 
What I was suggesting would be more of a manual task than an automated one
 
plus, from what you told me about FC, it sounds damn useful
 
yeah, but there is nobel kind of progress and ignobel kind of progress :)
@userabuser try for yourself, I pushed current state up bitbucket.org/Rarst/fragment-cache no invalidation yet, it's pain
 
@Rarst Why you no github whore?
 
because I much prefer Mercurial?
 
10:13 AM
Im surprised github havent implemented a mercurial wrapper like they did with svn
 
yeah quite ↑
 
@TomJNowell Kiln did (other way, they started with mercurial), not as easy as for SVN
more precisely Kiln didn't do "wrappers", they created single system which exposes both git and mercurial interfaces
out to drag cat for shots
PS composer makes github/bitbucket distinction irrelevant for install since it uses API for both to generate and provide HTTP download links. composer all the things!
 
how cosmopolitan
Ive someone who wanted a 1 line change to a file in a github repo so I suggested they send a pull request
behold 6 months of tirading against git
 
10:45 AM
@TomJNowell Should have listed pros/cons for this - maybe he did not understand
 
he'd have closed anyway
it's not so much a flaw in his PHP knowledge but a flaw in his workflow
 
What do you mean by workflow exactly?
 
11:01 AM
hehe
Just read all your conversation from last night and today about WP replacement. Maybe we should just start a rough sketch on a Google Doc.
 
@kaiser maybe we should...
 
my thoughts exactly
right what emails do I share this doc with?
 
thing is, can we write it from scratch or do we have to use a framework? I'd prefer only drop in libs where neccessary
 
well what frameworks would we use?
any replacement would benefit enormously from being able to grab libraries to speed up development to save time
I'd think that pulling in a library rather than building on top would be best
one should be glueing things together not depositing code on existing foundations
 
Even though I'm down with the likes of Laravel/Fuel/Silex/Slim and even Symfony to lesser extent, I'd rather use drop in libs and settle on our own framework.
 
11:12 AM
hmmm that's something I think you should research and put together something comparing
or at least design such a framework
afterall we could easily be bogged down in architecture astronaut hell
 
@TomJNowell e.g. Klein router just got re-write to v2, which is now class based. Something like this would be a nice drop in for routing. But as its a drop in, we are not confined.
 
there're advantages to reusing one of the existing frameworks. e.g. a well built symfony WP replacement would torpedo the symfony cms projects and draw in existing devs
 
@TomJNowell Well... it really starts with our choice in router, as to where we go from there imo.
 
we need to define our scope of WordPress support too
 
@TomJNowell True that, but then we have to consider Laravel... imo.
 
11:13 AM
I dont know much of laravel
@userabuser @kaiser doc setup, where do I share it to?
 
I'd more inclined to use Silex than Symf.. but that's me
 
Already at sharing... @TomJNowell What's your mail again?
 
contact@tomjn.com
 
@Rarst @bungeshea @anu Yours?
 
What?
 
11:17 AM
mail address
 
For google or other
 
google docs
 
Oh wait... it will be the same
 
/drive
 
info@bungeshea.com should work
 
11:18 AM
done
nice thing with google docs: you see everyones name inline exactly where he currently has the cursor
already thought about if it would be worth the time to build a google apps collab code editor on top of it
 
@kaiser there are other collab tools like this on github
 
@kaiser you are familiar with etherpad-lite, right...?
 
as @lkraav said.. :)
 
@lkraav nope
 
get on it, then. best thing since sliced google docs.
 
11:21 AM
kool - thanks
 
@lkraav isnt that java?
google docs is essentially staroffice with a wrapper isnt it?
 
Something mentioned on WP Daily … Mozilla Towtruck
It looks pretty slick … just link a js file, and send someone a link
 
what the heck, when did that arrive
i thought i knew ALL of them
ALL
 
Back to WP Replacement
 
11:24 AM
lol
 
Do we need hooks/filters/action API?
 
yes!
@kaiser I have been doing much playing in this area myself... Filters
 
I'm highly against hooks. Don't think that they're ever needed if there're already filters.
 
we'll need an API implementation of that kind anyway if we're to implement WP APIs at all
hooks are a more sophisticated goto
they have their use but there are far better ways of doing things
 
Same goes for every public API function/method that echos something. Everyone can simply echo something. Never understood that concept.
 
11:26 AM
@kaiser I agree, that filters are better than an action.
 
noob friendliness that ends up being counterproductive
 
And it's far less confusing when there's only one thing
 
exactly..
 
oh so the main topic here was "how to we replace WP?"
 
Reduce the amount of things and make the concept clear - imo the only goal that's really needed.
@lkraav jes
 
11:28 AM
if we rebuilt WP what would it look like
speccing' it out essentially
 
@kaiser and actions vs filters is a good example of just that
 
the_filter() and get_the_filters() :D
 
I will laugh everything out of business that relies on public static callback string identifiers.
 
confusion all over
 
what about p2p and taxonomies?
should we roll them in together into a generic node map style implementation?
 
11:31 AM
Question: Templating, I am not fond of global things like get_header(), get_f*cked(), etc... how to approach this?
 
current DB structure is hardly optimal
 
How about … phpdoc for plugin headers? :)
 
@TomJNowell Yeah for that DB structure needs to be re-thought entirely
 
@userabuser at the very least stuff like get_header() could be swapped for get_template_part( 'header' )
@bungeshea composer json
 
Ooh yes!
 
11:33 AM
@TomJNowell It'd be nice to prefix with static call like Template::DoSomething();
 
it'd possibly be an improvement but it feels wrong
I doubt @toscho would approve
 
@toscho maybe you want to jump in on lower level ... right now? :)
 
@TomJNowell explain to me your feelings my son...
 
well it doesnt really fix the problem or define it, it just moves it somewhere else
 
true
 
11:34 AM
instead of a bunch of functions, we get a static class with a bunch of static functions
 
@kaiser no
 
Yes, that's a clear answer.
Question is: Templating - Twig? Mustache? Whatever? ... or PHP.
At least, PHP is a templating language as well.
 
blog stuff, comments, etc separated into modules
 
People will want PHP, some will want twig, I dont think we should force one upon people
 
I like both twig and mustache, but would really prefer to work this out in PHP - I'm sure we can come up with something that addressed the fundemental global issue of templating in WP.
 
11:36 AM
exactly
else we face a "eurgh twig" or "eurgh mustache" instant rejection
 
So just leaving it open if one wants to implement some templating engine on top of WPR.
 
same goes for post content format, markdown vs html, it needs to be a choice else we get a marmite reaction
 
right
 
I say we have an API and a default implementation
 
The template must be handled by an extendable view class.
 
11:37 AM
@TomJNowell You raise a good point, but the question then remains is are we creating something that has mass uptake, therefore requires some kind of standardization or are we going to do something that gives you every option under the sun to template with thus diluting ones ability to pick up from one installation to another..
remember this is a CMF/CMS, not necessarily a low-level framework
 
@userabuser standard APIs and extendability, if someone wants to implement it they have the ability to
 
even if it's mass uptake, some people will try to do unusual things
it's a case of providing good defaults
 
yeah the ability to decouple should be there... but good defaults is where my head is at.. right now
 
@toscho like $view = new View(); and $view->render()->header()? Or what's your basic idea about such class?
 
11:40 AM
well the choice for post content at the moment is either the WordPress way or the markdown way, the other methods havent the traction
 
For post content, there should be both methods available simultaneously, switching between view tabs.
Possibly will require some extending of markdown to handle some things...
 
Outcome should anyway have
A) one click install
B) install and _blog_
 
@kaiser Yes, something like this. Leaving the internals aside, a theme would be just a child class of the default view.
 
@userabuser or side-by-side live preview
 
@toscho Agree to everything, but not the theme word. Unless you extend theme to every sort of view.
Like admin-theme, public-theme, etc.
 
11:42 AM
theme is what the end user knows from Tumblr and WordPress.
 
@bungeshea exactly my thoughts! Kind of like how SE does it, and also in fact like @stephenharris Wp-markdown plugin does it.
 
and how ghost does it
 
@toscho yes. but from the requests I read over the last years, most people don't really need an admin interface. they want forms exactly where the content is. admin seems like a burden for most systems.
 
I use Stephen's WP-markdown plugin for this very purpose and love it, except the markdown itself needs to be extended to handle a more fluid approach to writing html.
 
it needs shell access
so you can just wordpress install <plugin-name>
 
11:44 AM
@kaiser an admin interface is useful, I dont know if it's avoidable, even with a good dose of frontend editing
 
@kaiser I haven’t said anything about admin.
 
@toscho You didn't. I did. :)
 
I say we stick to the theme terminology
 
Just wanted to include this instantly.
 
ya ↑
 
11:45 AM
it's useful, it's known, and people will latch on to it
 
@TomJNowell agreed 100%
theme, plugin... simple.
 
If you need a name four your … thingy, just ask me. :D
 
if we dont and we become popular, someone will likely try to create a themes bundle before reading more docs and face palming
 
@toscho feel yourself asked
 
eurgh names
 
11:46 AM
Chatty
 
TomPress
 
Tomy
 
TommyPress
 
iTom
 
...sorry had to say it.
 
11:47 AM
>_<
 
TomPalm
 
I have to go in a minute
 
It should be called... Thing
 
Thingadingdong
 
Patchwork
 
11:48 AM
"Content"
 
Anything but WordPress-reloaded-fix-extended
 
Kontent
 
like the plugins on wp.org
 
Ambiguous
 
@userabuser Cool, we could ask Kurt Russell for public support.
 
11:48 AM
@bungeshea hahaha
 
Yet Another WP WordPress Reloaded Fix Extended Redux Deluxe Pro Ultimate Edition
 
@toscho I'm sure he will oblige.
 
...delux
 
WP-Ultimate Edition
 
Word
 
11:49 AM
Lexicon
 
hmmmm all spammy SEO-ey or focusing on publishing
keep in mind people build apps and things
 
After three years of writing code, you all are sitting around like this. :)
 
which means an ajax api of sorts, we need to set a paradigm
@toscho shhhh, momentum is gathering, dont stall it
Ill be back soon, I expect v1.0 when I return
 
@TomJNowell No version numbering, we need things like XP and Millennium
 
is there anything optimize the wp_customize add_section, add_setting add_control dance
 
11:53 AM
@TomJNowell Symfony CMF, not CMS and I doubt WP clone would be contender for it
 
something more... QML style declarative thing
 
WordPress got Jazz musicians. I vote for a Ghetto-style-rap version naming.
Version 1.0 - Muthafugger
Version 1.1 - Spliffy King
 
We should start on 3.1, like Windows NT
Just to make people pay attention
 
NT came after 3.1
 
I step away and...
 
11:56 AM
@toscho ↑ after three years of programming...
 
hehe
@userabuser Aren't you half Italian?
 
yeah
 
SerpDrow
then we can have capital_D_dangit
 
WorpDress
 
@bungeshea That should be your first function anyway.
 
12:00 PM
fired on the spot for writing that function
 
Matt fires himself
 
capital_P_damnshit
 
WTF
Word The F***
 
@bungeshea ...and creates rip in space time continuum
What The Foundation?
 
perhaps
 
12:01 PM
...or better yet, Where's The Foundation? (hehe)
 
lol
WordZilla
 
BroZilla?
anything but a name with Word in it :)
 
BruZilla
 
haha
 
Sentences
 
12:06 PM
haha..
 
ParaPress
 
We can't agree on a name for this fucking thing
that's my final suggestion.
 
That's it!
 
untagged
 
Professional and catchy
 
12:08 PM
I don't care if people get offended...
our CMS comes complimentary with a box of tissues for those that want to cry about it
 
Ultimate SEO CMS Platinum Deluxe
 
You nearly made me throw up... sound like a bunch of marketing friends I have.
 
you have friends?
 
On my payroll yes...
 
Well, at least the licensing is set
" … and changing it is allowed as long
as the name is changed … "
 
12:16 PM
What thingy would need as well:
* User Management
* Capability Management
* Role Management
and everything on a solid, easy to use base.
with an UI
 
yes
 
old hat
 
@toscho see last update, it's two tables per thing
 
I know. Just a reminder not to make The Thing overly complex.
 
12:27 PM
Well, I'm going to bed now
see ya
 
Has anyone noticed how damn early those Australians go to bed?
 
And we need relationships
@bungeshea good night
Media Management - best combined with Assetic to use all those fancy image compression stuff as well
And Assetic can really do it all
@All off topic : Where the heck does WordPress save the display name for a role? The role object (WP_Role) doesn't hold it.
withdrawing question. it's an registration arg...
 
12:45 PM
@toscho define("EARLY", "?"); ?
 
@userabuser You, Sir, are the reason for our tag line.
 
Do I get a badge?
 
nope
Badges are for things you do, not for things you don’t do. :)
 
But you just said I was the "reason", therefore technically I "did" it...
 
1:02 PM
SE network updates: Retag option from questions is removed. Editing tags only will result in the same behavior as retag.
posted on May 08, 2013

Retag option from questions is removed. Editing tags only will result in the same behavior as retag.

SE network updates: Edits reverted during the grace period will now remain in the post history instead of vanishing.
posted on May 17, 2013

Edits reverted during the grace period will now remain in the post history instead of vanishing.

 
1:35 PM
A basic notifications api?
rather than random crud snippets of html bundled in and js'ed to the top of the page
 
@TomJNowell yes!
 
I should note that it should be basic, and not be dictated by UI
notification Y that has metadate
 
if the API is intended for the backend then some kind of UI would be required no? If this same API can extend itself to the front end then either no UI or a very minimal one could be present?
 
the form of the UI shouldnt dictate the API, sure one is probably necessary but maybe it's notifications via email? IM? FB style dropdown? Dashboard list? Inbox style UI? We cant know
we should set out a basic workflow from browser makes request to when page generation finishes, so we can flesh out architecture
it also forces us to think about caching
 
2:40 PM
Anyone know if any improvements to the media uploader are coming in the WP 3.6? Right now uploading a far number of HQ images (< 100) is a huge pain as the media uploader hangs.
 
@its_me none I think
 
Oh :/
 
@its_me I get some sluggish behavior on far fewer images sometimes...
 
@userabuser The reason is simple. The stupid uploader shows HQ versions of images resized as thumbnails, instead of using the "thumb" size.
 
@its_me this tends to happen regardless of location, be it OS X finder, windows explorer, or the media uploader
 
2:50 PM
@TomJNowell Not sure about what you are saying...
 
@its_me Well if that's the case then that's pathetic.
 
Yep. I was very surprised!
 
3:03 PM
@TomJNowell show this to certain... someone :) Submitting Your First Pull Request to a WordPress Plugin on Github
 
haha
 
3:21 PM
on what cases a plugin should use a separate table?
 
rarely if ever
 
@Sisir when your data model doesn’t fit into the WP schema
 
@toscho sounds like alien language. :P
okey.. If i were to create a live chat support plugin. Should I use a separate table to save chat messages? or just use cpt?
 
separate
There are probably too many write queries for a regular post table
 
that's what i thought
 
3:29 PM
you don’t need post meta fields, it doesn’t have to be part of the regular search, and the indexes should be kept separate too
 
poked hosting support and will probably move my VPS to SSD node (same cost, less storage space)
curious if there will be noticeable performance impact for visitors
 
any best practice tips for creating separate table? any good article link?
 
@Sisir scbFramework can abstract it for you
 
I've downloaded it other day, thanks
 
@Sisir Stephen Harris has written some articles about custom databases.
 
4:09 PM
@toscho its a very good article. Thanks!
 
 
1 hour later…
5:34 PM
Shog9 on May 20, 2013

Stack Overflow has always had a strong focus on individual merit. Although collaboration is encouraged to some extent by the editing features, attribution on posts and the design of user profiles all tend to emphasize rugged individuality, that lone wolf toiling away at a keyboard.

But most of us don’t actually work that way. We’re social creatures by nature, and the most challenging part of finding a good job can be finding the pack you want to run with. In spite of the dearth of features aimed at networking, folks have been using Stack Overflow to find and research potential colle …

 
Wasn’t there a developers tab on the wp.org plugin pages?
 
@toscho still is?
 
I see it?..
 
5:46 PM
it's after reviews, maybe stylesheet is off for you
 
Oh, found it. In a way …
When I make my font size too small to be readable, the tab comes back. Now what?
 
ask Otto to fix or UserCSS
 
Is multiple user roles already implemented by core behind the scenes or does user has to have a single role?
 
6:02 PM
zooming out brings it back
 
How stupid is that: $GLOBALS['wp_roles'], which is an instance of WP_Roles holds a roles name, which is the translated display name. But a single WP_Role object, which holds everything that's inside $GLOBALS['wp_roles'], doesn't have the name attached. So to retrieve or update the display name, you have to update WP_Roles as well... why? just: why?
Retrieve key/value (name/display name) pair: global $wp_roles; $wp_roles->get_names();... facepalm
And no pointer to builtin roles.
 
6:29 PM
There should be something like register_role_to_post_type() to automagically map custom post type capabilities to roles...
 
oo it called me a 9to5 PHP expert
 
what’s that?
 
> Rarst is a high caliber PHP expert who would rather be commenting on issues instead of pushing code. Rarst is an early-week worker who seems to work best in the morning.
timezones screwed up :)
and it died...
 
 
1 hour later…
8:22 PM
Reading that I'm one of the top 21% PHP guys on GitHub makes me sad.
 
says a lot about PHP :P
 
didn't even give me a percentile, probably to spare my feelings
 
It called me a JavaScripter, probably because some of my repos display in the wrong language
 
muhaha
 
Most watched: Symfony
_s is under the most watched on page 1... wow
Roots theme under most watched. More than WordPress and _s ... WOW
 
9:06 PM
Reason #1 why to not use the predefined .gitignore files: ~250 open pull requests and the most recent changes for nearly every file is 2 years old. More here.
 
I don't get that... when I want to ignore something - I ignore something.
 
Well, the thing they ignore most is .... pull requests
 
I tend to .gitignore my IDE's workspace/project files.
 
I want woo plushie. to do bad things to it.
 
@Rarst how about a Woo Voodoo plushie?
Voodoo Woo. Woodoo
 
 
1 hour later…
10:32 PM
@Rarst I've a woo ninja plush at work, and a little one with movable arms and wooden hands
 

« first day (947 days earlier)      last day (4005 days later) »